• 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 make ADE Assembler save ALL global variables to file...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14155
  • 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 make ADE Assembler save ALL global variables to file during a run?

Martinum
Martinum over 5 years ago

Hi,

I'm doing batch processing of the cadence results database outside cadence (in MATLAB).

I've noticed that all global variables are not saved to the variables_file in the psf directory. This is for example the case for config sweep variables. 

Is there some way to force ADE to save all variables? Or is it possible to read the configuration for a simulation point from some other file?

All the best,

Martin

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 5 years ago

    Hi Martin,

    If you used the ADE MATLAB integration product, then there is a set of functions you can use in MATLAB which allow you to read all the scalar results plus parameter conditions (i.e. the conditions for sweeps etc) from the database (an SQL database) that ADE uses directly into MATLAB. Perhaps you could look at that? Here are a couple of videos (one by me, and one by me with a colleague from the MathWorks):

    • Making the most of using MathWorks MATLAB and Virtuoso ADE Product Suite together
    • Using the Enhanced Virtuoso ADE Product Suite and MATLAB Integration: A Practical Guide

    There is also the database that spectre saves with its global parameters, but that too wouldn't include the config sweep variables, so that won't help you...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Martinum
    Martinum over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your super fast responce!

    Unfortunately it seems we do not have the necessary licenses to try this tight integration at this point.

    Just curious, where is the config info saved for ADE? It shows the config as a parameter just like a DC variable being swept... but doesnt save them together...

    All the best,

    Martin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Martinum
    Martinum over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your super fast responce!

    Unfortunately it seems we do not have the necessary licenses to try this tight integration at this point.

    Just curious, where is the config info saved for ADE? It shows the config as a parameter just like a DC variable being swept... but doesnt save them together...

    All the best,

    Martin

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to Martinum

    Martin,

    The setup is in the XML file for the view (maestro.sdb or active.state depending on which part it is), but the real record of what was simulated (i.e. what you want) here goes into the "Interactive.N.rdb" file. The PSF database for variables is there for calculations (and actually the designParamVals database is more important for this; variables is for legacy ADE L support more than anything). However, since you're not going to do calculations on the sweep view name, and spectre has no need to know this, it doesn't get stored into the PSF database. Most of the higher level sweep information is going to be in the "rdb" which is the SQL database used to keep track of results and so 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