• 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. Extracting transient operating points at different instants...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 144
  • Views 4161
  • 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

Extracting transient operating points at different instants using "infotimes" using skill script.

RFStuff
RFStuff over 12 years ago

 Dear All,

I thought this query may be suitable for this forum so posting here.

I want to find Operating Points of components at multiple time instants of  a transient analysis. One way, I used "infotimes" option.

But how I can use "OP( )" command in the script to extract/display the operting points of the components at differnt instants inserted in "infotimes" option.

Could anybody please tell how it can be done.

Kind Regards,

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

    A few thoughts.

    First of all, you can't use the report() function with the results of using infotimes - if I do selectResults("tran_info") and then report() - it fails. I filed CCR 1121977 for this.

    Secondly, you could use:  OPT("/I7/M1" "gds") to get the gds of the specific transistor - this will give you a waveform versus the infotimes on the x-axis. You could then use the value() function to extract at the specific time: value(OPT("/I7/M1" "gds") 1.2u)

    Thirdly, you could use:

    ocnPrint(OPT("/I7/M1" "??"))

    to display the operating point info for all parameters at all infotimes for a specific transistor.

    Fourthly, you could create a file, say "myInfo.scs" with the following contents:

    //
    myInfo info what=oppoint where=file

    and then reference this file as a Model Library from Setup->Model Libraries. Then in the transient analysis, don't fill in infotimes, but instead in the additional parameters field (on the transient options form at the bottom), enter:

    infoname=myInfo infotimes=[1.2u 2.3u]

    (the infoname has to match the first word on your info analysis).

    It will then write a report into the netlist directory containing a description of the operating point values of all devices in your design.

    Hopefully that's enough to get you going!

    Regards,

    Andrew.

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

    A few thoughts.

    First of all, you can't use the report() function with the results of using infotimes - if I do selectResults("tran_info") and then report() - it fails. I filed CCR 1121977 for this.

    Secondly, you could use:  OPT("/I7/M1" "gds") to get the gds of the specific transistor - this will give you a waveform versus the infotimes on the x-axis. You could then use the value() function to extract at the specific time: value(OPT("/I7/M1" "gds") 1.2u)

    Thirdly, you could use:

    ocnPrint(OPT("/I7/M1" "??"))

    to display the operating point info for all parameters at all infotimes for a specific transistor.

    Fourthly, you could create a file, say "myInfo.scs" with the following contents:

    //
    myInfo info what=oppoint where=file

    and then reference this file as a Model Library from Setup->Model Libraries. Then in the transient analysis, don't fill in infotimes, but instead in the additional parameters field (on the transient options form at the bottom), enter:

    infoname=myInfo infotimes=[1.2u 2.3u]

    (the infoname has to match the first word on your info analysis).

    It will then write a report into the netlist directory containing a description of the operating point values of all devices in your design.

    Hopefully that's enough to get you going!

    Regards,

    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