HTML automatically generated with rman
Table of Contents
xvpsnap - convert xvp NBODY files to snapshot format files
xvpsnap
in=xvp_fiiile [parameter=value] ...
xvpsnap converts (fortran)
direct access files in Quinn/Balcells format (see also rvp(5NEMO)
) to standard
snapshot(5NEMO)
format. Some control exists over which snapshots are extracted
from the input file.
Currently the user must know if the input xvp file
is in single or double precision (native floating point) format. The output
file will be in single precision snapshot format.
The following
parameters are recognized in any order if the keyword is also given:
- in=
- Input xyp(5NEMO)
file. No default.
- out=
- Output snapshot(5NEMO)
file. If none
given, the program will automatically operate in scan-mode and report all
selected (see model= and times= below) snapshots. Default:
- times=t1[:t2],...
- Select by time ranges. *** not implemented yet ***
- model=
- Select by model
numbers (0=all, 1=first). Any nemoinp(3NEMO)
expression can be given. [Default:
0 (all)].
- headline=
- Random verbiage added to the history of the output file.
- nbody=
- Maximum number of bodies allowed for memory allocation. By default,
the xvp input file will be scanned to retrieve the correct number of bodies.
By using this keyword, this scan will be skipped. In this case any too small
number will cause unpredictable results.
- nobytes=4|8
- Number of bytes per
floating point number in the xvp input data. Valid numbers are 4 (single
precision) and 8 (double precision) files. Note: There is no way, other
than trial and error, for the user to find out if a dataset of unknown
content is in single or double precision. Default: 4.
xvp(5NEMO)
files
that consist of multiple snapshots must all be equally sized.
xvp(5NEMO)
,
tabtos(1NEMO)
, atos(1NEMO)
, rvc(1NEMO)
, snapshot(5NEMO)
~/usr/balcells/nora/{xvpread.f,xvprd8.f} I/O routines for library
~/src/nbody/io/xvpsnap.c this program
Peter Teuben
30-May-94 V1.0 Created PJT
Table of Contents