• 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. Spectre: How to get rid of spectre.ic and spectre.fc?

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 125
  • Views 19453
  • 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

Spectre: How to get rid of spectre.ic and spectre.fc?

dontpanic
dontpanic over 8 years ago

Hi! I am running batch simulations over a large extracted design, so I need to trim down the size of the results directories to the bare minimum. The spectre.ic and spectre.fc occupy almost 50MB each, so I want to avoid generating them, but I haven't been able to figure out how...

-In my transient sim setup, tab "State file" I removed the text "spectre.ic"  and "spectre.fc" in the fields "write" and "writefinal", respectively, but the simulator seems to ignore this.

-In the "enviroment" options I have checked "Save state (ss)" and "Recover (rec)" to "n", but this also doesn't seem to have any effect.

Any ideas on how to achieve this? I'm using spectre version 15.1.0.679.isr14 64bit.

Thanks and regards,

Jorge.

P.S. I also noticed that even though I made sure to have no outputs selected for saving/plotting, and my "save all" setup is as in shown below, a "tran.tran.tran.dat" is still generated in the results directory. When I check its contents with the Results Browser tool, I see that one voltage node of my circuit is still being saved. Is this a bug, or spectre must by all means save at least one circuit node?

  • Cancel
Parents
  • dontpanic
    dontpanic over 8 years ago

    Oh, the problem is that the reference netlist directory is generated on a per-run basis, instead of a per-test basis. From the experiments I've quickly ran I see that unchecking "Save Netlists" in Options->Save keeps the following shared netlist directory:

    [results_dir]/[libname]/[cellname]/[adexl view name]/results/data/[run name. e.g. "Interactive.XYW"]/psf/[test name]/netlist

    This folder is still created for every run, even after unchecking "Save Simulation Data". I also can't use this latter option altogether because I rely on separate results directories for each point to dump the actual outputs of interest to disk by means of a verilog-A module in my testbench, which I later postprocess in Matlab (I forgot to mention all this, sorry about that!); unfortunately unchecking that option breaks this functionality, so the post-simulation trigger seemes to me the easiest workaround to try...

    Cheers,
    Jorge.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dontpanic
    dontpanic over 8 years ago

    Oh, the problem is that the reference netlist directory is generated on a per-run basis, instead of a per-test basis. From the experiments I've quickly ran I see that unchecking "Save Netlists" in Options->Save keeps the following shared netlist directory:

    [results_dir]/[libname]/[cellname]/[adexl view name]/results/data/[run name. e.g. "Interactive.XYW"]/psf/[test name]/netlist

    This folder is still created for every run, even after unchecking "Save Simulation Data". I also can't use this latter option altogether because I rely on separate results directories for each point to dump the actual outputs of interest to disk by means of a verilog-A module in my testbench, which I later postprocess in Matlab (I forgot to mention all this, sorry about that!); unfortunately unchecking that option breaks this functionality, so the post-simulation trigger seemes to me the easiest workaround to try...

    Cheers,
    Jorge.

    • 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