Stats

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

Exporting ADE-L Design Variables into a CSV file

Volker T

Dear all,

there is a similar post from about 2 years ago, addressing the same problem (but for AMS Designer), but not offering a solution to immediately work (in my case ADE-L and Spectre).

I would like to export all design variables of an ADE-L session (later maybe also ADE Explorer) for reasons of documentation. For Outputs, there is an Export (and Import) command, but not for Variables.

1) The ideal solution would be two menu commands, Variables/Export... and Variables/Import..., that will save or load the variables into/from a CSV file. Then I could use such file for both documentation and (selective) import into a different session.

2) As currently, there is no such command, some SKILL code would help out (to be written into a file and started from CIW by loading the file). Andrew Becket mentions a "asiGetDesignVarList(asiGetCurrentSession())" SKILL command that should help here, yet it only results in an error (when entered in CIW, but maybe that is the wrong place): *Error* asiGetDesignVarList: no applicable method for the class - list()

So, if anyone has any solution for this, it would be great to share it in this forum...

Thank you very much.

  • Volker T

    Strange, but now asiGetDesignVarList(asiGetCurrentSession( )) works...

    Now I only need to write the code to parse the list and export it to a CSV file.

  • Andrew Beckett
    in reply to Volker T

    ADE Explorer already has this (right mouse button over the Design Variables in the Setup Assistant), as does ADE Assembler (right mouse button over the Global Variables in the Data View Assistant). There are entries to Export and Import to/from CSV.

    For ADE L you'd need to write your own. The likely reason it didn't work before was probably that the current window wasn't correct, and asiGetCurrentSession() wasn't returning the current session because it didn't know which session you were talking about. 

    ADE L is in "Sunset mode" so you really should migrate to ADE Explorer if you can.

    Regards,

    Andrew.

  • Volker T
    in reply to Andrew Beckett

    Yes, you're right, I must have tried it with no ADE-L session open, so asiGetDesignVarList(asiGetCurrentSession( )) had to fail that time, but did not when I tried later with an open session.

    Now I have a solution which does import and export design variables, nicely integrated into ADE as two new menu items, which was very easy to implement, thanks to your code snippets in this and the Custom IC SKILL forum.

    And thanks for your hint to better migrate to ADE Explorer/Assembler. We actually use it in new projects, but my question came up when I had to re-simulate a rather old design. But of course, converting our old simulation states to ADE Explorer and then using the already existing Export/Import functionality might have been the faster and easier solution to my question...

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.