HTML automatically generated with rman
Table of Contents
keywords - list of standard keywords in NEMO.
Some keywords
in NEMO have a ‘‘reserved’’ meaning. Thus, if the meaning of a desired keyword
can be found in the description below, you should use that keyword given
with that description. They often come with associated subroutines which
aid in parsing, making it’s parsing (and error messages) even more uniform
to users. It significantly eases the pain of users if keywords are used
consistently. Also, parsing rules should be the same. For example xrange
always has two numbers, separated with a :, although it could also use
:max or min:, where in these cased 0 is meant for the number not specified.
The ? in the keywords below denotes any character, e.g. xrange and yrange
both apply to the comments under
Keywords
- in
- Any input file (snapshot,
image, table, orbit, fits)
- out
- Any output file, though not necessarely
the same as the in= format if used in the same program. Conversion programs
are notorious for this.
- times
- Selection of times: all or t1:t2,t3,..., frequently
used in snapshots (and orbits?). Note that this keyword is the one where
the nemoinp parsing rules do not apply.
- ?range
- Two numbers, separated by
a colon, to select a min and max x1:x2 {x,y,z,}
- ?var
- Expression (normally
used in bodytrans variables) {x,y,z,e,f,}
- ?col
- Columns {x,y}
- ?label
- Labels
with a graph {x,y}
- n?ticks
- Number of tickmarks an on axis in a graph {x,y}
- ?box
- Location of a box on graph. Two numbers, separated by a colon. The location
is in yapp units, i.e. cm, ranging from 0 to 20 on a full plot. {x,y}
- ?ticks
- Tickmark values, that belong to an axis. By default the number of tickmarks
(n?ticks and their range (?range) will determine the tickmark values, but
the user can also supply his own array. It must be a comma separated array,
normal nemoinp parsing rules apply. {x,y}.
- nsigma
- Rejection level of of
points from a distribution where points that are outside nsigma times the
current sigma from the mean. Often sigma is recomputed after a point has
been rejected, since they tend to bias the computation of sigma.
- visib
- Visibility
of points, used in snapplot and clones. Must evaluate as an integer, 0 meaning
no visible, anything else is.
- headline
- Random verbiage, often added to a
datafile, or labeling graphs.
- seed
- Random number seed. If 0 is used, the
time of the day is used as seed. Most programs should use 0 is the default.
- potname
- Name of a potential(5NEMO)
descriptor; normally required, rarely
a default is given.
- potpars
- Parameters of a potential(5NEMO)
descriptor;
The first one is always the pattern speed. Defaults depend on potname=.
- potfile
- Optional datafiles belonging to a potential(5NEMO)
descriptor. If it’s used
or if a default is allows, depends on potname=.
- nbody
- Number of bodies used
in nbody creators. Some ancient programs will use ndisk=.
- eps
- Gravitational
softening length, in the usual meaning (1/sqrt(r^2 + eps^2)).
- freq
- (Integration)
frequency, 1/t
- tstop
- Final time of integration.
- options
- Selections of options,
minimum match should be applied here. Options are separated by comma’s.
The
following example extracts a list of all used keywords used in NEMO, assuming
the $MIRPDOC database is up to date.
grep %A $NEMODOC/*.doc | awk ’{print $2}’ | sort | uniq -c | more
and sorted by frequency
grep %A $NEMODOC/*.doc | awk ’{print $2}’ | sort | uniq -c | sort -nr | more
getparam(3NEMO)
, nemoinp(3NEMO)
Peter Teuben
program.def keyword database used in advanced help=
12-jun-92 document created PJT
14-nov-93 minor updates PJT
7-jun-01 more keywords PJT
Table of Contents