• 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. spectre - saving by specific subcircuit

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 127
  • Views 12098
  • 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

spectre - saving by specific subcircuit

swdesigner
swdesigner over 14 years ago

Is it possible to tell spectre to save all nodes or terminal currents within a certain subckt? It's trivial in Hspice, you could do

 

save all Xtop.Xsub.*

 

I believe there's even a way to use the wildcards to get it to only do the top-level within that subcircuit, but I don't recall it..

 

Any ideas? How would it be done through the ADE, without messing with the netlist?

  • Cancel
Parents
  • swdesigner
    swdesigner over 14 years ago

    How about AMS?

    I find that the best way with spectre and the ADE is to put the full pathname of the include file in the Defintion files field under Simulation Files. (Model Libraries was suggested, but I think this is more meaningful).

    Could someone post an example of save commands for AMS and the best location to specify the file for inclusion (which field in ADE to use)?

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • swdesigner
    swdesigner over 14 years ago

    How about AMS?

    I find that the best way with spectre and the ADE is to put the full pathname of the include file in the Defintion files field under Simulation Files. (Model Libraries was suggested, but I think this is more meaningful).

    Could someone post an example of save commands for AMS and the best location to specify the file for inclusion (which field in ADE to use)?

    Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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