• 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. ADE-L: How to specify "options statements" for Spectre?

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 126
  • Views 9462
  • 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

ADE-L: How to specify "options statements" for Spectre?

dontpanic
dontpanic over 8 years ago

Hello! Trying to debug DC convergence issues I came across the "Spectre and APS Non-Convergence Debug Guide", where most solutions involve using "options statements". How and where in ADE-L do I specify these options statements for the simulator to catch them? I tried many options without success:

-Make an .scs file and include it with the simulation libraries
-Make an .scs file and include it in the "paramSet" directive
-Use the "user command-line options" field in the Setup->Environment menu
-Use the "Additional arguments" field in the Simulation->Options->Analog menu
-Use the "additionalParams" field in the tran analysis "Misc" tab

(...side question: is there any document where the differences between all these places for specifying options are explained?!)

Thanks in advance for any help!
Cheers,
Jorge.


P.S. I'm referring to this document: AppNote_nonConvergence_v2.pdf

  • Cancel
  • Quek
    Quek over 8 years ago

    Hi Jorge

    Adding the options cmd in "filename.scs" and including the file as one of the model files should work. Would you please provide your options cmd and also check spectre log file to see if there are any warnings about the added option?


    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    The document is referring to arguments to the "options" statement in spectre (this is "spectre -h options") for the most part. So that means that you can use options 1 or 4 in your list above. Let me explain the differences:

    1. Make an .scs file and include it with the simulation libraries
      This is a way of including something of arbitrary spectre syntax - you would need to ensure that the name of your options statement (the first word on the line) is different from the ones used by ADE, but apart from that you are just setting the cumulative set of options from the ADE Simulation->Options->Analog form (and also some from the Outputs->Save All form)
    2. Make an .scs file and include it in the "paramSet" directive
      I'm not sure what you're referring to here, but this doesn't sound as if it would be correct
    3. Use the "user command-line options" field in the Setup->Environment menu
      This is for command-line switches (i.e. arguments to the spectre executable) as described in "spectre -h". This is not what you want. From the document, this is for things  like +postlayout or +parasitics=100000 etc.
    4. Use the "Additional arguments" field in the Simulation->Options->Analog menu
      This would work too, although you wouldn't then specify the "options_debug options" part. Just specify things like "pivotdc=yes pivrel=0.1" i.e. the param=val parts. Note that some of these options are probably on the forms too for the Simulation->Options->Analog
    5. Use the "additionalParams" field in the tran analysis "Misc" tab 
      This is for transient-specific param=value options, such as cmin=10a.


    Hope that helps,

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dontpanic
    dontpanic over 8 years ago

    Thanks so much for your replies, Quek and Andrew; after the clarifications I was able to make it work! I'm using method 1, as I find it more convenient.

    • 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