Newer
Older
<!doctype linuxdoc system>
<!--
Changelog:
2000-09-25 created the changelog after a week of initial editing PJT
2000-10-10 made consistent with VERSION 0.1 release PJT
2000-12-28 document new movie features for the new CVS version
and lotsa more commands described now PJT
-->
<article>
<!-- Title information -->
<title> Partiview (PC-VirDir)
<author> Peter Teuben, Stuart Levy
<date> 19 March 2001
<abstract>
This document helps you installing and running the development version
of partiview.
Quite a few things in this manual have not been fleshed
out, in particular the detailed description of all the commands.
</abstract>
<!-- Table of contents -->
<toc>
<!-- Begin the document -->
<!--------------------------------------------------------------------------- -->
This assumes you have the October 2000 release (version 0.1 or later) of
<bf/partiview/, not the earlier "<bf/gview/" release that was described
in earlier versions of this document. We keep copies of some support
<htmlurl url="http://www.astro.umd.edu/nemo/amnh"
name="http://www.astro.umd.edu/nemo/amnh"> website. Note that
this current development release is only documented for work under Linux,
although we expect it to work for at least SGI and maybe Solaris too.
<sect1> MESA/OpenGL
<p>
First make sure <tt/Mesa/ is installed, for <tt/redhat6.2/
there are rpm files
available. Check if you have the following:
<tscreen><code>
% rpm -qa | grep Mesa
Mesa-3.2-2
Mesa-devel-3.2-2
% rpm -i Mesa-3.2-2.i686.rpm Mesa-devel-3.2-2.i686.rpm
You should have both installed. Some packages will use <tt/libMesaGL/, others
<tt/libGL/. The <tt/configure/ script (see below)
should take care of the two possible options.
<p>
Homepage: <htmlurl url="http://mesa3d.sourceforge.org"
name="http://mesa3d.sourceforge.org">
<p>
Redhat packages: (part of powertools I believe)
<sect1> FLTK
<p>
Also make sure <tt/fltk/ is installed. If you got my version, do this (as
root)
% locate libfltk.a
% locate Fl_Slider.h
</code></tscreen>
(you only need it if you want to recompile the program at some point,
not if you just want to run it)
<p>
Homepage: <htmlurl url="http://www.fltk.org/"
name="http://www.fltk.org/">
<p>
Redhat packages: <htmlurl url="http://www.cs.cornell.edu/nogin/RPM/fltk-devel.html"
name="http://www.cs.cornell.edu/nogin/RPM/fltk-devel.html">
<sect1> partiview
<p>
Extract the tarball, and install the program from within the
<tt/src/ directory:
% tar zxf partiview-0.5.tar.gz
% cd partiview-0.5/src
% make depend (might need to make new local dependancies)
% make partiview (should not have to edit Makefile anymore)
Since <tt/partiview-0.3/ is under CVS control, and occasionally we
will stamp out a new release when we deem it stable. Anonymous CVS may also
be offered, but this is not currently enabled. Currently the
CVS repository machine is
<tt/akash.astro.umd.edu/ and you will need to setup your developers account with
Peter (<tt/teuben@astro.umd.edu/). Here's a sample session with some commonly
used CVS commands:
<tscreen><code>
setenv CVSROOT :pserver:pteuben@akash.astro.umd.edu:/home/cvsroot
setenv CVS_RSH ssh (not needed for pserver access though)
cvs login (only needed once, and only for pserver type access)
mkdir ~/cvsstuff
cd ~/cvsstuff
cvs checkout partiview # get a new local sandbox to work in, or
cvs -n -q update partiview # check if others had made any changes
cvs update partiview # if so, update your sandbox and/or resolve conflicts
emacs partibrains.c # edit some files
./partiview # test the program
emacs partipanel.cc # edit another file
make all # check if it still compiles
cvs update # if so, update your sandbox again, resolve conflicts
cvs release partiview # if you want to release and remove this sandbox
<!--------------------------------------------------------------------------- -->
Here is the directory structure, as per version 0.1:
<p>
<tscreen><verb>
partiview/ root directory
partiview/src source code
partiview/data sample datafiles (e.g. Hipparcos Bright Star Catalogue)
partiview/doc manual (sgml, and derived html, txt, ps/dvi)
partiview/nemo NEMO specific converters/code
partiview/starlab STARLAB specific converters/code
partiview/windows windows executables/support (old)
</verb></tscreen>
<sect> Running the program
<p>
First we describe a simple example how to run <tt/partiview/ with a supplied sample
dataset. Then we describe the different windows that <tt/partiview/ is made up of, and
the different commands and keystrokes it listens to.
<sect1> Example 1: Hipparcos Bright Star Catalogue 3-D viewing
Start the program using one of the sample "speck" files in the
% cd partiview/data
and this should come up with a display familiar to most of us who
watch the skies. You should probably enlarge the
window a bit. Mine comes up in roughly a 300 by 300 display window,
which may be a bit small (certainly on my screen :-)
Hit the TAB key to bring focus to the (one line) command window inbetween
the log screen (top) and viewing screen (bottom). Type the commands
<tscreen><code>
fov 50 (field of view 50 degrees)
jump 0 0 0 80 70 60 (put yourself in the origin
and it should give another nice comfy view :-) If you ever get lost, use
the <tt/jump/ command to go back to a known position and/or viewing
<figure loc="tbp">
<img src="pv1.gif">
<caption>partiview view</caption>
</figure>
<p>
Now play with the display, use the 't', 'r', 'f' and 'o' keys in the viewing
window and use the
left and mouse buttons down to (carefully) move around a bit, and make
yourself comfortable with moving around. Using the 't' button you get
some idea of the distance of the stars by moving back and forth a little
(the parallax trick). In fact, if you 't' around a little bit, you may
see a green line flashing through the display. This is one of the RGB
(xyz) axes attached to the (0,0,0) [our sun] position. You should see
Procyon and Sirius exhibit pretty large parallaxes, but Orion is pretty
steady since it is several hundred parsecs away.
If you move the right mouse button you will zoom in/out and
should see our Sun flash by with the red-green-blue axes.
<p>
The RGB axes represent the XYZ axes in a cartesian system. For the Hipparcos
data the X (red) axis points to RA=0h, Y (green) axis to RA=6h, both in the equatorial
plane, and the Z (blue) axis points to the equatorial north pole.
Try and use the middle mouse button (or the 'p' key) to click on Sirius
or Procyon, and see if you can get it to view its properties. Now use
the 'P' key to switch center to rotation to that star. Sirius is
probably a good choice. Move around a bit, and try and get the sun and orion
in the same view :-)
<p>
[NOTE: these Hipparcos data do not have reliably distance above
100-200 pc, so Orion's distances are probably uncertain to 30%]
<p>
A little bit on the types of motion, and what the mouse buttons do
<tscreen><code>
| left middle right
| Button-1 Button-2 Button-3 Shift Button-1
------------------------------------------------------------------------------------
r (rotate) | rotate X/Y 'pick' rotate Z (+bug?) translate
t (translate) | translate 'pick' zoom
</code></tscreen>
The point of origin for rotations can be changed with the 'P' button.
First you can try and pick ('p' or Button-2) a point, and if found,
hit 'P' to make this point the new rotation center default.
<tscreen><code>
red = X axis
green = Y axis
blue = Z axis
</code></tscreen>
<sect1> Top Row
<p>
The top row, from left to right, shows the following buttons:
<p>
<descrip>
<tag> More </tag>
Pulldown g1, g2, ... (or whichever group)
is the currently selected group. See <tt/object/ 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.
Pulldown to select fly/orbit/rot/tran, which can also be activate
by pressing the f/o/r/t keys inside the viewing window.
<tag> point </tag>
Toggle to turn the points on/off. See also the <tt/points/ command.
Toggle to turn polygons on/off. See also the <tt/polygon/ command.
Toggle to turn labels on/off. See also the <tt/label/ command.
Toggle to turn textures on/off. See also the <tt/texture/ command.
Toggle to turn boxes on/off. See also the <tt/boxes/ command.
<tag> #.### </tag>
The current displayed value of <tt/logslum lum/ (see below)
Slider controlling a <bf/datavar/ variable (the one selected as
luminosity)
</descrip>
<sect1> Group row (optional)
<p>
When more than one group has been activated (groups of particles or objects
can have their own display properties, and be turned on and off at will),
a new Group Row will appear as the 2nd row.
<p>
Left-clicking (button 1) on a button toggles the display of that group;
right-clicking (button 3) enables display of the group,
and also selects it as the current group for GUI controls and
text commands.
<sect1> Time Animation rows (Optional)
For time-dependent data, the third and fourth row from
the top control the currently displayed data-time.
This time-control bar is only visible when the object
has a nonzero time range.
<descrip>
<tag> T </tag>
Shows the current time (or offset from the tripmeter).
The absolute time is the sum of the <bf/T/ and <bf/+/ fields.
Both are editable.
See also the <tt/step/ control command.
<tag>trip </tag>
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.
<tag>back </tag>
Press to return to reference time (sets T to 0).
<tag> + </tag>
Current last time where tripmeter was set. You can reset to
the first frame with the command <tt/step 0/
<tag> dial </tag>
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 * <it/speed/ in data time units.
<tag> |< </tag>
<tag> >| </tag>
Step time backwards or forwards by 0.1 * <it/speed/ data time units.
See also the <tt/</ and <tt/>/ keyboard shortcuts.
<tag> << </tag> <p>
<tag> >> </tag> toggle movie move forwards in time
Toggle animating backwards or forwards in time, by
1 * <it/speed/ data time units per real-time second.
See also the <tt/{/, <tt/~/, and <tt/}/ keyboard shortcuts.
<tag> #.#### </tag>
(Logarithmic) value denoting <it/speed/ of animation.
See also the <tt/speed/ control command.
The fifth (or 4th or 3rd, depending if Group and/or Time rows are present)
row from the top controls loading and playing sequences of moving through space.
<p>
<descrip>
<tag> Load... </tag>
Brings up a filebrowser to load a <bf/.wf/ path file. This is a file with on each
line 7 numbers: xyz location, RxRyRz viewing direction, and FOV (field of view).
The <tt/rdata/ command loads such path files too.
Play the viewpoint along the currently loaded path,
as the <tt/play/ command does.
Right-click for a menu of play-speed options.
Step through camera-path frames.
See also <tt/frame/ control command.
Slides through camera path, and displays current frame.
The third window from the top contains a logfile of past commands
and responses to them, and can be resized by dragging the bar between
command window and viewing window.
The Logfile window also has a scroll bar on the left. You can
direct the mouse to any previous command, and it will show up in the
command window. Using the arrow keys this command can then be edited.
The Command window is a single line entry window, in which Control
Commands can be given. Their responses appear in the Logfile
window and on the originating console. (unlike Data Commands,
which show no feedback).
The Up- and Down-arrow keys (not those on the keypad) scroll through
previous commands, and can be edited using the arrow keys and a subset
of the emacs control characters.
The (OpenGL) Viewing window is where all the action occurs. Typically
this is where you give single keystroke commands and/or move the mouse
for an interactive view of the data. It can be resized two ways:
either by resizing the master window, or by picking up the separator
between Viewing window and Command window above.
<sect1> Example 2: a (starlab) animation
<p>
Setting up a small animation in for example Starlab can be done quite simply as follows:
<tscreen><code>
mkplummer -i -n 20 | mkmass -l 0.5 -u 10.0 | scale -s | kira -d 2 -D x10 > run1
(lots of output from kira will still appear on the screen)
partiview run1.cf
cat run1.cf
eval every
eval lum mass 0 0.01
eval psize 100
eval cment 1 1 .7 .3
eval color clump exact
</code></tscreen>
Alternatively, if you had started up partiview without any arguments, the following
Control Command (see below) would have done the same
<tscreen><code>
<sect1> Example 3: stereo viewing
<p>
The 's' key within the viewing window toggles stereo viewing. By default each
object is split in a blue and a red part, that should be viewed with a pair
of red(left)/blue(right) glasses. Red/green glasses will probably work too.
See <bf/stereo/ and <bf/focallen/ in the View Commands section.
<!--
-->
<p>
<sect> Commands
<p>
There are two types of commands in <tt/partiview/:
Control Commands and Data Commands.
Probably the most important difference between the two is that Control
Commands return feedback to the user, whereas Data Commands
are interpreted without comment. The command window expects
to receive Control Commands. However, it is possible to
enter a Data Command where a Control Command is expected,
using the <tt/add/ command prefix. (Likewise, a control command
may be given where data is expected, using the <tt/eval/ prefix.)
<!--
Before we explain the two types of Commands in
more detail, a few other concepts are needed:
-->
<!--
-->
<p>
<sect1> Control Commands
(see partibrains.c::specks_parse_args)
<p>
Control Commands are accepted in the Command window, and in some other contexts.
Generally, <tt/partiview/ gives a response to every Control Command,
reporting the (possibly changed) status.
Typically, if parameters are omitted, the current state is reported.
<p>
Some commands apply to particles in the current group (see Object group commands);
others affect global things, such as time or display settings.
<p>
Data Commands can also be given, if prefixed with <tt/add/.
<sect1>I/O commands
<p>
read <it/specks-file/
Read a file containing Data Commands (typical suffix <tt/.cf/ or <tt/.speck/).
NOTYET (would read a file containing control commands)
async <it/unix-command/
Run an arbitrary unix command (invoked via /bin/sh) as a subprocess of <tt/partiview/.
Its standard output is interpreted as a stream of control commands.
Thus <tt/partiview/ can be driven externally, e.g. to record an animation
(using the <tt/snapshot/ command), or to provide additional GUI controls.
Several <tt/async/ commands can run concurrently.
add <it/data-command/
Enter a Data Command where a Control Command is expected,
e.g. in the text input box. For example,
<verb>
add 10 15 -1 text blah
</verb>
adds a new label "blah" at 10 15 -1, or
<verb>
add kira myrun.out
</verb>
loads a starlab output file.
eval <it/control-command/
Processes that control command just as if the <tt/eval/ prefix weren't there.
Provided for symmetry: wherever either a control command or a data command
is expected, entering <tt/eval/ <it/control-command/ ensures that it's
add filepath (data-command)
Determines the list of directories where all data files, color maps, etc.
are sought. See the <tt/filepath/ entry under
<!-- ref id="datacommands" name="Data Commands" --> Data Commands.
<sect1>Object group commands
<p>
<tt/Partiview/ can load multiple groups of particles,
each with independent display settings, colormaps, etc.
When more than one group is loaded, the Group Row appears on the GUI,
with one toggle-button for each group. Toggling the button turns
display of that group on or off. Right-clicking turns the group unconditionally on,
and selects that group as the current one for other GUI controls.
<p>
Many Control Commands apply to the <it/currently selected/ group.
Groups always have names of the form g<it/N/ for some small positive <it/N/;
each group may also have an alias.
g<it/N/ </tag>
Select group g<it/N/. Create a new group if it doesn't already exist.
g<it/N/=<it/alias/ </tag>
Assign name <it/alias/ to group g<it/N/.
object <it/objectname/
Likewise, select object <it/objectname/, which may be either an alias name
g<it/N/ <it/control-command/
object <it/objectname/ <it/control-command/
Either form may be used as a <it/prefix/ to any control command
to act on the specified group, e.g. <tt/object fred poly on/
gall <it/control-command/
Invoke the given <it/control-command/ in all groups.
For example, to turn display of group 3 on and all others off, use:
<tscreen><verb>
gall off
g3 on
</verb></tscreen>
Enable display of currently selected group (as it is by default).
Turn off display of current group.
</descrip>
<sect1>View commands
View commands affect the view; they aren't specific to data groups.
fov <it/float/
Angular field of view (in degrees) in Y-direction.
cen[ter] <it/X Y Z/ [<it/RADIUS/]
<!-- int[erest] <it/X Y Z/ [<it/RADIUS/] -->
Set point of interest. This is the center of rotation in
<tt/[o]rbit/ and <tt/[r]otate/ modes. Also, in <tt/[o]rbit/ mode,
translation speed is proportional to the viewer's distance from this point.
The optional <it/RADIUS/ (also set by <tt/censize/) determines the size
of the marker crosshair, initially 1 unit.
censize [<it/RADIUS/]
Set size of point-of-interest marker.
<p>
where <it/(also)/ w
Report the 3-D camera position and forward direction vector.
clip <it/NEAR/ <it/FAR/
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
may appear to blink if the <it/FAR//<it/NEAR/ ratio exceeds 10000 or so.
To set the far clip range without changing the near, use a non-numeric
near clip value, e.g. <tt/clip - 1000/.
<!--
jump [<it/X Y Z/] [<it/Rx Ry Rz/]
Get or set the current position (XYZ) and/or viewing (RxRyRz) angle.
Read a Wavefront (<tt/.wf/) file describing a path through space.
Play the currently loaded (from <tt/readpath//<tt/rdata/) camera animation
path, at <it/speed/ 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 <it/speed/-th frame, without regard to real
time.
Get or set the current frame the <it/frameno/-th.
<tag>
<tag>
update
</tag>
Ensures the display is updated, as before taking a snapshot.
Probably only useful in a stream of control commands from an <tt/async/
subprocess.
<tag>
bgcolor <it/R G B/
</tag>
Set window background color (three R G B numbers or one grayscale value).
cen[ter] [<it/X Y Z/ [<it/RADIUS/]]
int[erest] [<it/X Y Z/ [<it/RADIUS/]]
Set point of interest. This is the center of rotation in
<tt/[o]rbit/ and <tt/[r]otate/ modes. And, in <tt/[o]rbit/ mode,
translation speed is proportional to the viewer's distance from this point.
The optional <it/RADIUS/ (also set by <tt/censize/) determines the size
of the marker crosshair, initially 1 unit.
focallen <it/distance/
Focal length: distance from viewer to a typical object of interest.
This affects stereo display (see below) and navigation: the speed of
motion in <tt/[t]ranslate/ and <tt/[f]ly/ modes is proportional to this
distance.
stereo [on|off|redcyan|glasses] [<it/separation/]
Stereo display. Also toggled on/off by typing <tt/'s'> key in graphics window.
Where hardware allows it, <tt/stereo glasses/ selects
CrystalEyes-style stereo. All systems should be capable of
<tt/stereo redcyan/, which requires wearing red/green or red/blue glasses.
Useful <it/separation/ values might be 0.02 to 0.1, or -0.02 to -0.1 to swap
eyes. See also <tt/focallen/ command, which gives the distance to
a typical object of interest: left- and right-eye images of an object
at that distance will coincide on the screen.
<tag>
snapset <it/FILESTEM/ [<it/FRAMENO/]
</tag>
Set parameters for future <tt/snapshot/ commands.
<it/FILESTEM/ may be a printf format string with frame number as
argument, e.g. <tt>snapset pix/%04d.ppm</tt>, generating image names
of <tt>pix/0000.ppm</tt>, <tt>pix/0001.ppm</tt>, etc.
If <it/FILESTEM/ contains no % sign, then <tt/.%03d.ppm.gz/ is
appended to it, so <tt>snapset ./pix/fred</tt>
yields snapshot images named <tt>./pix/fred.000.ppm.gz</tt> etc.
<p>
Frame number <it/FRAMENO/ (default 0) increments with each snapshot taken.
<p>
snapshot [<it/FRAMENO/]
Capture a snapshot image of the current view.
Use <tt/snapset/ to specify the output image name.
Default format is <tt/snap.%03d.tif/.
<tt/Partiview/ generally invokes the ImageMagick program <tt/convert(1)/,
which must be installed and be on the user's $PATH. <tt/Convert/ determines
the type of image (jpeg, sgi, bmp, etc.) based on the file suffix.
<tt/Convert/ is not needed if the <tt/snapset/ <it/FILESTEM/ ends in
<tt/.ppm.gz/ (invokes gzip rather than convert) or <tt/.ppm/
(no external program required).
</descrip>
<sect1>Particle Display Commands
<p>
These commands affect how particles (in the current group) are
displayed.
<descrip>
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
psize <it/scalefactor/
</tag>
All particle luminosities (as specified by <tt/lum/ command)
are scaled by the product of two factors:
a <it/lumvar/-specific factor given by <tt/slum/,
and a global factor given by <tt/psize/.
So the intrinsic brightness of a particle is
<it/value-specified-by-/<tt/lum/
* <it/slum-for-current-lumvar/
* <it/psize-scalefactor/.
<tag>
slum <it/slumfactor/
</tag>
Data-field specific luminosity scale factor, for current choice of
<it/lumvar/ as given by the <tt/lum/ command.
A <it/slumfactor/ is recorded independently for each data field, so
if data fields <tt/mass/ and <tt/energy/ were defined, one might say
<tscreen><verb>
lum mass
slum 1000
lum energy
slum 0.25
</verb></tscreen>
having chosen each variable's <it/slumfactor/ for useful display,
and then freely switch between <tt/lum mass/ and <tt/lum energy/
without having to readjust particle brightness each time.
<!-- Just describe "slum"
<tag>
scale-lum
</tag>
-->
<tag>
ptsize <it/minpixels/ <it/maxpixels/
</tag>
<!-- DEPRECATED COMMAND
<tag>
pointsize
</tag>
-->
<tag>
polysize [on|off] [a|s|r]
</tag>
<tag>
polylum
</tag>
<tag>
polyminpixels
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
Specify how particles are colored.
Generally, a linear function of some data field of each particle
becomes an index into a colormap (see <tt/cmap/, <tt/cment/).
<descrip>
<tag> color <it/colorvar/ [<it/minval maxval/] </tag>
Use data field <it/colorvar/ (either a name as set by <tt/datavar/
or a 0-based integer column number) to determine color.
Map <it/minval/ to color index 1, and <it/maxval/ to
the next-to-last entry in the colormap (<it/Ncmap-2/).
The 0th and last (<it/Ncmap-1/) colormap entry are used for
out-of-range data values.
If <it/minval/ and <it/maxval/ are omitted, the actual range of
values is used.
<tag> color <it/colorvar/ exact [<it/baseval/] </tag>
Don't consider field <it/colorvar/ as a continuous variable;
instead, it's integer-valued, and mapped one-to-one with
color table slots. Data value <it/N/ is mapped to
color index <it/N+baseval/.
<tag> color <it/colorvar/ -exact </tag>
Once the <tt/exact/ tag is set, it's sticky. To interpret
it as a continuous, scalable variable again, use <tt/-exact/.
<tag> color const <it/R G B/ </tag>
Show all particles as color <it/R G B/, each value in range 0 to 1,
independent of any data fields.
</descrip>
Specify how particles' intrinsic luminosity is computed:
a linear function of some data field of each particle.
<descrip>
<tag> lum <it/lumvar/ [<it/minval maxval/] </tag>
Map values of data field <it/lumvar/ (<tt/datavar/ name or
field number) to luminosity.
The (linear) mapping takes field value <it/minval/ to
luminosity 0 and <it/maxval/ to luminosity 1.0.
<p>
If <it/minval/ and <it/maxval/ are omitted,
the actual range of values is mapped to the luminosity range
0 to 1.
<p>
Note that the resulting luminosities are then scaled by
the <tt/psize/ and <tt/slum/ scale factors, and further
scaled according to distance as specified by <tt/fade/, to compute
apparent brightness of points.
<tag> lum const <it/L/ </tag>
Specify constant particle luminosity <it/L/ independent of
any data field values.
</descrip>
fade [planar|spherical|linear <it/refdist/|const <it/refdist/]
Determines how distance affects particles' apparent brightness (or "size").
The default <tt/fade planar/ gives 1/r^2 light falloff, with r measured
as distance from the view plane. <tt/fade spherical/ is also 1/r^2,
but with r measured as true distance from the viewpoint.
<tt/fade linear/ <it/refdist/ gives 1/r light falloff -- not physically
accurate, but useful to get a limited sense of depth.
<tt/fade const/ <it/refdist/ gives constant apparent brightness
independent of distance, and may be appropriate for orthographic views.
The <it/refdist/ for linear and const modes is that distance <it/r/
at which apparent brightness should match that in the 1/r^2 modes --
a distance to a "typical" particle.
labelminpixels
point[s] [on|off]
Turn display of points on or off. With no argument, toggles display.
poly[gons] [on|off]
Turn display of points on or off. With no argument, toggles display.
texture [on|off]
Turn display of textures on or off. With no argument, toggles.
label[s] [on|off]
Turn display of label text on or off. With no argument, toggles.
txscale <it/scalefactor/
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 <tt/polysides/ is 4.
Report setting of <tt/polyorivar/ data-command, which see.
Report setting of <tt/texturevar/ data-command, which see.
laxes [on|off]
Toggle label axes. When on, and when labels are displayed,
shows a