This HTML automatically generated with rman for NEMO
Table of Contents


program [key1=]val1 [key2=]val2 .!.!.
program --help.


ZENO is Josh Barnes’ version of NEMO. The code is derived from NEMO, with a common ancestor around 1988. The binary datafiles, via filestruct(3NEMO) are largely compatible.

When installed, ZENO adds well over 100 executables via $ZENOPATH/bin, but some have the same name as NEMO’s counterpart. See EXAMPLES below how to add ZENO to your NEMO environment. See zeno(8NEMO) for a list of all programs


From within NEMO the following command should load ZENO:
   source $NEMO/usr/zeno/
but note this may shield likewise named executables of NEMO.

A snapshot(5NEMO) created with ZENO has Position and Velocity, as well as using NBody instead of Nobj. It can be converted to NEMO’s PhaseSpace with e.g. snapcopy(1NEMO) , and then processed like NEMO snapshots. E.g.:

    % plumsnap - | snapcopy -  - | snapplot -
The magic of this ZENO detection is in get_snap.c, and programs (such as snapplot) that use older direct reading of snapshots will not be able to process these snapshots with such a filter.

Differences with Nemo

A ZENO snapshot uses NBody instead of NEMO’s Nobj, but as get as snapshot I/O is done via the get_snap macros, they will be converted. NEMO uses PhaseSpace whereas ZENO uses separate Position and Velocity.

NEMO has no real support for SPH (though some tags in snapshot’s are supported)

ZENO has no plotting such as NEMO’s yapp

NEMO’s command line userface is a bit more richer


$NEMO/usr/zeno            directory, with instructions how to install
$NEMO/usr/zeno/zeno        symlink to the actual location of ZENO
$NEMO/usr/zeno/    startup script

See Also

nemo(1NEMO) , zeno(8NEMO)


Josh Barnes

Further Information

Table of Contents