partiview.txt 89.22 KiB
Partiview (PC-VirDir)
Peter Teuben, Stuart Levy
25 June 2002
partiview is a program that enables you to visualize and animate par-
ticle data. partiview runs on relatively simple desktops and laptops,
but is mostly compatible with its big brother VirDir. This document
helps you installing and running the development version of partiview.
______________________________________________________________________
Table of Contents
1. Installation
1.1 MESA/OpenGL
1.2 FLTK 1.3 partiview
1.4 CVS
1.5 Compiling under Windows
2. Directory structure
3. Running the program
3.1 Example 1: Hipparcos Bright Star Catalogue 3-D viewing
3.2 Top Row
3.3 Group row (optional)
3.4 Time Animation rows (Optional)
3.5 Camera (path) Animation row
3.6 Logfile window
3.7 Command window
3.8 Viewing window
3.9 Example 2: a (starlab) animation
3.10 Example 3: stereo viewing
3.11 Example 4: subsetting
4. Commands
4.1 Control Commands
4.2 I/O Control Commands
4.3 Object Group Control Commands
4.4 View Control commands
4.5 Particle Display Control Commands
4.6 Particle subsetting & statistics
4.7 Boxes
4.8 Data commands
4.9 Kira/Starlab
4.9.1 Kira particle attributes
4.9.2 Hertzsprung-Russell diagram
4.9.3 kira control commands
4.10 Textures
4.11 Coordinates and Coordinate Transformations
4.12 Colormap Files
5. Viewing Window Keyboard Shortcuts
6. Partiview and NEMO
7. Tips
8. Bugs, Features and Limitations
8.1 Limitations w.r.t. VirDir:
8.2 Some notes for newcomers to VirDir
9. Glossary
______________________________________________________________________
11.. IInnssttaallllaattiioonn
This assumes you have the July 2001 release (version 0.6 or later) of
ppaarrttiivviieeww, not the earlier "ggvviieeww" release that was described in
earlier versions of this document. We keep copies of some Linux
support files (Mesa, FLTK) on our current
http://www.astro.umd.edu/nemo/amnh website. Although more current
versions of support libraries may be available, they may not have been
tested out. This release has been tried on Linux (red hat 6.2, 7.1,
7.2), Irix and Windows.
partiview needs two libraries to compile: OpenGL (or MESA) for the
drawing operations, and FLTK for the graphical user interface. These
libraries are known to work on MS-Windows as well as many Unix flavors.
11..11.. MMEESSAA//OOppeennGGLL
First make sure Mesa is installed, for redhat6.2 there are rpm files
available. For redhat7.1+ they are now included in the basic
distribution. Check if you have something like the following (version
numbers may be different):
______________________________________________________________________
% rpm -qa | grep Mesa
Mesa-3.2-2
Mesa-devel-3.2-2
else:
% rpm -i Mesa-3.2-2.i686.rpm Mesa-devel-3.2-2.i686.rpm
______________________________________________________________________
You should have both installed. Some packages will use libMesaGL,
others libGL. Our configure script (see below) should take care of the
two possible options.
Homepage: http://mesa3d.sourceforge.net/
Redhat packages: (part of powertools I believe)
Mesa3D is under continuous development. As of this writing the stable
release is 4.0.1, but it has not been tested with the current
partiview release. Redhat 7.1 comes with Mesa-3.4 and also works with
partiview. You can also use a CVS release of Mesa.
11..22.. FFLLTTKK
Also make sure FLTK is installed. If you got our version, do this (as
root)
______________________________________________________________________
% locate libfltk.a
% locate Fl_Slider.h
if they fail, then
% cd <where-ever>/fltk-1.0.9
% make install
______________________________________________________________________
(you only need it if you want to recompile the program at some point,
not if you just want to run it)
Homepage: http://www.fltk.org/
Redhat packages: http://www.cs.cornell.edu/nogin/RPM/fltk-devel.html
Find rpms: http://rpmfind.net
FLTK is under continuous development. Versions from 1.0.9 through
1.1.0rc3 have been successfully tested with partiview. The upcoming
2.0 version of FLTK is unlikely to work with partiview.
11..33.. ppaarrttiivviieeww
You can decide to use a branded version, usually available as a tar or
zip file, or use the CVS (see below). Extract the tarball, and
install the program from within the src directory:
______________________________________________________________________
% tar zxf partiview-0.6.tar.gz
% cd partiview-0.6/src
% make clean (if you really must compile a new executable)
% ./configure (GNU autoconf toolset to ease installation)
% make depend (might need to make new local dependancies)
% make partiview (should not have to edit Makefile anymore)
______________________________________________________________________
If you encounter difficulties of locating either the FLTK or
MESA/OpenGL libraries, configure script options can specify them:
--with-fltk=_d_i_r_n_a_m_e names the directory which contains the lib and FL
subdirectories, --with-mesa=_d_i_r_n_a_m_e can specify the Mesa installation
directory [??], and --with-kira=_d_i_r_n_a_m_e names the Starlab directory,
whose default value is taken from environment variable STARLAB_PATH if
that is set.
11..44.. CCVVSS
Since version 0.5 partiview is under CVS control, and occasionally we
will stamp out a new release when we deem it stable. Anonymous or
read-only CVS access is also offered. Currently the CVS repository
machine is cvs.astro.umd.edu and you will need to setup your
developers account with Peter (teuben@astro.umd.edu). Here's a sample
session with some commonly used CVS commands:
______________________________________________________________________
setenv CVSROOT :pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot
setenv CVSEDITOR emacs
setenv CVS_RSH ssh (not needed for pserver access though)
cvs login (only needed once, and only for pserver type access)
cvs checkout partiview # get a new local sandbox to work in, or
cd partiview # goto the root directory of partiview
cvs -n -q update # check if others had made any changes
cvs update # if so, update your sandbox and/or resolve conflicts
cd partiview/src # goto the 'src' directory of partiview
./configure
emacs partibrains.c # edit some files
make all # compile the program
./partiview # test the program
emacs kira_parti.cc # edit another file
make all # check if it still compiles
cvs -n -q update # check if anybody else made changes
cvs update # if so, update your sandbox again, resolve conflicts
cvs commit # and commit your changes
______________________________________________________________________
11..55.. CCoommppiilliinngg uunnddeerr WWiinnddoowwss
Partiview can be compiled from the command line on Windows using
either the Microsoft Visual C tools (cl, nmake, etc.) or using gcc/g++
with MinGW32, MSYS and w32api. The MinGW route is currently the only
way to compile with kira/Starlab support. There's no provision for
building partiview within the MS Visual Studio GUI.
To compile with Microsoft C:
1. Install FLTK using MS Visual C++ as described in its documentation.
2. Unpack the partiview distribution from its tarball or via CVS.
3. Edit the file partiview/src/partiview.mak, changing FLTK_DIR as
appropriate.
4. Run the vcvars32.bat script from the Developer Studio Bin
directory; this will set the MSVCDIR environment variable, add the
Bin directory to PATH, etc.
5. In the partiview/src directory, compile with
nmake -f partiview.mak
Dependencies are _n_o_t properly maintained by this Makefile, so use
nmake -f partiview.mak clean if you change anything.
To compile with MinGW and company, you'll need to:
1. Install MinGW (gcc, etc.), its associated w32api libraries and
header files, and the MSYS suite of UNIX-like tools. All three
packages are available at:
http://www.sourceforge.net/projects/mingw/ Recent releases of
w32api include MinGW versions of OpenGL libraries and headers,
which partiview needs. As of June 2002, current versions seem to
be mingw-1.0.1-20010726, w32api-1.4-2, and MSYS-1.0.7. Unpack the
.zip or .tar archives of MinGW and w32api; both packages are
intended to live in the same directory. The MSYS package comes as
a self-extracting archive and can be extracted into a different
directory as desired. (But don't attempt to merge the MSYS bin
directory contents into mingw/bin.)
2. Add both the MSYS bin subdirectory and MinGW bin subdirectory to the Windows PATH environment variable, with the MSYS directory
coming earlier, e.g. in a command window
set path=%path%;C:\util\msys\1.0\bin;C:\util\mingw\bin
or the analogous setting of PATH using (on WinNT/2000 at least) My
Computer -> Control Panel -> System -> Environment to make a permanent
change to PATH.
3. Build FLTK using MinGW. Unpack its source distribution and say
sh configure
make
4. Build the Starlab libraries, if desired:
a. You may need to install CVS for Windows. Binary packages are
available; follow the Win32 link on
http://www.cvshome.org/downloads.html. Put the resulting
cvs.exe file into the PATH somewhere.
b. Use CVS to checkout the Starlab sources into some directory:
cd C:\some\where
set CVSROOT=:pserver:anonymous@cvs.astro.umd.edu:/home/cvsroot
cvs login
cvs checkout starlab
cd starlab
c. Copy templates\starlab_setup.bat to local\starlab_setup.bat, and
edit it. Change the first two set commands: set STARLAB_PATH to
the installation directory -- in the above example, set
STARLAB_PATH=C:\some\where\starlab. Also optionally update (or
remove) set PATH=... to add MSYS and MinGW bin directories to
it.
d. From a Windows command window, type
local\starlab_setup
make libs
e. If successful, you should find in the lib directory the files
libdstar.a libdyn.a libnode.a librdc.a libsstar.a libstd.a
libtdyn.a
5. Now, back in the partiview/src directory, use configure and make as
under Unix. The MSYS package imposes its own UNIX-like syntax for
Windows pathnames, which you'll need to use as arguments to configure and friends, with forward- instead of backslashes and a
/_d_r_i_v_e_-_l_e_t_t_e_r prefix. Also, if typing to a Windows command-window,
shell scripts like configure must be explicitly fed to sh. Thus
for example if FLTK is installed in C:\util\fltk-1.1.0 and Starlab
is in F:\src\starlab, then you might build partiview by typing
sh configure --with-fltk=/c/util/fltk-1.1.0 --with-kira=/f/src/starlab
make
Note there's no need to specify the location of the OpenGL or other
libraries; the configure script and MinGW tools already know where to
find them.
22.. DDiirreeccttoorryy ssttrruuccttuurree
Here is the directory structure, as per version 0.1:
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/tutor examples of tutorial type code (added in 0.2)
partiview/windows windows executables/support (old)
33.. RRuunnnniinngg tthhee pprrooggrraamm
First we describe a simple example how to run partiview with a
supplied sample dataset. Then we describe the different windows that
partiview is made up of, and the different commands and keystrokes it
listens to.
33..11.. EExxaammppllee 11:: HHiippppaarrccooss BBrriigghhtt SSttaarr CCaattaalloogguuee 33--DD vviieewwiinngg
Start the program using one of the sample "speck" files in the data
directory:
______________________________________________________________________
% cd partiview/data
% ./hipbright
or
% partiview hipbright
______________________________________________________________________
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 :-) (Hint: the .partiviewrc file may
contain commands like eval winsize 600 400.)
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
______________________________________________________________________
fov 50 (field of view 50 degrees)
jump 0 0 0 80 70 60 (put yourself in the origin
and look at euler angles
RxRyRz (80,70,60)
______________________________________________________________________
and it should give another nice comfy view :-) If you ever get lost,
and this is not hard, use the jump command to go back to a known
position and/or viewing angle.
partiview view
Note that spatial units for this dataset are parsecs, though angular
units are degrees for any data in partiview.
Now play with the display, use the 't', 'r', 'f' and 'o' keys (keys
are case sensitive) 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.
The RGB axes represent the XYZ axes in a (right-handed) 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 :-)
[NOTE: these Hipparcos data do not have reliably distance above
100-200 pc, so Orion's individual distances are probably uncertain to
30%]
A little bit on the types of motion, and what the mouse buttons do
______________________________________________________________________
| left middle right
| Button-1 Button-2 Button-3 Shift Button-1
------------------------------------------------------------------------------------ f (fly) | fly 'pick' zoom
o (orbit) | orbit 'pick' zoom
r (rotate) | rotate X/Y 'pick' rotate Z translate
t (translate) | translate 'pick' zoom
______________________________________________________________________
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.
______________________________________________________________________
red = X axis
green = Y axis
blue = Z axis
______________________________________________________________________
To choose an arbitrary center of rotation, use the center command.
33..22.. TToopp RRooww
The top row contains some shortcuts to some frequently used commands.
From left to right, it should show the following buttons:
MMoorree
Offers some mode switches as toggles: inertia for continues spin
or motion, and an H-R Diagram to invoke a separate H-R diagram
window for datasets that support stellar evolution.
[[gg11]]
Pulldown g1, g2, ... (or whichever group) is the currently
selected group. See 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.
[[ff]]llyy
Pulldown to select fly/orbit/rot/tran, which can also be
activate by pressing the f/o/r/t keys inside the viewing window.
ppooiinntt
Toggle to turn the points on/off. See also the points command.
ppoollyy
Toggle to turn polygons on/off. See also the polygon command.
llbbll
Toggle to turn labels on/off. See also the label command.
tteexx
Toggle to turn textures on/off. See also the texture command.
bbooxx Toggle to turn boxes on/off. See also the boxes command.
##..######
The current displayed value of the logslum lum slider (see next)
llooggsslluumm lluumm
Slider controlling the logarithm of the ddaattaavvaarr variable
selected as luminosity (with the lum command).
33..33.. GGrroouupp rrooww ((ooppttiioonnaall))
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.
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.
33..44.. TTiimmee AAnniimmaattiioonn rroowwss ((OOppttiioonnaall))
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.
TT Shows the current time (or offset from the tripmeter). The
absolute time is the sum of the TT and ++ fields. Both are
editable. See also the step control command.
ttrriipp
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.
bbaacckk
Press to return to reference time (sets T to 0).
++ Current last time where tripmeter was set. You can reset to the
first frame with the command step 0
ddiiaall
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 * _s_p_e_e_d in data time
units.
||<<
>>||
Step time backwards or forwards by 0.1 * _s_p_e_e_d data time units.
See also the < and > keyboard shortcuts.
<<<<
>>>>
toggle movie move forwards in time Toggle animating backwards or
forwards in time, by 1 * _s_p_e_e_d data time units per real-time
second. See also the {, ~, and } keyboard shortcuts.
##..########
(Logarithmic) value denoting _s_p_e_e_d of animation. See also the
speed control command.
33..55.. CCaammeerraa ((ppaatthh)) AAnniimmaattiioonn rrooww
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.
PPaatthh......
Brings up a filebrowser to load a ..wwff path file. This is a file
with on each line 7 numbers: xyz location, RxRyRz viewing
direction, and FOV (field of view). The rdata command loads
such path files too.
PPllaayy
Play the viewpoint along the currently loaded path, as the play
command does. Right-click for a menu of play-speed options.
<<<< << [[######]] >>>>>>
Step through camera-path frames. See also frame control
command.
sslliiddeerr
Slides through camera path, and displays current frame.
33..66.. LLooggffiillee wwiinnddooww
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.
33..77.. CCoommmmaanndd wwiinnddooww
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). You can still give Data Commands in this window by
prefixing them with the add command. 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.
33..88.. VViieewwiinngg wwiinnddooww
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.
33..99.. EExxaammppllee 22:: aa ((ssttaarrllaabb)) aanniimmaattiioonn
Setting up a small animation in for example Starlab can be done quite
simply as follows: (see also the primbim16.mk makefile to create a
standard one):
______________________________________________________________________
% makeplummer -i -n 20 | makemass -l 0.5 -u 10.0 | scale -s | kira -d 2 -D x10 > run1
% partiview run1.cf
% cat run1.cf
kira run1
eval every
eval lum mass 0 0.01
eval psize 100
eval cment 1 1 .7 .3
eval color clump exact
______________________________________________________________________
Alternatively, if you had started up partiview without any arguments,
the following Control Command (see below) would have done the same
______________________________________________________________________
read run1.cf
______________________________________________________________________
33..1100.. EExxaammppllee 33:: sstteerreeoo vviieewwiinngg
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. Crosseyed viewing is also available if
selected by sstteerreeoo ccrroossss. See sstteerreeoo and ffooccaalllleenn in the View
Commands section.
33..1111.. EExxaammppllee 44:: ssuubbsseettttiinngg
In the data directory, run
partiview hip.cf
One of the data fields for these stars is the _B_-_V color, colorb_v,
abbreviatable to just color. Look at just the bluest stars: try
thresh color < -.1
Back off to a large distance (drag with right mouse button, and drag
the logslum lum slider to brighten) and look at the distribution of
these blue stars. The Orion spiral-arm spur, extending generally
along the +Y (green) axis, has lots of them. Now look at more reddish
stars, those with .5 <= _B_-_V <= 1.5, with:
thresh color .5 1.5
These are much more uniformly distributed in the galactic plane.
Return to seeing all stars, with:
see all
or re-view the threshold-selected subset (reddish stars) with
see thresh
or its complement with
see -thresh
44.. CCoommmmaannddss
There are two types of commands in 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 add command
prefix. Likewise, a Control Command may be given where data is
expected, using the eval prefix, e.g. in a data (or .cf) file. The
real (Control) Command expects data commands, but if Control Commands
are needed, they need to be preceded with the eval command. See also
the previous ssttaarrllaabb example.
44..11.. CCoonnttrrooll CCoommmmaannddss
(see partibrains.c::specks_parse_args)
Control Commands are accepted in the Command window, and in some other
contexts. Generally, partiview gives a response to every Control
Command, reporting the (possibly changed) status.
Typically, if parameters are omitted, the current state is reported.
Some commands apply to particles in the current group (see Object group commands); others affect global things, such as time or display
settings.
Data Commands can also be given, if prefixed with add.
44..22.. II//OO CCoonnttrrooll CCoommmmaannddss
rreeaadd _s_p_e_c_k_s_-_f_i_l_e
Read a file containing Data Commands (typical suffix .cf or
.speck).
aassyynncc _u_n_i_x_-_c_o_m_m_a_n_d
Run an arbitrary unix command (invoked via /bin/sh) as a
subprocess of partiview. Its standard output is interpreted as
a stream of control commands. Thus partiview can be driven
externally, e.g. to record an animation (using the snapshot
command), or to provide additional GUI controls. Several async
commands can run concurrently. Examples are given later.
Warning: you cannot interrupt a started command, short of
hitting ESC to exit partiview.
aadddd _d_a_t_a_-_c_o_m_m_a_n_d
Enter a Data Command where a Control Command is expected, e.g.
in the text input box. For example,
add 10 15 -1 text blah
adds a new label "blah" at 10 15 -1, or
add kira myrun.out
loads a kira (starlab) output file.
eevvaall _c_o_n_t_r_o_l_-_c_o_m_m_a_n_d
Processes that control command just as if the eval prefix
weren't there. Provided for symmetry: wherever either a control
command or a data command is expected, entering eval _c_o_n_t_r_o_l_-
_c_o_m_m_a_n_d ensures that it's taken as a control command.
aadddd ffiilleeppaatthh ((ddaattaa--ccoommmmaanndd))
Determines the list of directories where all data files, color
maps, etc. are sought. See the filepath entry under Data
Commands.
44..33.. OObbjjeecctt GGrroouupp CCoonnttrrooll CCoommmmaannddss
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.
Many Control Commands apply to the _c_u_r_r_e_n_t_l_y _s_e_l_e_c_t_e_d group.
Groups always have names of the form g_N for some small positive _N;
each group may also have an alias.
gg_N Select group g_N. Create a new group if it doesn't already
exist.
gg_N=_a_l_i_a_s
Assign name _a_l_i_a_s to group g_N. Note there must be no blanks
around the = sign.
oobbjjeecctt _o_b_j_e_c_t_n_a_m_e
Likewise, select object _o_b_j_e_c_t_n_a_m_e, which may be either an alias
name or g_N.
gg_N _c_o_n_t_r_o_l_-_c_o_m_m_a_n_d
oobbjjeecctt _o_b_j_e_c_t_n_a_m_e _c_o_n_t_r_o_l_-_c_o_m_m_a_n_d
Either form may be used as a _p_r_e_f_i_x to any control command to
act on the specified group, e.g. object fred poly on
ggaallll _c_o_n_t_r_o_l_-_c_o_m_m_a_n_d
Invoke the given _c_o_n_t_r_o_l_-_c_o_m_m_a_n_d in all groups. For example, to
turn display of group 3 on and all others off, use:
gall off
g3 on
oonn
eennaabbllee
Either one will enable the display of the currently selected
group (as it is by default).
ooffff
ddiissaabbllee
Either one will turn off the display of the current group.
44..44.. VViieeww CCoonnttrrooll ccoommmmaannddss
View commands affect the view; they aren't specific to data groups.
ffoovv _f_l_o_a_t
Angular field of view (in degrees) in Y-direction.
cceenn[[tteerr]] _X _Y _Z [_R_A_D_I_U_S]
Set point of interest. This is the center of rotation in
[o]rbit and [r]otate modes. Also, in [o]rbit mode, translation
speed is proportional to the viewer's distance from this point.
The optional _R_A_D_I_U_S (also set by censize) determines the size of
the marker crosshair, initially 1 unit.
cceenn[[tteerr]] [[_X _Y _Z [_R_A_D_I_U_S]]
int[erest] [_X _Y _Z [_R_A_D_I_U_S]]" Set point of interest. This is the
center of rotation in [o]rbit and [r]otate modes. And, in
[o]rbit mode, translation speed is proportional to the viewer's
distance from this point. The optional _R_A_D_I_U_S (also set by censize) determines the size of the marker crosshair, initially
1 unit.
**** why is center/interest commented out in the first example.
Originally this command was documented twice, the first one has
/interest commented out.
cceennssiizzee [[_R_A_D_I_U_S]
Set size of point-of-interest marker.
wwhheerree _(_a_l_s_o_) w
Report the 3-D camera position and forward direction vector.
cclliipp _N_E_A_R _F_A_R
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 _F_A_R/_N_E_A_R ratio
exceeds 10000 or so.
To set the far clip range without changing the near, use a non-
numeric near clip value, e.g. clip - 1000.
jjuummpp [[_X _Y _Z] [_R_x _R_y _R_z]
Get or set the current position (XYZ) and/or viewing (RxRyRz)
angle.
rreeaaddppaatthh
Read a Wavefront (.wf) file describing a path through space.
rrddaattaa
Synonym for readpath.
ppllaayy _s_p_e_e_d[f]
Play the currently loaded (from readpath/rdata) camera animation
path, at _s_p_e_e_d 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 _s_p_e_e_d-th frame,
without regard to real time.
ffrraammee [[_f_r_a_m_e_n_o]
Get or set the current frame the _f_r_a_m_e_n_o-th.
uuppddaattee
Ensures the display is updated, as before taking a snapshot.
Probably only useful in a stream of control commands from an
async subprocess.
wwiinnssiizzee [[_X_S_I_Z_E [_Y_S_I_Z_E]]
wwiinnssiizzee _X_S_I_Z_Ex_Y_S_I_Z_E+_X_P_O_S+_Y_P_O_S
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), e.g. winsize 400x350+20-10, also sets position
of graphics window, with +X and +Y measured from left/top, -X
and -Y measured from right/bottom of screen.
ddeettaacchh [[ffuullll||hhiiddee]] [[_+_X_P_O_S_+_Y_P_O_S]
Detach graphics window from GUI control strip and optionally
specify position of control strip. With full or hide, makes
graphics window full-screen with GUI visible or hidden,
respectively. With neither full nor hide, the graphics window
is detached but left at its current size.
The _+_X_P_O_S_+_Y_P_O_S is a window position in X window geometry style,
so e.g. detach full -10+5 places the GUI near the upper right
corner of the screen, 10 pixels in from the right and 5 pixels
down from the top edge.
If you don't mind typing blindly, it's still possible to enter
text-box commands even with the controls hidden; press the _T_a_b
key before each command to ensure that input focus is in the
text box. Use _T_a_bdetach full_E_n_t_e_r to un-hide a hidden control
strip.
bbggccoolloorr _R _G _B
Set window background color (three R G B numbers or one
grayscale value).
ffooccaalllleenn _d_i_s_t_a_n_c_e
Focal length: distance from viewer to a typical object of
interest. This affects stereo display (see below) and
navigation: the speed of motion in [t]ranslate and [f]ly modes
is proportional to this distance.
sstteerreeoo [[oonn||ooffff||rreeddccyyaann||ggllaasssseess||ccrroossss||lleefftt||rriigghhtt]] [[_s_e_p_a_r_a_t_i_o_n]
Stereo display. Also toggled on/off by typing 's' key in
graphics window. Where hardware allows it, stereo glasses
selects CrystalEyes-style quad-buffered stereo. All systems
should be capable of stereo redcyan, which requires wearing
red/green or red/blue glasses, and of cross (crosseyed), which
splits the window horizontally. left and right show just that
eye's view, and may be handy for taking stereo snapshots.
Useful _s_e_p_a_r_a_t_i_o_n values might be 0.02 to 0.1, or -0.02 to -0.1
to swap eyes. See also 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.
Virtual-world eyes will be separated by distance 2 * _f_o_c_a_l_l_e_n _*
_s_e_p_a_r_a_t_i_o_n, with convergence angle 2 * arctan(_s_e_p_a_r_a_t_i_o_n).
See also the winsize and detach commands for control over
graphics window size and placement.
Beware: some systems which support hardware ("glasses") stereo
also require that the display be set to a stereo-capable video
mode. Partiview does not do this automatically. For example,
on stereo-capable SGI Irix systems, you may need to type (to a
unix shell) /usr/gfx/setmon -n 1024x768_96s to allow stereo
viewing and something like /usr/gfx/setmon -n 72 to revert.
Otherwise, turning partiview's stereo on will just show the left
eye's view -- displacing the viewpoint but nothing else.
ssnnaappsseett [[-n _F_R_A_M_E_N_O] _F_I_L_E_S_T_E_M [_F_R_A_M_E_N_O]
Set parameters for future snapshot commands. _F_I_L_E_S_T_E_M may be a
printf format string with frame number as argument, e.g. snapset
pix/%04d.ppm, generating image names of pix/0000.ppm,
pix/0001.ppm, etc. If _F_I_L_E_S_T_E_M contains no % sign, then
.%03d.ppm.gz is appended to it, so snapset ./pix/fred yields
snapshot images named ./pix/fred.000.ppm.gz etc.
Frame number _F_R_A_M_E_N_O (default 0) increments with each snapshot
taken.
ssnnaappsshhoott [[_F_R_A_M_E_N_O]
Capture a snapshot image of the current view. Use snapset to
specify the output image name. Default format is snap.%03d.tif.
Partiview generally invokes the ImageMagick program convert(1),
which must be installed and be on the user's $PATH. Convert
determines the type of image (jpeg, sgi, bmp, etc.) based on the
file suffix.
Convert is not needed if the snapset _F_I_L_E_S_T_E_M ends in .ppm.gz
(invokes gzip rather than convert) or .ppm (no external program
required).
44..55.. PPaarrttiiccllee DDiissppllaayy CCoonnttrrooll CCoommmmaannddss
These commands affect how particles (in the current group) are
displayed.
ppssiizzee _s_c_a_l_e_f_a_c_t_o_r
All particle luminosities (as specified by lum command) are
scaled by the product of two factors: a _l_u_m_v_a_r-specific factor
given by slum, and a global factor given by psize. So the
intrinsic brightness of a particle is _v_a_l_u_e_-_s_p_e_c_i_f_i_e_d_-_b_y_-lum *
_s_l_u_m_-_f_o_r_-_c_u_r_r_e_n_t_-_l_u_m_v_a_r * _p_s_i_z_e_-_s_c_a_l_e_f_a_c_t_o_r.
sslluumm _s_l_u_m_f_a_c_t_o_r
Data-field specific luminosity scale factor, for current choice
of _l_u_m_v_a_r as given by the lum command. A _s_l_u_m_f_a_c_t_o_r is recorded
independently for each data field, so if data fields mass and
energy were defined, one might say
lum mass
slum 1000
lum energy
slum 0.25
having chosen each variable's _s_l_u_m_f_a_c_t_o_r for useful display, and
then freely switch between lum mass and lum energy without having
to readjust particle brightness each time.
ppttssiizzee _m_i_n_p_i_x_e_l_s _m_a_x_p_i_x_e_l_s
Specifies the range of _a_p_p_a_r_e_n_t sizes of points, in pixels.
Typical values might be ptsize 0.1 5. The graphics system may
silently impose an upper limit of about 10 pixels.
ppoollyyssiizzee [[oonn||ooffff]] [[aa||ss||rr]]
ppoollyylluumm
ppoollyymmiinnppiixxeellss
ppoollyymmiinn _m_i_n_r_a_d_i_u_s [_m_a_x_r_a_d_i_u_s]
ccoolloorr
Specify how particles are colored. Generally, a linear function
of some data field of each particle becomes an index into a
colormap (see cmap, cment).
ccoolloorr _c_o_l_o_r_v_a_r [_m_i_n_v_a_l _m_a_x_v_a_l]
Use data field _c_o_l_o_r_v_a_r (either a name as set by datavar or a
0-based integer column number) to determine color. Map
_m_i_n_v_a_l to color index 1, and _m_a_x_v_a_l to the next-to-last entry
in the colormap (_N_c_m_a_p_-_2). The 0th and last (_N_c_m_a_p_-_1)
colormap entry are used for out-of-range data values.
If _m_i_n_v_a_l and _m_a_x_v_a_l are omitted, the actual range of values
is used.
ccoolloorr _c_o_l_o_r_v_a_r exact [_b_a_s_e_v_a_l]
Don't consider field _c_o_l_o_r_v_a_r as a continuous variable;
instead, it's integer-valued, and mapped one-to-one with
color table slots. Data value _N is mapped to color index
_N_+_b_a_s_e_v_a_l.
ccoolloorr _c_o_l_o_r_v_a_r -exact
Once the exact tag is set (for a particular data-field), it's
sticky. To interpret that data field as a continuous,
scalable variable again, use -exact.
ccoolloorr ccoonnsstt _R _G _B
Show all particles as color _R _G _B, each value in range 0 to
1, independent of any data fields.
lluumm
Specify how particles' intrinsic luminosity is computed: a
linear function of some data field of each particle.
lluumm _l_u_m_v_a_r [_m_i_n_v_a_l _m_a_x_v_a_l]
Map values of data field _l_u_m_v_a_r (datavar name or field
number) to luminosity. The (linear) mapping takes field
value _m_i_n_v_a_l to luminosity 0 and _m_a_x_v_a_l to luminosity 1.0.
If _m_i_n_v_a_l and _m_a_x_v_a_l are omitted, the actual range of values
is mapped to the luminosity range 0 to 1.
Note that the resulting luminosities are then scaled by the
psize and slum scale factors, and further scaled according to
distance as specified by fade, to compute apparent brightness
of points.
lluumm ccoonnsstt _L
Specify constant particle luminosity _L independent of any
data field values.
ffaaddee [[ppllaannaarr||sspphheerriiccaall||lliinneeaarr _r_e_f_d_i_s_t|const _r_e_f_d_i_s_t]
Determines how distance affects particles' apparent brightness
(or "size"). The default fade planar gives 1/r^2 light falloff,
with r measured as distance from the view plane. fade spherical
is also 1/r^2, but with r measured as true distance from the
viewpoint. fade linear _r_e_f_d_i_s_t gives 1/r light falloff -- not
physically accurate, but useful to get a limited sense of depth.
fade const _r_e_f_d_i_s_t gives constant apparent brightness
independent of distance, and may be appropriate for orthographic
views.
The _r_e_f_d_i_s_t for linear and const modes is that distance _r at
which apparent brightness should match that in the 1/r^2 modes
-- a distance to a "typical" particle.
llaabbeellmmiinnppiixxeellss
llaabbeellssiizzee
llssiizzee
ppooiinntt[[ss]] [[oonn||ooffff]]
Turn display of points on or off. With no argument, toggles
display.
ppoollyy[[ggoonnss]] [[oonn||ooffff]]
Turn display of points on or off. With no argument, toggles
display.
tteexxttuurree [[oonn||ooffff]]
Turn display of textures on or off. With no argument, toggles.
llaabbeell[[ss]] [[oonn||ooffff]]
Turn display of label text on or off. With no argument,
toggles.
ttxxssccaallee _s_c_a_l_e_f_a_c_t_o_r
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 polysides is 4.
ppoollyyoorriivvaarr
Report setting of polyorivar data-command, which see.
tteexxttuurreevvaarr
Report setting of texturevar data-command, which see.
llaaxxeess [[oonn||ooffff]]
Toggle label axes. When on, and when labels are displayed,
shows a
ppoollyyssiiddee((ss))
Number of sides a polygon should have. Default 11, for fairly
round polygons. For textured polygons, polysides 4 might do as
well, and be slightly speedier.
ffaasstt
see also ptsize
ppttssiizzee _m_i_n_p_i_x_e_l_s [_m_a_x_p_i_x_e_l_s]
Specifies range of apparent (pixel) size of points. Those with
computed sizes (based on luminosity and distance) smaller than
_m_i_n_p_i_x_e_l_s are randomly (but repeatably) subsampled -- i.e. some
fraction of them are not drawn. Those computed to be larger
than _m_a_x_p_i_x_e_l_s are drawn at size _m_a_x_p_i_x_e_l_s.
ggaammmmaa _d_i_s_p_l_a_y_g_a_m_m_a
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 gamma 1 through gamma
2.5 or so. Larger values raise the apparent brightness of dim
things.
aallpphhaa _a_l_p_h_a
Get or set the alpha value, in the range 0 to 1; it determines
the opacity of polygons.
ssppeeeedd
For time-dependent data, advance datatime by this many time
units per wall-clock second.
sstteepp [[_t_i_m_e_s_t_e_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, step also stops datatime
animation. (See run.)
sstteepp [[++||--]]_d_e_l_t_a_t_i_m_e_s_t_e_p
If preceded with a plus or minus sign, adds that amount to
current time.
(note that fspeed has been deprecated)
rruunn
Continue a stopped animation (see also step).
ttffmm [[--vv]] [[_n_u_m_b_e_r_s_._._.]
Object-to-world transformation. May take 1, 6, 7, 9 or 16
parameters: either _s_c_a_l_e_f_a_c_t_o_r, or _t_x _t_y _t_z _r_x _r_y _r_z
_s_c_a_l_e_f_a_c_t_o_r>], or 16 numbers for 4x4 matrix, or 9 numbers for
3x3 matrix. See _C_o_o_r_d_i_n_a_t_e_s _a_n_d _C_o_o_r_d_i_n_a_t_e _T_r_a_n_s_f_o_r_m_a_t_i_o_n_s.
With no numeric parameters, reports the current object-to-world
transform. Use tfm -v to see the transform and its inverse in
several forms.
mmoovvee [[gg_N] {on|off}
Normally, navigation modes [r]otate and [t]ranslate just adjust
the viewpoint (camera). However, if you turn move on, then
[r]otate and [t]ranslate move the currently-selected object
group instead, e.g. to adjust its alignment relative to other
groups. ([o]rbit and [f]ly modes always move the camera.)
To indicate that move mode is enabled, the control strip shows
the selected group's name in bold italics, as _[_g_3_]. Use move
off to revert to normal. The tfm command reports the current
object-group-to-global-world transformation.
ffwwdd
ddaattaawwaaiitt oonn||ooffff
For asynchronously-loaded data (currently only ieee data
command), say whether wait for current data step to be loaded.
(If not, then keep displaying previous data while loading new.)
ccmmaapp _f_i_l_e_n_a_m_e Load (ascii) filename with RGB values, for coloring particles.
The color command selects which data field is mapped to color
index and how.
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 _C_o_l_o_r_m_a_p_s section.
vvccmmaapp --vv _f_i_e_l_d_n_a_m_e _f_i_l_e_n_a_m_e
Load colormap as with cmap command. But use this colormap only
when the given data field is selected for coloring. Thus the
cmap color map applies to all data fields for which no vcmap has
ever been specified.
ccmmeenntt _c_o_l_o_r_i_n_d_e_x [_R _G _B]
Report or set that colormap entry.
rraawwdduummpp _d_u_m_p_-_f_i_l_e_n_a_m_e
All particle attributes (not positions though) are written to a
_d_u_m_p_-_f_i_l_e_n_a_m_e. Useful for debugging. Warning: it will happily
overwrite an existing file with that name.
44..66.. PPaarrttiiccllee ssuubbsseettttiinngg && ssttaattiissttiiccss
cclliippbbooxx ......
see cb below.
ccbb ........
Display only a 3D subregion of the data -- the part lying within
the clipbox.
ccbb _x_m_i_n _y_m_i_n _z_m_i_n _x_m_a_x _y_m_a_x _z_m_a_x
Specified by coordinate ranges. Note only spaces are used to
separate the 6 numbers.
ccbb _x_c_e_n_,_y_c_e_n_,_z_c_e_n _x_r_a_d_,_y_r_a_d_,_z_r_a_d
Specified by center and "radius" of the box. Note no spaces
after the commas!
ccbb _x_m_i_n_,_x_m_a_x _y_m_i_n_,_y_m_a_x _z_m_i_n_,_z_m_a_x
Specified by coordinate ranges.
ccbb off
Disable clipping. The entire dataset is again visible.
ccbb on
Re-enable a previously defined clipbox setting. It will also
display the clipbox again
ccbb hide
Hide the clipbox, but still discard objects whose centers lie
outside it.
Note this command does not toggle clipping if no arguments given
(that would be handy and more in line with similar commands).
If no arguments given, it reports the current clipbox.
tthhrreesshh
Display a subset of particles, chosen by the value of some data
field. Each thresh command overrides settings from previous commands, so it cannot be used to show unions or intersections
of multiple criteria. For that, see the only command. However,
unlike only, the thresh criterion applies to time-varying data.
tthhrreesshh _f_i_e_l_d _m_i_n_v_a_l _m_a_x_v_a_l
Display only those particles where _m_i_n_v_a_l <= field _f_i_e_l_d <=
_m_a_x_v_a_l. The _f_i_e_l_d may be given by name (as from datavar) or
by field number.
tthhrreesshh _f_i_e_l_d <_m_a_x_v_a_l
tthhrreesshh _f_i_e_l_d >_m_i_n_v_a_l
Show only particles where _f_i_e_l_d is <= or >= the given
threshold.
tthhrreesshh [[ooffff||oonn]]
Disable or re-enable a previously specified threshold.
oonnllyy== _d_a_t_a_f_i_e_l_d _v_a_l_u_e _m_i_n_v_a_l_u_e_-_m_a_x_v_a_l_u_e <_v_a_l_u_e >_v_a_l_u_e ...
oonnllyy++ _d_a_t_a_f_i_e_l_d _v_a_l_u_e _m_i_n_v_a_l_u_e_-_m_a_x_v_a_l_u_e <_v_a_l_u_e >_v_a_l_u_e ...
oonnllyy-- _d_a_t_a_f_i_e_l_d _v_a_l_u_e _m_i_n_v_a_l_u_e_-_m_a_x_v_a_l_u_e <_v_a_l_u_e >_v_a_l_u_e ...
Scans particles (in the current timestep only!), finding those
where _d_a_t_a_f_i_e_l_d has value _v_a_l_u_e, or has a value in range
_m_i_n_v_a_l_u_e <= value <= _m_a_x_v_a_l_u_e, or whatever. Multiple value-
ranges may be specified to select the union of several sets.
The resulting set of particles is assigned to (only=), added to
(only+) or subtracted from (only-) the thresh selection-set.
Also display just particles in that selection-set, as if see
thresh had been typed.
The net effect is illustrated by these examples:
oonnllyy== ttyyppee 11--33 55
Show only particles of type 1, 2, 3 or 5.
oonnllyy-- mmaassss <<22..33 >>33..55
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. Maybe some day
there'll be an only&.
sseeee selexpr
Show just those particles in the selection-set selexpr.
Predefined set names are all, none, thresh and pick, and other
names may be defined by the sel command. The default is see
all. Using the thresh or only commands automatically switch to
displaying see thresh.
Note that you can see the complement of a named set, e.g. all
except the thresh-selected objects, with see -thresh.
sseell selname = selexpr
Compute a logical combination of selection-sets and assign them
to another such set. The set membership is originally assigned
by thresh or only commands. Yeah, I know this doesn't make
sense. Need a separate section to document selection-sets.
sseell selexpr
Count the number of particles in the selection-set selexpr.
cclleeaarroobbjj
Erase all particles in this group. Useful for reloading on the
fly.
eevveerryy _N
Display a random subset (every _N-th) of all particles. E.g.
every 1 shows all particles, every 2 shows about half of them.
Reports current subsampling factor, and the current total number
of particles.
hhiisstt _d_a_t_a_f_i_e_l_d [-n _n_b_u_c_k_e_t_s] [-l] [-c] [-t] [_m_i_n_v_a_l] [_m_a_x_v_a_l]
Generates a (numerical) histogram of values of _d_a_t_a_f_i_e_l_d, which
may be a named field (as from datavar) or a field index.
Divides the value range (either _m_i_n_v_a_l.._m_a_x_v_a_l or the actual
range of values for that field) into _n_b_u_c_k_e_t_s equal buckets (11
by default). Uses logarithmically-spaced intervals if -l (so
long as the data range doesn't include zero). If a clipbox is
defined, use -c to count only particles within it. If a thresh
or only subset is defined, use -t to count only the chosen
subset.
bboouunndd [[ww]]
Reports 3D extent of the data. With w, reports it in world
coordinates, otherwise in object coordinates.
ddaattaavvaarr
ddvv Report names and value ranges (over all particles in current
group) of all named data fields.
44..77.. BBooxxeess
sshhoowwbbooxx _l_i_s_t _o_f _i_n_t_e_g_e_r _b_o_x _l_e_v_e_l _n_u_m_b_e_r_s_._._.
hhiiddeebbooxx _l_i_s_t _o_f _i_n_t_e_g_e_r _b_o_x _l_e_v_e_l _n_u_m_b_e_r_s_._._.
bbooxx[[eess]] [[ooffff||oonn||oonnllyy]]
Turn box display off or on; or display boxes but hide all
particles.
bbooxxccmmaapp _f_i_l_e_n_a_m_e
Color boxes using that colormap. Each box's level number (set
by -l option of box data-command, default 0) is the color index.
bbooxxccmmeenntt _c_o_l_o_r_i_n_d_e_x [_R _G _B]
Get or set the given box-colormap index. E.g. boxcment 0
reports the color of boxes created with no -l specified.
bbooxxllaabbeell [[oonn||ooffff]]
Label boxes by id number (set by -n option of box data-command).
bbooxxaaxxeess [[oonn||ooffff]]
Toggle or set box axes display mode.
bbooxxssccaallee [[ffllooaatt]] [[oonn||ooffff]]
ggoobbooxx _b_o_x_n_u_m_b_e_r
ggoobbooxxssccaallee
mmeennuu ffmmeennuu
BEGIN CAVEMENU
pos P1 P2
wall P1
hid [P1]
show [P1]
h [P1]
demandfps [P1]
font
help
?
END CAVEMENU
ddaattaassccaallee
44..88.. DDaattaa ccoommmmaannddss
(see also partibrains.c::specks_read)
Data Commands can be placed in a data file. Lines starting with #
will be skipped.
Control Commands can also be given, if prefixed with the eval command.
rreeaadd _f_i_l_e
read a speck formatted file. Recursive, commands can nest.
(strtok ok??) Note that read is also a Control Command, doing
exactly the same thing.
iinncclluuddee _f_i_l_e
read a speck formatted file.
iieeeeee [[--tt ttiimmee]] _f_i_l_e
read a IEEEIO formatted file, with optional timestep number (0
based). Support for this type of data must be explicitly
compiled into the program.
kkiirraa _f_i_l_e
read a kira formatted file. See the kiractl Control Command to
modify the looks of the objects.
sseetteennvv nnaammee vvaalluuee
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
$. _N_o_t_e _t_h_e_r_e _p_r_o_b_a_b_l_y _i_s _n_o_t _a_n _u_n_s_e_t_e_n_v _c_o_m_m_a_n_d.
oobbjjeecctt _g_N_=_A_L_I_A_S
Defines/Selects a particular group number (N=1,2,3....) to an
ALIAS. In command mode you can use gN=ALIAS. Any data following
this command will now belong to this group.
oobbjjeecctt _O_b_j_e_c_t_N_a_m_e
Select an existing group. Following data will now belong to this
group.
ssddbbvvaarrss _v_a_r
Choose which data fields to extract from binary sdb files (any
of: mMcrogtxyzSn) for subsequent sbd commands.
ssddbb [[--tt ttiimmee]] _f_i_l_e
Read an SDB (binary) formatted file, with optional timestep
number (0 based).
bbooxx[[eess]] _._._._.
Draw a box, using any of the following formats:
xmin ymin zmin xmax ymax zmax
xmin,xmax ymin,ymax zmin,zmax
xcen,ycen,zcen xrad,yrad,zrad
[-t time] [-n boxno] [-l level] xcen,ycen,zcen xrad,yrad,zrad
level determines color.
mesh [-t _t_x_n_o] [-c _c_o_l_o_r_i_n_d_e_x] [-s _s_t_y_l_e]
Draw a quadrilateral mesh, optionally colored or textured.
Following the mmeesshh line, provide a line with the mesh
dimensions: nu nv
Following this comes the list of _n_u*_n_v mesh vertices, one vertex
(specified by several blank-separated numbers) per line. (Blank
lines and comments may be interspersed among them.) Note that
the mesh connections are implicit: vertex number i*nu+j is
adjacent to (i-1)*nu+j, (i+1)*nu+j, i*nu+(j-1), and i*nu+(j+1).
Each vertex line has three or five numbers: the first three give
its 3-D position, and if a -t texture was specified, then two
more fields give its u and v texture coordinates.
Options:
-t _t_x_n_o
Apply texture number _t_x_n_o to surface. In this case, each
mesh vertex should also include u and v texture coordinates.
-c _c_o_l_o_r_i_n_d_e_x
Color surface with color from integer cmap entry _c_o_l_o_r_i_n_d_e_x.
-s _s_t_y_l_e
Drawing style:
_s_o_l_i_d
filled polygonal surface (default)
_w_i_r_e
just edges
_p_o_i_n_t
just points (one per mesh vertex)
_X_c_e_n _Y_c_e_n _Z_c_e_n ellipsoid _[_o_p_t_i_o_n_s_]_._._. _[_t_r_a_n_s_f_o_r_m_a_t_i_o_n_]
Draw an ellipsoid, specified by:
Xcen Ycen Zcen
Center position in world coordinates
-c _c_o_l_o_r_i_n_d_e_x
Integer color index (default -1 => white)
-s _s_t_y_l_e
Drawing style:
_s_o_l_i_d
filled polygonal surface (default)
_p_l_a_n_e
3 ellipses: XY, XZ, YZ planes
_w_i_r_e
latitude/longitude ellipses
_p_o_i_n_t
point cloud: one per lat/lon intersection
-r _X_r_a_d_i_u_s[,_Y_r_a_d_i_u_s,_Z_r_a_d_i_u_s]
Radius (for sphere) or semimajor axes (for ellipsoid)
-n _n_l_a_t_[_,_n_l_o_n_]
Number of latitude and longitude divisions. Relevant even
for _p_l_a_n_e style, where they determine how finely the
polygonal curves approximate circles. Default _n_l_o_n = _n_l_a_t/2
+ 1.
_t_r_a_n_s_f_o_r_m_a_t_i_o_n
Sets the spatial orientation of the ellipsoid. May take any
of three forms:
((nnootthhiinngg))
If absent, the ellipsoid's coordinate axes are the same as
the world axes for the group it belongs to.
99 bbllaannkk--sseeppaarraatteedd nnuummbbeerrss
A 3x3 transformation matrix T from ellipsoid coordinates
to world coordinates, in the sense Pworld = Pellipsoid * T
+ [Xcen, Ycen, Zcen].
1166 bbllaannkk--sseeppaarraatteedd nnuummbbeerrss
A 4x4 transformation matrix, as above but for the obvious
changes.
wwaavveeoobbjj [[--ttiimmee _t_i_m_e_s_t_e_p] [-static] [-texture _n_u_m_b_e_r] [-c
_c_o_l_o_r_i_n_d_e_x] [-s _s_t_y_l_e] _f_i_l_e_._o_b_j
Load a Wavefront-style .obj model. Material properties are
ignored; the surface is drawn in white unless -c _c_o_l_o_r_i_n_d_e_x in
which case it's drawn using that color-table color. Also if
-texture (alias -tx) is supplied, the surface is textured using
whatever texture coordinates are supplied in the .obj file. The
model is displayed at all times only if marked -static;
otherwise it's displayed only at the time given by -time
_t_i_m_e_s_t_e_p or by the most recent _d_a_t_a_t_i_m_e.
ttffmm [[ccaammeerraa]] _n_u_m_b_e_r_s_._._.
Object-to-world transformation. May take 1, 6, 7, 9 or 16
numbers: either _s_c_a_l_e_f_a_c_t_o_r or _t_x _t_y _t_z _r_x _r_y _r_z
[it/scalefactor/] or 16 numbers for 4x4 matrix, or 9 numbers for
3x3 matrix. See _C_o_o_r_d_i_n_a_t_e_s _a_n_d _C_o_o_r_d_i_n_a_t_e _T_r_a_n_s_f_o_r_m_a_t_i_o_n_s.
Normally the transform is to world coordinates; but with optional camera prefix, the object's position is specified
relative to the camera, useful to place legends in a fixed
position on the screen. In camera coordinates, (0,0,0) is the
viewpoint, x=y=0 at screen center, and negative z extends
forward. Try for example
tfm camera -3 -3 -20 0 0 0
0 0 0 text -size 20 Legend
eevvaall _c_o_m_m_a_n_d
execute a Control Command.
ffeeeedd _c_o_m_m_a_n_d
Synonym for eval.
VVIIRRDDIIRR _c_o_m_m_a_n_d
Synonym for eval.
ffiilleeppaatthh _p_a_t_h
A colon-separated list of directories in which datafiles, color
maps, etc. will be searched for. If preceded with the + symbol,
this list will be appended to the current _f_i_l_e_p_a_t_h.
ppoollyyoorriivvaarr _i_n_d_e_x_n_o
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 vectors which span the
plane of the disk. Then use polyorivar _i_n_d_e_x_n_o giving the data
field number of the first of the 6 fields. The vectors define
the X and Y directions on the disk, respectively -- relevant if
texturing is enabled.
Actually, unit vectors aren't essential; making them different
lengths yields non-circular polygonal disks.
If polyorivar is specified for the group, but some polygons
should still lie in the screen plane, use values 9 9 9 9 9 9 for
those polygons.
tteexxttuurree [[--aaiiAAOOllmmnnMMDDBB]] _t_x_n_o _f_i_l_e_._s_g_i
--aa((llpphhaa))
A single-channel image would normally be used as luminance
data. With -a, the image is taken as opacity data instead
(GL_ALPHA texture format).
--ii((nntteennssiittyy))
For 1- or 3-channel images, compute the intensity of each
pixel and use it to form an alpha (opacity) channel.
--AA((dddd))
Use additive blending. This texture will add to, not
obscure, the brightness of whatever lies behind it (i.e.
whatever is drawn later).
--OO((vveerr))
Use "over" compositing. This texture will obscure features
lying behind it according to alpha values at each point.
--MM((oodduullaattee))
Multiply texture brightness/color values by the colormap-
determined color of each particle.
--DD((eeccaall))
The textured polygon's color is determined entirely by the
texture, suppressing any colormapped color.
--BB((lleenndd))
Probably not very useful.
tteexxttuurreevvaarr _f_i_e_l_d
If polygon-drawing and texturing are turned on, use the given
_f_i_e_l_d (datavar name or number) in each particle to select which
texture (if any) to draw on its polygon.
ccoooorrdd _n_a_m_e _._._. _1_6 _w_o_r_l_d_-_t_o_-_c_o_o_r_d _t_f_m _f_l_o_a_t_s _(_G_L _o_r_d_e_r_)
ddaattaasseett _i_n_d_e_x_n_o _d_a_t_a_s_e_t_n_a_m_e
Give names to multiple datasets in IEEEIO files (read with ieee
command). _i_n_d_e_x_n_o is an integer, 0 being the first dataset.
ddaattaavvaarr _i_n_d_e_x_n_o _n_a_m_e _[_m_i_n_v_a_l _m_a_x_v_a_l_]
Name the variable in data field _i_n_d_e_x_n_o. The first data field
has _i_n_d_e_x_n_o 0. If provided, _m_i_n_v_a_l _m_a_x_v_a_l supply the nominal
range of that data variable; some control commands (lum, color)
need to know the range of data values, and will use this instead
of measuring the actual range.
ddaattaattiimmee _t_i_m_e
Label subsequent data with this _t_i_m_e (a non-negative integer).
_X_p_o_s _Y_p_o_s _Z_p_o_s _V_a_r_0 _._._._.
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 ddaattaavvaarr commands. Note that data variable (field) numbers
are 0-based.
44..99.. KKiirraa//SSttaarrllaabb
To read Kira output, in human-readable or binary ttddyynn form, use the
``kira _k_i_r_a_f_i_l_e_n_a_m_e'' data-command.
44..99..11.. KKiirraa ppaarrttiiccllee aattttrriibbuutteess
The particles read in have the following attributes:
iidd
positive integer worldline index for single stars (matching the
id in the kira stream). For non-leaf (center-of-mass) tree
nodes, id is a negative integer.
mmaassss
Mass, in solar mass units (see ``kira mscale'' control command).
nncclluummpp Number of stars in this particle's subtree. 1 for isolated
stars, 2 for binaries, etc.
TTlloogg
base-10 log of temperature (K)
LLuumm
Luminosity in solar-mass units. (Note this is linear, not log
luminosity.)
ssttyyppee
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.
iissmmeemmbbeerr
Is this star still a member of (bound to) the cluster?
rroooottiidd
id of root of subtree. For single stars, rootid = id.
ttrreeeeaaddddrr
bit-encoded location of star in subtree.
rriinnggssiizzee
0 for stars. For nonleaf nodes, this is the semimajor axis or
instantaneous separation (according to ``kira sep''). This
field isn't multiplied by the scale factor given in kira sep; it
gives the actual distance in kira units.
ssqqrrttmmaassss
Square root of mass/Msun. Might be useful for luminosity
scaling.
mmuu
Mass ratio for center-of-mass nodes. Zero for stars.
44..99..22.. HHeerrttzzsspprruunngg--RRuusssseellll ddiiaaggrraamm
The H-R diagram can be invoked via the More... menu (upper left) or by
the kira hrdiag on control command. Axes for this plot are log
temperature (initial range from 5 to 3) and log luminosity (initial
range -4 to 6). Ranges may be changed with the kira hrdiag range
command or with keystrokes.
Keystroke commands in the H-R window:
bb//BB
Adjust the (b)rightness (dot size) of the dots plotted for each
star. Small b brightens (enlarges); capital B shrinks.
aa//AA
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.
vv//VV
Zoom out (v) or in (V) by 33%. The point under the cursor
becomes the center of the view.
44..99..33.. kkiirraa ccoonnttrrooll ccoommmmaannddss
Viewing control options for kira/Starlab formatted data that have been
read in with the kira Data Command. All control commands begin with
kira too.
kkiirraa nnooddee {{oonn||ooffff||rroooott}}
Show or hide center-of-mass nodes for multiple stars. With on,
show CM nodes for each level in a binary tree. With root, show
only the top-level CM node for each multiple.
kkiirraa rriinngg {{oonn||ooffff||rroooott}}
Show circles around multiple stars; on and root as above.
kkiirraa ttrreeee {{oonn||ooffff||ccrroossss||ttiicckk}} [[_t_i_c_k_s_c_a_l_e]
Show lines connecting pairs of stars at each binary-tree level
in a multiple group. With cross, also show a perpendicular line
-- a tick mark -- which crosses at the CM point, and whose
length is tickscale (default 0.5) times the true separation of
the pair. With tick, just show the tick-mark with no connecting
line.
kkiirraa ssiizzee [[sseepp||sseemmii]] [[_r_i_n_g_s_c_a_l_e_f_a_c_t_o_r]
Determines 3-D size of circles when kira ring on. With kira
size sep, ring diameter is scalefactor * instanteous separation.
With kira size semi, ring radius is scalefactor * a (the
semimajor axis of the two-body system, or |a| for hyperbolic
orbits). Using semi gives typically more stable-looking rings,
though they will pop if they become marginally (un-)bound.
Default: kira size semi 1.5.
kkiirraa ssccaallee _r_i_n_g_s_c_a_l_e_f_a_c_t_o_r
Synonym for kira size above.
kkiirraa ssppaann _m_i_n_p_i_x _m_a_x_p_i_x
Sets screen-space (pixel) size limits on rings. They'll never
get smaller than radius _m_i_n_p_i_x nor larger than _m_a_x_p_i_x,
regardless of true 3-D size. Thus even vanishingly tight
binaries can always be visibly marked. Default: kira span 2 50.
kkiirraa ttrraacckk _i_d|on|off
As particle _i_d 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. kira track off
disables tracking, and kira track on re-enables it. Use the p
key or mouse button 2 to pick a particle (or CM node if kira
node on) to see its numeric _i_d. Transient center-of-mass nodes
(shown if kira node on) can be tracked while they exist.
kkiirraa mmssccaallee _m_a_s_s_s_c_a_l_e_f_a_c_t_o_r[!]
Set/check the mass scale factor. Starlab dynamical mass values
are multiplied by this factor for reporting to the user.
Normally _m_a_s_s_s_c_a_l_e_f_a_c_t_o_r should equal the initial cluster mass
in solar-mass units. For some input files, starlab can
determine what was specified in the original kira run. If so,
``kira mscale _n_u_m_b_e_r'' will be ignored unless _n_u_m_b_e_r ends with
an exclamation point (!). So with no !, the user (or .cf
script) provides a default value; use ! to override the original
mass scale.
kkiirraa iinntt _s_e_l_d_e_s_t [= _s_e_l_s_r_c]
Track interactions between particles. As the cluster evolves,
whenever any star matching selection-expression _s_e_l_s_r_c
encounters (is a member of the same kira tree as) another
particle, then the other particle is added to the _s_e_l_d_e_s_t set.
If _s_e_l_d_e_s_t and _s_e_l_s_r_c are the same (or if ``= _s_e_l_s_r_c'' is omitted), then kira int computes the transitive closure of the
interaction set. Otherwise, only stars that encounter members
of the initial _s_e_l_s_r_c set become members of the _s_e_l_d_e_s_t set.
Example:
cclliicckk oonn ssoommee ssttaarr
The clicked-on star(s) become members of the pick set.
sseell xx == ppiicckk
Save a copy in the new set named x.
kkiirraa iinntt xx
Accumulate encounters in the set x.
eemmpphh xx
Increase brightness of members of x.
kkiirraa ttrraaiill xx
Extend trails from these set members.
kkiirraa ttrraaiill _s_e_l_e_x_p_r_e_s_s_i_o_n|off
Leave trails behind particles selected by _s_e_l_e_x_p_r_e_s_s_i_o_n (see the
sel 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:
kkiirraa ttrraaiill aallll
Makes trails grow behind all particles (including CM nodes,
if they're displayed)
kkiirraa ttrraaiill ppiicckk
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.
tthhrreesshh --ss bbiigg mmaassss >> 11..55
threshold when masses are larger than 1.5
kkiirraa ttrraaiill bbiigg
These two commands (a) select all stars exceeding 1.5 solar
masses and (b) extend trails behind them.
kkiirraa ttrraaiill cclleeaarr
Erase current trails, but let them continue to accumulate as
time passes.
kkiirraa mmaaxxttrraaiill _n_s_a_m_p_l_e_s
Set how many time-points are kept for each particle's trail,
initially 50.
kkiirraa hhrrddiiaagg oonn||ooffff
toggle to turn HD Diagram on or off. Initially off.
kkiirraa hhrrddiiaagg rraannggee _l_o_g_T_l_e_f_t _l_o_g_T_r_i_g_h_t _l_o_g_L_b_o_t_t_o_m _l_o_g_L_t_o_p
set limits on the HD Diagram axes.
44..1100.. TTeexxttuurreess
To make polygons be textured:
+o Use a series of texture data-commands to provide a table of textures, each named by a small integer _t_e_x_t_u_r_e_-_i_n_d_e_x;
+o Create a data field in each particle whose value is the _t_e_x_t_u_r_e_-
_i_n_d_e_x for that particle's polygon
+o Use data-command texturevar _f_i_e_l_d_n_o to specify which data field
that is.
+o Use control commands (poly, polylumvar, polysize) to enable drawing
polygons and textures, and to give the polygons nonzero size.
+o Possibly use control command polysides to specify 4-sided polygons
-- a bit faster to draw than default 11-gons.
It doesn't matter whether the texture-index data field is given a
datavar name.
For each particle, if the value of its _t_e_x_t_u_r_e_v_a_r'th field either (a)
doesn't match the value in some texture command or (b) the file named
in that texture command couldn't be read, then its polygon is drawn as
if texturing were disabled.
44..1111.. CCoooorrddiinnaatteess aanndd CCoooorrddiinnaattee TTrraannssffoorrmmaattiioonnss
Matrices as for the ttffmm command are intended to be multiplied by an
object-coordinate row vector on the left, so that 4x4 matrices specify
a translation in their 13th through 15th entries. Generally they're
in the sense of an object-or-camera-to-world transform.
The six- or seven-number transforms (_t_x _t_y _t_z _r_x _r_y _r_z
[it/scalefactor/], as accepted by the ttffmm and jjuummpp commands) are
interpreted as
_P_w_o_r_l_d _= _P_o_b_j_e_c_t _* _s_c_a_l_e_f_a_c_t_o_r _* rotY(_r_y) * rotX(_r_x) * rotZ(_r_z) *
translate(_t_x_,_t_y_,_t_z)
44..1122.. CCoolloorrmmaapp FFiilleess
Colormap files, as read by the cmap and vcmap commands, are line-
oriented text files. Blank lines are ignored, as are # comments. The
first nonblank, non-comment line gives the colormap _s_i_z_e (number of
entries). Later lines may have the form
<it/R G B/
giving red, green, and blue, each in the range 0 .. 1. Typically
there will be _s_i_z_e of these lines. However the colormap need not be
written sequentially; a line like
<it/colorindex/: <it/R G B/
places that RGB value at that _c_o_l_o_r_i_n_d_e_x, in the range 0 .. _s_i_z_e-1.
Later _R _G _B lines are assigned to _c_o_l_o_r_i_n_d_e_x_+_1, _c_o_l_o_r_i_n_d_e_x_+_2 and so
on. Also,
<it/colorindex/ := <it/oldcolorindex/
copies the (previously-assigned) RGB value from _o_l_d_c_o_l_o_r_i_n_d_e_x and
assigns it to _c_o_l_o_r_i_n_d_e_x.
55.. VViieewwiinngg WWiinnddooww KKeeyybbooaarrdd SShhoorrttccuuttss
Commands that you can give from within the viewing window are all
single keystroke commands, often combined with moving the mouse. TAB change focus to command window for Control Commands
S/s toggle STEREO mode (need blue/red glasses :-)
modes: mono redcyan crosseyed glasses
See also the 'stereo' View Command
> single frame forward stepping, in time animation mode
< single frame backward stepping, in time animation mode
Button-N various translation/rotation/zoom, depending on mode (fly/orbit/rot/tran)
SHIFT + Button-N modifier to the usual Button-N action, to have more fine control
CTRL + Button-N modifier to orbit-mode, e.g. to do translations instead of rotations
playmodes:
s playnow
l loop (rock)
f,e playevery=1
r,t playevery=0
Gview.cpp : Fl_Gview::handle()
cw reset camera position
p identify nearest object under mouse cursor
P pick that object as the new origin
o ORBIT mode
f FLY mode
r ROTATE mode
t TRANSLATE mode
O toggle perspective mode
v make field of view larger
V make field of view smaller
^v toggle debug output
@ report viewpoint position
= show object-to-world, world-to-object 4x4 matrices
(precede by object name, e.g. "c=", "g3=")
ESC exit
PrintScreen Take image snapshot of current view
< > Step backwards/forwards in dynamical time
(numeric prefix sets time step)
{ } Animate backwards/forwards in dynamical time
~ Fermionic dynamical-time animation toggle:
cycle between stop/forward/stop/backward/...
z Z Halve/double animation speed (dyn units/sec)
(numeric prefix sets animation speed)
66.. PPaarrttiivviieeww aanndd NNEEMMOO
The program snapspecks converts a NEMO snapshot to specks format that
can be read in directly by partiview. The default viewing variables
are x,y,z,m, but you can add and changed them by using the ooppttiioonnss==
keyword. In fact, arbitrary _b_o_d_y_t_r_a_n_s expressions can be used for
output. In the following example a 32-body Plummer sphere is created,
which is then given a power-law mass spectrum (with slope -2) between
0.5 and 10 mass units, and animated:
______________________________________________________________________
% mkplummer - 32 |\
snapmass - - massname='n(m)' masspars=p,-2 massrange=0.5,10 |\
hackcode1 - run1.dat % snapspecks run1.dat > run1.tab
% partiview run1.cf
% cat run1.cf
read run1.tab
eval labels off
eval lum lum 0 1
eval polylumvar point-size .1 area
texturevar 4
eval psize 5000
eval slum 5
eval every 1
______________________________________________________________________
77.. TTiippss
During animation the trip/back buttons can effectively be used to
return to a point in time where you want to return back to if you
wanted to browse around some specific point in time.
You can spend most of the time moving in [o]rbit mode. Left-button
moves around chosen center; control-left pans around the sky. As
opposed to switching to 't' mode to zoom and translate, you can also
use SHIFT-Mouse-1 and SHIFT-Mouse-3 to achieve the same from the other
('o', 'f') modes.
To make an animation, create an executable shell script movie1 with
for example the following commands:
______________________________________________________________________
#! /bin/csh -f
#
echo step 0
echo update
echo snapshot
echo step 0.01
echo update
echo snapshot
echo step 0.02
echo update
echo snapshot
echo step 0.03
echo update
echo snapshot
...
______________________________________________________________________
the Control Command async movie1, and it will create files
snap.000.sgi, snap.001.sgi, .... and already with xv a movie can be
shown:
______________________________________________________________________
xv -wait 0 snap.???.sgi
______________________________________________________________________
To make animated GIFs, here are some examples with common software, all with a default 0.1 sec delay between frames. Some animation
software (e.g. xanim) can change these:
______________________________________________________________________
convert -delay 10 -loop 0 snap.???.sgi try1.gif
gifsicle -d 10 snap.???.gif > try2.gif
______________________________________________________________________
The script will run asynchronously within partiview, so if you then
use the mouse to change orientation or zoom, these actions (minus the
location of the mouse of course) will be nicely recorded in the
snapshots.
88.. BBuuggss,, FFeeaattuurreess aanndd LLiimmiittaattiioonnss
Here is a list of known peculiarities, some of them bugs, others just
features and others limitations, and there is always that class of
things I simply have not understood how it works.
88..11.. LLiimmiittaattiioonnss ww..rr..tt.. VViirrDDiirr::
1. cannot set an auto-motion, as we can in the dome, although one
could of course load a path and move through the dataset :-) I was
able to make a path (*.wf) file and load that though. Now mostly
solved via the Inertia toggle under the More button from the Top
Row Window.
88..22.. SSoommee nnootteess ffoorr nneewwccoommeerrss ttoo VViirrDDiirr
Although starting virdir is very similar to partiview,
______________________________________________________________________
% parti gal2.cf
or,
% virir gal2.cf
______________________________________________________________________
the seasoned partiview user will need to relearn a few modes to get
used to virdir. In particular, at AMNH starting virdir will probably
cause your console screen (which is normally panel#1 on the dome) to
go dark with no visible command prompt. To regain control, type the
commands (blindly)
______________________________________________________________________
raise
fly
idle
______________________________________________________________________
which will put virdir in fly and animation mode.
Here are some important modes, make sure you keep the mouse in the
console window. It is easy to get it lost in any of the other 6
displays which are only visible on the dome.
1. Pushing the Left and Right mouse buttons simultaneously will send
the display to the HOME position.
2. Left mouse button will toggle the Pause mode in animate/fly mode.
3. Holding the Ctrl-button down while moving the mouse will bring your
point of interest into view
4. Holding the Alt-button down while moving the mouse will rotate
around your point of interest.
5. The 'p' key
6. The middle mouse button toggles Head display vs. Center display.
7. Holding the Shift-button down while moving the mouse will change
the available screen-space (works like a zoom).
99.. GGlloossssaarryy
1. group: particles can be grouped with the object command. If
multiple groups exist, a separate Group row will be activated
automatically.
2. data command, not to be confused with control command
3. control command, not to be confused with data command
4.