docs/wiki/geda-ngsconvert_mp.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html>
   4 <head>
   5   <link rel="stylesheet" media="screen" type="text/css" href="./style.css" />
   6   <link rel="stylesheet" media="screen" type="text/css" href="./design.css" />
   7   <link rel="stylesheet" media="print" type="text/css" href="./print.css" />
   8
   9   <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
  10 </head>
  11 <body>
  12
  13 <h1 class="sectionedit1" id="ngsconvert_man-page">ngsconvert man-page</h1>
  14 <div class="level1">
  15 <pre class="code">SCONVERT(1)                                                      SCONVERT(1)
  16
  17
  18
  19 NAME
  20        sconvert - convert spice formats
  21
  22 SYNOPSIS
  23        sconvert fromtype fromfile totype tofile
  24        sconvert fromtype totype
  25        sconvert
  26
  27 DESCRIPTION
  28        Sconvert  translates  spice  output  files among three formats: the old
  29        binary format, a new binary format, and a new ascii format.   The  for-
  30        mats  are  specified  by the fromtype and totype arguments: â€˜oâ€™ for the
  31        old format, â€˜bâ€™ for the new binary format, and â€˜aâ€™ for  the  new        ascii
  32        format.  Fromtype specifies the format to be read, and totype specifies
  33        the format to be written.  If fromfile and tofile are given, then  they
  34        are  used  as the input and output, otherwise standard input and output
  35        are used.  (Note that this second option is only available on UNIX sys-
  36        tems  - on VMS and other systems you must supply the filenames.)  If no
  37        arguments are given, the parameters are prompted for.
  38
  39        Binary format is the preferred format for general use,  as  it  is  the
  40        most  economical  in  terms  of space and speed of access, and ascii is
  41        provided to make it easy to modify data files and transfer them between
  42        machines with different floating-point formats.  The old format is pro-
  43        vided only for backward compatibility. The three formats  are  as  fol-
  44        lows:
  45
  46        Old:
  47
  48                 What          Size in Bytes
  49
  50             title                    80
  51             date                8
  52             time                8
  53             numoutputs               2
  54             the integer 4            2
  55             variable names --
  56                  char[numoutputs][8] numoutputs * 8
  57             types of output               numoutputs * 2
  58             node index               numoutputs * 2
  59             plot title               numoutputs * 24
  60             the actual data               numpoints * numoutputs * 8
  61
  62        Ascii:
  63
  64             Title: Title Card String
  65             Date: Date
  66             [ Plotname: Plot Name
  67               Flags: complex or real
  68               No. Variables: numoutputs
  69               No. Points: numpoints
  70               Command: nutmeg command
  71               Variables:   0 varname1 typename1
  72                       1 varname2 typename2
  73                       etc...
  74               Values:
  75                 0     n    n    n    n    ...
  76                 1     n    n    n    n    ...
  77                 And so forth...
  78             ] repeated one or more times
  79
  80
  81        If one of the flags is complex, the points look like r,i where r and i
  82        are floating point (in %e format). Otherwise they are in %e format.
  83        Only one of real and complex should appear.
  84
  85        The lines are guaranteed to be less than 80 columns wide (unless the
  86        plot title or variable names are very long), so this format is safe
  87        to mail between systems like CMS.
  88
  89        Any number of Command: lines may appear between the No. Points:
  90        and the Variables: lines, and whenever the plot is loaded into
  91        nutmeg they will be executed.
  92
  93        Binary:
  94
  95             Title Card            (a NULL terminated string)
  96             Date, Time            (a NULL terminated string)
  97             [
  98               Plot title          (a NULL terminated string)
  99               Number of variables   (an int)
 100               Number of data points (an int)
 101               flags          (a short)
 102               variable header struct (repeated numoutputs times)
 103                  variable name    (a NULL terminated string)
 104                  variable type    (an int)
 105               set of outputs      (repeated numpoints times)
 106             ] repeated one or more times.
 107
 108
 109        A set of outputs is a vector of doubles of length numoutputs, or
 110        a vector of real-imaginary pairs of doubles if the data is complex.
 111
 112 SEE ALSO
 113        nutmeg(1), spice(1), writedata(3)
 114
 115 AUTHOR
 116        Wayne Christopher (faustus@cad.berkeley.edu)
 117
 118 BUGS
 119        If  variable  names  and  the  title and plotname strings have trailing
 120        blanks in them they will be stripped off when the file is read,  if  it
 121        is in ascii format.
 122
 123        If  a plot title begins with &quot;Title:&quot; nutmeg will be fooled into think-
 124        ing that this is an ascii format file.  Sconvert  always  requires  the
 125        type to be specified, however.
 126
 127
 128
 129
 130 4th Berkeley Distribution        20 March 1986                     SCONVERT(1)</pre>
 131
 132 </div>
 133 </body>
 134 </html>