diff --git a/doc/partiview-1.html b/doc/partiview-1.html
index c7cb957ddfa6917df6538ea7dd332e6f7120fbec..fdcc4988b60a4e916902e7d13fca3925a760085b 100644
--- a/doc/partiview-1.html
+++ b/doc/partiview-1.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Installation</TITLE>
<LINK HREF="partiview-2.html" REL=next>
diff --git a/doc/partiview-2.html b/doc/partiview-2.html
index 893b8709cd1d1cde206a4b2bc1756510c82697bb..da2ea942c0ce12b707eafbf31c5248a7b6172777 100644
--- a/doc/partiview-2.html
+++ b/doc/partiview-2.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Directory structure</TITLE>
<LINK HREF="partiview-3.html" REL=next>
<LINK HREF="partiview-1.html" REL=previous>
diff --git a/doc/partiview-3.html b/doc/partiview-3.html
index 1f9e3f8115741800162beeb4649455a1694af679..9b555e08b1974d04ae068e84ce1876d1babc8912 100644
--- a/doc/partiview-3.html
+++ b/doc/partiview-3.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Running the program</TITLE>
<LINK HREF="partiview-4.html" REL=next>
<LINK HREF="partiview-2.html" REL=previous>
@@ -137,33 +137,43 @@ From left to right, it should show the following buttons:</P>
<P>
<DL>
-<DT><B> More </B><DD><P>Offers some mode switches as toggles: <CODE>inertia</CODE>
+<DT><B> More </B><DD>
+<P>Offers some mode switches as toggles: <CODE>inertia</CODE>
for continues spin or motion,
and an <CODE>H-R Diagram</CODE> to invoke a separate H-R diagram window
for datasets that support stellar evolution.</P>
-<DT><B> [g1] </B><DD><P>Pulldown g1, g2, ... (or whichever group)
+<DT><B> [g1] </B><DD>
+<P>Pulldown g1, g2, ... (or whichever group)
is the currently selected group. See <CODE>object</CODE> command
to make aliases which group is defined to what object. If multiple
groups are defined, the next row below this contains a list of all
the groups, and their aliases, so you can toggle them to be displayed.</P>
-<DT><B> [f]ly </B><DD><P>Pulldown to select fly/orbit/rot/tran, which can also be activate
+<DT><B> [f]ly </B><DD>
+<P>Pulldown to select fly/orbit/rot/tran, which can also be activate
by pressing the f/o/r/t keys inside the viewing window.</P>
-<DT><B> point </B><DD><P>Toggle to turn the points on/off. See also the <CODE>points</CODE> command.</P>
+<DT><B> point </B><DD>
+<P>Toggle to turn the points on/off. See also the <CODE>points</CODE> command.</P>
-<DT><B> poly </B><DD><P>Toggle to turn polygons on/off. See also the <CODE>polygon</CODE> command.</P>
+<DT><B> poly </B><DD>
+<P>Toggle to turn polygons on/off. See also the <CODE>polygon</CODE> command.</P>
-<DT><B> lbl </B><DD><P>Toggle to turn labels on/off. See also the <CODE>label</CODE> command.</P>
+<DT><B> lbl </B><DD>
+<P>Toggle to turn labels on/off. See also the <CODE>label</CODE> command.</P>
-<DT><B> tex </B><DD><P>Toggle to turn textures on/off. See also the <CODE>texture</CODE> command.</P>
+<DT><B> tex </B><DD>
+<P>Toggle to turn textures on/off. See also the <CODE>texture</CODE> command.</P>
-<DT><B> box </B><DD><P>Toggle to turn boxes on/off. See also the <CODE>boxes</CODE> command.</P>
+<DT><B> box </B><DD>
+<P>Toggle to turn boxes on/off. See also the <CODE>boxes</CODE> command.</P>
-<DT><B> #.### </B><DD><P>The current displayed value of the <CODE>logslum lum</CODE> slider (see next)</P>
+<DT><B> #.### </B><DD>
+<P>The current displayed value of the <CODE>logslum lum</CODE> slider (see next)</P>
-<DT><B> logslum lum </B><DD><P>Slider controlling the logarithm of the <B>datavar</B> variable
+<DT><B> logslum lum </B><DD>
+<P>Slider controlling the logarithm of the <B>datavar</B> variable
selected as luminosity (with the <CODE>lum</CODE> command).</P>
</DL>
@@ -190,38 +200,48 @@ has a nonzero time range.</P>
<P>
<DL>
-<DT><B> T </B><DD><P>Shows the current time (or offset from the tripmeter).
+<DT><B> T </B><DD>
+<P>Shows the current time (or offset from the tripmeter).
The absolute time is the sum of the <B>T</B> and <B>+</B> fields.
Both are editable.
See also the <CODE>step</CODE> control command.</P>
-<DT><B>trip </B><DD><P>Press to mark a reference point in time.
+<DT><B>trip </B><DD>
+<P>Press to mark a reference point in time.
The T field becomes zero, and the + field (below)
is set to current time. As time passes, T shows the
offset from this reference time.</P>
-<DT><B>back </B><DD><P>Press to return to reference time (sets T to 0).</P>
+<DT><B>back </B><DD>
+<P>Press to return to reference time (sets T to 0).</P>
-<DT><B> + </B><DD><P>Current last time where tripmeter was set. You can reset to
+<DT><B> + </B><DD>
+<P>Current last time where tripmeter was set. You can reset to
the first frame with the command <CODE>step 0</CODE></P>
-<DT><B> dial </B><DD><P>Drag to adjust the current time. Sensitivity depends
+<DT><B> dial </B><DD>
+<P>Drag to adjust the current time. Sensitivity depends
on the speed setting; dragging by one dial-width
corresponds to 0.1 wall-clock second of animation,
i.e. 0.1 * <I>speed</I> in data time units.</P>
<DT><B> |< </B><DD>
-<DT><B> >| </B><DD><P>Step time backwards or forwards by 0.1 * <I>speed</I> data time units.
+
+<DT><B> >| </B><DD>
+<P>Step time backwards or forwards by 0.1 * <I>speed</I> data time units.
See also the <CODE><</CODE> and <CODE>></CODE> keyboard shortcuts.</P>
<DT><B> << </B><DD>
-<DT><B> >> </B><DD><P>toggle movie move forwards in time
+
+<DT><B> >> </B><DD>
+<P>toggle movie move forwards in time
Toggle animating backwards or forwards in time, by
1 * <I>speed</I> data time units per real-time second.
See also the <CODE>{</CODE>, <CODE>~</CODE>, and <CODE>}</CODE> keyboard shortcuts.</P>
-<DT><B> #.#### </B><DD><P>(Logarithmic) value denoting <I>speed</I> of animation.
+<DT><B> #.#### </B><DD>
+<P>(Logarithmic) value denoting <I>speed</I> of animation.
See also the <CODE>speed</CODE> control command.</P>
@@ -237,18 +257,22 @@ row from the top controls loading and playing sequences of moving through space.
<P>
<DL>
-<DT><B> Path... </B><DD><P>Brings up a filebrowser to load a <B>.wf</B> path file. This is a file with on each
+<DT><B> Path... </B><DD>
+<P>Brings up a filebrowser to load a <B>.wf</B> path file. This is a file with on each
line 7 numbers: xyz location, RxRyRz viewing direction, and FOV (field of view).
The <CODE>rdata</CODE> command loads such path files too.</P>
-<DT><B> Play </B><DD><P>Play the viewpoint along the currently loaded path,
+<DT><B> Play </B><DD>
+<P>Play the viewpoint along the currently loaded path,
as the <CODE>play</CODE> command does.
Right-click for a menu of play-speed options.</P>
-<DT><B> << < [###] >>> </B><DD><P>Step through camera-path frames.
+<DT><B> << < [###] >>> </B><DD>
+<P>Step through camera-path frames.
See also <CODE>frame</CODE> control command.</P>
-<DT><B> slider </B><DD><P>Slides through camera path, and displays current frame.</P>
+<DT><B> slider </B><DD>
+<P>Slides through camera path, and displays current frame.</P>
</DL>
</P>
diff --git a/doc/partiview-4.html b/doc/partiview-4.html
index da06bdfd0736522d6ba35109b031ec2206c6055b..9e42f34a75ddd9143bad092ee9d7923c95954df4 100644
--- a/doc/partiview-4.html
+++ b/doc/partiview-4.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Commands</TITLE>
<LINK HREF="partiview-5.html" REL=next>
<LINK HREF="partiview-3.html" REL=previous>
@@ -74,10 +74,12 @@ others affect global things, such as time or display settings.</P>
<P>
<DL>
-<DT><B>read <I>specks-file</I></B><DD><P>Read a file containing Data Commands (typical suffix <CODE>.cf</CODE> or <CODE>.speck</CODE>).</P>
+<DT><B>read <I>specks-file</I></B><DD>
+<P>Read a file containing Data Commands (typical suffix <CODE>.cf</CODE> or <CODE>.speck</CODE>).</P>
-<DT><B>async <I>unix-command</I></B><DD><P>Run an arbitrary unix command (invoked via /bin/sh) as a subprocess of <CODE>partiview</CODE>.
+<DT><B>async <I>unix-command</I></B><DD>
+<P>Run an arbitrary unix command (invoked via /bin/sh) as a subprocess of <CODE>partiview</CODE>.
Its standard output is interpreted as a stream of control commands.
Thus <CODE>partiview</CODE> can be driven externally, e.g. to record an animation
(using the <CODE>snapshot</CODE> command), or to provide additional GUI controls.
@@ -85,7 +87,8 @@ Several <CODE>async</CODE> commands can run concurrently.
Examples are given later. Warning: you cannot interrupt a started command,
short of hitting ESC to exit partiview.</P>
-<DT><B>add <I>data-command</I></B><DD><P>Enter a Data Command where a Control Command is expected,
+<DT><B>add <I>data-command</I></B><DD>
+<P>Enter a Data Command where a Control Command is expected,
e.g. in the text input box. For example,
<PRE>
add 10 15 -1 text blah
@@ -98,13 +101,15 @@ adds a new label "blah" at 10 15 -1, or
loads a kira (starlab) output file.</P>
-<DT><B>eval <I>control-command</I></B><DD><P>Processes that control command just as if the <CODE>eval</CODE> prefix weren't there.
+<DT><B>eval <I>control-command</I></B><DD>
+<P>Processes that control command just as if the <CODE>eval</CODE> prefix weren't there.
Provided for symmetry: wherever either a control command or a data command
is expected, entering <CODE>eval</CODE> <I>control-command</I> ensures that it's
taken as a control command.</P>
-<DT><B>add filepath (data-command)</B><DD><P>Determines the list of directories where all data files, color maps, etc.
+<DT><B>add filepath (data-command)</B><DD>
+<P>Determines the list of directories where all data files, color maps, etc.
are sought. See the <CODE>filepath</CODE> entry under
Data Commands.</P>
@@ -126,19 +131,25 @@ and selects that group as the current one for other GUI controls.</P>
each group may also have an alias.</P>
<P>
<DL>
-<DT><B>g<I>N</I> </B><DD><P>Select group g<I>N</I>. Create a new group if it doesn't already exist.</P>
+<DT><B>g<I>N</I> </B><DD>
+<P>Select group g<I>N</I>. Create a new group if it doesn't already exist.</P>
-<DT><B>g<I>N</I>=<I>alias</I> </B><DD><P>Assign name <I>alias</I> to group g<I>N</I>.
+<DT><B>g<I>N</I>=<I>alias</I> </B><DD>
+<P>Assign name <I>alias</I> to group g<I>N</I>.
Note there must be no blanks around the <CODE>=</CODE> sign.</P>
-<DT><B>object <I>objectname</I></B><DD><P>Likewise, select object <I>objectname</I>, which may be either an alias name
+<DT><B>object <I>objectname</I></B><DD>
+<P>Likewise, select object <I>objectname</I>, which may be either an alias name
or g<I>N</I>. </P>
<DT><B>g<I>N</I> <I>control-command</I></B><DD>
-<DT><B>object <I>objectname</I> <I>control-command</I></B><DD><P>Either form may be used as a <I>prefix</I> to any control command
+
+<DT><B>object <I>objectname</I> <I>control-command</I></B><DD>
+<P>Either form may be used as a <I>prefix</I> to any control command
to act on the specified group, e.g. <CODE>object fred poly on</CODE></P>
-<DT><B>gall <I>control-command</I></B><DD><P>Invoke the given <I>control-command</I> in all groups.
+<DT><B>gall <I>control-command</I></B><DD>
+<P>Invoke the given <I>control-command</I> in all groups.
For example, to turn display of group 3 on and all others off, use:
<BLOCKQUOTE><CODE>
<PRE>
@@ -149,11 +160,15 @@ g3 on
</P>
<DT><B>on</B><DD>
-<DT><B>enable</B><DD><P>Either one will
+
+<DT><B>enable</B><DD>
+<P>Either one will
enable the display of the currently selected group (as it is by default).</P>
<DT><B>off</B><DD>
-<DT><B>disable</B><DD><P>Either one will turn off the display of the current group.</P>
+
+<DT><B>disable</B><DD>
+<P>Either one will turn off the display of the current group.</P>
</DL>
</P>
@@ -164,16 +179,19 @@ enable the display of the currently selected group (as it is by default).</P>
<P>View commands affect the view; they aren't specific to data groups.</P>
<P>
<DL>
-<DT><B>fov <I>float</I></B><DD><P>Angular field of view (in degrees) in Y-direction.</P>
+<DT><B>fov <I>float</I></B><DD>
+<P>Angular field of view (in degrees) in Y-direction.</P>
-<DT><B>cen[ter] <I>X Y Z</I> [<I>RADIUS</I>]</B><DD><P>Set point of interest. This is the center of rotation in
+<DT><B>cen[ter] <I>X Y Z</I> [<I>RADIUS</I>]</B><DD>
+<P>Set point of interest. This is the center of rotation in
<CODE>[o]rbit</CODE> and <CODE>[r]otate</CODE> modes. Also, in <CODE>[o]rbit</CODE> mode,
translation speed is proportional to the viewer's distance from this point.
The optional <I>RADIUS</I> (also set by <CODE>censize</CODE>) determines the size
of the marker crosshair, initially 1 unit.</P>
<DT><B>cen[ter] [<I>X Y Z</I> [<I>RADIUS</I>]]
-int[erest] [<I>X Y Z</I> [<I>RADIUS</I>]]</B><DD><P>Set point of interest. This is the center of rotation in
+int[erest] [<I>X Y Z</I> [<I>RADIUS</I>]]</B><DD>
+<P>Set point of interest. This is the center of rotation in
<CODE>[o]rbit</CODE> and <CODE>[r]otate</CODE> modes. And, in <CODE>[o]rbit</CODE> mode,
translation speed is proportional to the viewer's distance from this point.
The optional <I>RADIUS</I> (also set by <CODE>censize</CODE>) determines the size
@@ -181,11 +199,14 @@ of the marker crosshair, initially 1 unit.</P>
<P>**** why is center/interest commented out in the first example. Originally
this command was documented twice, the first one has /interest commented out.</P>
-<DT><B>censize [<I>RADIUS</I>]</B><DD><P>Set size of point-of-interest marker.</P>
+<DT><B>censize [<I>RADIUS</I>]</B><DD>
+<P>Set size of point-of-interest marker.</P>
-<DT><B>where <I>(also)</I> w</B><DD><P>Report the 3-D camera position and forward direction vector.</P>
+<DT><B>where <I>(also)</I> w</B><DD>
+<P>Report the 3-D camera position and forward direction vector.</P>
-<DT><B>clip <I>NEAR</I> <I>FAR</I></B><DD><P>Clipping distances. The computer graphics setup always requires
+<DT><B>clip <I>NEAR</I> <I>FAR</I></B><DD>
+<P>Clipping distances. The computer graphics setup always requires
drawing only objects in some finite range of distances in front of the
viewpoint. Both values must be strictly positive, and their ratio
is limited; depending on the graphics system in use, distant objects
@@ -194,27 +215,35 @@ may appear to blink if the <I>FAR</I>/<I>NEAR</I> ratio exceeds 10000 or so.</P>
near clip value, e.g. <CODE>clip - 1000</CODE>.</P>
-<DT><B>jump [<I>X Y Z</I>] [<I>Rx Ry Rz</I>]</B><DD><P>Get or set the current position (XYZ) and/or viewing (RxRyRz) angle.</P>
+<DT><B>jump [<I>X Y Z</I>] [<I>Rx Ry Rz</I>]</B><DD>
+<P>Get or set the current position (XYZ) and/or viewing (RxRyRz) angle.</P>
-<DT><B>readpath</B><DD><P>Read a Wavefront (<CODE>.wf</CODE>) file describing a path through space.</P>
+<DT><B>readpath</B><DD>
+<P>Read a Wavefront (<CODE>.wf</CODE>) file describing a path through space.</P>
-<DT><B>rdata</B><DD><P>Synonym for readpath.</P>
+<DT><B>rdata</B><DD>
+<P>Synonym for readpath.</P>
-<DT><B>play <I>speed</I>[f]</B><DD><P>Play the currently loaded (from <CODE>readpath</CODE>/<CODE>rdata</CODE>) camera animation
+<DT><B>play <I>speed</I>[f]</B><DD>
+<P>Play the currently loaded (from <CODE>readpath</CODE>/<CODE>rdata</CODE>) camera animation
path, at <I>speed</I> times normal speed,
skipping frames as needed to keep up with wall-clock time.
(Normal speed is 30 frames per second.)
With "f" suffix, displays every <I>speed</I>-th frame, without regard to real
time.</P>
-<DT><B>frame [<I>frameno</I>]</B><DD><P>Get or set the current frame the <I>frameno</I>-th.</P>
+<DT><B>frame [<I>frameno</I>]</B><DD>
+<P>Get or set the current frame the <I>frameno</I>-th.</P>
-<DT><B>update </B><DD><P>Ensures the display is updated, as before taking a snapshot.
+<DT><B>update </B><DD>
+<P>Ensures the display is updated, as before taking a snapshot.
Probably only useful in a stream of control commands from an <CODE>async</CODE>
subprocess.</P>
<DT><B>winsize [<I>XSIZE</I> [<I>YSIZE</I>]]</B><DD>
-<DT><B>winsize <I>XSIZE</I>x<I>YSIZE</I>+<I>XPOS</I>+<I>YPOS</I></B><DD><P>Resize graphics window. With no arguments, reports current size.
+
+<DT><B>winsize <I>XSIZE</I>x<I>YSIZE</I>+<I>XPOS</I>+<I>YPOS</I></B><DD>
+<P>Resize graphics window. With no arguments, reports current size.
With one argument, resizes to given width, preserving aspect ratio.
With two arguments, reshapes window to that height and width.
With complete X geometry specification (no embedded spaces),
@@ -222,7 +251,8 @@ e.g. <CODE>winsize 400x350+20-10</CODE>,
also sets position of graphics window, with +X and +Y measured from
left/top, -X and -Y measured from right/bottom of screen.</P>
-<DT><B>detach [full|hide] [<I>+XPOS+YPOS</I>]</B><DD><P>Detach graphics window from GUI control strip and optionally
+<DT><B>detach [full|hide] [<I>+XPOS+YPOS</I>]</B><DD>
+<P>Detach graphics window from GUI control strip and optionally
specify position of control strip. With <CODE>full</CODE> or <CODE>hide</CODE>,
makes graphics window full-screen with GUI visible or hidden, respectively.
With neither <CODE>full</CODE> nor <CODE>hide</CODE>, the graphics window
@@ -238,15 +268,18 @@ input focus is in the text box.
Use <I>Tab</I><CODE>detach full</CODE><I>Enter</I>
to un-hide a hidden control strip.</P>
-<DT><B>bgcolor <I>R G B</I></B><DD><P>Set window background color (three R G B numbers or one grayscale value).</P>
+<DT><B>bgcolor <I>R G B</I></B><DD>
+<P>Set window background color (three R G B numbers or one grayscale value).</P>
-<DT><B>focallen <I>distance</I></B><DD><P>Focal length: distance from viewer to a typical object of interest.
+<DT><B>focallen <I>distance</I></B><DD>
+<P>Focal length: distance from viewer to a typical object of interest.
This affects stereo display (see below) and navigation: the speed of
motion in <CODE>[t]ranslate</CODE> and <CODE>[f]ly</CODE> modes is proportional to this
distance.</P>
-<DT><B>stereo [on|off|redcyan|glasses|cross|left|right] [<I>separation</I>]</B><DD><P>Stereo display. Also toggled on/off by typing <CODE>'s'</CODE> key in graphics window.
+<DT><B>stereo [on|off|redcyan|glasses|cross|left|right] [<I>separation</I>]</B><DD>
+<P>Stereo display. Also toggled on/off by typing <CODE>'s'</CODE> key in graphics window.
Where hardware allows it, <CODE>stereo glasses</CODE> selects
CrystalEyes-style quad-buffered stereo. All systems should be capable of
<CODE>stereo redcyan</CODE>, which requires wearing red/green or red/blue glasses,
@@ -273,7 +306,8 @@ to revert. Otherwise, turning partiview's stereo on
will just show the left eye's view -- displacing the viewpoint
but nothing else.</P>
-<DT><B>snapset [<CODE>-n</CODE> <I>FRAMENO</I>] <I>FILESTEM</I> [<I>FRAMENO</I>]</B><DD><P>Set parameters for future <CODE>snapshot</CODE> commands.
+<DT><B>snapset [<CODE>-n</CODE> <I>FRAMENO</I>] <I>FILESTEM</I> [<I>FRAMENO</I>]</B><DD>
+<P>Set parameters for future <CODE>snapshot</CODE> commands.
<I>FILESTEM</I> may be a printf format string with frame number as
argument, e.g. <CODE>snapset pix/%04d.ppm</CODE>, generating image names
of <CODE>pix/0000.ppm</CODE>, <CODE>pix/0001.ppm</CODE>, etc.
@@ -283,7 +317,8 @@ yields snapshot images named <CODE>./pix/fred.000.ppm.gz</CODE> etc.</P>
<P>Frame number <I>FRAMENO</I> (default 0) increments with each snapshot taken.</P>
-<DT><B>snapshot [<I>FRAMENO</I> | <I>FILENAME</I>]</B><DD><P>Capture a snapshot image of the current view.</P>
+<DT><B>snapshot [<I>FRAMENO</I> | <I>FILENAME</I>]</B><DD>
+<P>Capture a snapshot image of the current view.</P>
<P>Either give <CODE>snapshot</CODE> an explicit filename,
or else specify a file format string with <CODE>snapset</CODE>
and then let <CODE>snapshot</CODE> fill in the frame number.
@@ -307,7 +342,8 @@ the type of image (jpeg, sgi, bmp, etc.) based on the file suffix.</P>
displayed.</P>
<P>
<DL>
-<DT><B>psize <I>scalefactor</I></B><DD><P>All particle luminosities (as specified by <CODE>lum</CODE> command)
+<DT><B>psize <I>scalefactor</I></B><DD>
+<P>All particle luminosities (as specified by <CODE>lum</CODE> command)
are scaled by the product of two factors:
a <I>lumvar</I>-specific factor given by <CODE>slum</CODE>,
and a global factor given by <CODE>psize</CODE>.
@@ -316,7 +352,8 @@ So the intrinsic brightness of a particle is
* <I>slum-for-current-lumvar</I>
* <I>psize-scalefactor</I>.</P>
-<DT><B>slum <I>slumfactor</I></B><DD><P>Data-field specific luminosity scale factor, for current choice of
+<DT><B>slum <I>slumfactor</I></B><DD>
+<P>Data-field specific luminosity scale factor, for current choice of
<I>lumvar</I> as given by the <CODE>lum</CODE> command.
A <I>slumfactor</I> is recorded independently for each data field, so
if data fields <CODE>mass</CODE> and <CODE>energy</CODE> were defined, one might say
@@ -334,19 +371,23 @@ and then freely switch between <CODE>lum mass</CODE> and <CODE>lum energy</CODE>
without having to readjust particle brightness each time.</P>
-<DT><B>ptsize <I>minpixels</I> <I>maxpixels</I></B><DD><P>Specifies the range of <I>apparent</I> sizes of points,
+<DT><B>ptsize <I>minpixels</I> <I>maxpixels</I></B><DD>
+<P>Specifies the range of <I>apparent</I> sizes of points,
in pixels. Typical values might be <CODE>ptsize 0.1 5</CODE>.
The graphics system may silently impose an upper limit
of about 10 pixels.</P>
-<DT><B>poly [on|off]</B><DD><P>Display polygons, or don't.</P>
+<DT><B>poly [on|off]</B><DD>
+<P>Display polygons, or don't.</P>
-<DT><B>polysize [<I>scalefactor</I>]</B><DD><P>Multiplier for polygon size. Default is zero (!), so you must
+<DT><B>polysize [<I>scalefactor</I>]</B><DD>
+<P>Multiplier for polygon size. Default is zero (!), so you must
set polysize to something else before polygons will show up.</P>
-<DT><B>polylumvar [<I>attrname</I> | <CODE>point-size</CODE>] [<CODE>area</CODE> | <CODE>radius</CODE>]</B><DD><P>Choose which attribute determines the radius of a particle's polygon.
+<DT><B>polylumvar [<I>attrname</I> | <CODE>point-size</CODE>] [<CODE>area</CODE> | <CODE>radius</CODE>]</B><DD>
+<P>Choose which attribute determines the radius of a particle's polygon.
By default, it is <CODE>point-size</CODE>, a pseudo-attribute which varies with
the brightness of points (so adjusting the slum slider scales polygons too).</P>
<P>Each polygon's 3-D radius is the <CODE>polysize</CODE> <I>scalefactor</I> times its particle's
@@ -356,14 +397,17 @@ of attribute * scalefactor. <CODE>area</CODE> is useful if the attribute repre
a luminosity; in that case, the polygon total brightness (which is proportional
to its screen area) becomes proportional to the attribute / distance^2.</P>
-<DT><B>polymin <I>minradius</I> [<I>maxradius</I>]</B><DD><P>Specify a minimum screen radius for polygons, in pixels.
+<DT><B>polymin <I>minradius</I> [<I>maxradius</I>]</B><DD>
+<P>Specify a minimum screen radius for polygons, in pixels.
If smaller than this, they are not drawn.</P>
-<DT><B>color</B><DD><P>Specify how particles are colored.
+<DT><B>color</B><DD>
+<P>Specify how particles are colored.
Generally, a linear function of some data field of each particle
becomes an index into a colormap (see <CODE>cmap</CODE>, <CODE>cment</CODE>).
<DL>
-<DT><B> color <I>colorvar</I> [<I>minval maxval</I>] </B><DD><P>Use data field <I>colorvar</I> (either a name as set by <CODE>datavar</CODE>
+<DT><B> color <I>colorvar</I> [<I>minval maxval</I>] </B><DD>
+<P>Use data field <I>colorvar</I> (either a name as set by <CODE>datavar</CODE>
or a 0-based integer column number) to determine color.
Map <I>minval</I> to color index 1, and <I>maxval</I> to
the next-to-last entry in the colormap (<I>Ncmap-2</I>).
@@ -372,24 +416,29 @@ out-of-range data values.</P>
<P>If <I>minval</I> and <I>maxval</I> are omitted, the actual range of
values is used.</P>
-<DT><B> color <I>colorvar</I> exact [<I>baseval</I>] </B><DD><P>Don't consider field <I>colorvar</I> as a continuous variable;
+<DT><B> color <I>colorvar</I> exact [<I>baseval</I>] </B><DD>
+<P>Don't consider field <I>colorvar</I> as a continuous variable;
instead, it's integer-valued, and mapped one-to-one with
color table slots. Data value <I>N</I> is mapped to
color index <I>N+baseval</I>.</P>
-<DT><B> color <I>colorvar</I> -exact </B><DD><P>Once the <CODE>exact</CODE> tag is set (for a particular data-field),
+<DT><B> color <I>colorvar</I> -exact </B><DD>
+<P>Once the <CODE>exact</CODE> tag is set (for a particular data-field),
it's sticky. To interpret that data field as a continuous, scalable
variable again, use <CODE>-exact</CODE>.</P>
-<DT><B> color const <I>R G B</I> </B><DD><P>Show all particles as color <I>R G B</I>, each value in range 0 to 1,
+<DT><B> color const <I>R G B</I> </B><DD>
+<P>Show all particles as color <I>R G B</I>, each value in range 0 to 1,
independent of any data fields.</P>
</DL>
</P>
-<DT><B>lum</B><DD><P>Specify how particles' intrinsic luminosity is computed:
+<DT><B>lum</B><DD>
+<P>Specify how particles' intrinsic luminosity is computed:
a linear function of some data field of each particle.
<DL>
-<DT><B> lum <I>lumvar</I> [<I>minval maxval</I>] </B><DD><P>Map values of data field <I>lumvar</I> (<CODE>datavar</CODE> name or
+<DT><B> lum <I>lumvar</I> [<I>minval maxval</I>] </B><DD>
+<P>Map values of data field <I>lumvar</I> (<CODE>datavar</CODE> name or
field number) to luminosity.
The (linear) mapping takes field value <I>minval</I> to
luminosity 0 and <I>maxval</I> to luminosity 1.0.</P>
@@ -401,12 +450,14 @@ the <CODE>psize</CODE> and <CODE>slum</CODE> scale factors, and further
scaled according to distance as specified by <CODE>fade</CODE>, to compute
apparent brightness of points.</P>
-<DT><B> lum const <I>L</I> </B><DD><P>Specify constant particle luminosity <I>L</I> independent of
+<DT><B> lum const <I>L</I> </B><DD>
+<P>Specify constant particle luminosity <I>L</I> independent of
any data field values.</P>
</DL>
</P>
-<DT><B>fade [planar|spherical|linear <I>refdist</I>|const <I>refdist</I>]</B><DD><P>Determines how distance affects particles' apparent brightness (or "size").
+<DT><B>fade [planar|spherical|linear <I>refdist</I>|const <I>refdist</I>]</B><DD>
+<P>Determines how distance affects particles' apparent brightness (or "size").
The default <CODE>fade planar</CODE> gives 1/r^2 light falloff, with r measured
as distance from the view plane. <CODE>fade spherical</CODE> is also 1/r^2,
but with r measured as true distance from the viewpoint.
@@ -418,40 +469,54 @@ independent of distance, and may be appropriate for orthographic views.</P>
at which apparent brightness should match that in the 1/r^2 modes --
a distance to a "typical" particle.</P>
-<DT><B>labelmin <I>minpixels</I></B><DD><P>Labels computed to be smaller than this screen size (pixels) are suppressed.</P>
+<DT><B>labelmin <I>minpixels</I></B><DD>
+<P>Labels computed to be smaller than this screen size (pixels) are suppressed.</P>
<DT><B>labelsize <I>scalefactor</I></B><DD>
-<DT><B>lsize <I>scalefactor</I></B><DD><P>lsize (alias labelsize) sets the 3-D height of labels. If the text was created with a
+
+<DT><B>lsize <I>scalefactor</I></B><DD>
+<P>lsize (alias labelsize) sets the 3-D height of labels. If the text was created with a
<CODE>text -size </CODE><I>textsize</I> option, the scalefactor is multiplied by that to determine
the 3-D size.</P>
-<DT><B>point[s] [on|off]</B><DD><P>Turn display of points on or off. With no argument, toggles display.</P>
+<DT><B>point[s] [on|off]</B><DD>
+<P>Turn display of points on or off. With no argument, toggles display.</P>
-<DT><B>poly[gons] [on|off]</B><DD><P>Turn display of points on or off. With no argument, toggles display.</P>
+<DT><B>poly[gons] [on|off]</B><DD>
+<P>Turn display of points on or off. With no argument, toggles display.</P>
-<DT><B>texture [on|off]</B><DD><P>Turn display of textures on or off. With no argument, toggles.</P>
+<DT><B>texture [on|off]</B><DD>
+<P>Turn display of textures on or off. With no argument, toggles.</P>
-<DT><B>label[s] [on|off]</B><DD><P>Turn display of label text on or off. With no argument, toggles.</P>
+<DT><B>label[s] [on|off]</B><DD>
+<P>Turn display of label text on or off. With no argument, toggles.</P>
-<DT><B>txscale <I>scalefactor</I></B><DD><P>Scale size of all textures relative to their polygons.
+<DT><B>txscale <I>scalefactor</I></B><DD>
+<P>Scale size of all textures relative to their polygons.
A scale factor of 0.5 (default) make the texture square
just fill its polygon, if <CODE>polysides</CODE> is 4.</P>
-<DT><B>polyorivar</B><DD><P>Report setting of <CODE>polyorivar</CODE> data-command, which see.</P>
+<DT><B>polyorivar</B><DD>
+<P>Report setting of <CODE>polyorivar</CODE> data-command, which see.</P>
-<DT><B>texturevar</B><DD><P>Report setting of <CODE>texturevar</CODE> data-command, which see.</P>
+<DT><B>texturevar</B><DD>
+<P>Report setting of <CODE>texturevar</CODE> data-command, which see.</P>
-<DT><B>laxes [on|off]</B><DD><P>Toggle label axes. When on, and when labels are displayed,
+<DT><B>laxes [on|off]</B><DD>
+<P>Toggle label axes. When on, and when labels are displayed,
shows a set of red/green/blue (X/Y/Z) axes to indicate orientation.</P>
-<DT><B>polyside(s)</B><DD><P>Number of sides a polygon should have. Default 11, for fairly round
+<DT><B>polyside(s)</B><DD>
+<P>Number of sides a polygon should have. Default 11, for fairly round
polygons. For textured polygons, <CODE>polysides 4</CODE> might do as well,
and be slightly speedier.</P>
-<DT><B>fast [on|off]</B><DD><P>see also <CODE>ptsize</CODE></P>
+<DT><B>fast [on|off]</B><DD>
+<P>see also <CODE>ptsize</CODE></P>
-<DT><B>ptsize <I>minpixels</I> [<I>maxpixels</I>]</B><DD><P>Specifies range of apparent (pixel) size of points.
+<DT><B>ptsize <I>minpixels</I> [<I>maxpixels</I>]</B><DD>
+<P>Specifies range of apparent (pixel) size of points.
Those with computed sizes (based on luminosity
and distance) smaller than <I>minpixels</I> are
randomly (but repeatably) subsampled -- i.e. some
@@ -459,31 +524,38 @@ fraction of them are not drawn. Those computed to be
larger than <I>maxpixels</I> are drawn at size
<I>maxpixels</I>.</P>
-<DT><B>gamma <I>displaygamma</I></B><DD><P>Tells the particle renderer how the display + OpenGL
+<DT><B>gamma <I>displaygamma</I></B><DD>
+<P>Tells the particle renderer how the display + OpenGL
relates image values to visible lightness.
You don't need to change this, but may adjust it
to minimize the brightness glitches when particles change size.
Typical values are <CODE>gamma 1</CODE> through <CODE>gamma 2.5</CODE> or so.
Larger values raise the apparent brightness of dim things.</P>
-<DT><B>alpha <I>alpha</I></B><DD><P>Get or set the alpha value, in the range 0 to 1; it determines
+<DT><B>alpha <I>alpha</I></B><DD>
+<P>Get or set the alpha value, in the range 0 to 1; it determines
the opacity of polygons.</P>
-<DT><B>speed</B><DD><P>For time-dependent data, advance datatime by this many time units
+<DT><B>speed</B><DD>
+<P>For time-dependent data, advance datatime by this many time units
per wall-clock second.</P>
-<DT><B>step [<I>timestep</I>]</B><DD><P>For time-varying data, sets current timestep number.
+<DT><B>step [<I>timestep</I>]</B><DD>
+<P>For time-varying data, sets current timestep number.
Real-valued times are meaningful for some kinds of data including those
from Starlab/kira; for others, times are rounded to nearest integer.
If running, <CODE>step</CODE> also stops datatime animation. (See <CODE>run</CODE>.)</P>
-<DT><B>step [+|-]<I>deltatimestep</I></B><DD><P>If preceded with a plus or minus sign, adds that amount to current time.</P>
+<DT><B>step [+|-]<I>deltatimestep</I></B><DD>
+<P>If preceded with a plus or minus sign, adds that amount to current time.</P>
<P>(note that <CODE>fspeed</CODE> has been deprecated)</P>
-<DT><B>run</B><DD><P>Continue a stopped animation (see also <CODE>step</CODE>).</P>
+<DT><B>run</B><DD>
+<P>Continue a stopped animation (see also <CODE>step</CODE>).</P>
-<DT><B>tfm [-v] [<I>numbers...</I>]</B><DD><P>Object-to-world transformation.
+<DT><B>tfm [-v] [<I>numbers...</I>]</B><DD>
+<P>Object-to-world transformation.
May take 1, 6, 7, 9 or 16 parameters: either
<I>scalefactor</I>,
or <I>tx ty tz rx ry rz </I><I>scalefactor</I>>],
@@ -493,7 +565,8 @@ See <I>Coordinates and Coordinate Transformations</I>.</P>
<P>With no numeric parameters, reports the current object-to-world transform.
Use <CODE>tfm -v</CODE> to see the transform and its inverse in several forms.</P>
-<DT><B>move [g<I>N</I>] {on|off}</B><DD><P>Normally, navigation modes <CODE>[r]otate</CODE> and <CODE>[t]ranslate</CODE>
+<DT><B>move [g<I>N</I>] {on|off}</B><DD>
+<P>Normally, navigation modes <CODE>[r]otate</CODE> and <CODE>[t]ranslate</CODE>
just adjust the viewpoint (camera). However,
if you turn <CODE>move on</CODE>, then <CODE>[r]otate</CODE> and <CODE>[t]ranslate</CODE>
move the currently-selected object group instead,
@@ -507,29 +580,36 @@ The <CODE>tfm</CODE> command reports the current object-group-to-global-world
transformation.</P>
<DT><B>fwd</B><DD>
-<DT><B>datawait on|off</B><DD><P>For asynchronously-loaded data (currently only <CODE>ieee</CODE> data command),
+
+<DT><B>datawait on|off</B><DD>
+<P>For asynchronously-loaded data (currently only <CODE>ieee</CODE> data command),
say whether wait for current data step to be loaded.
(If not, then keep displaying previous data while loading new.)</P>
-<DT><B>cmap <I>filename</I></B><DD><P>Load (ascii) filename with RGB values, for coloring particles.
+<DT><B>cmap <I>filename</I></B><DD>
+<P>Load (ascii) filename with RGB values, for coloring particles.
The <CODE>color</CODE> command selects which data field is mapped to color index
and how.</P>
<P>Colormaps are text files, beginning with a number-of-entries
line and followed by R G B or R G B A entries one per line;
see the <I>Colormaps</I> section.</P>
-<DT><B>vcmap -v <I>fieldname</I> <I>filename</I></B><DD><P>Load colormap as with <CODE>cmap</CODE> command. But use this colormap
+<DT><B>vcmap -v <I>fieldname</I> <I>filename</I></B><DD>
+<P>Load colormap as with <CODE>cmap</CODE> command. But use this colormap
only when the given data field is selected for coloring.
Thus the <CODE>cmap</CODE> color map applies to all data fields for which
no <CODE>vcmap</CODE> has ever been specified.</P>
-<DT><B>cment <I>colorindex</I> [<I>R G B</I>]</B><DD><P>Report or set that colormap entry.</P>
+<DT><B>cment <I>colorindex</I> [<I>R G B</I>]</B><DD>
+<P>Report or set that colormap entry.</P>
-<DT><B>rawdump <I>dump-filename</I></B><DD><P>All particle attributes (not positions though)
+<DT><B>rawdump <I>dump-filename</I></B><DD>
+<P>All particle attributes (not positions though)
are written to a <I>dump-filename</I>. Useful for debugging.
Warning: it will happily overwrite an existing file with that name.</P>
-<DT><B>warp [on|off]</B><DD><P>Enable, disable, or report the status of any <CODE>warp</CODE> data-command set up for the current group.
+<DT><B>warp [on|off]</B><DD>
+<P>Enable, disable, or report the status of any <CODE>warp</CODE> data-command set up for the current group.
If it exists, particles's positions can change with time, in a handful of canned ways
built into the <CODE>warp</CODE> command. See the <CODE>warp</CODE> entry under Data Commands.</P>
@@ -543,19 +623,27 @@ built into the <CODE>warp</CODE> command. See the <CODE>warp</CODE> entry under
<P>
<DL>
-<DT><B>clipbox ...</B><DD><P>see <CODE>cb</CODE> below.</P>
+<DT><B>clipbox ...</B><DD>
+<P>see <CODE>cb</CODE> below.</P>
-<DT><B>cb ....</B><DD><P>Display only a 3D subregion of the data -- the part lying within the clipbox.
+<DT><B>cb ....</B><DD>
+<P>Display only a 3D subregion of the data -- the part lying within the clipbox.
<DL>
-<DT><B>cb <I>xmin ymin zmin xmax ymax zmax</I> </B><DD><P>Specified by coordinate ranges.
+<DT><B>cb <I>xmin ymin zmin xmax ymax zmax</I> </B><DD>
+<P>Specified by coordinate ranges.
Note only spaces are used to separate the 6 numbers.</P>
-<DT><B>cb <I>xcen,ycen,zcen xrad,yrad,zrad</I> </B><DD><P>Specified by center and "radius" of the box.
+<DT><B>cb <I>xcen,ycen,zcen xrad,yrad,zrad</I> </B><DD>
+<P>Specified by center and "radius" of the box.
Note no spaces after the commas!</P>
-<DT><B>cb <I>xmin,xmax ymin,ymax zmin,zmax</I> </B><DD><P>Specified by coordinate ranges.</P>
-<DT><B>cb <CODE>off</CODE> </B><DD><P>Disable clipping. The entire dataset is again visible.</P>
-<DT><B>cb <CODE>on</CODE> </B><DD><P>Re-enable a previously defined clipbox setting. It will also
+<DT><B>cb <I>xmin,xmax ymin,ymax zmin,zmax</I> </B><DD>
+<P>Specified by coordinate ranges.</P>
+<DT><B>cb <CODE>off</CODE> </B><DD>
+<P>Disable clipping. The entire dataset is again visible.</P>
+<DT><B>cb <CODE>on</CODE> </B><DD>
+<P>Re-enable a previously defined clipbox setting. It will also
display the clipbox again</P>
-<DT><B>cb <CODE>hide</CODE> </B><DD><P>Hide the clipbox, but still discard objects whose centers
+<DT><B>cb <CODE>hide</CODE> </B><DD>
+<P>Hide the clipbox, but still discard objects whose centers
lie outside it.</P>
</DL>
@@ -564,27 +652,35 @@ if no arguments given (that would be handy
and more in line with similar commands).
If no arguments given, it reports the current clipbox.</P>
-<DT><B>thresh</B><DD><P>Display a subset of particles, chosen by the value of
+<DT><B>thresh</B><DD>
+<P>Display a subset of particles, chosen by the value of
some data field. Each <CODE>thresh</CODE> command overrides
settings from previous commands, so it cannot be used to
show unions or intersections of multiple criteria.
For that, see the <CODE>only</CODE> command. However, unlike <CODE>only</CODE>,
the <CODE>thresh</CODE> criterion applies to time-varying data.
<DL>
-<DT><B>thresh <I>field</I> <I>minval</I> <I>maxval</I> </B><DD><P>Display only those particles where
+<DT><B>thresh <I>field</I> <I>minval</I> <I>maxval</I> </B><DD>
+<P>Display only those particles where
<I>minval</I> <= field <I>field</I> <= <I>maxval</I>.
The <I>field</I> may be given by name (as from <CODE>datavar</CODE>)
or by field number.</P>
<DT><B>thresh <I>field</I> <CODE><</CODE><I>maxval</I> </B><DD>
-<DT><B>thresh <I>field</I> <CODE>></CODE><I>minval</I> </B><DD><P>Show only particles where <I>field</I> is <=
+
+<DT><B>thresh <I>field</I> <CODE>></CODE><I>minval</I> </B><DD>
+<P>Show only particles where <I>field</I> is <=
or >= the given threshold.</P>
-<DT><B>thresh [off|on]</B><DD><P>Disable or re-enable a previously specified threshold.</P>
+<DT><B>thresh [off|on]</B><DD>
+<P>Disable or re-enable a previously specified threshold.</P>
</DL>
</P>
<DT><B>only= <I>datafield</I> <I>value</I> <I>minvalue-maxvalue</I> <<I>value</I> ><I>value</I> ...</B><DD>
+
<DT><B>only+ <I>datafield</I> <I>value</I> <I>minvalue-maxvalue</I> <<I>value</I> ><I>value</I> ...</B><DD>
-<DT><B>only- <I>datafield</I> <I>value</I> <I>minvalue-maxvalue</I> <<I>value</I> ><I>value</I> ...</B><DD><P>Scans particles (in the current timestep only!), finding those where
+
+<DT><B>only- <I>datafield</I> <I>value</I> <I>minvalue-maxvalue</I> <<I>value</I> ><I>value</I> ...</B><DD>
+<P>Scans particles (in the current timestep only!), finding those where
<I>datafield</I> has value <I>value</I>, or has a value in range
<I>minvalue</I> <= value <= <I>maxvalue</I>, or whatever.
Multiple value-ranges may be specified to select the union of several sets.
@@ -594,8 +690,10 @@ Also display just particles in that selection-set, as if <CODE>see thresh</CODE>
had been typed.</P>
<P>The net effect is illustrated by these examples:
<DL>
-<DT><B>only= type 1-3 5</B><DD><P>Show only particles of type 1, 2, 3 or 5.</P>
-<DT><B>only- mass <2.3 >3.5</B><DD><P>After the above command, shows only the subset
+<DT><B>only= type 1-3 5</B><DD>
+<P>Show only particles of type 1, 2, 3 or 5.</P>
+<DT><B>only- mass <2.3 >3.5</B><DD>
+<P>After the above command, shows only the subset
of type 1/2/3/5 particles AND have mass between 2.3 and 3.5.
(Note that to take the intersection of two conditions,
you must subtract the complement of the latter one.
@@ -603,7 +701,8 @@ Maybe some day there'll be an <CODE>only&</CODE>.</P>
</DL>
</P>
-<DT><B>see <CODE>selexpr</CODE></B><DD><P>Show just those particles in the selection-set <CODE>selexpr</CODE>.
+<DT><B>see <CODE>selexpr</CODE></B><DD>
+<P>Show just those particles in the selection-set <CODE>selexpr</CODE>.
Predefined set names are <CODE>all</CODE>, <CODE>none</CODE>, <CODE>thresh</CODE> and <CODE>pick</CODE>,
and other names may be defined by the <CODE>sel</CODE> command.
The default is <CODE>see all</CODE>. Using the <CODE>thresh</CODE> or <CODE>only</CODE>
@@ -612,20 +711,25 @@ commands automatically switch to displaying <CODE>see thresh</CODE>.</P>
e.g. all except the <CODE>thresh</CODE>-selected objects, with
<CODE>see -thresh</CODE>.</P>
-<DT><B>sel <CODE>selname = selexpr</CODE></B><DD><P>Compute a logical combination of selection-sets and assign them
+<DT><B>sel <CODE>selname = selexpr</CODE></B><DD>
+<P>Compute a logical combination of selection-sets and assign them
to another such set. The set membership is originally assigned by
<CODE>thresh</CODE> or <CODE>only</CODE> commands. Yeah, I know this doesn't make sense.
Need a separate section to document selection-sets.</P>
-<DT><B>sel <CODE>selexpr</CODE></B><DD><P>Count the number of particles in the selection-set <CODE>selexpr</CODE>.</P>
+<DT><B>sel <CODE>selexpr</CODE></B><DD>
+<P>Count the number of particles in the selection-set <CODE>selexpr</CODE>.</P>
-<DT><B>clearobj</B><DD><P>Erase all particles in this group. Useful for reloading on the fly.</P>
+<DT><B>clearobj</B><DD>
+<P>Erase all particles in this group. Useful for reloading on the fly.</P>
-<DT><B>every <I>N</I></B><DD><P>Display a random subset (every <I>N</I>-th) of all particles.
+<DT><B>every <I>N</I></B><DD>
+<P>Display a random subset (every <I>N</I>-th) of all particles.
E.g. <CODE>every 1</CODE> shows all particles, <CODE>every 2</CODE> shows about half of them.
Reports current subsampling factor, and the current total number of particles.</P>
-<DT><B>hist <I>datafield</I> [-n <I>nbuckets</I>] [-l] [-c] [-t] [<I>minval</I>] [<I>maxval</I>]</B><DD><P>Generates a (numerical) histogram of values of <I>datafield</I>,
+<DT><B>hist <I>datafield</I> [-n <I>nbuckets</I>] [-l] [-c] [-t] [<I>minval</I>] [<I>maxval</I>]</B><DD>
+<P>Generates a (numerical) histogram of values of <I>datafield</I>,
which may be a named field (as from <CODE>datavar</CODE>) or a field index.
Divides the value range (either <I>minval</I>..<I>maxval</I>
or the actual range of values for that field) into <I>nbuckets</I>
@@ -635,11 +739,14 @@ If a clipbox is defined, use <CODE>-c</CODE> to count only
particles within it. If a <CODE>thresh</CODE> or <CODE>only</CODE>
subset is defined, use <CODE>-t</CODE> to count only the chosen subset.</P>
-<DT><B>bound [w]</B><DD><P>Reports 3D extent of the data. With <CODE>w</CODE>, reports it in
+<DT><B>bound [w]</B><DD>
+<P>Reports 3D extent of the data. With <CODE>w</CODE>, reports it in
world coordinates, otherwise in object coordinates.</P>
<DT><B>datavar</B><DD>
-<DT><B>dv</B><DD><P>Report names and value ranges (over all particles in current group)
+
+<DT><B>dv</B><DD>
+<P>Report names and value ranges (over all particles in current group)
of all named data fields.</P>
@@ -652,25 +759,36 @@ of all named data fields.</P>
<P>
<DL>
<DT><B>showbox <I>list of integer box level numbers...</I></B><DD>
+
<DT><B>hidebox <I>list of integer box level numbers...</I></B><DD>
-<DT><B>box[es] [off|on|only]</B><DD><P>Turn box display off or on; or display boxes but hide all particles.</P>
-<DT><B>boxcmap <I>filename</I></B><DD><P>Color boxes using that colormap.
+<DT><B>box[es] [off|on|only]</B><DD>
+<P>Turn box display off or on; or display boxes but hide all particles.</P>
+
+<DT><B>boxcmap <I>filename</I></B><DD>
+<P>Color boxes using that colormap.
Each box's level number (set by <CODE>-l</CODE> option of <CODE>box</CODE> data-command,
default 0) is the color index.</P>
-<DT><B>boxcment <I>colorindex</I> [<I>R G B</I>]</B><DD><P>Get or set the given box-colormap index. E.g. <CODE>boxcment 0</CODE>
+<DT><B>boxcment <I>colorindex</I> [<I>R G B</I>]</B><DD>
+<P>Get or set the given box-colormap index. E.g. <CODE>boxcment 0</CODE>
reports the color of boxes created with no <CODE>-l</CODE> specified.</P>
-<DT><B>boxlabel [on|off]</B><DD><P>Label boxes by id number
+<DT><B>boxlabel [on|off]</B><DD>
+<P>Label boxes by id number
(set by <CODE>-n</CODE> option of <CODE>box</CODE> data-command).</P>
-<DT><B>boxaxes [on|off]</B><DD><P>Toggle or set box axes display mode.</P>
+<DT><B>boxaxes [on|off]</B><DD>
+<P>Toggle or set box axes display mode.</P>
<DT><B>boxscale [float] [on|off] </B><DD>
+
<DT><B>gobox <I>boxnumber</I></B><DD>
+
<DT><B>goboxscale</B><DD>
+
<DT><B>menu fmenu</B><DD>
+
<P>
<BLOCKQUOTE><CODE>
<PRE>
@@ -692,6 +810,7 @@ reports the color of boxes created with no <CODE>-l</CODE> specified.</P>
<DT><B>datascale</B><DD>
+
</DL>
</P>
@@ -706,37 +825,47 @@ Lines starting with <CODE>#</CODE> will be skipped. </P>
<P>
<DL>
-<DT><B>read <I>file</I> </B><DD><P>read a <CODE>speck</CODE> formatted file. Recursive, commands can nest. (strtok ok??)
+<DT><B>read <I>file</I> </B><DD>
+<P>read a <CODE>speck</CODE> formatted file. Recursive, commands can nest. (strtok ok??)
Note that <CODE>read</CODE> is also a Control Command, doing exactly the same thing.</P>
-<DT><B>include <I>file</I></B><DD><P>read a <CODE>speck</CODE> formatted file.</P>
+<DT><B>include <I>file</I></B><DD>
+<P>read a <CODE>speck</CODE> formatted file.</P>
-<DT><B>ieee [-t time] <I>file</I></B><DD><P>Read a IEEEIO formatted file, with optional timestep number (0 based).
+<DT><B>ieee [-t time] <I>file</I></B><DD>
+<P>Read a IEEEIO formatted file, with optional timestep number (0 based).
Support for this type of data must be explicitly compiled into the program.</P>
-<DT><B>kira <I>file</I> </B><DD><P>read a <CODE>kira</CODE> formatted file. See the <CODE>kiractl</CODE> Control
+<DT><B>kira <I>file</I> </B><DD>
+<P>read a <CODE>kira</CODE> formatted file. See the <CODE>kiractl</CODE> Control
Command to modify the looks of the objects. Only present if Starlab is compiled
into partiview.</P>
-<DT><B>setenv name value</B><DD><P>Add (or change) a named variable of the environment variables space of
+<DT><B>setenv name value</B><DD>
+<P>Add (or change) a named variable of the environment variables space of
partiview. Enviroment variables, like in the normal unix shell, can be
referred to by prepending their name with a $.
<I>Note there probably is not an unsetenv command</I>.</P>
-<DT><B>object <I>gN=ALIAS</I></B><DD><P>Defines/Selects a particular group number (N=1,2,3....) to an ALIAS. In
+<DT><B>object <I>gN=ALIAS</I></B><DD>
+<P>Defines/Selects a particular group number (N=1,2,3....) to an ALIAS. In
command mode you can use <CODE>gN=ALIAS</CODE>. Any data following this command
will now belong to this group.</P>
-<DT><B>object <I>ObjectName</I></B><DD><P>Select an existing group. Following data will now belong to this group.</P>
+<DT><B>object <I>ObjectName</I></B><DD>
+<P>Select an existing group. Following data will now belong to this group.</P>
-<DT><B>sdbvars <I>var</I></B><DD><P>Choose which data fields to
+<DT><B>sdbvars <I>var</I></B><DD>
+<P>Choose which data fields to
extract from binary sdb files (any of: <CODE>mMcrogtxyzSn</CODE>) for subsequent
<CODE>sdb</CODE> commands.</P>
-<DT><B>sdb [-t time] <I>file</I></B><DD><P>Read an SDB (binary) formatted file, with optional timestep number.
+<DT><B>sdb [-t time] <I>file</I></B><DD>
+<P>Read an SDB (binary) formatted file, with optional timestep number.
(Default time is latest <CODE>datatime</CODE>, or 0.)</P>
-<DT><B>pb [-t time] <I>file</I></B><DD><P>Read a <CODE>.pb</CODE> (binary) particle file, with optional timestep number.
+<DT><B>pb [-t time] <I>file</I></B><DD>
+<P>Read a <CODE>.pb</CODE> (binary) particle file, with optional timestep number.
(Default time is latest <CODE>datatime</CODE>, or 0.)
A <CODE>.pb</CODE> file contains (all values 32-bit integer or 32-bit IEEE float):
<OL>
@@ -761,18 +890,24 @@ ending at the end of the file (i.e. there's no particle-count field).</LI>
Either big- or little-endian formats are accepted; the value of the
magic number determines endianness of all values in that file.</P>
-<DT><B>box[es] <I>....</I></B><DD><P>Draw a box, using any of the following formats:</P>
+<DT><B>box[es] <I>....</I></B><DD>
+<P>Draw a box, using any of the following formats:</P>
<P>
<DL>
<DT><B> <CODE>xmin ymin zmin xmax ymax zmax</CODE> </B><DD>
+
<DT><B> <CODE>xmin,xmax ymin,ymax zmin,zmax</CODE> </B><DD>
+
<DT><B> <CODE>xcen,ycen,zcen xrad,yrad,zrad</CODE> </B><DD>
+
<DT><B> <CODE>[-t time] [-n boxno] [-l level] xcen,ycen,zcen xrad,yrad,zrad </CODE> </B><DD>
+
</DL>
<CODE>level</CODE> determines color.</P>
-<DT><B><CODE>mesh</CODE> [<CODE>-t</CODE> <I>txno</I>] [<CODE>-c</CODE> <I>colorindex</I>] [<CODE>-s</CODE> <I>style</I>]</B><DD><P>Draw a quadrilateral mesh, optionally colored or textured.
+<DT><B><CODE>mesh</CODE> [<CODE>-t</CODE> <I>txno</I>] [<CODE>-c</CODE> <I>colorindex</I>] [<CODE>-s</CODE> <I>style</I>]</B><DD>
+<P>Draw a quadrilateral mesh, optionally colored or textured.
Following the <B>mesh</B> line, provide a line with the mesh dimensions:
nu nv</P>
<P>Following this comes the list of <I>nu</I>*<I>nv</I> mesh vertices,
@@ -786,55 +921,76 @@ specified, then two more fields give its u and v texture coordinates.</P>
<P>Options:
<DL>
-<DT><B> <CODE>-t</CODE> <I>txno</I> </B><DD><P>Apply texture number <I>txno</I> to surface.
+<DT><B> <CODE>-t</CODE> <I>txno</I> </B><DD>
+<P>Apply texture number <I>txno</I> to surface.
In this case, each mesh vertex should also include
u and v texture coordinates.</P>
-<DT><B> <CODE>-c</CODE> <I>colorindex</I> </B><DD><P>Color surface with color from
+<DT><B> <CODE>-c</CODE> <I>colorindex</I> </B><DD>
+<P>Color surface with color from
integer cmap entry <I>colorindex</I>.</P>
-<DT><B> <CODE>-s</CODE> <I>style</I> </B><DD><P>Drawing style:
+<DT><B> <CODE>-s</CODE> <I>style</I> </B><DD>
+<P>Drawing style:
<DL>
-<DT><B> <I>solid</I> </B><DD><P>filled polygonal surface (default)</P>
-<DT><B> <I>wire</I> </B><DD><P>just edges</P>
-<DT><B> <I>point</I> </B><DD><P>just points (one per mesh vertex)</P>
+<DT><B> <I>solid</I> </B><DD>
+<P>filled polygonal surface (default)</P>
+<DT><B> <I>wire</I> </B><DD>
+<P>just edges</P>
+<DT><B> <I>point</I> </B><DD>
+<P>just points (one per mesh vertex)</P>
</DL>
</P>
</DL>
</P>
-<DT><B><I>Xcen Ycen Zcen</I> ellipsoid <I>[options]... [transformation]</I></B><DD><P>Draw an ellipsoid, specified by:
+<DT><B><I>Xcen Ycen Zcen</I> ellipsoid <I>[options]... [transformation]</I></B><DD>
+<P>Draw an ellipsoid, specified by:
<DL>
-<DT><B> <CODE>Xcen Ycen Zcen</CODE> </B><DD><P>Center position in world coordinates</P>
-<DT><B> <CODE>-c</CODE> <I>colorindex</I> </B><DD><P>Integer color index (default -1 => white)</P>
-<DT><B> <CODE>-s</CODE> <I>style</I> </B><DD><P>Drawing style:
+<DT><B> <CODE>Xcen Ycen Zcen</CODE> </B><DD>
+<P>Center position in world coordinates</P>
+<DT><B> <CODE>-c</CODE> <I>colorindex</I> </B><DD>
+<P>Integer color index (default -1 => white)</P>
+<DT><B> <CODE>-s</CODE> <I>style</I> </B><DD>
+<P>Drawing style:
<DL>
-<DT><B> <I>solid</I> </B><DD><P>filled polygonal surface (default)</P>
-<DT><B> <I>plane</I> </B><DD><P>3 ellipses: XY, XZ, YZ planes</P>
-<DT><B> <I>wire</I> </B><DD><P>latitude/longitude ellipses</P>
-<DT><B> <I>point</I> </B><DD><P>point cloud: one per lat/lon intersection</P>
+<DT><B> <I>solid</I> </B><DD>
+<P>filled polygonal surface (default)</P>
+<DT><B> <I>plane</I> </B><DD>
+<P>3 ellipses: XY, XZ, YZ planes</P>
+<DT><B> <I>wire</I> </B><DD>
+<P>latitude/longitude ellipses</P>
+<DT><B> <I>point</I> </B><DD>
+<P>point cloud: one per lat/lon intersection</P>
</DL>
</P>
-<DT><B> <CODE>-r</CODE> <I>Xradius</I>[,<I>Yradius</I>,<I>Zradius</I>] </B><DD><P>Radius (for sphere) or semimajor axes (for ellipsoid)</P>
-<DT><B> <CODE>-n</CODE> <I>nlat[,nlon]</I> </B><DD><P>Number of latitude and longitude divisions.
+<DT><B> <CODE>-r</CODE> <I>Xradius</I>[,<I>Yradius</I>,<I>Zradius</I>] </B><DD>
+<P>Radius (for sphere) or semimajor axes (for ellipsoid)</P>
+<DT><B> <CODE>-n</CODE> <I>nlat[,nlon]</I> </B><DD>
+<P>Number of latitude and longitude divisions.
Relevant even for <I>plane</I> style, where they determine
how finely the polygonal curves approximate circles.
Default <I>nlon</I> = <I>nlat</I>/2 + 1.</P>
-<DT><B> <I>transformation</I> </B><DD><P>Sets the spatial orientation of the ellipsoid.
+<DT><B> <I>transformation</I> </B><DD>
+<P>Sets the spatial orientation of the ellipsoid.
May take any of three forms:
<DL>
-<DT><B> (nothing) </B><DD><P>If absent, the ellipsoid's
+<DT><B> (nothing) </B><DD>
+<P>If absent, the ellipsoid's
coordinate axes are the same as the world axes
for the group it belongs to.</P>
-<DT><B> 9 blank-separated numbers </B><DD><P>A 3x3 transformation matrix T from ellipsoid coordinates
+<DT><B> 9 blank-separated numbers </B><DD>
+<P>A 3x3 transformation matrix T from ellipsoid coordinates
to world coordinates, in the sense
Pworld = Pellipsoid * T + [Xcen, Ycen, Zcen].</P>
-<DT><B> 16 blank-separated numbers </B><DD><P>A 4x4 transformation matrix, as above but for the
+<DT><B> 16 blank-separated numbers </B><DD>
+<P>A 4x4 transformation matrix, as above but for the
obvious changes.</P>
</DL>
</P>
</DL>
</P>
-<DT><B>waveobj [-time <I>timestep</I>] [-static] [-texture <I>number</I>] [-c <I>colorindex</I>] [-s <I>style</I>] <I>file.obj</I></B><DD><P>Load a Wavefront-style .obj model. Material properties are
+<DT><B>waveobj [-time <I>timestep</I>] [-static] [-texture <I>number</I>] [-c <I>colorindex</I>] [-s <I>style</I>] <I>file.obj</I></B><DD>
+<P>Load a Wavefront-style .obj model. Material properties are
ignored; the surface is drawn in white unless <CODE>-c</CODE> <I>colorindex</I>
in which case it's drawn using that color-table color.
Also if <CODE>-texture</CODE> (alias <CODE>-tx</CODE>) is supplied,
@@ -844,14 +1000,20 @@ only if marked <CODE>-static</CODE>; otherwise it's displayed only
at the time given by <CODE>-time</CODE> <I>timestep</I> or by the most recent <I>datatime</I>.</P>
<P>A subset of the .obj format is accepted:
<DL>
-<DT><B>v <I>X Y Z</I></B><DD><P>-- vertex position</P>
-<DT><B>vt <I>U V</I></B><DD><P>-- vertex texture coordinates</P>
-<DT><B>vn <I>NX NY NZ</I></B><DD><P>-- vertex normal</P>
-<DT><B>f <I>V1 V2 V3 ...</I></B><DD><P>-- face, listing just position indices for each vertex.
+<DT><B>v <I>X Y Z</I></B><DD>
+<P>-- vertex position</P>
+<DT><B>vt <I>U V</I></B><DD>
+<P>-- vertex texture coordinates</P>
+<DT><B>vn <I>NX NY NZ</I></B><DD>
+<P>-- vertex normal</P>
+<DT><B>f <I>V1 V2 V3 ...</I></B><DD>
+<P>-- face, listing just position indices for each vertex.
The first <CODE>v</CODE> line in the .obj file has index 1, etc.</P>
-<DT><B>f <I>V1/T1 V2/T2 V3/T3 ...</I></B><DD><P>-- face,
+<DT><B>f <I>V1/T1 V2/T2 V3/T3 ...</I></B><DD>
+<P>-- face,
listing position and texture coordinates for each vertex of the face.</P>
-<DT><B>f <I>V1/T1/N1 V2/T2/N2 V3/T3/N3 ...</I></B><DD><P>-- face,
+<DT><B>f <I>V1/T1/N1 V2/T2/N2 V3/T3/N3 ...</I></B><DD>
+<P>-- face,
listing position, texture-coordinate, and normal indices for each vertex.</P>
</DL>
@@ -864,7 +1026,8 @@ then the given texture color multiplies or replaces the <CODE>-c</CODE> color,
according to the texture options.</P>
-<DT><B>tfm [camera] <I>numbers...</I></B><DD><P>Object-to-world transformation.
+<DT><B>tfm [camera] <I>numbers...</I></B><DD>
+<P>Object-to-world transformation.
May take 1, 6, 7, 9 or 16 numbers: either
<I>scalefactor</I> or
<I>tx ty tz rx ry rz </I>[it/scalefactor/]
@@ -884,18 +1047,23 @@ Try for example
</PRE>
</P>
-<DT><B>eval <I>command</I></B><DD><P>execute a Control Command.</P>
+<DT><B>eval <I>command</I></B><DD>
+<P>execute a Control Command.</P>
-<DT><B>feed <I>command</I></B><DD><P>Synonym for <CODE>eval</CODE>.</P>
+<DT><B>feed <I>command</I></B><DD>
+<P>Synonym for <CODE>eval</CODE>.</P>
-<DT><B>VIRDIR <I>command</I></B><DD><P>Synonym for <CODE>eval</CODE>.</P>
+<DT><B>VIRDIR <I>command</I></B><DD>
+<P>Synonym for <CODE>eval</CODE>.</P>
-<DT><B>filepath <I>path</I></B><DD><P>A colon-separated list of directories in which datafiles, color maps, etc.
+<DT><B>filepath <I>path</I></B><DD>
+<P>A colon-separated list of directories in which datafiles, color maps, etc.
will be searched for. If preceded with the <CODE>+</CODE> symbol,
this list will be appended to the current <I>filepath</I>.</P>
-<DT><B>polyorivar <I>indexno</I></B><DD><P>By default, when polygons are drawn, they're parallel to the screen plane --
+<DT><B>polyorivar <I>indexno</I></B><DD>
+<P>By default, when polygons are drawn, they're parallel to the screen plane --
simple markers for the points. It's sometimes useful to give each
polygon a fixed 3-D orientation (as for disk galaxies). To do this,
provide 6 consecutive data fields, representing two 3-D orthogonal unit
@@ -909,45 +1077,68 @@ yields non-circular polygonal disks. </P>
<P>If <CODE>polyorivar</CODE> is specified for the group, but some polygons should
still lie in the screen plane, use values <CODE>9 9 9 9 9 9</CODE> for those polygons.</P>
-<DT><B>texture [-aiAOlmnMDB] <I>txno file.sgi</I> </B><DD><P>
+<DT><B>vecvar <I>indexno</I></B><DD>
+<P>If enabled with the <CODE>vec</CODE> a.k.a. <CODE>vectors</CODE> control command,
+partiview can draw a vector, or an arrow, based from each point.
+A triple of consecutive data fields define the vector,
+whose length can be scaled with the <CODE>vecscale</CODE> command.</P>
+<P>Use the <CODE>vecvar</CODE> data command to specify the first (x component)
+of the triple of fields. </P>
+<P>See <CODE>partiview/data/vectordemo.cf</CODE> and <CODE>vector.speck</CODE> for an example.</P>
+
+<DT><B>texture [-aiAOlmnMDB] <I>txno file.sgi</I> </B><DD>
+<P>
<DL>
-<DT><B> -a(lpha) </B><DD><P>A single-channel image would normally be used as luminance data.
+<DT><B> -a(lpha) </B><DD>
+<P>A single-channel image would normally be used as luminance data.
With <CODE>-a</CODE>, the image is taken as opacity data instead
(GL_ALPHA texture format).</P>
-<DT><B> -i(ntensity) </B><DD><P>For 1- or 3-channel images, compute the intensity of each pixel
+<DT><B> -i(ntensity) </B><DD>
+<P>For 1- or 3-channel images, compute the intensity of each pixel
and use it to form an alpha (opacity) channel.</P>
-<DT><B> -A(dd) </B><DD><P>Use additive blending. This texture will add to, not obscure,
+<DT><B> -A(dd) </B><DD>
+<P>Use additive blending. This texture will add to, not obscure,
the brightness of whatever lies behind it (i.e. whatever is drawn later).</P>
-<DT><B> -O(ver) </B><DD><P>Use "over" compositing. This texture will obscure features lying
+<DT><B> -O(ver) </B><DD>
+<P>Use "over" compositing. This texture will obscure features lying
behind it according to alpha values at each point.</P>
-<DT><B> -M(odulate) </B><DD><P>Multiply texture brightness/color values by the colormap-determined
+<DT><B> -M(odulate) </B><DD>
+<P>Multiply texture brightness/color values by the colormap-determined
color of each particle.</P>
-<DT><B> -D(ecal) </B><DD><P>The textured polygon's color is determined entirely by the texture,
+<DT><B> -D(ecal) </B><DD>
+<P>The textured polygon's color is determined entirely by the texture,
suppressing any colormapped color.</P>
-<DT><B> -B(lend) </B><DD><P>Probably not very useful.</P>
+<DT><B> -B(lend) </B><DD>
+<P>Probably not very useful.</P>
</DL>
</P>
-<DT><B>texturevar <I>field</I></B><DD><P>If polygon-drawing and texturing are turned on, use the given
+<DT><B>texturevar <I>field</I></B><DD>
+<P>If polygon-drawing and texturing are turned on, use the given
<I>field</I> (datavar name or number) in each particle to select
which texture (if any) to draw on its polygon.</P>
<DT><B>coord <I>name ... 16 world-to-coord tfm floats (GL order)</I></B><DD>
-<DT><B>dataset <I>indexno datasetname</I></B><DD><P>Give names to multiple datasets in IEEEIO files (read with <CODE>ieee</CODE> command).
+
+<DT><B>dataset <I>indexno datasetname</I></B><DD>
+<P>Give names to multiple datasets in IEEEIO files (read with <CODE>ieee</CODE> command).
<I>indexno</I> is an integer, 0 being the first dataset.</P>
-<DT><B>datavar <I>indexno name [minval maxval]</I></B><DD><P>Name the variable in data field <I>indexno</I>. The first data field has
+<DT><B>datavar <I>indexno name [minval maxval]</I></B><DD>
+<P>Name the variable in data field <I>indexno</I>. The first data field has
<I>indexno</I> 0.
If provided, <I>minval maxval</I> supply the nominal range of that data variable;
some control commands (<CODE>lum</CODE>, <CODE>color</CODE>) need to know the range of data
values, and will use this instead of measuring the actual range.</P>
-<DT><B>datatime <I>time</I></B><DD><P>Label subsequent data with this <I>time</I> (a non-negative integer).</P>
+<DT><B>datatime <I>time</I></B><DD>
+<P>Label subsequent data with this <I>time</I> (a non-negative integer).</P>
-<DT><B>warp</B><DD><P>When 'warp' has been defined for a group,
+<DT><B>warp</B><DD>
+<P>When 'warp' has been defined for a group,
all its particles get their positions (re)computed according to
(a) the warp data-command's parameters, (b) the current time, (c) the particle's
initial position, and (d) maybe some attributes of each particle.</P>
@@ -959,47 +1150,62 @@ initial position, and (d) maybe some attributes of each particle.</P>
(time-independent) linear combinations of attribute values;</LI>
<LI> linear or polynomial extrapolation of the particle position with time,
with coefficients specified as triples of attributes</LI>
+<LI> for putting particles on epicycle-style orbits,
+resembling the motions of stars in a disk galaxy</LI>
</UL>
</P>
<P>Options to <CODE>warp</CODE> data command:
<DL>
-<DT><B>-p period0[f|s]</B><DD><P>"Rotation period". Sets timescale of motion, in frames (f) or seconds (s). </P>
+<DT><B>-p period0[f|s]</B><DD>
+<P>"Rotation period". Sets timescale of motion, in frames (f) or seconds (s). </P>
-<DT><B>-extrap coef0[,degree]]</B><DD><P>Extrapolate position with time. Velocity is given by attribute coef0 and the two attributes following it
+<DT><B>-extrap coef0[,degree]]</B><DD>
+<P>Extrapolate position with time. Velocity is given by attribute coef0 and the two attributes following it
(coef0 .. coef0+2), in the sense p = p_0 + [coef0 .. coef0+2] * (time/period0).
If <I>degree</I> given (default 1), uses 3*<I>degree</I> attributes as polynomial coefficients, as
p=p0+(t/period0)*field[coef0..coef0+2]+(t/period0)^2*[coef0+3..coef0+5]+...</P>
-<DT><B>-sheet ampl,xlength,zlength</B><DD><P>For disk galaxy style: Applies exponential sheet warp for disk lying in the X-Z plane.
+<DT><B>-sheet ampl,xlength,zlength</B><DD>
+<P>For disk galaxy style: Applies exponential sheet warp for disk lying in the X-Z plane.
Scale set by xlength and zlength, Y-displacement set by ampl.</P>
-<DT><B>-f fin,fout</B><DD><P>For disk-galaxy style: gives time range over which warp applies. </P>
+<DT><B>-f fin,fout</B><DD>
+<P>For disk-galaxy style: gives time range over which warp applies. </P>
-<DT><B>-z zerotime</B><DD><P>For disk galaxy style: sets time at which particles are in their original positions.</P>
+<DT><B>-z zerotime</B><DD>
+<P>For disk galaxy style: sets time at which particles are in their original positions.</P>
-<DT><B>-R rot[,drot]</B><DD><P>Disk galaxy style: Add constant to rotation angle.</P>
+<DT><B>-R rot[,drot]</B><DD>
+<P>Disk galaxy style: Add constant to rotation angle.</P>
-<DT><B>-T o2d</B><DD><P>Provide object-to-disk coordinate transform (in "disk" coordinates, the disk lies in X-Z plane).
+<DT><B>-T o2d</B><DD>
+<P>Provide object-to-disk coordinate transform (in "disk" coordinates, the disk lies in X-Z plane).
9 or 16 numbers.</P>
-<DT><B>-F d2o</B><DD><P>Provide disk-to-object transform. 9 or 16 numbers.</P>
+<DT><B>-F d2o</B><DD>
+<P>Provide disk-to-object transform. 9 or 16 numbers.</P>
-<DT><B>-r rcore[,transition][w]</B><DD><P>Disk galaxy style: set radius of rigidly-rotating inner region, and transition to constant-velocity region</P>
+<DT><B>-r rcore[,transition][w]</B><DD>
+<P>Disk galaxy style: set radius of rigidly-rotating inner region, and transition to constant-velocity region</P>
-<DT><B>-fix x,y,z[w]|radius[w]</B><DD><P>Disk galaxy style: Keep the given 3-D point, or a point at the given disk radius, fixed.
+<DT><B>-fix x,y,z[w]|radius[w]</B><DD>
+<P>Disk galaxy style: Keep the given 3-D point, or a point at the given disk radius, fixed.
E.g. track the sun.</P>
-<DT><B>-galaxy gorbcoef0</B><DD><P>Special disk galaxy style. Each star is on its own disk-galaxy-like orbit,
+<DT><B>-galaxy gorbcoef0</B><DD>
+<P>Special disk galaxy style. Each star is on its own disk-galaxy-like orbit,
with 8 orbital parameters given by 8 consecutive attributes starting with gorbcoef0.
See galaxyorbit.h (read the source).</P>
-<DT><B>-ride speckno</B><DD><P>Ride along with speckno'th particle in first loaded group (displace particles by the difference
+<DT><B>-ride speckno</B><DD>
+<P>Ride along with speckno'th particle in first loaded group (displace particles by the difference
between their computed orbit position and the ridden-on particle).</P>
</DL>
</P>
-<DT><B><I>Xpos Ypos Zpos Var0 .... </I></B><DD><P>These lines, with XYZ positions in the first 3 columns, will make up the bulk
+<DT><B><I>Xpos Ypos Zpos Var0 .... </I></B><DD>
+<P>These lines, with XYZ positions in the first 3 columns, will make up the bulk
of a typical dataset. The 4th and subsequent columns contain the values of the
datavariables as named with the <B>datavar</B> commands. Note that
data variable (field) numbers are 0-based.</P>
@@ -1020,28 +1226,40 @@ data variable (field) numbers are 0-based.</P>
<P>The particles read in have the following attributes:
<DL>
-<DT><B> id </B><DD><P>positive integer worldline index for single stars
+<DT><B> id </B><DD>
+<P>positive integer worldline index for single stars
(matching the id in the kira stream).
For non-leaf (center-of-mass) tree nodes, <CODE>id</CODE> is a
negative integer.</P>
-<DT><B> mass </B><DD><P>Mass, in solar mass units (see ``kira mscale'' control command).</P>
-<DT><B> nclump </B><DD><P>Number of stars in this particle's subtree.
+<DT><B> mass </B><DD>
+<P>Mass, in solar mass units (see ``kira mscale'' control command).</P>
+<DT><B> nclump </B><DD>
+<P>Number of stars in this particle's subtree.
1 for isolated stars, 2 for binaries, etc.</P>
-<DT><B> Tlog </B><DD><P>base-10 log of temperature (K)</P>
-<DT><B> Lum </B><DD><P>Luminosity in solar-mass units. (Note this is linear, not log luminosity.)</P>
-<DT><B> stype </B><DD><P>Stellar type code (small integer).
+<DT><B> Tlog </B><DD>
+<P>base-10 log of temperature (K)</P>
+<DT><B> Lum </B><DD>
+<P>Luminosity in solar-mass units. (Note this is linear, not log luminosity.)</P>
+<DT><B> stype </B><DD>
+<P>Stellar type code (small integer).
The [bracketed] message reported when picking (button-2 or p key)
on a star gives the corresponding human-readable stellar type too.</P>
-<DT><B> ismember </B><DD><P>Is this star still a member of (bound to) the cluster?</P>
-<DT><B> rootid </B><DD><P>id of root of subtree. For single stars, rootid = id.</P>
-<DT><B> treeaddr </B><DD><P>bit-encoded location of star in subtree.</P>
-<DT><B> ringsize </B><DD><P>0 for stars.
+<DT><B> ismember </B><DD>
+<P>Is this star still a member of (bound to) the cluster?</P>
+<DT><B> rootid </B><DD>
+<P>id of root of subtree. For single stars, rootid = id.</P>
+<DT><B> treeaddr </B><DD>
+<P>bit-encoded location of star in subtree.</P>
+<DT><B> ringsize </B><DD>
+<P>0 for stars.
For nonleaf nodes, this is the semimajor axis or instantaneous
separation (according to ``<CODE>kira sep</CODE>'').
This field isn't multiplied by the scale factor given in
<CODE>kira sep</CODE>; it gives the actual distance in kira units.</P>
-<DT><B> sqrtmass </B><DD><P>Square root of mass/Msun. Might be useful for luminosity scaling.</P>
-<DT><B> mu </B><DD><P>Mass ratio for center-of-mass nodes. Zero for stars.</P>
+<DT><B> sqrtmass </B><DD>
+<P>Square root of mass/Msun. Might be useful for luminosity scaling.</P>
+<DT><B> mu </B><DD>
+<P>Mass ratio for center-of-mass nodes. Zero for stars.</P>
</DL>
</P>
@@ -1055,13 +1273,16 @@ and log luminosity (initial range -4 to 6). Ranges may be changed
with the <CODE>kira hrdiag range</CODE> command or with keystrokes.</P>
<P>Keystroke commands in the H-R window:
<DL>
-<DT><B> b/B </B><DD><P>Adjust the (b)rightness (dot size) of the dots plotted for each star.
+<DT><B> b/B </B><DD>
+<P>Adjust the (b)rightness (dot size) of the dots plotted for each star.
Small b brightens (enlarges); capital B shrinks.</P>
-<DT><B> a/A </B><DD><P>Adjust (a)lpha (opacity) of dots plotted for each star.
+<DT><B> a/A </B><DD>
+<P>Adjust (a)lpha (opacity) of dots plotted for each star.
If many stars coincide in H-R, their brightnesses add.
Thus reducing opacity may help clarify the relative L-T space
densities, if there are many stars.</P>
-<DT><B> v/V </B><DD><P>Zoom out (v) or in (V) by 33%. The point under the cursor
+<DT><B> v/V </B><DD>
+<P>Zoom out (v) or in (V) by 33%. The point under the cursor
becomes the center of the view.</P>
</DL>
</P>
@@ -1073,20 +1294,24 @@ formatted data that have been read in with
the <CODE>kira</CODE> Data Command.
All control commands begin with <CODE>kira</CODE> too.
<DL>
-<DT><B> kira node {on|off|root} </B><DD><P>Show or hide center-of-mass nodes for multiple stars.
+<DT><B> kira node {on|off|root} </B><DD>
+<P>Show or hide center-of-mass nodes for multiple stars.
With <CODE>on</CODE>, show CM nodes for each level in a binary tree.
With <CODE>root</CODE>, show only the top-level CM node for each multiple.</P>
-<DT><B> kira ring {on|off|root} </B><DD><P>Show circles around multiple stars; <CODE>on</CODE> and <CODE>root</CODE> as above.</P>
+<DT><B> kira ring {on|off|root} </B><DD>
+<P>Show circles around multiple stars; <CODE>on</CODE> and <CODE>root</CODE> as above.</P>
-<DT><B> kira tree {on|off|cross|tick} [<I>tickscale</I>] </B><DD><P>Show lines connecting pairs of stars at each binary-tree level
+<DT><B> kira tree {on|off|cross|tick} [<I>tickscale</I>] </B><DD>
+<P>Show lines connecting pairs of stars at each binary-tree level
in a multiple group. With <CODE>cross</CODE>, also show a perpendicular
line -- a tick mark -- which crosses at the CM point,
and whose length is <CODE>tickscale</CODE> (default 0.5) times the
true separation of the pair.
With <CODE>tick</CODE>, just show the tick-mark with no connecting line.</P>
-<DT><B> kira size [sep|semi] [<I>ringscalefactor</I>] </B><DD><P>Determines 3-D size of circles when <CODE>kira ring on</CODE>.
+<DT><B> kira size [sep|semi] [<I>ringscalefactor</I>] </B><DD>
+<P>Determines 3-D size of circles when <CODE>kira ring on</CODE>.
With <CODE>kira size sep</CODE>, ring diameter is scalefactor * instanteous
separation. With <CODE>kira size semi</CODE>, ring radius is scalefactor * a
(the semimajor axis of the two-body system, or <CODE>|a|</CODE> for
@@ -1094,15 +1319,18 @@ hyperbolic orbits). Using <CODE>semi</CODE> gives typically more stable-looking
rings, though they will pop if they become marginally (un-)bound.
Default: <CODE>kira size semi 1.5</CODE>.</P>
-<DT><B>kira scale <I>ringscalefactor</I></B><DD><P>Synonym for <CODE>kira size</CODE> above.</P>
+<DT><B>kira scale <I>ringscalefactor</I></B><DD>
+<P>Synonym for <CODE>kira size</CODE> above.</P>
-<DT><B> kira span <I>minpix</I> <I>maxpix</I> </B><DD><P>Sets screen-space (pixel) size limits on rings.
+<DT><B> kira span <I>minpix</I> <I>maxpix</I> </B><DD>
+<P>Sets screen-space (pixel) size limits on rings.
They'll never get smaller than radius <I>minpix</I> nor larger than
<I>maxpix</I>, regardless of true 3-D size. Thus even vanishingly
tight binaries can always be visibly marked.
Default: <CODE>kira span 2 50</CODE>.</P>
-<DT><B> kira track <I>id</I>|on|off </B><DD><P>As particle <I>id</I> moves through time, move the viewpoint in the
+<DT><B> kira track <I>id</I>|on|off </B><DD>
+<P>As particle <I>id</I> moves through time, move the viewpoint in the
same way, so that (if you don't move the view by navigation)
the particle remains fixed in apparent position.
<CODE>kira track off</CODE> disables tracking, and <CODE>kira track on</CODE>
@@ -1112,7 +1340,8 @@ Use the <CODE>p</CODE> key or mouse button 2 to pick a particle
Transient center-of-mass nodes (shown if <CODE>kira node on</CODE>)
can be tracked while they exist.</P>
-<DT><B> kira mscale <I>massscalefactor</I>[!] </B><DD><P>Set/check the mass scale factor.
+<DT><B> kira mscale <I>massscalefactor</I>[!] </B><DD>
+<P>Set/check the mass scale factor.
Starlab dynamical mass values are multiplied by this factor
for reporting to the user. Normally <I>massscalefactor</I>
should equal the initial cluster mass in solar-mass units.
@@ -1122,7 +1351,8 @@ will be ignored unless <I>number</I> ends with an exclamation point (!).
So with no <CODE>!</CODE>, the user (or .cf script) provides a default value;
use <CODE>!</CODE> to override the original mass scale.</P>
-<DT><B> kira int <I>seldest</I> [= <I>selsrc</I>] </B><DD><P>Track interactions between particles.
+<DT><B> kira int <I>seldest</I> [= <I>selsrc</I>] </B><DD>
+<P>Track interactions between particles.
As the cluster evolves, whenever any star matching
selection-expression <I>selsrc</I> encounters (is a member of
the same kira tree as) another particle, then the other
@@ -1134,40 +1364,54 @@ Otherwise, only stars that encounter members of the initial
<I>selsrc</I> set become members of the <I>seldest</I> set.
Example:
<DL>
-<DT><B> click on some star </B><DD><P>The clicked-on star(s) become members of the <CODE>pick</CODE> set.</P>
-<DT><B> sel x = pick </B><DD><P>Save a copy in the new set named <CODE>x</CODE>.</P>
-<DT><B> kira int x </B><DD><P>Accumulate encounters in the set <CODE>x</CODE>.</P>
-<DT><B> emph x </B><DD><P>Increase brightness of members of <CODE>x</CODE>.</P>
-<DT><B> kira trail x </B><DD><P>Extend trails from these set members.</P>
+<DT><B> click on some star </B><DD>
+<P>The clicked-on star(s) become members of the <CODE>pick</CODE> set.</P>
+<DT><B> sel x = pick </B><DD>
+<P>Save a copy in the new set named <CODE>x</CODE>.</P>
+<DT><B> kira int x </B><DD>
+<P>Accumulate encounters in the set <CODE>x</CODE>.</P>
+<DT><B> emph x </B><DD>
+<P>Increase brightness of members of <CODE>x</CODE>.</P>
+<DT><B> kira trail x </B><DD>
+<P>Extend trails from these set members.</P>
</DL>
</P>
-<DT><B> kira trail <I>selexpression</I>|off </B><DD><P>Leave trails behind particles selected by <I>selexpression</I>
+<DT><B> kira trail <I>selexpression</I>|off </B><DD>
+<P>Leave trails behind particles selected by <I>selexpression</I>
(see the <CODE>sel</CODE> command). As (dynamical) time passes, for each
display update, one sample point is added to the trail
for each selected particle. (If you reverse the direction of
time, the trails will fold back on themselves.) Some examples:
<DL>
-<DT><B> kira trail all </B><DD><P>Makes trails grow behind all particles
+<DT><B> kira trail all </B><DD>
+<P>Makes trails grow behind all particles
(including CM nodes, if they're displayed)</P>
-<DT><B> kira trail pick </B><DD><P>Clicking on a star will make a trail grow behind it.
+<DT><B> kira trail pick </B><DD>
+<P>Clicking on a star will make a trail grow behind it.
If several stars are within picking range (under the cursor),
trails will grow behind each of them.</P>
-<DT><B> thresh -s big mass > 1.5 </B><DD><P>threshold when masses are larger than 1.5</P>
-<DT><B> kira trail big </B><DD><P>These two commands (a) select all stars exceeding
+<DT><B> thresh -s big mass > 1.5 </B><DD>
+<P>threshold when masses are larger than 1.5</P>
+<DT><B> kira trail big </B><DD>
+<P>These two commands (a) select all stars exceeding
1.5 solar masses and (b) extend trails behind them.</P>
</DL>
</P>
-<DT><B> kira trail clear </B><DD><P>Erase current trails, but let them continue to accumulate
+<DT><B> kira trail clear </B><DD>
+<P>Erase current trails, but let them continue to accumulate
as time passes.</P>
-<DT><B> kira maxtrail <I>nsamples</I> </B><DD><P>Set how many time-points are kept for each particle's trail,
+<DT><B> kira maxtrail <I>nsamples</I> </B><DD>
+<P>Set how many time-points are kept for each particle's trail,
initially 50.</P>
-<DT><B> kira hrdiag on|off </B><DD><P>toggle to turn HD Diagram on or off. Initially off.</P>
-<DT><B> kira hrdiag range <I>logTleft logTright logLbottom logLtop</I> </B><DD><P>set limits on the HD Diagram axes.</P>
+<DT><B> kira hrdiag on|off </B><DD>
+<P>toggle to turn HD Diagram on or off. Initially off.</P>
+<DT><B> kira hrdiag range <I>logTleft logTright logLbottom logLtop</I> </B><DD>
+<P>set limits on the HD Diagram axes.</P>
</DL>
</P>
diff --git a/doc/partiview-5.html b/doc/partiview-5.html
index a000efd377c3b0a13da08369d546be4e35bafae8..bd0d86720250c4da6c9bad921d98d1854733da8e 100644
--- a/doc/partiview-5.html
+++ b/doc/partiview-5.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Viewing Window Keyboard Shortcuts </TITLE>
<LINK HREF="partiview-6.html" REL=next>
<LINK HREF="partiview-4.html" REL=previous>
diff --git a/doc/partiview-6.html b/doc/partiview-6.html
index 35769962e4c9062de7b325b1fc9b59e8e7412ba1..0b842f1b58e47fc749d6194ab932d1ae4b8e4974 100644
--- a/doc/partiview-6.html
+++ b/doc/partiview-6.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Partiview and NEMO</TITLE>
<LINK HREF="partiview-7.html" REL=next>
<LINK HREF="partiview-5.html" REL=previous>
diff --git a/doc/partiview-7.html b/doc/partiview-7.html
index ede8bdc284fb40f5802818cfb36f8562751798c7..02695e07084e8f1ee6c4ad22afd5932559da891b 100644
--- a/doc/partiview-7.html
+++ b/doc/partiview-7.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Tips</TITLE>
<LINK HREF="partiview-8.html" REL=next>
<LINK HREF="partiview-6.html" REL=previous>
diff --git a/doc/partiview-8.html b/doc/partiview-8.html
index b4703a416e41abc6742c1df8904a1c10b58ca515..60cd3b53ba88e961dff9339b34d4746a93e7a380 100644
--- a/doc/partiview-8.html
+++ b/doc/partiview-8.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Bugs, Features and Limitations</TITLE>
<LINK HREF="partiview-9.html" REL=next>
<LINK HREF="partiview-7.html" REL=previous>
diff --git a/doc/partiview-9.html b/doc/partiview-9.html
index eec8501335d038ff8da60747d82cafe9bb0e42c2..3bafb74e30f5d38bae729fbfd3a2687bf783af16 100644
--- a/doc/partiview-9.html
+++ b/doc/partiview-9.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir): Glossary</TITLE>
<LINK HREF="partiview-8.html" REL=previous>
<LINK HREF="partiview.html#toc9" REL=contents>
diff --git a/doc/partiview.html b/doc/partiview.html
index b2c0b6c9902396dd794eaca9d906299bae18a0e7..b010fecf8112abe8e6340e3578a4761720e9c275 100644
--- a/doc/partiview.html
+++ b/doc/partiview.html
@@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
- <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.21">
+ <META NAME="GENERATOR" CONTENT="LinuxDoc-Tools 0.9.66">
<TITLE> Partiview (PC-VirDir)</TITLE>
<LINK HREF="partiview-1.html" REL=next>
diff --git a/doc/partiview.ps.gz b/doc/partiview.ps.gz
index 8fb90407a882de8cef35c98f8345c49b2a84217f..8e4cd40d992fe1b329a355a32c205edb67beb228 100644
Binary files a/doc/partiview.ps.gz and b/doc/partiview.ps.gz differ
diff --git a/doc/partiview.sgml b/doc/partiview.sgml
index 0584b710f426d814aa8067523a95e264ce3c54d2..7944a45f90646f5da57d8012328bd3ddb4b7502f 100644
--- a/doc/partiview.sgml
+++ b/doc/partiview.sgml
@@ -31,6 +31,10 @@
<!--
$Log$
+ Revision 1.27 2011/12/07 16:24:42 slevy
+ Describe vecvar command.
+ Update derived files.
+
Revision 1.26 2010/04/27 23:47:58 slevy
Fix bugs...
@@ -2000,6 +2004,19 @@ yields non-circular polygonal disks.
If <tt/polyorivar/ is specified for the group, but some polygons should
still lie in the screen plane, use values <tt/9 9 9 9 9 9/ for those polygons.
+<tag>
+vecvar <it/indexno/
+</tag>
+If enabled with the <tt/vec/ a.k.a. <tt/vectors/ control command,
+partiview can draw a vector, or an arrow, based from each point.
+A triple of consecutive data fields define the vector,
+whose length can be scaled with the <tt/vecscale/ command.
+<p>
+Use the <tt/vecvar/ data command to specify the first (x component)
+of the triple of fields.
+<p>
+See <tt>partiview/data/vectordemo.cf</tt> and <tt>vector.speck</tt> for an example.
+
<tag>
texture [-aiAOlmnMDB] <it/txno file.sgi/
</tag>
@@ -2083,6 +2100,8 @@ There are several (mutually exclusive) kinds of warping available:
(time-independent) linear combinations of attribute values;
<item> linear or polynomial extrapolation of the particle position with time,
with coefficients specified as triples of attributes
+ <item> for putting particles on epicycle-style orbits,
+ resembling the motions of stars in a disk galaxy
</itemize>
Options to <tt/warp/ data command: