• 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. Processing raw Spectre Monte Carlo data ?

Stats

  • Locked Locked
  • Replies 23
  • Subscribers 127
  • Views 29242
  • 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

Processing raw Spectre Monte Carlo data ?

MarkGr15
MarkGr15 over 10 years ago

I am using OceanXL (within ADEXL created scripts) to kick off Monte Carlo simulations. I would like to be able to post process the data myself, to be able to calculate the mean, sigmas etc... 

Is the raw data available for this, and how is it organized? I am having a hard time deciphering the file structure etc....

I do see the results listed in an output log, when I add " -log ocean_montecarlo_output.log" as a an option to the command line that I use to kick off my scripts.

The upshot is I want to be able to find the raw data in the output directory, and post process the measured data.

I am using IC6.1.6-64b.500.9.  

spectre -W  => sub-version  13.1.1.049

thanks

Mark

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

    Mark,

    Unknown said:

    1)  Are you saying I can do For Loops, etc... within my OceanXL coding that I have set up based on the ADE-XL testbench?

    No. My assumption is that you've got some kind of monte carlo setup in a script generated from ADE XL. You might be doing monte carlo across corners (maybe temperature and voltage corners, say), and then a number of "points" (each is one iteration of the monte carlo) and multiple tests. For each history, you have a single "RDB" (results database) and the code I gave shows how you iterate through the results to read all the points.

    Unknown said:

    2) for the abStats.il code :   the file says " Modified   Jul 30, 2013 " ...., do I have the correct file?  Or did you forget to update your comments.

    That's correct. I often do forget to update the "Modified" line, but actually the date in the SCCS line is consistent with that. I last modified this code in 2013, having fixed a few things between version 1.6 (which was previously on the support site) and version 1.10 (which is now on the support site). I didn't have to do any fixes this week - I just needed to re-upload the solution. I maintain an internal library of all my SKILL code, which is version controlled, and then I selectively publish some of that as Cadence Online Support solutions. I'd done that, but had forgotten to update the solution to the latest version.

    Unknown said:

    another question about the abStats.il code in solution 11026072. What is the "rmult_27" ? I do not understand what it is, how it is set, or selected. Thanks

    The parameter (or measurement) was called rmult. In IC5141 you could specify a parameter to sweep, and the default parameter was the temperature, and so you see the default temperature shown after all the parameters.

    With ADE XL you can't sweep a parameter with monte carlo, but you can do monte carlo over corners instead. In my example above, I had XXX_monte, where "monte" was my corner name. Note I didn't try using abStats.il where I actually had more than one corner - I only quickly tried it out to make sure it still worked.

    Probably I'd go for the RDB approach as I think it's more future proof.

    Regards,

    Andrew.

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

    Mark,

    Unknown said:

    1)  Are you saying I can do For Loops, etc... within my OceanXL coding that I have set up based on the ADE-XL testbench?

    No. My assumption is that you've got some kind of monte carlo setup in a script generated from ADE XL. You might be doing monte carlo across corners (maybe temperature and voltage corners, say), and then a number of "points" (each is one iteration of the monte carlo) and multiple tests. For each history, you have a single "RDB" (results database) and the code I gave shows how you iterate through the results to read all the points.

    Unknown said:

    2) for the abStats.il code :   the file says " Modified   Jul 30, 2013 " ...., do I have the correct file?  Or did you forget to update your comments.

    That's correct. I often do forget to update the "Modified" line, but actually the date in the SCCS line is consistent with that. I last modified this code in 2013, having fixed a few things between version 1.6 (which was previously on the support site) and version 1.10 (which is now on the support site). I didn't have to do any fixes this week - I just needed to re-upload the solution. I maintain an internal library of all my SKILL code, which is version controlled, and then I selectively publish some of that as Cadence Online Support solutions. I'd done that, but had forgotten to update the solution to the latest version.

    Unknown said:

    another question about the abStats.il code in solution 11026072. What is the "rmult_27" ? I do not understand what it is, how it is set, or selected. Thanks

    The parameter (or measurement) was called rmult. In IC5141 you could specify a parameter to sweep, and the default parameter was the temperature, and so you see the default temperature shown after all the parameters.

    With ADE XL you can't sweep a parameter with monte carlo, but you can do monte carlo over corners instead. In my example above, I had XXX_monte, where "monte" was my corner name. Note I didn't try using abStats.il where I actually had more than one corner - I only quickly tried it out to make sure it still worked.

    Probably I'd go for the RDB approach as I think it's more future proof.

    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