Re: [ng-spice-devel] Temperature and other options


To ng-spice-devel@ieee.ing.uniroma1.it
From Steve Hamm <Steve.Hamm@motorola.com>
Date Fri, 16 Feb 2001 10:28:43 -0600 (CST)
Delivered-To mailing list ng-spice-devel@ieee.ing.uniroma1.it
In-Reply-To <Pine.LNX.3.96.1010215150741.21931C-100000@ieee.ing.uniroma1.it >
Mailing-List contact ng-spice-devel-help@ieee.ing.uniroma1.it; run by ezmlm
References <Pine.LNX.3.96.1010215150741.21931C-100000@ieee.ing.uniroma1.it >
Reply-To ng-spice-devel@ieee.ing.uniroma1.it


For what it's worth:

We decided to sort out this mess as follows, which kind of makes sense 
in the spice3 context. I'm not sure I would do it the same way today,
but here is how we handled this:

.option values come and go with the netlist -- since the .option
statement is part of the netlist. Source a new netlist or do a setcirc 
to a previously sourced netlist and the .option values switch to those 
associated with the that netlist.

However, option values changed with "set" always override values on
.option statements, and are persistent across netlists. So, "set
reltol=1e-4" would apply to all simulations until "unset reltol" is
done. This is somewhat dangerous for the unwary, but easy to explain
and consistent with other things in the command line interface. This
can also be helped by telling the user the values used for various
options of importance for the analysis.

There are obviously other ways of approaching the problem...

--Steve

Partial thread listing: