1NGSPICE(1) General Commands Manual NGSPICE(1)
2
6 ngspice - circuit simulator derived from SPICE3f5
7
9 ngspice [options] [file ...]
10
12 This man page is just a small overview. The primary documentation of
13 ngspice is in the ngspice User's Manual, which is available as a pdf
14 file.
15
17 -n or --no-spiceinit
18 Don't try to source the file ".spiceinit" upon startup. Normally
19 ngspice tries to find the file in the current directory, and if
20 it is not found then in the user's home directory.
21 -q or --completion
23 Enable command completion. (defect)
24 -t term or --term=term
26 The program is being run on a terminal with mfb name term.
27 -b or --batch
29 Run in batch mode. ngspice will read the standard input or the
30 specified input file and do the simulation. Note that if the
31 standard input is not a terminal, ngspice will default to batch
32 mode, unless the -i flag is given.
33 -s or --server
35 Run in server mode. This is like batch mode, except that a tem‐
36 porary rawfile is used and then written to the standard output,
37 preceded by a line with a single "@", after the simulation is
38 done. This mode is used by the ngspice daemon.
39 -i or --interactive
41 Run in interactive mode. This is useful if the standard input
42 is not a terminal but interactive mode is desired. Command com‐
43 pletion is not available unless the standard input is a termi‐
44 nal, however.
45 -r rawfile or --rawfile=file
47 Use rawfile as the default file into which the results of the
48 simulation are saved.
49 -c circuitfile or --circuitfile=circuitfile
51 Use circuitfile as the default input deck.
52 -h or --help
54 Display a verbose help on the arguments available to the pro‐
55 gram.
56 -v or --version
58 Display a version number and copyright information of the pro‐
59 gram.
60 -a or --autorun
62 FIXME
63 -o outfile or --output=outfile
65 All logs generated during a batch run (-b) will be saved in out‐
66 file.
67 -p or --pipe
69 Allow a program (e.g., xcircuit) to act as a GUI frontend for
70 ngspice through a pipe. Thus ngspice will assume that the pipe
71 is a tty and allows one to run in interactive mode.
72 Further arguments are taken to be SPICE input decks, which are read and
74 saved. (If batch mode is requested then they are run immediately.)
75
77 SPICE_LIB_DIR
78 SPICE_EXEC_DIR
80 SPICE_HOST
82 SPICE_BUGADDR
84 SPICE_EDITOR
86 SPICE_ASCIIRAWFILE default 0
88 Format of the rawfile. 0 for binary, and 1 for ascii.
89 SPICE_NEWS default $SPICE_LIB_DIR/news
91 A file which is copied verbatim to stdout when ngspice starts in
92 interactive mode.
93 SPICE_MFBCAP default $SPICE_LIB_DIR/mfbcap
95 SPICE_HELP_DIR default $SPICE_LIB_DIR/helpdir
97 SPICE_SCRIPTS default $SPICE_LIB_DIR/scripts
99 In this directory the spinit file will be searched.
100 SPICE_PATH default $SPICE_EXEC_DIR/ngspice
102 various undocumented ngspice centric environment variables :
104 NGSPICE_MEAS_PRECISION
106 SPICE_NO_DATASEG_CHECK
108 Common environment variables :
110 TERM LINES COLS DISPLAY HOME PATH EDITOR SHELL
112 POSIXLY_CORRECT
114
116 $SPICE_LIB_DIR/scripts/spinit
117 The System's Initialisation File.
118 .spiceinit or $HOME/.spiceinit
120 The User's Initialisation File.
121
123 sconvert(1), ngnutmeg(1), mfb(3), writedata(3), and
124 ngspice User's Manual at http://ngspice.sourceforge.net/docs.html
125
127 Please report bugs to the ngspice project via
128 http://ngspice.sourceforge.net/bugrep.html
129
131 spice3: Tom Quarles (quarles@cad.berkeley.edu)
132 nutmeg: User interface: Wayne Christopher (faustus@cad.berkeley.edu)
133 ngspice: various authors (see http://sourceforge.net/projects/ngspice/)
134 2014-10-28 NGSPICE(1)