• 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 Design
  3. Problems visualizing results with Wavescan - MMSIM 6.2 ...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 128
  • Views 2873
  • 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

Problems visualizing results with Wavescan - MMSIM 6.2 - IC 5.1.14

yoyega
yoyega over 15 years ago

 Hi, I am using MMSIM 6.2 with IC.5.1.14. I have to run a large tran simulation with spectre and I've been having problems at the moment of visualizing the results with wavescan. According to sourcelink solution 11264780 I should set the following variable to have the tran.tran file broken up in 2GB files: setenv PSF_WRITE_CHUNK_MODE_ON true. So I have set this environment variable, but I still have only one tran.tran file of 70GB. Is there a solution for this?

 

Thanks,

Pedro

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    First of all, the forum guidelines tell you not to post on the end of an old post - this one is 4 years old. But forgiving that for now, here's some answers:

    1. The "chunk mode" is only supported for PSF, and even then only for transient (not for SP or AC type data). 
    2. Changing the format via the usrCmdLineOption isn't really the right way to do it. For a start, ADE will output -format sst2 and then later you'll have -format psfbin too on the command line. Spectre will actually use whichever format is specified last on its command line - so psfbin will win. However, certain mapping functions in ADE will still think that sst2 was used, and hence it might have issues plotting currents in particular. As a result, the right thing to do would be to use:
      envSetVal("spectre.envOpts" "simOutputFormat" 'string "psfbin")
      before starting ADE.
    3. It's somewhat irrelevant picking psfbin or sst2 anyway, since if sst2 is used as the format, it's only used for transient data. For sp and ac data etc it used psfbin anyway since sst2 doesn't support representing the kind of data needed.
    4. The reason why there are multiple formats is historical. There are some very old formats supported by spectre (e.g. nutmeg), and then there is psf (in various flavours) and sst2. sst2 originated from the digital tools, and was made the default in ADE because it handled certain large transient databases more quickly than the older psfbin. In more recent IC version (IC615, IC616) the default is now "psfxl" which is a much newer format which scales much better when dealing with huge amounts of transient data (it's still using psfbin for some of the small signal analyses though even if you pick psfxl). In IC61X there's a field on a form in ADE now to choose the output format as well as a cdsenv setting.
    5. I'm pretty amazed that an sp analysis could produce that amount of data. You'd have to have a very large number of ports and also a very large number of points in your frequency sweep, I'd have thought. Even with noise... so I'd check your setup.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    First of all, the forum guidelines tell you not to post on the end of an old post - this one is 4 years old. But forgiving that for now, here's some answers:

    1. The "chunk mode" is only supported for PSF, and even then only for transient (not for SP or AC type data). 
    2. Changing the format via the usrCmdLineOption isn't really the right way to do it. For a start, ADE will output -format sst2 and then later you'll have -format psfbin too on the command line. Spectre will actually use whichever format is specified last on its command line - so psfbin will win. However, certain mapping functions in ADE will still think that sst2 was used, and hence it might have issues plotting currents in particular. As a result, the right thing to do would be to use:
      envSetVal("spectre.envOpts" "simOutputFormat" 'string "psfbin")
      before starting ADE.
    3. It's somewhat irrelevant picking psfbin or sst2 anyway, since if sst2 is used as the format, it's only used for transient data. For sp and ac data etc it used psfbin anyway since sst2 doesn't support representing the kind of data needed.
    4. The reason why there are multiple formats is historical. There are some very old formats supported by spectre (e.g. nutmeg), and then there is psf (in various flavours) and sst2. sst2 originated from the digital tools, and was made the default in ADE because it handled certain large transient databases more quickly than the older psfbin. In more recent IC version (IC615, IC616) the default is now "psfxl" which is a much newer format which scales much better when dealing with huge amounts of transient data (it's still using psfbin for some of the small signal analyses though even if you pick psfxl). In IC61X there's a field on a form in ADE now to choose the output format as well as a cdsenv setting.
    5. I'm pretty amazed that an sp analysis could produce that amount of data. You'd have to have a very large number of ports and also a very large number of points in your frequency sweep, I'd have thought. Even with noise... so I'd check your setup.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information