Manuals >Reference >Saber Simulator
Print version of this Book (PDF file) 		prevnext

Piped and Non-Piped Saber Simulations

Non-piped Saber simulations are identical to non-piped SPICE simulations. However, there are differences between the 2 types of piped simulation. A piped simulation in Saber does the following:

  1   Read the input deck from a file upon start up of the simulator

  2   Read in the analysis commands from a pipe connected to standard input

  3   Perform the simulation

  4   Send the text output to a pipe connected to standard output

  5   Save the output data to files

Saber is restarted if any topological changes are made to the circuit description. If changes are made which do not affect the topology of the circuit, such as changed parameter values, then alter commands are used and the simulator is not restarted.

Note


The path of the AIM shell interpreter (aimsh) must be specified in usersimulators. IC-CAP uses this utility from the saber installation to interpret the simulation results and read them into IC-CAP. (AIM is a high-level, embedded scripting language that controls and manages user input and other kinds of analyses and processes in SaberDesigner applications.) The default saber specification in $ICCAP_ROOT\iccap\lib\usersimulators is as follows: 

 saber saber $SABER_HOME/bin/saber "" CAN_PIPE "" 
$SABER_HOME/bin/aimsh

Therefore, no modifications to usersimulators are required if SABER_HOME is properly set in your environment before launching IC-CAP.

Syntax: Non-Piped simulations

This section describes the argument syntax required to invoke the template simulator. This information is needed when writing the user translation module, since these are the arguments supplied by IC-CAP when it calls the translation module. For information on the translation module and adding a simulator, refer to "Adding a Simulator" in the User's Guide.

The command format for a Saber non-piped simulation is as follows: 

 saber -b deckfile

where:

-b specifies batch mode.

deckfile is the input file name. Saber will read deckfile as the input deck file containing the circuit description and deckfile as the command file containing the analysis statements.

The textfile is written to a file called deckfile.out.

The rawfile information is written to 2 files, called the control file and the data file. The control file is named deckfile.p1.suffix and the data file is named deckfile.p2.suffix where suffix is a keyword assigned by Saber according to the analysis being performed. Refer to the Saber User's Manual for more information.

Syntax: Piped simulations

The command format for a Saber piped simulation is as follows: 

 saber -c deckfile

where:

-c specifies the Saber command mode.

deckfile is the input deck file containing the circuit description.

Saber reads the analysis commands through standard input.

The textfile is written to a file called <deckfile>.out.

The rawfile is written to a file called <deckfile>.p1.<suffix> where suffix is a keyword assigned by Saber according to the analysis being performed. Refer to the Saber User's Manual for more information.

prevnext