• 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. Using ocnxlRun in a loop

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 143
  • Views 16110
  • 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

Using ocnxlRun in a loop

webbyguy
webbyguy over 14 years ago

I am trying to run multiple ADE XL runs from an ocean script, but each time I run simulations using the ocnxlRun command the script waits until that job is finished.  Is there any way to setup the ocnxljob such that it doesn't wait on previous runs to finish before starting the next jobs?

 

Thanks

  • Cancel
Parents
  • webbyguy
    webbyguy over 14 years ago
    Here are two examples of what I'm trying to do:

    Example 1:

    I have 2 designs that I am trying to simulate.  On design1 I want to simulate resistor corners of 5 and 10 ohms across 30 iterations of monte carlo (no temperature).  On design2 I want to simulate capacitor corners of 1uF and 10uF across 100 iterations of monte carlo with temperature steps of -40C, 27C, and 125C.

    In my script I set up design1 simulate and call the ocnxlrun command.  Here the script waits until the simulations for design 1 complete before executing the rest of the script which sets up design 2 and calls ocnxlrun again.  I would like to have the option for the script not to wait on design1’s simulations to finish before submitting the sims for design2.

    Example 2:

    Sometimes I want to change a variable on each monte carlo iteration.  In cadence 5 I could simply run each monte carlo iteration by itself in a for loop.  So for iteration #1 I would set the variable Vref to 5V, set the monte carlo iteration number to 1, and the number of iterations to run to 1.  Then I would call monteRun, the job would be submitted, and the script would continue on to iteration #2 setup.  For iteration #2 I would set the variable Vref to 4.5V, set the monte carlo iteration number to 2, and the number of iterations to run to 1.  The call the monteRun, the job would be submitted, and the script would continue on to iteration #3 setup…etc…

    The reason I was saying functionality has been removed is:  I don't think there is anyway to submit multiple monte carlo jobs from a script in cadence 6, but it was possible in cadence 5.  I may have missed something though in the documentation.  Is there some way to still use the non blocking run when submitting monte carlo jobs?

     Thanks,

     John
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • webbyguy
    webbyguy over 14 years ago
    Here are two examples of what I'm trying to do:

    Example 1:

    I have 2 designs that I am trying to simulate.  On design1 I want to simulate resistor corners of 5 and 10 ohms across 30 iterations of monte carlo (no temperature).  On design2 I want to simulate capacitor corners of 1uF and 10uF across 100 iterations of monte carlo with temperature steps of -40C, 27C, and 125C.

    In my script I set up design1 simulate and call the ocnxlrun command.  Here the script waits until the simulations for design 1 complete before executing the rest of the script which sets up design 2 and calls ocnxlrun again.  I would like to have the option for the script not to wait on design1’s simulations to finish before submitting the sims for design2.

    Example 2:

    Sometimes I want to change a variable on each monte carlo iteration.  In cadence 5 I could simply run each monte carlo iteration by itself in a for loop.  So for iteration #1 I would set the variable Vref to 5V, set the monte carlo iteration number to 1, and the number of iterations to run to 1.  Then I would call monteRun, the job would be submitted, and the script would continue on to iteration #2 setup.  For iteration #2 I would set the variable Vref to 4.5V, set the monte carlo iteration number to 2, and the number of iterations to run to 1.  The call the monteRun, the job would be submitted, and the script would continue on to iteration #3 setup…etc…

    The reason I was saying functionality has been removed is:  I don't think there is anyway to submit multiple monte carlo jobs from a script in cadence 6, but it was possible in cadence 5.  I may have missed something though in the documentation.  Is there some way to still use the non blocking run when submitting monte carlo jobs?

     Thanks,

     John
    • 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