• 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. exclude signal using save command for spectre simulatio...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 13783
  • 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

exclude signal using save command for spectre simulation

jasongong
jasongong over 9 years ago

Dear all,

i am trying to exclude signal from a subcircuit when writing a save file for simulation.

the circuit has hierarchy of X1.X2.X3.

where X3 corresponding subckt name is A.

A includes one transistor TN330, which i don't want to save any voltage or terminal current associated with it.

below is what i put into a file and included in the spectre simulation.

save * subckt=A depth=1 exclude=[TN330:*]

save * subckt=A depth=1 exclude=[TN330:*] sigtype=subckt

however, after simulation, i still get output like:

TN330:ids, TN330:ig  etc etc. and many those signals have a small icon of "E".

i am not sure what the correct format should be and hope someone here can help.

thanks

jason

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    Jason,

    It's not clear what you're trying to do here. What analysis are  you looking at the output of? I can't see why this would save any operating point parameters unless it was the dcOpInfo (i.e. a info analysis with what=oppoint) you were looking at - and that's not controlled by the save statements anyway.

    Perhaps it would be useful to see the analysis statements you have in your netlist and also the version of spectre you're using (should show this at the top of the spectre.out log file).

    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