spectre : plotting device parameters

If you know what model it is, you can see the available outputs - see "spectre -h bsim4" for example, and in the section labelled "Operating Point Parameters" you'll see them listed. With spectre, it would be "ids" not "IDS" - so :

save xlx5.MN9.MN:ids

Or to save all operating point outputs, use:

save xlx5.MN9.MN:oppoint

You can also save using wildcards:

save *:oppoint sigtype=dev

(saves operating point data for all devices - you might want to be more selective so you don't create quite so much).

See "spectre -h save" for more details too.

Regards,

Andrew.

Thank you!

Is there a reason this would not work :

I put 

save xlx5.MN9.MN:ids

and run the simulation using the runSimulation script that ADE creates.

When I reload or Open Results from my viva, I don't get ids.

The only way I'm able to get it is by doing an include file approach..

The right way to do this would always be to create an include file and reference it from Setup->Model Libraries.

You say "I put save..." - you didn't say where you it it. Where did you put it?

Note that the runSimulation script is not intended to be run by users - often it has options in there (such as +inter=mpsc) which mean that it will only work properly if ADE has launched it - because it expects to be controlled by ADE.

Andrew

Hmm... that's good to know. IC5 was convenient that way - you could ssh to a server and launch the sim using ./runSimulation. Never had a problem.

I was putting the save at the very end of the input.scs

This is no different between IC5 and IC6 - it's always been this way. 

Provided that the simulation is being run in "batch" mode (i.e. there are no arguments mentioning mps in the runSimulation script) you can get away with running it this way, because it's essentially the same as what ADE is doing. You might need to do Results->Select in ADE so that it knows the results have changed before you bring up the results browser (this is the same in IC5 and IC6 too).

Andrew.

The advantage of using the Setup->Model Libraries approach is that it will be persistent - if you edit the input.scs and run the simulation by hand, next time you hit the run button in ADE, it will overwrite the input.scs and won't do your manual edit...

Andrew.

Turned out that the problem was due to putting my save right at the very end - If I put it after the existing save, before the saveOptions, then it works okay.

 NOT OK :

save whateverr

saveOptions options save=allpub

save xlx5.MN9.MN:ids

EOF

OK :

save whatever

save xlx5.MN9.MN:ids

saveOptions options save=allpub

EOF