• 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. Running multiple AC sims during a transient analysis

Stats

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

Running multiple AC sims during a transient analysis

CADcasualty
CADcasualty over 6 years ago

I was looking for a way to run a transient analysis and at various times along the way perform an stability analysis. I found a way to do this via e.g.:

analysis('tran ?stop "250n" ?actimes list("0" "250n") ?acnames list("stb") )
analysis('stb ?start "10" ?stop "100M" ?dec "10" ?probe "/stage1/amp/I1/vinj" )
run()

However at the times I want to pause the transient analysis to perform the stability analysis I actually want to perform multiple stability analyses. An example reason is that my circuit is a multi-stage switched capacitor amplifier and in one phase all of the stages are disconnected so I can easily do separate stability analyses for each stage without them interfering with each other.

The method outlined in the code above only lets me do one stability analysis per paused transient time. I know there is a way to save the full transient state at various points during the transient simulation. Is there a way later to retrieve that state and force the circuit to use it for multiple subsequent stability analyses?

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    You can define more than one stability analysis - the rest you'd need to define in an include file rather than through OCEAN (so you could use OCEAN to add another model file (say) containing the spectre statements for the additional stability analyses). For example:

    stb1 stb start=1 stop=1G dec=20 probe=IPRB0
    stb2 stb start=1 stop=10G dec=20 probe=IPRB1
    stb3 stb start=1 stop=100G dec=20 probe=I7.IPRB1

    (they don't have to have the same sweeps). Then you can do ?acnames list("stb" "stb1" "stb2" "stb3") to reference the one defined via an analysis() call in OCEAN plus the rest coming from the include file.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • CADcasualty
    CADcasualty over 6 years ago in reply to Andrew Beckett

    Just back into the office and wanted to say thanks for your assistance again. I'll give this method a try a little later on. It isn't very intuitive to me - it would be nicer if there was a way to just capture the nodes at a given transient time point and use that for any number of subsequent AC (or whatever) analyses.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to CADcasualty

    Whilst it might seem a good idea to capture (say) the operating point as a set of node voltages/branch currents at a point in time and save this to a file, it could be problematic restoring that later, since even if you used it as an initial condition, it would probably clash with the driven voltages into the circuit unless they magically knew the time at which the operating point was captured and so the driven sources would be at their correct phase for that point. That's not possible, and I suspect the flow would be even more complicated as a result.

    Of course, this (using actimes during a transient with several analyses) would be a whole lot easier if ADE let you define multiple analyses of the same type in the UI (a long-standing request, unfortunately not entirely trivial to implement because of lots of assumptions in various places that there's only one of each type).

    Regards,

    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