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.
Hi all, (sorry for this loooong first post :) )
- I need to do a Monte-Carlo simulation (Virtuoso 6.1.5) for a RF circuit with N runs for different combinaisons of parameters (voltages V1 to V4)
- For each of the 256 combinaisons I want to run a Monte-Carlo to evaluate 4 different parameters (like gain, linearity... Perf1 to Perf4) for each iteration ( N*256 runs totally)
- For each iteration of this Monte-Carlo I want to store the data into a .csv file like this:
- I did a script in OCEAN XL which is basically a loop in which I create a Monte-carlo script with the right parameters, run it and write the results into a .csv file
for each combinaison(
write MC Run (with good parameters)
Perform MC Run
write Results into the csv file()
Everything works fine (the MC is done with good parameters, results are well-written)
The problem is the following:
After approx. 50 or 60 of the 256 combinaisons a memory warning appears saying than my RAM available is low. The memory continues to go down until the simulation crashes by lack of RAM memory. I run Cadence on a 24GB-RAM server (shared with other users) so I guess than the issue is in my script because I did not have any problems before...
How can I be sure than after eah iteration of the loop (MC+writing results) my MC run is deleted from RAM memory?
Leaving a file open for all the simulation process is it "RAM-consuming"?
What can be the problem?
If someone has an idea it would be very helpfull...
Investing it in more details, I think that for each iteration time it creates a new job.
When I lauch my script no jobs are running. If I look into the jobs ".cdslck" folder I see that the number of locked jobs is increasing xith the number of loop iterations. I guess that all those cdslck files are staying in the memory, filling it up until the memory is completely full...
The problem is so (I guess) to kill the finnisehd job(s) after each iteration but as I am in oceanXL and I don't know how to do this...