• 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 SKILL
  3. How can I access the Monte Carlo parameter variation data...

Stats

  • Replies 4
  • Subscribers 143
  • Views 1898
  • Members are here 0

How can I access the Monte Carlo parameter variation data in the results database?

RudyE
RudyE 27 days ago

For each MC run, I'd like to get data for each parameter regarding the base value of the parameter, and how it was varied for this particular run. I have been going through the database structure, but was not able to find the data:

db~>??
(dataFile stdobj@0x40a603f8 name "modelParameter-info" wave
    nil obj \*slotUnbound\* type "info"
    sweepValue nil _pDistoHarmonicListCache nil _pDistoHarmonicFreqListCache
    nil _pacHarmonicFreqListCache nil sweepName "mcparamset"
    sweepValues 
    ((1.0 2.0 3.0 4.0 5.0
        6.0 7.0 8.0 9.0 10.0
        11.0 12.0 13.0 14.0 15.0
        16.0 17.0 18.0 19.0 20.0
        21.0 22.0 23.0 24.0 25.0
        26.0 27.0 28.0 29.0 30.0
        31.0 32.0 33.0 34.0 35.0
        36.0 37.0 38.0 39.0 40.0
        41.0 42.0 43.0 44.0 45.0
        46.0 47.0 48.0 49.0 50.0
    ) 50.0
    ) sweepTable table:sweepTable analysisSignals
    nil
)

  • Cancel
  • Sign in to reply
  • RudyE
    RudyE 26 days ago

    Just to clarify:  I want access to the model parameter variations of each Monte Carlo run through Skill. Specifically, I want to be able to write a matrix with the variation data, where the rows of the matrix are the runs and the columns represent each of the individual parameters that were randomly varied over the runs. Examples of the parameters are each individual threshold voltage model parameter for the mosfets, or the resistor sheet rho model parameter.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 26 days ago in reply to RudyE

    The only way (through a procedural interface) to access the per-point statistical data is (I believe) through the ADE MATLAB Integration - you can get to the information through:

    res=adeInfo.loadResult()
    rdb=res.adeRDB
    rdb.statParams
    % or - to get the values rather than just the names
    rdb.results(table=Table.StatResults)

    I think it would make sense to provide a way to access the same data through the maeReadResDB() API - this turns an object which allows you to get to simulation result database information (note, the statistical data is stored in a different database in current versions, but other interfaces take care of that).

    Interactively, you can use Right Mouse->Print Statistical Parameters over a Monte Carlo point in the Detail or Detail Transpose view. Note, in all cases you have to have elected to save Statistical Parameters from the Monte Carlo Options form (otherwise this data is not saved).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 26 days ago in reply to Andrew Beckett
    Andrew Beckett said:
    I think it would make sense to provide a way to access the same data through the maeReadResDB() API

    Pressed Reply too quickly. Meant to suggest that you contact customer support and use the Case menu to submit a request that an enhancement request to do this is added on your behalf. I didn't spot such a request in my searching (I had a recollection that I'd requested this, but I may have been mixing up where the rdb.statParams was broken a while back when we switched to the new statistics database storage mechanism, and that's what I filed a request to fix - since resolved).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • RudyE
    RudyE 26 days ago in reply to Andrew Beckett

    Thank you Andrew!

    Rudy

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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