A NEMO N-body snapshot is stored in a type of hierarchically structured (binary) format, something we refer to as snapshot(5NEMO) . Once generated, a program called tsf(1NEMO) displays the contents of such a file in human readable format. For example: 
% mkplummer out=p100 nbody=100
% hackcode1 p100 p100.out tstop=1 freqout=1 minor_freqout=1
% tsf p100.out 
char Headline[33] "set_xrandom: seed used 785115319"
char History[70] "hackcode1 p100 p100.out tstop=1 freqout=1 minor_freqo
  ut=1 VERSION=1.3"
char History[32] "mkplummer p100 100 VERSION=2.5a"
set SnapShot
  set Parameters
    int Nobj 0144 
    double Time 0.00000 
  tes
  set Particles
    int CoordSystem 0201402 
    double Mass[100] 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      . . .
    double PhaseSpace[100][2][3] 2.92755 -0.0144016 0.518072 0.189891 
      0.176455 0.00700346 -0.223636 -0.165417 0.0867212 0.335269 
      -1.01872 0.423232 -0.0160384 -0.224425 -0.191900 -0.855766 
      0.602218 0.829114 -0.258040 -0.0684037 -0.355246 -1.03564 
      . . .
  tes
  set Diagnostics
    double Energy[3] -0.220211 0.267903 -0.488114 
    double KETensor[3][3] 0.104253 -0.00950930 -0.00971601 -0.00950930 
      0.0864617 0.0106677 -0.00971601 0.0106677 0.0771882 
    double PETensor[3][3] -0.158499 -0.00928755 0.0151406 -0.00856445 
      -0.170975 0.00113292 0.0156464 -2.08423e-05 -0.144504 
    double AMTensor[3][3] 0.00000 0.0181900 -0.0686400 -0.0181900 
      0.00000 0.0154333 0.0686400 -0.0154333 0.00000 
    double CMPhaseSpace[2][3] 2.60209e-17 -8.50015e-17 -3.57787e-17 
      -1.73472e-17 -1.56125e-17 5.63785e-18 
    double cputime 0.00166667 
  tes
tes
set SnapShot
  set Parameters
    int Nobj 0144 
    double Time 1.00000 
  tes
  set Particles
    int CoordSystem 0201402 
    double Mass[100] 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 0.0100000 
      . . .
    double PhaseSpace[100][2][3] 3.07151 0.162005 0.512921 0.0989014 
      0.175136 -0.0166633 0.306874 -0.801018 0.228809 0.449163 
      -0.360232 0.156949 -0.625397 0.514803 0.494536 -0.263653 
      0.587491 0.373807 -0.823002 -0.0750948 0.407099 -0.112537 
      . . .
  tes
  set Diagnostics
    double Energy[3] -0.219507 0.253757 -0.473264 
    double KETensor[3][3] 0.0817022 0.00880759 -0.0197782 0.00880759 
      0.0843517 -0.00376696 -0.0197782 -0.00376696 0.0877030 
    double PETensor[3][3] -0.168001 0.00498722 0.00852368 0.00543992 
      -0.158295 -0.0117678 0.00813333 -0.00834957 -0.135714 
    double AMTensor[3][3] 0.00000 0.0183290 -0.0689624 -0.0183290 
      0.00000 0.0155440 0.0689624 -0.0155440 0.00000 
    double CMPhaseSpace[2][3] -0.000792582 0.000699400 -0.000711580 
      -0.00195073 0.00125384 -0.00131546 
    double cputime 0.0513889 
  tes
tes
As you can see, two snapshots are stored in this dataset, with some associated diagnostics. A corresponding program rsf(1NEMO) can read this human readable output, and convert it back into binary format.

Here are some sample data of the above file p100.out in a few formats that I could write in NEMO. Depending on your WWW browser, you may have to load them to local disk through an option: (Options/Load To Local Disk, in Mosaic)

Last updated on 23-dec-94 by PJT.
teuben@astro.umd.edu