• 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. Memory issues with ocean script (Monte-Carlo+Parametric...

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 143
  • Views 995
  • 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

Memory issues with ocean script (Monte-Carlo+Parametric analysis)

Martin A
Martin A over 12 years ago

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:

V1,V2,V3,V4,Perf1,Perf2,Perf3,Perf4 

- 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... 

 

  • Cancel
  • Martin A
    Martin A over 12 years ago

     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...

    • 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