• 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. Monte Carlo - Virtuoso IC 6.1.5

Stats

  • Locked Locked
  • Replies 17
  • Subscribers 126
  • Views 9819
  • 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

Monte Carlo - Virtuoso IC 6.1.5

kenambo
kenambo over 11 years ago

Hi,

In monte carlo analysis, what is the need for the "monte carlo seeds" field.

Is there any result variation for the different number of seeds..

Thanks.

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

    First of all, I would suggest looking at your device models. If you look at the model files that are included in your netlist (i.e. those referenced from ADE) and check to see if there is a statistics block in the model files. This will look something like this:

    statistics {
        process {   // process: generate random number once per MC run
            vary rshsp dist=gauss std=12 percent=yes
            vary rshpi dist=gauss std=rshpi_std // rshpi_std is a parameter
            vary xxx dist=lnorm std=12
            vary uuu dist=unif N=10 percent=yes
            truncate tr=2.0 // +/- 2 sigma
        }
        mismatch {  // mismatch: generate a random number per instance
            vary rshsp dist=gauss std=2     
            vary xisn dist=gauss std=0.5    
            vary xisp dist=gauss std=0.5    
            truncate tr=7.0 // +/- 7 sigma
        }
    }

    Probably just doing "grep statistics *.scs" would be a good start to find it. Check to see if there's a mismatch section.

    Assuming all looks OK there, the models themselves need to be subckts. Mismatch is applied to each subckt and then the models within those subckts can be unique. If the transistors you are using are just direct models (without a subckt around them), then no mismatch will be applied. Some technologies have different components for mismatch than for normal use (for strange reasons).

    Not sure if you said, but what technology are you using?

    Regards,

    Andrew.

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

    First of all, I would suggest looking at your device models. If you look at the model files that are included in your netlist (i.e. those referenced from ADE) and check to see if there is a statistics block in the model files. This will look something like this:

    statistics {
        process {   // process: generate random number once per MC run
            vary rshsp dist=gauss std=12 percent=yes
            vary rshpi dist=gauss std=rshpi_std // rshpi_std is a parameter
            vary xxx dist=lnorm std=12
            vary uuu dist=unif N=10 percent=yes
            truncate tr=2.0 // +/- 2 sigma
        }
        mismatch {  // mismatch: generate a random number per instance
            vary rshsp dist=gauss std=2     
            vary xisn dist=gauss std=0.5    
            vary xisp dist=gauss std=0.5    
            truncate tr=7.0 // +/- 7 sigma
        }
    }

    Probably just doing "grep statistics *.scs" would be a good start to find it. Check to see if there's a mismatch section.

    Assuming all looks OK there, the models themselves need to be subckts. Mismatch is applied to each subckt and then the models within those subckts can be unique. If the transistors you are using are just direct models (without a subckt around them), then no mismatch will be applied. Some technologies have different components for mismatch than for normal use (for strange reasons).

    Not sure if you said, but what technology are you using?

    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