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