• 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 SKILL
  3. Starting analog environment and schematic editor

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 148
  • Views 14364
  • 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

Starting analog environment and schematic editor

archive
archive over 17 years ago

I am writing few SKILL/OCEAN scripts that perform the analysis of simple circuits.
From those scripts, I would like to be able to start the Analog Design Environment interface and the Schematic Editor, so that extra data extraction could be done with the UI.

How can I do that such that the design, the design variables, the result directory, etc... is all set up, without inserting it manually in the UI forms?

How can I annotate the schematic from the script (e.g. Results->Annotate->DC operating options)?

Thanks in advance for your answer to this questions.
Marco Ballini


Originally posted in cdnusers.org by mballini
  • Cancel
  • archive
    archive over 17 years ago

    Well, that's not the normal use model. In practice you'd run the OCEAN scripts to setup the analyses and run the simulations - and potentially report on the results. If you've kept the normal simulation directory hierarchy, you could then open the schematic, start ADE, and then do Results->Select to pick the set of results you want to work with, and backannotate.

    Potentially you could automate that, I suppose. I'm not on the Cadence network at the moment, so I can't check - but it would be "sev" functions you'd need to start ADE. geOpen() to open the schematic.

    With OCEAN XL in IC612 and later, this is really easy, because essentially it creates a "history point" in ADE XL which you can then point at and explore the results through the GUI. Not really much different though - you'd still probably open the schematic and so on yourself.

    Regards,

    Andrew.


    Originally posted in cdnusers.org by adbeckett
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thank you for your kind answer. I found I can start ADE from an OCEAN script, as you suggested. The problem is that I also need then to load all design variables which were set in the script into the ADE. I had a look at sev* functions, and they generally allow you to open forms to insert values which are stored in the current ADE sessions.

    E.g. I can start a session with:
    sevSession = sevStartSession()
    Choose the design
    sevDesignForm = sevChooseDesign(sevSession)
    then in the ADE click on "Results->Select..." (the design _has_ to be chosen first otherwise that won't work).

    I would like to do all those operations from the script.
    Also, the design variables are not set in this way, while I would like to load them in the ADE from the script without having to enter them manually in a form each time (many variables).
    Is this possible?

    At this point I also would like to open and annotate a schematic, ALL from the script with no manual operations in the form (that is the reason why I am using scripts, to avoid to do the same point-and-click operations each time).

    I saw many SKILL functions (sev* and asi*), which allow you to open a form, so I thought that it could be also be possible to set the values from the script need of opening the forms at all, to do things such as open and annotate a schematic automatically.
    Is this the case?

    Thanks again.
    Kind regards,
    mb



    Originally posted in cdnusers.org by mballini
    • 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