So I'm running cadence 6.1.3 and I'm trying to do an APS simulation. I found that if I do a saveOption('save "all"), it wouldn't save all. In fact it would randomly throw away nodes that should have been saved (i.e. nodes with two end points connected to transistors).
So, I switched to save selected.
I wrote a small script to generate the save script to save a bunch of nodes and pasted the result into my ocean script. This ended up being ~ 100+ signals in a save statement.
Now, when I try launching the simulation it takes MUCH longer to start as it's spending a long time parsing the save statements.
Is this what other people are seing? Does the save command really only work well with just a few nodes?
I wouldn't expect this; it should not present any kind of noticeable slow down to have a large number of explictly saved nodes (unless the list is really huge, maybe).
Please can you file a service request with customer support so this can be investigated in more detail, and if something needs fixing, it can be fixed.
In reply to Andrew Beckett:
I am not seeing this in 5.1.41, but only in 6.1.3.
Created SR: 41815744
In reply to markbeck:
Try using a single save statement. In Spectre syntax it's:
In reply to Samir Jafferali:
I failed to try the most basic 'fix'... shutdown for the weekend, restart on Monday. The problem seems to have magically disappeared.
As for the "save *", I've found that it doesn't work for APS hence the reason for explicitly declaring each and every net.