• 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. Ocean XL: running the same script twice makes the CIW s...

Stats

  • Replies 4
  • Subscribers 130
  • Views 169
  • Members are here 0

Ocean XL: running the same script twice makes the CIW stuck

MC20250412421
MC20250412421 1 day ago

Hi everyone !

So I have a ADE assembler cellview with a single test: a simple single run transient simulation (nominal corner only) of a circuit.

When using the ADE assembler GUI as I would do normally, the whole simulation takes exactly 30 seconds.
Without changing anything I then go to "File > Save Script" to export the ocean XL script, close the assembler view and then in the CIW I type:

load("ocnScript.ocn")

The first time I run the command it takes exactly 40 seconds. The second time I run the command in the same CIW, the "Run setup summary" appears quickly but then it gets stuck indefinitely on "Entering Optimize Single Point Run netlisting..." and I need to force kill virtuoso (pkill -9 virtuoso) for it to even close. Using the assembler GUI I can launch the simulation as many times as I want.
Any ideas of how I can fix that ?

Thanks in advance !

Mike

  • Cancel
  • Sign in to reply
  • Andrew Beckett
    Andrew Beckett 1 day ago

    Mike,

    I don't see this, but maybe there's a dependency on the version you're using or exactly how the simulation is set up. I would recommend contacting customer support (use the Case menu to submit a support case after logging in) to investigate further.

    An alternative (and simpler approach) is to use the mae functions instead to avoid having to replicate the whole setup in a script. You can then use:

    maeOpenSetup(...)
    maeRunSimulation(...)
    maeCloseSession()

    If you need to vary things from the ADE setup, you can do that too. For me, this is preferable over having a fixed snapshot of the setup in an OCEAN script.

    Regards,

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • MC20250412421
    MC20250412421 1 day ago in reply to Andrew Beckett

    Thank you very much for the quick response Andrew, I did not think about mae functions but they seem quite simple, the axl functions too, I will probably use them a lot.

    I have another more general question for this since you have experience with all of this.
    If you must run simulations that calculate complex metrics and has conditional execution of runs (running new simulations with new design variables based on the calculated metrics), what group of functions would you generally use ? mae, axl, ocean, ocean xl... ? 

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 18 hours ago in reply to MC20250412421

    Much of this can be done with Run Plans in ADE Assembler anyway, and that also allows for the use of "mae" functions for more complex scripts to compute dependencies between runs. However, if you need more than that provided by Run Plans then I'd use mae functions to do it (occasionally you might have to revert to axl or asi functions if there are gaps, but the mae API covers most things and is simpler to use)

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • MC20250412421
    MC20250412421 15 hours ago in reply to Andrew Beckett

    You're right, run plans are a very nice feature to have which I did not know existed. But I still do like the more scalable and predictable nature of scripts compared to gui features. I think I'll settle like you said with a blend of both depending on what the tool allows me to do.

    Thanks a lot for the help Andrew !

    Mike

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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