• 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. Maestro - problem with sweeping a transistor parameter because...

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 666
  • 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

Maestro - problem with sweeping a transistor parameter because of netlist format

frankp
frankp 7 months ago

Hello all,

When perform a designVar sweep analysis (be it in a "dc" or "ac" analysis) for the number of fingers of a transistor ("nf"), I get simulation results that do not make sense.

I was able to trace this down that each transistor macro cell has 2 netlist lines:

The 1st one containing all the basic info, gl, nf, m (not too many parameters)

And the 2nd one, where the real deep-dive netlist parameters of the said transistor exist. This 2nd line was generated as a consequence of the 1st line.

So basically when sweeping nf (number of fingers), the 2nd line of netlist will not be getting altered. Hence the wonky simulation results.

Is there an environment variable that permits the recreation of the netlist, even though the schematic does not change ?

Note: I am not sweeping the desVar through multiple corners, I doing so via the desVar sweep capability of a regular "dc" or "ac" analyses - In case I was not clear earlier.

Thank you

Frank

Cadence virtuoso version: IC23.1-64b.1SR9.24

  • Cancel
  • frankp
    frankp 7 months ago

    Reason why I am not using multiple corners to sweep the design variable is that I need to have multiple corners too (80+ corners).

    So I want to bury the desVar sweep (of the transistor) in a series of multiple corners.

    Hence, I need something that forces netlist recreation, despite the fact that from a tool (meastro) perspective it does not make sense to have multiple netlist files (that should be identical)

    Frank 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • frankp
    frankp 7 months ago in reply to frankp

    Correction:

    Even with using multiple corners to sweep a desVar (5 corners in this simulation), my simulation is still only generating only one netlist/netlist file (in the maestro/<history entry>/psf/<testname> directory. All 5 corners have their netlist/netlist linked to that said .../psf/<testname>/netlist/netlist file.

    What needs to be done to have a netlist/netlist file (not link) per corner ?

    Frank

    • 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