• 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. Making a monte carlo simulation component specific

Stats

  • Locked Locked
  • Replies 18
  • Subscribers 129
  • Views 25459
  • 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

Making a monte carlo simulation component specific

simbamford
simbamford over 12 years ago
Does anyone know how to specify that for a monte carlo mismatch simulation (presumably using spectre though I also have an ultrasim license), one or two specific transistors will not be subject to mismatch, i.e. will give nominal performance, whilst every other component will be subject to mismatch? Of course it would be convenient if this were possible through the virtuoso inferface, but any method would be useful.Any help gratefully received. 
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    In ADE XL (assuming you're using IC61X; there's no UI support for doing what you want in IC5141), on the "Gear" icon next to the Monte Carlo Sampling cyclic choice (also available via Run->Monte Carlo Sampling in the pulldown), there's a button at the bottom of the form called "Specify Instances/Devices". If you bring this up it allows you to specify devices for mismatch - either as an inclusion or exclusion list. It's partly used to allow the mismatch to correlate between multiple tests which have different testbenches, but can also be used for the purpose you describe.

    The mmcflag parameter that Shawn describes must be specific to a particular PDK because it's not a parameter in spectre as far as I know (certainly not for bsim4 or bsim3v3; to be honest, the mismatch variation is handled outside of the model, so I can't see how it would be done in the device model. For a PDK they might choose to multiply the mismatch variations by this flag inside their subckt models, but as I said, that would be PDK-specific).

    Regards,

    Andrew.

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

    In ADE XL (assuming you're using IC61X; there's no UI support for doing what you want in IC5141), on the "Gear" icon next to the Monte Carlo Sampling cyclic choice (also available via Run->Monte Carlo Sampling in the pulldown), there's a button at the bottom of the form called "Specify Instances/Devices". If you bring this up it allows you to specify devices for mismatch - either as an inclusion or exclusion list. It's partly used to allow the mismatch to correlate between multiple tests which have different testbenches, but can also be used for the purpose you describe.

    The mmcflag parameter that Shawn describes must be specific to a particular PDK because it's not a parameter in spectre as far as I know (certainly not for bsim4 or bsim3v3; to be honest, the mismatch variation is handled outside of the model, so I can't see how it would be done in the device model. For a PDK they might choose to multiply the mismatch variations by this flag inside their subckt models, but as I said, that would be PDK-specific).

    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