• 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 netlist

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 8213
  • 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 netlist

shaarawy2023
shaarawy2023 over 3 years ago

when i write a spectre netlist to perform dcOp on a circuit that contains mosfet device, the ouput (dcOp.dc) only contain the voltages nodes and current, how to make spectre save also the mosfet parameters (like gm,vth, etc..) in the output file   

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    The way it's usually done (in ADE) is to add an info analysis to save the operating point data:

    dcOp dc annotate=status
    dcOpInfo info what=oppoint where=rawfile

    However, you can also add oppoint=rawfile to the dc analysis (note that ADE doesn't expect the results to be there for operating point analysis, but this is probably irrelevant for command-line use). You can also use where=file or oppoint=file to save to a text file rather than a PSF database.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 3 years ago

    The way it's usually done (in ADE) is to add an info analysis to save the operating point data:

    dcOp dc annotate=status
    dcOpInfo info what=oppoint where=rawfile

    However, you can also add oppoint=rawfile to the dc analysis (note that ADE doesn't expect the results to be there for operating point analysis, but this is probably irrelevant for command-line use). You can also use where=file or oppoint=file to save to a text file rather than a PSF database.

    Andrew

    • 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