HTML automatically generated with rman
Table of Contents


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


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

When installed, ZENO adds about 130 executables via $ZENOPATH/bin. Within NEMO, a user would source the $NEMO/usr/zeno/ script.


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 p16k
    % snapcopy p16k - | 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

As highlighted in the example, 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’s potential(5NEMO) are similar to ZENO’s gspmodels, where the latter also allows for adding potentials (much harder in NEMO). falcON has similar tools to add potentials.

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/usr/zeno            directory, with instructions how to install
$NEMO/usr/zeno/    startup script

See Also



Josh Barnes

Further Information

Table of Contents