Stats

  • Locked Locked
  • Replies 4
  • Subscribers 124
  • Views 10463
  • 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

"simulation data not available" problem

archive

Hello,

I used "tran" analysis for a simulation, with simulation setup all correct (ie. same setup as my prev. known good ones). Indeed, simulation finished, and the tran.tran file was about 290 Giga. However, when I used plot to see nodes' voltage/current, it said the wavefore data was not available, and then it crashed the whole "icfb" tool kits.

I am wondering if this is a bug, or a limitation that I was not aware before. This happened several times so I am wondering if there is a solution for it. Thank you !

san



Originally posted in cdnusers.org by sz5g
Parents

  • A simulator can sequentially write out the data to a massive file as it goes along.

    However, to plot the waveforms, it has to load the data for that waveform into memory. Given that the waveform tool is a 32 bit executable, the absolute maximum memory it can use is 4G (2^32 bytes). Given that there's some overhead over what is stored on disk, it's not hard for you to run out of memory...

    290G is pretty massive. You might want to try to cut down the amount of data. Save less waveforms, and you might want to cut down the number of points in the results database (e.g. skipcount, starttime, strobeperiod - lots of options).

    Andrew.


    Originally posted in cdnusers.org by adbeckett
Reply

  • A simulator can sequentially write out the data to a massive file as it goes along.

    However, to plot the waveforms, it has to load the data for that waveform into memory. Given that the waveform tool is a 32 bit executable, the absolute maximum memory it can use is 4G (2^32 bytes). Given that there's some overhead over what is stored on disk, it's not hard for you to run out of memory...

    290G is pretty massive. You might want to try to cut down the amount of data. Save less waveforms, and you might want to cut down the number of points in the results database (e.g. skipcount, starttime, strobeperiod - lots of options).

    Andrew.


    Originally posted in cdnusers.org by adbeckett
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.