• 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. print values for dc analysis

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 6060
  • 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

print values for dc analysis

AndyWangsh
AndyWangsh over 2 years ago

I'm currently using spectre for the dc analysis for a simple NMOS, represented as 

mn0 (d_n g_n 0 b_n) g45n1svt w=w_n l=l_n

vg_n_inst (g_n 0) vsource dc=vg_n

I would trying to save the mn0:vsat for individual vg_nvalue  to the log file or other files for the dc analysis:

dc_a dc param=vg_n start=0 stop=2 step=0.01 save=all print=yes  

I also added the following at the end of scs file:

outputInfo info what=output where=logfile
element info what=inst where=logfile

However, there is no vdsat printed in the log file or elsewhere. 

I tried to search over the Spectre® Simulator Fundamentals course & the spectre manual, but it seems like I cannot find the solution out there. 

I'm not sure what could be the possible solution. I would expect similar results as .print mn0:vdsat if written in SPICE. 

Thanks in advance. 

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 2 years ago

    Dear AndyWangsh,

    AndyWangsh said:

    I would trying to save the mn0:vsat for individual vg_nvalue  to the log file or other files for the dc analysis:

    dc_a dc param=vg_n start=0 stop=2 step=0.01 save=all print=yes  

    I also added the following at the end of scs file:

    outputInfo info what=output where=logfile
    element info what=inst where=logfile

    However, there is no vdsat printed in the log file or elsewhere. 

    According to the Spectre reference manual, the "print" argument to the dc analysis command refers to printing the node voltages and not the operating point information. If you want to observe the operating point information, I might suggest you refer to the response to the recent Forum post at URL:

    https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/52194/results-display-window/1384734#1384734

    There are 3 links that include a video on how to save operating point information, a troubleshooting article on the subject, and a means to print the DC oeprating point information to a file.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 2 years ago

    Dear AndyWangsh,

    AndyWangsh said:

    I would trying to save the mn0:vsat for individual vg_nvalue  to the log file or other files for the dc analysis:

    dc_a dc param=vg_n start=0 stop=2 step=0.01 save=all print=yes  

    I also added the following at the end of scs file:

    outputInfo info what=output where=logfile
    element info what=inst where=logfile

    However, there is no vdsat printed in the log file or elsewhere. 

    According to the Spectre reference manual, the "print" argument to the dc analysis command refers to printing the node voltages and not the operating point information. If you want to observe the operating point information, I might suggest you refer to the response to the recent Forum post at URL:

    https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/52194/results-display-window/1384734#1384734

    There are 3 links that include a video on how to save operating point information, a troubleshooting article on the subject, and a means to print the DC oeprating point information to a file.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Andrew Beckett
    Andrew Beckett over 2 years ago in reply to ShawnLogan

    Very simply, you can just use:

    opPoint info what=oppoint where=logfile

    (the first word doesn't really matter, as long as it is unique; it's the what=oppoint which tells it to output operating point parameters in the info analysis).

    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