• 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
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Functionality has not been removed here. ocnxlRun() is new in IC61, to correspond to ADE XL functionality. You can still use a non-blocking run() function in an OCEAN simulation, so that functionality has not been removed. I agree that it would be very useful to be able to do a non-blocking ocnxlRun() though, which is why I filed the enhancement before.

    Wrapping spectre and getting it to appear to exit might work, but it would rather destroy much of the benefit of ADE XL and OCEAN XL scripts, which allows you to set up measurements and specification limits - these would all fail. So I don't think that's a sensible solution.

    What are you actually trying to achieve here? Understanding that might allow me (or someone else) to suggest alternative methodologies.

    Best Regards,

    Andrew.

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

    Functionality has not been removed here. ocnxlRun() is new in IC61, to correspond to ADE XL functionality. You can still use a non-blocking run() function in an OCEAN simulation, so that functionality has not been removed. I agree that it would be very useful to be able to do a non-blocking ocnxlRun() though, which is why I filed the enhancement before.

    Wrapping spectre and getting it to appear to exit might work, but it would rather destroy much of the benefit of ADE XL and OCEAN XL scripts, which allows you to set up measurements and specification limits - these would all fail. So I don't think that's a sensible solution.

    What are you actually trying to achieve here? Understanding that might allow me (or someone else) to suggest alternative methodologies.

    Best 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