1 <!DOCTYPE html PUBLIC
"-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
6 <link rel=
"stylesheet" media=
"screen" type=
"text/css" href=
"./style.css" />
7 <link rel=
"stylesheet" media=
"screen" type=
"text/css" href=
"./design.css" />
8 <link rel=
"stylesheet" media=
"print" type=
"text/css" href=
"./print.css" />
10 <meta http-equiv=
"Content-Type" content=
"text/html; charset=utf-8" />
15 <h1 class=
"sectionedit275"><a name=
"ngsconvert_man-page" id=
"ngsconvert_man-page">ngsconvert man-page
</a></h1>
17 <pre class=
"code">SCONVERT(
1) SCONVERT(
1)
22 sconvert - convert spice formats
25 sconvert fromtype fromfile totype tofile
26 sconvert fromtype totype
30 Sconvert translates spice output files among three formats: the old
31 binary format, a new binary format, and a new ascii format. The for-
32 mats are specified by the fromtype and totype arguments: ‘o’ for the
33 old format, ‘b’ for the new binary format, and ‘a’ for the new ascii
34 format. Fromtype specifies the format to be read, and totype specifies
35 the format to be written. If fromfile and tofile are given, then they
36 are used as the input and output, otherwise standard input and output
37 are used. (Note that this second option is only available on UNIX sys-
38 tems - on VMS and other systems you must supply the filenames.) If no
39 arguments are given, the parameters are prompted for.
41 Binary format is the preferred format for general use, as it is the
42 most economical in terms of space and speed of access, and ascii is
43 provided to make it easy to modify data files and transfer them between
44 machines with different floating-point formats. The old format is pro-
45 vided only for backward compatibility. The three formats are as fol-
58 char[numoutputs][
8] numoutputs *
8
59 types of output numoutputs *
2
60 node index numoutputs *
2
61 plot title numoutputs *
24
62 the actual data numpoints * numoutputs *
8
66 Title: Title Card String
69 Flags: complex or real
70 No. Variables: numoutputs
72 Command: nutmeg command
73 Variables:
0 varname1 typename1
80 ] repeated one or more times
83 If one of the flags is complex, the points look like r,i where r and i
84 are floating point (in %e format). Otherwise they are in %e format.
85 Only one of real and complex should appear.
87 The lines are guaranteed to be less than
80 columns wide (unless the
88 plot title or variable names are very long), so this format is safe
89 to mail between systems like CMS.
91 Any number of Command: lines may appear between the No. Points:
92 and the Variables: lines, and whenever the plot is loaded into
93 nutmeg they will be executed.
97 Title Card (a NULL terminated string)
98 Date, Time (a NULL terminated string)
100 Plot title (a NULL terminated string)
101 Number of variables (an int)
102 Number of data points (an int)
104 variable header struct (repeated numoutputs times)
105 variable name (a NULL terminated string)
106 variable type (an int)
107 set of outputs (repeated numpoints times)
108 ] repeated one or more times.
111 A set of outputs is a vector of doubles of length numoutputs, or
112 a vector of real-imaginary pairs of doubles if the data is complex.
115 nutmeg(
1), spice(
1), writedata(
3)
118 Wayne Christopher (faustus@cad.berkeley.edu)
121 If variable names and the title and plotname strings have trailing
122 blanks in them they will be stripped off when the file is read, if it
125 If a plot title begins with
"Title:
" nutmeg will be fooled into think-
126 ing that this is an ascii format file. Sconvert always requires the
127 type to be specified, however.
132 4th Berkeley Distribution
20 March
1986 SCONVERT(
1)
</pre>