• 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 SKILL
  3. ocean XL monte carlo abort on internal error

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 143
  • Views 13152
  • 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

ocean XL monte carlo abort on internal error

FredWang
FredWang over 12 years ago

Dear All,  

In ocean XL monte carlo simulation, it seems the job controller will abort all unfinished jobs once it detects that one of the simulation has an fatal/internal error. Is there a way to resume the computation even if there is such an error?

Thanks,

Fred 

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Fred,

    I'm guessing that this is because you have a relatively small number of jobs set up in your job policy. For example, if you have 1 job set up, and 100 points in your monte carlo, it will tell spectre to do a 100 point monte carlo analysis. If you had 2 jobs and 100 points, then you'd get two jobs, each with 50 points (this is assuming a single test and a single corner). Anyway, since spectre is doing the monte carlo analysis, if there's a fatal error, the simulator will exit - and the remaining monte carlo points in that invocation of the simulator will be aborted.

    You could run more jobs - but then they'll run in parallel.

    However, the key thing is probably getting the fatal error addressed - this shouldn't happen. Either it's due to something in the setup, or it's a bug in the simulator. I'd guess that it's likely to fail on subsequent points too, depending on the reason for the fatal error.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • FredWang
    FredWang over 11 years ago

    Hi Andrew,

    I indeed had set 'maxjobs' less than the number of corners (or number of test points) in a single mc run. Now I changed it to a higher value, hoping that once a simulation encounters an error, it won't affect the other simulations which are still running.

    The fatal error is somewhat expected in my simulation, though, I can live with that.

    Thanks for your help.

    Fred

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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