• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. APS:Monte Carlo:Output waveforms in a single file

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 3929
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

APS:Monte Carlo:Output waveforms in a single file

Ionutz
Ionutz over 11 years ago

  Hi,

 I am running Monte Carlo sims with aps from command line  using spice netlist.

For each of the monte carlo runs, the tool dumps a separate waveform file. Is there any option to have all the monte carlo waveforms built into a single output waveform?

 

 Thank U,

Ionut

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Hi Ionut,

    I just tried using this, and it already saves the family data. I used the statements you provided above, and I get this:

    UNIX> ls monteres.raw
    logFile      sweep1-001_timeSweep.tran  sweep1-003_timeSweep.tran  sweep1-005_timeSweep.tran
    logFile.tmp  sweep1-002_timeSweep.tran  sweep1-004_timeSweep.tran  sweep1_timeSweep.montecarlo

    The last file is the root of the tree to give a family of the individual iteration results. If I open this result directory in ViVA, I see the picture in the attachment below. As you can see, I see "tran" as the results, and the set of waveforms gets opened together.

    What tool are you using to look at the waveforms? 

    The alternative would be to use spectre syntax for the monte carlo, but that seems unnecessary here since it works fine:

    simulator lang=spectre
    parameters  xnlx_tran_stop=100n
    monte montecarlo numruns=5 savefamilyplots=yes {
      tran tran stop=xnlx_tran_stop
    }

    there's no real need to set step= on the transient (you could if you really wanted to).

    Kind Regards,

    Andrew.

    • vivaMonteResults.png
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Hi Ionut,

    I just tried using this, and it already saves the family data. I used the statements you provided above, and I get this:

    UNIX> ls monteres.raw
    logFile      sweep1-001_timeSweep.tran  sweep1-003_timeSweep.tran  sweep1-005_timeSweep.tran
    logFile.tmp  sweep1-002_timeSweep.tran  sweep1-004_timeSweep.tran  sweep1_timeSweep.montecarlo

    The last file is the root of the tree to give a family of the individual iteration results. If I open this result directory in ViVA, I see the picture in the attachment below. As you can see, I see "tran" as the results, and the set of waveforms gets opened together.

    What tool are you using to look at the waveforms? 

    The alternative would be to use spectre syntax for the monte carlo, but that seems unnecessary here since it works fine:

    simulator lang=spectre
    parameters  xnlx_tran_stop=100n
    monte montecarlo numruns=5 savefamilyplots=yes {
      tran tran stop=xnlx_tran_stop
    }

    there's no real need to set step= on the transient (you could if you really wanted to).

    Kind Regards,

    Andrew.

    • vivaMonteResults.png
    • View
    • Hide
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information