• 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. A stochastic model in Verilog A for Monte Carlo simulat...

Stats

  • Locked Locked
  • Replies 29
  • Subscribers 125
  • Views 33243
  • 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

A stochastic model in Verilog A for Monte Carlo simulation

UUinfini
UUinfini over 11 years ago

 Hello Guys,

I have a problem for Veriglog A in Cadence, I hope you can help me. In fact I need to elaborate a stochastic model by coding in Verilog A executed under Cadence. My aim is to offer a model with which the customers can do the Monte Carlo Analysis. But I used the functions like "$random", "$temperature" etc. to generate a seed for obtaining a parameter which changes each time of simulation. But finally it changes just according to the real time of simulation, but not according to different times of simulation. Do you have any experiences like this? Thank you for you response.

Best regards,

UU

  • Cancel
  • UUinfini
    UUinfini over 11 years ago
    Ok, thank you. I'am using the version 6.1.5
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    That's the IC version; as I mentioned earlier, it's the MMSIM version that makes the difference in terms of parsing the Verilog and creating the CDF which controls how it is netlisted. You're using MMSIM10.1 and this was fixed in MMSIM11.1 ISR17.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UUinfini
    UUinfini over 11 years ago

     Hello Andrew,

    When I did the MC simulation with ten points, every time the ten numbers I got are always the same(for example always 203,184,151,91,66,46,-1,-28,-86,-90). Is it normal? When I used the library of CMOS to do the MC simulation it's the same case. For one time, the parameter is random, but for 10 times, always the same random numbers. Thank you.

    Best ragards,

    UU

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Yes, it's normal. The seed in ADE XL is set (by default) to 12345 - and this means that simulation results are repeatable. That's nearly always what people want - if I don't change anything, I should get the same answer. You can get a different sequence by specifying a seed on the monte carlo options form, but this isn't any  more random - it's an equally random, different sequence of random numbers. So I always think it's of limited usefulness.

    Kind Regards,

    Andrew.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UUinfini
    UUinfini over 11 years ago

     Ok, thank you. For the statistic blocs, I used gauss distribution as the majority of people used. If I want to use other distributions, like exponential, uniform etc. what should I write? Can you recommend me a document to learn more about this? Because in the Verilogaref there is just VerilogA file, no other things. Thank you.

    Best regards,

    UU

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    If you run <MMSIMinstDir>/tools/bin/cdnshelp you can access the entire documentation for the simulator. Look in the spectre reference and user guides for more detail - or search for "statistics" or "montecarlo".

    Or you could type:

    spectre -h montecarlo

    from the UNIX command line. This will describe the statistics block used by  monte carlo too.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UUinfini
    UUinfini over 11 years ago

     Hello Andrew,

    I have found that when I execute the simulation in a computer of 32 bits, "seedin"(defined as cds_inherited parameter) is regarded as a component parameter, and the Monte Carlo simulation goes well, but in a computer of 64 bits, "seedin" is automatically eliminated from the list of component parameters(not in the CDF),  at the same time Monte Carlo simulation doesn't work(always one result with no matter how many points of simulation of Monte Carlo). Is there any difference between the use of this kind of parameter in the two systems? Thank you for your response.

    Best regards,

    UU 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    That seems a bit unlikely - are you sure you're using the same version of the tools on the different machines? I've never seen this behaviour before. On very rare occasions there can be issues which only show up when running spectre in 32 bit or 64 mode (and I'm talking about the bitness of the application here, not the bitness of the OS), but I've not seen any issues between the OS bitness for many years. Even then it was not a difference in functionality, as you're describing here.

    I was certainly running on a 64 bit OS when I tried this out, because in fact nowadays (since MMSIM11.1 if my memory is correct) we only support 64-bit OS. I was using MMSIM13.1. You were (I think) using MMSIM10.1 - and it's probably wise to update to something more recent (and supported) anyway.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • UUinfini
    UUinfini over 11 years ago

     Thank you, I will try to find the real problem.

    Best regards,

    UU

    • 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