1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
Notes on output files from Berkeley Spice 3F5.
Ran spice3 -b <deck> -r <rawfile>
Rawfile contains:
Title: Basic RC circuit
Date: Tue Sep 15 11:35:58 1998
Plotname: Transient Analysis
Flags: real
No. Variables: 4
No. Points: 66
Command: version 3f5
Variables:
0 time time
1 V(1) voltage
2 V(2) voltage
3 vin#branch current
Binary:
<binary data - 2112 bytes>
Looks like the data is native-format doubles, No.varibles * No.points of them.
This doesn't quite seem to match any of the descriptions of file formats in
the sconvert(1) man page.
It appears to be what's written by the routines in
spice3f5/src/lib/fte/rawfile.c, however. This example is pretty
simple, but there are a bunch of options in the "flags:" line that can
affect what's in the data portion. In particular, values can be
complex instead of real, and there's an "unpadded" option that means not to
put 0's at the end of columns that contain fewer values than the others.
If things are unpadded, there is apparently some additional
per-variable indication of length.
The full generality of this appears tied up in all of nutmeg's
functionality, but the basic spice-output case may be pretty simple.
|
