• 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. How transient operating point is calculated in cadence

Stats

  • Locked Locked
  • Replies 27
  • Subscribers 127
  • Views 32432
  • 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

How transient operating point is calculated in cadence

prashu
prashu over 13 years ago

 When performing transient analysis with cadence my input is changing and accordingly its operating point should change but when i see its transient operating point than it only show one region throughout the transient analysis please expalin

  • Cancel
Parents
  • imagesensor123
    imagesensor123 over 13 years ago

    Hi Andrew,

         here is the analysis statements:

        simulatorOptions options reltol=100e-6 vabstol=1e-6 iabstol=1e-12 temp=27 \
        tnom=27 homotopy=all limit=delta scalem=1.0 scale=1.0 \
        compatible=spice2 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5 digits=5 \
        cols=80 pivrel=1e-3 ckptclock=1800 sensfile="../psf/sens.output" \
        checklimitdest=psf
    dcOp dc write="spectre.dc" save=all maxiters=150 maxsteps=10000 \
        annotate=status
    capInfo_dc info what=captab where=logfile threshold=0.0 detail=node \
        sort=name
    dcOpInfo info what=oppoint where=rawfile
    tran tran stop=30m errpreset=conservative step=1n ic=dc write="spectre.ic" \
        writefinal="spectre.fc" annotate=status save=all oppoint=rawfile \
        maxiters=5 infoname="capInfo_dc" infotimes=[3m 7m 11m]
    finalTimeOP info what=oppoint where=rawfile
    modelParameter info what=models where=rawfile
    element info what=inst where=rawfile
    outputParameter info what=output where=rawfile
    designParamVals info what=parameters where=rawfile
    primitives info what=primitives where=rawfile
    subckts info what=subckts  where=rawfile
    save MCOLUMNAMP:d MCOLUMNAMP:g Pixel0.MSELECT:d Pixel0.MSELECT:s
    saveOptions options save=all currents=selected 

    could you see it clearly now?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • imagesensor123
    imagesensor123 over 13 years ago

    Hi Andrew,

         here is the analysis statements:

        simulatorOptions options reltol=100e-6 vabstol=1e-6 iabstol=1e-12 temp=27 \
        tnom=27 homotopy=all limit=delta scalem=1.0 scale=1.0 \
        compatible=spice2 gmin=1e-12 rforce=1 maxnotes=5 maxwarns=5 digits=5 \
        cols=80 pivrel=1e-3 ckptclock=1800 sensfile="../psf/sens.output" \
        checklimitdest=psf
    dcOp dc write="spectre.dc" save=all maxiters=150 maxsteps=10000 \
        annotate=status
    capInfo_dc info what=captab where=logfile threshold=0.0 detail=node \
        sort=name
    dcOpInfo info what=oppoint where=rawfile
    tran tran stop=30m errpreset=conservative step=1n ic=dc write="spectre.ic" \
        writefinal="spectre.fc" annotate=status save=all oppoint=rawfile \
        maxiters=5 infoname="capInfo_dc" infotimes=[3m 7m 11m]
    finalTimeOP info what=oppoint where=rawfile
    modelParameter info what=models where=rawfile
    element info what=inst where=rawfile
    outputParameter info what=output where=rawfile
    designParamVals info what=parameters where=rawfile
    primitives info what=primitives where=rawfile
    subckts info what=subckts  where=rawfile
    save MCOLUMNAMP:d MCOLUMNAMP:g Pixel0.MSELECT:d Pixel0.MSELECT:s
    saveOptions options save=all currents=selected 

    could you see it clearly now?

    • 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