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
    Hi Andrew, thanks so much for your prompt reply! (Indeed I missed the snapshot in my post; I've added it for completeness--might be helpful to other users in the future). Both issues are solved now:

    1) [Short reply:] You're right, leaving the empty the "write" and "writefinal" fields causes their respective files not to be produced. [Long reply: I got lost in my sea-of-simulations and was looking at the results of a "clon" adexl view running on another server, where I hadn't cleared these fields yet! I'm in tapeout-mode currently, so the quality of my wakefulness is pretty low, sorry!).
    2) The "save=nooutput" totally makes the trick of no signal at all being written to the "tran.tran.tran.dat" file! :)

    Now, that being solved, my simulation run directories are still considerably big due to 2 files in the netlist directory : "input.scs" and "netlist" (~50MB each). Is there an easy way to tell ADE-XL to delete these after the run is complete? Maybe with a SKILL procedure installed as a post-simulation trigger somehow?

    Thanks so much again for your help!
    Cheers,
    Jorge.
Reply
  • dontpanic
    Hi Andrew, thanks so much for your prompt reply! (Indeed I missed the snapshot in my post; I've added it for completeness--might be helpful to other users in the future). Both issues are solved now:

    1) [Short reply:] You're right, leaving the empty the "write" and "writefinal" fields causes their respective files not to be produced. [Long reply: I got lost in my sea-of-simulations and was looking at the results of a "clon" adexl view running on another server, where I hadn't cleared these fields yet! I'm in tapeout-mode currently, so the quality of my wakefulness is pretty low, sorry!).
    2) The "save=nooutput" totally makes the trick of no signal at all being written to the "tran.tran.tran.dat" file! :)

    Now, that being solved, my simulation run directories are still considerably big due to 2 files in the netlist directory : "input.scs" and "netlist" (~50MB each). Is there an easy way to tell ADE-XL to delete these after the run is complete? Maybe with a SKILL procedure installed as a post-simulation trigger somehow?

    Thanks so much again for your help!
    Cheers,
    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.