This section describes how to use standard input files.
The design name identifies the circuit and any related files, including schematic and netlist files, simulator input and output files, design configuration files and hardcopy files. Both Star-Hspice and AvanWaves extract the design name from their input files and perform subsequent actions based on that name. For example, AvanWaves reads the <design>.cfg configuration file to restore node setups used in previous AvanWaves runs.
Both Star-Hspice and AvanWaves read and write files related to the current circuit design. All files related to a design generally reside in one directory, although the output file is standard output on UNIX platforms and can be redirected.
Star-Hspice input file types and their standard names are listed in Star-Hspice Input Files. These files are described in the following sections.
This file sets up the printer, plotter, and terminal. It includes a line, default_include = file name , which sets up a path to the default .ini file (hspice.ini, for example).
The default_include file name is case sensitive (except for the PC and Windows versions of Star-Hspice).
User defaults are specified in an hspice.ini initialization file. If an hspice.ini file exists in the run directory, Star-Hspice includes its contents at the top of the Star-Hspice input file.
Other ways to include initialization files are to define "DEFAULT_INCLUDE = <filename>" in the system or in a meta.cfg file.
Typical uses of an initialization file are to set options (with an .OPTIONS statement) and for library access, as is done in the Avant! installation procedure.
The <design>.ic file is an optional input file that contains initial DC conditions for particular nodes. You can use it to initialize DC conditions, with either a . NODESET or an .IC statement.
The .SAVE statement creates a <design>.ic file. A subsequent .LOAD statement initializes the circuit to the DC operating point values in the <design>.ic file.
Star-Hspice Manual - Release 2001.2 - June 2001