• 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. Maestro - customizing default ouptut save options

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 126
  • Views 3601
  • 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

Maestro - customizing default ouptut save options

firebolt
firebolt over 2 years ago

In general, I save only selected voltages & currents, and no other information to save disk space & time. For any new test, I have to customize settings again (from allpub). Is there a way to make them default?

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 2 years ago

    Dear firebolt,

    I think this might accomplish what you want firebolt. There is a troubleshooting article at URL:

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1O0V000007Mmz9UAC&pageName=ArticleContent&oMenu=People%20who%20viewed%20this%20also%20viewed

    that contains a set of SKILL statements at the end of it to include in your .csdinit file. The code contains a set of defaults you can either create and save or include the .cdsinit statements. The SKILL command of interest is

    asiSetKeepOptionVal()

    and is documented in the SKILL reference manual (part 1) at URL:

    https://support.cadence.com/apex/techpubDocViewerPage?xmlName=skartistref.xml&title=Virtuoso%20ADE%20SKILL%20Reference%20-%20Part%20I%20--%20Keep%20Option%20Functions%20-%20asiSetKeepOptionVal&hash=pgfId-1032956&c_version=ICADVM20.1&path=skartistref/skartistrefICADVM20.1/chap12.html#pgfId-1032956

    I hope this is what you were hoping to find!

    Shawn

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to ShawnLogan

    Shawn,

    That's not really the best way to set defaults for new views though - it's much simpler to do with cdsenv settings:

    spectre.outputs save    string  "selected"
    spectre.outputs primitivesInfo boolean t
    spectre.outputs modelParamInfo boolean t
    spectre.outputs subcktsInfo boolean t
    spectre.outputs elementInfo boolean t
    spectre.outputs assertsInfo boolean nil
    spectre.outputs designParamValInfo boolean t
    spectre.outputs outputParamInfo boolean t
    spectre.outputs allcapInfo boolean nil
    spectre.outputs extremesInfo boolean nil

    You can set these to nil or t (for the "Info" analyses). This is the .cdsenv syntax, and for an entry in the .cdsinit it would be:

    envSetVal("spectre.outputs" "elementInfo" 'boolean nil)

    for example. Or:

    envSetVal("spectre.outputs" "save" 'string  "selected")

    Andrew

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to ShawnLogan

    Shawn,

    That's not really the best way to set defaults for new views though - it's much simpler to do with cdsenv settings:

    spectre.outputs save    string  "selected"
    spectre.outputs primitivesInfo boolean t
    spectre.outputs modelParamInfo boolean t
    spectre.outputs subcktsInfo boolean t
    spectre.outputs elementInfo boolean t
    spectre.outputs assertsInfo boolean nil
    spectre.outputs designParamValInfo boolean t
    spectre.outputs outputParamInfo boolean t
    spectre.outputs allcapInfo boolean nil
    spectre.outputs extremesInfo boolean nil

    You can set these to nil or t (for the "Info" analyses). This is the .cdsenv syntax, and for an entry in the .cdsinit it would be:

    envSetVal("spectre.outputs" "elementInfo" 'boolean nil)

    for example. Or:

    envSetVal("spectre.outputs" "save" 'string  "selected")

    Andrew

    • Cancel
    • Vote Up +2 Vote Down
    • Cancel
Children
  • firebolt
    firebolt over 2 years ago in reply to Andrew Beckett

    Thanks Andrew & Shawn. Works for spectre simulator. Does it support for third-party simulator? I tried, its not working.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to firebolt

    I would expect there would be similar cdsenv settings for a third-party simulator, but of course they will be specific to that simulator. You should ask the vendor/provider of that integration for details as to how to set the defaults in their integration (in general this should be controlled by cdsenv settings, but I can't tell you what they are called in an unnamed (or even a named) third-party integration).

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • firebolt
    firebolt over 2 years ago in reply to Andrew Beckett

    I will check with them. 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