Cadence® system design and verification solutions, integrated under our System Development Suite, provide the simulation, acceleration, emulation, and management capabilities.
System Development Suite Related Products A-Z
Cadence® digital design and signoff solutions provide a fast path to design closure and better predictability, helping you meet your power, performance, and area (PPA) targets.
Full-Flow Digital Solution Related Products A-Z
Cadence® custom, analog, and RF design solutions can help you save time by automating many routine tasks, from block-level and mixed-signal simulation to routing and library characterization.
Overview Related Products A-Z
Driving efficiency and accuracy in advanced packaging, system planning, and multi-fabric interoperability, Cadence® package implementation products deliver the automation and accuracy.
Cadence® PCB design solutions enable shorter, more predictable design cycles with greater integration of component design and system-level simulation for a constraint-driven flow.
An open IP platform for you to customize your app-driven SoC design.
Comprehensive solutions and methodologies.
Helping you meet your broader business goals.
A global customer support infrastructure with around-the-clock help.
24/7 Support - Cadence Online Support
Locate the latest software updates, service request, technical documentation, solutions and more in your personalized environment.
Cadence offers various software services for download. This page describes our offerings, including the Allegro FREE Physical Viewer.
Get the most out of your investment in Cadence technologies through a wide range of training offerings.
This course combines our Allegro PCB Editor Basic Techniques, followed by Allegro PCB Editor Intermediate Techniques.
Virtuoso Analog Design Environment Verifier 16.7
Learn learn to perform requirements-driven analog verification using the Virtuoso ADE Verifier tool.
Exchange ideas, news, technical information, and best practices.
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.
It's not all about the technlogy. Here we exchange ideas on the Cadence Academic Network and other subjects of general interest.
Cadence is a leading provider of system design tools, software, IP, and services.
I need help to extract information about model parameters for each Monte-Carlo iteration in a Spectre simulation.
The scenario is as follows:
For now, I have circumvented the issue by adding a line just before the transient analysis:
paramInfo info what=all where=file file="MC_MODEL_PARAM" save=all
it does what I want but it has two drawbacks:
Basically, I got the problem solved, but I would be interested in knowing whether it can be done in a similar way as mismatch parameters (which results in different files for each MC iteration)
Thanks for your help!
If you use what=models it will save less information. Secondly, by using where=rawfile, it would save into the psf directory - and that way the data is organized by iteration number. It's binary, but easily processed using OCEAN functions.
In reply to Andrew Beckett:
thanks a lot for your help. I have used what=models and what=inst to relax the amount of information to be saved, as well as where=rawfile. I tinkered around with data but I'm still experiencing problems.
I would like to process the MC data into MATLAB and then stumbled upon Spectre/RF MATLAB library, which looks great. I'm able to run the cds_srr command, however I'm not getting the results expected.
The picture of my simulation structure is as follows:
`-- monteCarlo |-- MC3_separate | |-- MC3-001 | |-- MC3-002 | |-- MC3-003 | |-- MC3-004 | |-- MC3-005 | `-- MC3-006 `-- params
In the first level (.) I have the netlist *.scs files of both the testbench and the top design../montecarlo Contains the results of the simulation of the testbench. At this level I can find both latest transient analysis and parameters (inst, in this particular case): TRAN1.tran and paramInfo.info. Then, two more files appear: MC3_TRAN1.montecarlo and MC3_paramInfo.montecarlo. I guess they are the files that point to the rest of MC simulations which are in the MC3_separate subfolders. Finally, logFile (attached, as well) is the file which MATLAB reads to know which files to evaluate../params I have all the MC parameters specified in testbench file (which is attached in this post). ./MC3_separate contains all the MC runs specified. Inside the subfolder I can find both transient and paramaters information for each run.
The problem arises whenever I try to load my data in MATLAB. cds_srr(dirname) is unable to find the MC simulations, even though they appear in logFile (to whom folder I point to via dirname). I can only access to the latest transient and parameter info files: TRAN1.tran and paramInfo.info. I have noticed that changing from psfbin to sst2 exporting options makes montecarlo simulations appear when calling cds_srr. However I'm bogged down again when trying to access this simulation: it is empty.
To summarize everything up, whenever I run cds_srr I'm not able to load MC simulations.
In case you need further information do not hesitate to ask.
Thanks a lot for your help.