• 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. Can't plot transient signals until after simulation is ...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 125
  • Views 6327
  • 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

Can't plot transient signals until after simulation is complete

forXTer
forXTer over 5 years ago

I'm having a problem where I cannot plot any signals in a spectre transient sim until it is complete. This is a long sim, so I want to make sure things are correct along the way. I've tried using the graph button, calculator, and direct plot with no luck. I also typed "results()" into the CIW window and the output is only "trans(variables)"

It seems like the data is being stored somewhere other than the specified path. Typically I see a psf file in "/testbench/spectre/config/distributed/jobname/psf" while the sim is running, but this folder is empty. Opening this path in a terminal or in results browser both show nothing.

virtuoso - IC6.1.7-64b.500.23

spectre - 17.1.0.515.isr12

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 5 years ago

    Dear forXTer,

    A couple of questions if I may....

    1. Have you navigated in UNIX to the psf directory to see if there is a "spectre.out" file - or are you just trying to locate it with the Results Browser?

    2. Have you examined or changed any of your flushtime parameters? These parameters detail how often the data is written to disk. The more freuqently it is is written, the greater the overall simulation time. These options are under the "Options->Output tab" of the transient analysis and are documented at URL:

    https://support.cadence.com/apex/techpubDocViewerPage?xmlName=spectreref.xml&title=Spectre%20Circuit%20Simulator%20Reference%20--%20Analysis%20Statements%20-%20Transient%20Analysis%20(tran)&hash=pgfId-1063371&c_version=19.1&path=spectreref/spectreref19.1/chap3.html#pgfId-1063371

    or as shown below.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • forXTer
    forXTer over 5 years ago in reply to ShawnLogan

    Hi Shawn,

    All of the flush parameters parameters in the output tab were blank, but I did finally see results after setting CDS_PSFXL_FLUSH_INTERVAL to 300. I think this is default, but I guess it must have forced a flush. I'll mess around with these a bit more, but I think this will fix my problem, thank you for the suggestion.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • forXTer
    forXTer over 5 years ago in reply to ShawnLogan

    Hi Shawn,

    All of the flush parameters parameters in the output tab were blank, but I did finally see results after setting CDS_PSFXL_FLUSH_INTERVAL to 300. I think this is default, but I guess it must have forced a flush. I'll mess around with these a bit more, but I think this will fix my problem, thank you for the suggestion.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to forXTer

    Dear forXTer,

    forXTer said:
    , but I did finally see results after setting CDS_PSFXL_FLUSH_INTERVAL to 300.

    Excellent - thank you for letting me know! Just for your information, the values we use follow:

    $ env | grep FLUSH
    CDS_PSFXL_FLUSH_INTERVAL=10
    CDS_PSFXL_INIT_FLUSH_INTERVAL=10
    CDS_PSFXL_MAX_FLUSH_INTERVAL=10

    I can't say I see any noticeable simulation time increase with the maximum flush interval set to 10. However, I have not benchmarked simulations with the value varied from 10 to 300. I do know other team members experienced your problem and the default value was reduced from 300. I lost track of what it has been set to since that problem occurred a number of years back.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 5 years ago in reply to ShawnLogan

    Note that the flushpoints/flushtime/flushperiod parameters of a tran analysis don't help with PSF XL, you need to use the UNIX env vars that Shawn mentioned. However, I would caution against setting CDS_PSFXL_FLUSH_INTERVAL and CDS_PSFXL_MAX_FLUSH_INTERVAL so low, as if they are set very low, it limits the chunk size of the data that is written, which compromises read performance (that's one of the performance gains that PSF XL offers). I understand why you might want to have the flush interval lower, particularly near the beginning if a simulation to make sure it's starting OK, but if the simulation is taking hours, then after it's up and running, there's not so much need to see immediate feedback every 10 seconds. So that's why the CDS_PSFXL_INIT_FLUSH_INTERVAL is more reasonable to set, to allow initial quick updates, but then that increases over time so that you get the read-performance gains of bigger chunks being saved.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ShawnLogan
    ShawnLogan over 5 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thank you for adding your insights!

    Andrew Beckett said:
    I understand why you might want to have the flush interval lower, particularly near the beginning if a simulation to make sure it's starting OK, but if the simulation is taking hours, then after it's up and running, there's not so much need to see immediate feedback every 10 seconds. So that's why the CDS_PSFXL_INIT_FLUSH_INTERVAL is more reasonable to set, to allow initial quick updates, but then that increases over time so that you get the read-performance gains of bigger chunks being saved.

    Your comment about changing the value of environmental variables after a validating that the simulation is progressing as expected is a very good one. Thank you, as always!

    Shawn

    • 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