• 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. Functional Verification
  3. Redirect Spectre results to buffer

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 13368
  • 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

Redirect Spectre results to buffer

Khenglish
Khenglish over 10 years ago

I have written a program which reads in a text formatted tran.tran Spectre results file, analyzes the results, then modifies component parameters within input.scs in attempt to improve circuit behaviour. it does this repeatedly for many iterations.

The problem I am having is that the tran.tran file can be very large, making it time consuming to write and read a result file on the disk. I would like to know if it is possible to redirect Spectre's output to a memory buffer which my program could read from, avoiding the overhead of hard disk IO.

  • Cancel
  • Khenglish
    Khenglish over 10 years ago

    I ended up working around this issue by stopping spectre from saving every node in the tran.tran file at every timestep.

    in input.scs:

    saveOptions options save=selected


    Now the simulation literally runs twice as fast.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Khenglish
    Khenglish over 9 years ago
    Writing and reading the tran.tran file is leading to some issues with the Linux file system. I would still like to be able to write to a buffer than can be read by an external program to circumvent the file system. Is that possible?
    • 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