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

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?

Parents
  • dontpanic
    Thanks for the information, Andrew! Unchecking "Save Netlists" in Options->Save improved a lot the situation, but a reference netlist directory is still created common to all run points (digging in the manual I found: "[...]To save only the results, and not the netlist, for each design point, deselect Save Netlists and select only Save Simulation Data. With these of options, a reference netlist directory is created. The point-specific netlist is not saved and the netlist directory for every point is replaced with a symbolic link to the reference netlist directory.)

    Since during design validation dozens of runs are easily needed, keeping these netlist directories still yields results directories occupying some gigabytes. Do you think a skill procedure+post-simulation trigger approach could be used to delete these directories, or maybe it could break some causality order (i.e. delete stuff while the tool still expects it to exist)? I've never worked with post-simulation triggered procedures, so I don't know how difficult would be to implement this.

    Thanks and regards,
    Jorge
Reply
  • dontpanic
    Thanks for the information, Andrew! Unchecking "Save Netlists" in Options->Save improved a lot the situation, but a reference netlist directory is still created common to all run points (digging in the manual I found: "[...]To save only the results, and not the netlist, for each design point, deselect Save Netlists and select only Save Simulation Data. With these of options, a reference netlist directory is created. The point-specific netlist is not saved and the netlist directory for every point is replaced with a symbolic link to the reference netlist directory.)

    Since during design validation dozens of runs are easily needed, keeping these netlist directories still yields results directories occupying some gigabytes. Do you think a skill procedure+post-simulation trigger approach could be used to delete these directories, or maybe it could break some causality order (i.e. delete stuff while the tool still expects it to exist)? I've never worked with post-simulation triggered procedures, so I don't know how difficult would be to implement this.

    Thanks and regards,
    Jorge
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.