RunSIMPLIS Command

Runs the SIMPLIS simulator. Note that you must have a SIMetrix/SIMPLIS license for this command to work.

The RunSIMPLIS command will not pre-process the netlist. This must be done separately using the PreProcessNetlist command.

RunSIMPLIS [/fresh] [/append] [/label division-label] [/sweep start|continue|finish] [/checkAbort] filename

Parameters

/append	Append data to current group. Otherwise creates a new data group.
/checkAbort	Instructs SIMPLIS to check abort requests.
/fresh	Instructs SIMPLIS to run simulation afresh and not to use any state information saved from previous runs.
/label	Used with `/sweep` to name the division of a linked run
/noHistory	Disables fixed probe history feature. Equivalent to adding separateCurves=true to the .GRAPH statement
/sweep	Used for multi-step runs. See Run command above for details.
/sweeptype	Affects the format of multi-division plots in linked simulations. Use stepped for multi-step parametric runs or stat for Monte-Carlo runs. 'stepped' will list each step in the legend window and set each curve to a different colour. 'stat' will show only a single curve legend and any measurements will create statistical values.

Notes

RunSIMPLIS is the primitive SIMetrix command that launches SIMPLIS. However, when running a simulation on a schematic, a number of other activities are performed. These include pre-processing the netlist generated by the schematic editor and also resolving a trigger device for POP analysis. If you wish to simulate a schematic in exactly the same manner as the Run menu, you need to execute the script simplis_run. This simulates the currently open schematic. The full source for simplis_run can be found in the built-in scripts zip files available from https://www.simetrix.co.uk/app/supplementary-files.htm. Linking Runs The data from multiple runs may be linked together in the same manner as multi-step runs such as Monte Carlo. This makes it possible to develop customised multi-step runs using the script language. Simple multi-step runs may be defined using the simulator's built in features which cover a wide range of applications. The simulator's multi-step features allow the stepping of a single component or a parameter which can define several components. But it doesn't allow, for example, a complete model to be changed, or any kind of topological changes. The script language may be used to control multiple runs of a circuit with no limit as to the changes that may be performed between each run. In such situations it is useful to be able to organise the data in the same way that the native multi-step facilities use. This can be done by linking runs. By running simulations in this manner, the data generated by the simulator will be organised using multi-division vectors which are similar to 2 dimensional arrays. Care must be taken when making topological changes between runs. Names of nodes that are of interest must always be preserved otherwise the data generated for their voltage may be lost of mixed up with other nodes. Note also that the data for new nodes created since the first run will not be available. The same problems arise for device pin currents. Note that this method can only be used for transient analyses or single POP analyses as the method only supports joining data from single data groups. AC analyses for example generate data groups for both POP and AC. Linked Run Example

unselect
Select /prop REF R1
Prop value 2k

netlist /simplis design.net
PreProcessNetlist design.net design.deck

runsimplis  /label "R1=2K" /sweep start /sweeptype stepped design.deck

unselect
Select /prop REF R1
Prop value 5k

netlist /simplis design.net
PreProcessNetlist design.net design.deck

runsimplis /label "R1=5K" /sweep continue /sweeptype stepped design.deck

unselect
Select /prop REF R1
Prop value 10k

netlist /simplis design.net
PreProcessNetlist design.net design.deck

runsimplis /label "R1=10K" /sweep finish /sweeptype stepped design.deck

▲ Command Summary ▲
◄ RunCurrentScript		Save ▶