• 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. How to setup ADE Explorer to save last N runs automatic...

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 4108
  • 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

How to setup ADE Explorer to save last N runs automatically

nrk1
nrk1 over 1 year ago

How to setup ADE Explorer to save last N runs automatically? With ADE-L the following line in .cdsinit would save the last 5 runs. 

envSetVal("asimenv.misc" "numberOfSavedRuns" 'int 5)

Thanks

Nagendra

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago

    Nagendra,

    There's not a direct equivalence. The closest is:

    envSetVal("maestro.explorer" "onHistoryNameCollision" 'cyclic   "IncrementAsNew")

    which increments the Explorer history number after each run, so it's equivalent to saving after each run. It doesn't limit the number of saved "histories" to N runs - you have to manage that yourself (this was not a particularly widely used ADE L feature). ADE Assembler has the ability to save full histories after each run and limit those to N runs (on the Options→Save form).

    Andrew

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

    Thanks! Both work. I find this feature useful in the exploratory phase when making changes to (small) circuits and simulating them. Too lazy to explicitly save every result. 

    The assembler option is easier. Is there a reason to not use assembler for everything?

    Nagendra

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 1 year ago in reply to nrk1
    nrk1 said:
    The assembler option is easier. Is there a reason to not use assembler for everything?

    Not really. The only point is maybe that there are more mouse clicks needed in Assembler because of the fact that you can have multiple tests, so you then need to indicate which test you are operating on.

    Andrew

    • 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