• 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 script not converging in transient simulation

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 125
  • Views 5199
  • 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 script not converging in transient simulation

milind0z
milind0z over 1 year ago

I have a ADE-L setup which runs just fine but if I save it as a ocean script file and run it from the ICFB window (on the same session where I ran the ADE-L simulation) using the load command it fails to converge. Should this be reported to Cadence support or is there something I can check on my side to see why there is a difference in behavior.

I am running Cadence Virtuoso IC6.1.8-64b.500.30

Thanks,

Milind

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Milind,

    I'd check the resulting input.scs files and compare them - there must be a difference if the simulator is behaving differently (you should be able to diff the two files).

    One likely explanation is that saving an OCEAN script does not (by default) save settings which are default in your Virtuoso environment, and if those defaults (set by cdsenv variables) are different from the default defaults (!), this could lead to a difference. You can save a more complete OCEAN scripts (which potentially as a lot of redundant statements in it) by using:

    envSetVal("asimenv.misc" "saveDefaultsToOCEAN" 'boolean  t)

    (you might need to set this before opening ADE L, I can't remember, sorry!) - and then save the OCEAN script.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • milind0z
    milind0z over 1 year ago in reply to Andrew Beckett

    Thank you for your response. Yes I did that based on my other searches through this forum. The files are exactly the same till the first time point of the transient step. The only difference before that are things like time, license checkout time, process ID, etc.

    So now I tried doing the envSetVal command that you suggested. I restarted the Cadence Session and then ran this before opening the ADE session. Ran the simulation in ADE. Saved the Ocean script and tried the ocean script. The script failed convergence, although I do see a lot of additional parameters in the ocean script.

    Now I tried the command once more and resaved the ocean script. This time it worked! I will experiment a bit more and follow up here.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to milind0z

    That sounds as if you’ve compared the output log (spectre.out) rather than the input netlist (input.scs). If the results are different the input really must be different because it is calling the same executable in both cases (assuming too that the command-line options for the simulator are the same).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • milind0z
    milind0z over 1 year ago in reply to milind0z

    I think I spoke too soon. Tried it again. Doesn't converge. Also when it did somehow the spectre.out had a difference. The one from ADE-L was clean at the starting of the transient steps, for the one in ocean it had a Notice saying solution failed to converge and disaster recovery algorithm is enabled, after which it was able to continue. Now it is not able to get there as well.

    However I see that it converges in the script when I have APS++ enabled. But still it is not the same output log as ADE-L output log.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • milind0z
    milind0z over 1 year ago in reply to Andrew Beckett

    I checked the input.scs and it is the same same in both cases. The only difference is the order in which of the design variables are listed on the top (also the ocean script version the variables are written in scientific format while in ADEL it is using the micro-u or M symbols). The other difference is the order in which the save elements are written at the end. Other than that the input.scs that I get after running the simulation are the same.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to milind0z

    I can't really see how Spectre can do different things given the same netlist (if the command-line options are the same). I suggest you contact customer support so that an application engineer can take a look.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • milind0z
    milind0z over 1 year ago in reply to Andrew Beckett

    Ok, I have initiated that through the CAD group here. Thanks.

    • 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