• 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. ADEXL Montecarlo, only netlisting

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 15909
  • 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

ADEXL Montecarlo, only netlisting

demsar
demsar over 13 years ago

Hi!

For the reason of some preprocessing I need to separate the netlisting and the montacerlo simulation itself. Does anybody know, which skill/ocean procedure is used to trigger the netlisting (including the netlist variations in case of using multiple jobs).

Best regards!

Blaz

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

    Hi Pierre,

    The reason why " /MonteCarlo.0/11/Test:sim_wr:1/   and /MonteCarlo.0/12/Test:sim_wr:1/" have different waveforms, is because spectre generated both of them from a single run of spectre. The netlist is shown per monte carlo point, but it ran several of them together (because numruns was greater than 1). So if max jobs=20, nb runs=100, spectre will do a simulation with firstrun=1 numruns=5, then firstrun=6, numruns=5 etc. If you look at the netlists for runs 1 through 5, they all have the same netlist - but the results were generated by the same invocation of spectre - it ran with the sweep inside the simulator - it wrote out the results for point 1,2,3,4,5 from the single netlist it was given.

    If it is failing (to converge) then that is not necessarily a circuit issue, but more a simulation issue (it might be due to the models, or a need to give a better starting point for the simulator). Anyway, if it converges in the first run (in sets of 5, rather than individual runs), I would be fairly confident in the results.

    If however you get significantly different results, and it's a spec failure you're getting, it's possible that your circuit has more than one stable operating point - circuit simulators will DC converge to one solution - but which one you'll get if there is more than one depends on the starting conditions.

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Hi Pierre,

    The reason why " /MonteCarlo.0/11/Test:sim_wr:1/   and /MonteCarlo.0/12/Test:sim_wr:1/" have different waveforms, is because spectre generated both of them from a single run of spectre. The netlist is shown per monte carlo point, but it ran several of them together (because numruns was greater than 1). So if max jobs=20, nb runs=100, spectre will do a simulation with firstrun=1 numruns=5, then firstrun=6, numruns=5 etc. If you look at the netlists for runs 1 through 5, they all have the same netlist - but the results were generated by the same invocation of spectre - it ran with the sweep inside the simulator - it wrote out the results for point 1,2,3,4,5 from the single netlist it was given.

    If it is failing (to converge) then that is not necessarily a circuit issue, but more a simulation issue (it might be due to the models, or a need to give a better starting point for the simulator). Anyway, if it converges in the first run (in sets of 5, rather than individual runs), I would be fairly confident in the results.

    If however you get significantly different results, and it's a spec failure you're getting, it's possible that your circuit has more than one stable operating point - circuit simulators will DC converge to one solution - but which one you'll get if there is more than one depends on the starting conditions.

    Kind Regards,

    Andrew.

    • 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