Skip to content
Snippets Groups Projects
Commit 29f738e4 authored by slevy's avatar slevy
Browse files

Misc small changes, documenting some of the not-yet-written items. 

More texture options.
Describe new kira features (trails, H-R diagram, etc.).
Move them into their own kira/Starlab section.
XXX "sel" command not yet documented.
parent 0d5e056a
No related branches found
No related tags found
No related merge requests found
Hide whitespace changes
Inline Side-by-side
Showing
with 385 additions and 124 deletions
doc/partiview.sgml
+ 385
− 124
View file @ 29f738e4
......@@ -16,7 +16,7 @@
<title> Partiview (PC-VirDir)
<author> Peter Teuben, Stuart Levy
<date> 19 March 2001
<date> 2 May 2001
<abstract>
This document helps you installing and running the development version
of partiview.
......@@ -34,7 +34,7 @@ out, in particular the detailed description of all the commands.
<sect> Installation
<p>
This assumes you have the October 2000 release (version 0.1 or later) of
This assumes you have the July 2001 release (version 0.6 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
files (Mesa, FLTK) on our initial
......@@ -96,7 +96,7 @@ Extract the tarball, and install the program from within the
<tt/src/ directory:
<tscreen><code>
% tar zxf partiview-0.5.tar.gz
% tar zxf partiview-0.6.tar.gz
% cd partiview-0.5/src
% make clean (if you really must compile a new executable)
......@@ -107,7 +107,7 @@ Extract the tarball, and install the program from within the
<sect1> CVS
<p>
Since <tt/partiview-0.3/ is under CVS control, and occasionally we
<tt/partiview-0.5/ 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
......@@ -134,7 +134,7 @@ used CVS commands:
emacs partibrains.c # edit some files
make all # compile the program
./partiview # test the program
emacs partipanel.cc # edit another file
emacs kira_parti.cc # edit another file
make all # check if it still compiles
cvs -n -q update # check if anybody else made changes
......@@ -189,6 +189,8 @@ 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 <tt/.partiviewrc/ file may contain commands like
<tt/eval winsize 600 400/.)
Hit the TAB key to bring focus to the (one line) command window inbetween
......@@ -274,7 +276,8 @@ The top row, from left to right, shows the following buttons:
<descrip>
<tag> More </tag>
Nothting implemented here yet.
Offers some mode switches: <tt/inertia/ (not yet implemented)
and a button to invoke an H-R diagram window.
<tag> [g1] </tag>
Pulldown g1, g2, ... (or whichever group)
......@@ -590,6 +593,7 @@ Select group g<it/N/. Create a new group if it doesn't already exist.
<tag>
g<it/N/=<it/alias/ </tag>
Assign name <it/alias/ to group g<it/N/.
Note no blanks around the <tt/=/ sign.
<tag>
object <it/objectname/
......@@ -727,6 +731,12 @@ 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>
winsize [<it/XSIZE/ [<it/YSIZE/]]
</tag>
Resize graphics window. With no arguments, reports current size.
With one argument, resizes to given width, preserving aspect ratio.
<tag>
bgcolor <it/R G B/
</tag>
......@@ -760,7 +770,7 @@ distance.
<tag>
stereo [on|off|redcyan|glasses] [<it/separation/]
</tag>
Stereo display. Also toggled on/off by typing <tt/'s'> key in graphics window.
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.
......@@ -770,7 +780,7 @@ 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/]
snapset [<tt/-n/ <it/FRAMENO/] <it/FILESTEM/ [<it/FRAMENO/]
</tag>
Set parameters for future <tt/snapshot/ commands.
<it/FILESTEM/ may be a printf format string with frame number as
......@@ -845,8 +855,10 @@ scale-lum
<tag>
ptsize <it/minpixels/ <it/maxpixels/
</tag>
Specifies the range of <it/apparent/ sizes of points,
in pixels. Typical values might be <tt/ptsize 0.1 5/.
The graphics system may silently impose an upper limit
of about 10 pixels.
<!-- DEPRECATED COMMAND
<tag>
......@@ -865,6 +877,9 @@ polylum
<tag>
polyminpixels
</tag>
<tag>
polymin <it/minradius/ [<it/maxradius/]
</tag>
<tag>
color
......@@ -891,8 +906,9 @@ color
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/.
Once the <tt/exact/ tag is set (for a particular data-field),
it's sticky. To interpret that data field 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,
......@@ -1000,7 +1016,9 @@ shows a
<tag>
polyside(s)
</tag>
Number of sides a polygon should have
Number of sides a polygon should have. Default 11, for fairly round
polygons. For textured polygons, <tt/polysides 4/ might do as well,
and be slightly speedier.
<tag>
fast
......@@ -1008,26 +1026,31 @@ fast
see also <tt/ptsize/
<tag>
ptsize
ptsize <it/minpixels/ [<it/maxpixels/]
</tag>
makes more sense than <tt/fast/.
Specifies range of apparent (pixel) size of points.
Those with computed sizes (based on luminosity
and distance) smaller than <it/minpixels/ are
randomly (but repeatably) subsampled -- i.e. some
fraction of them are not drawn. Those computed to be
larger than <it/maxpixels/ are drawn at size
<it/maxpixels/.
<tag>
gamma
gamma <it/displaygamma/
</tag>
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 <tt/gamma 1/ through <tt/gamma 2.5/ or so.
Larger values raise the apparent brightness of dim things.
<tag>
alpha [float]
alpha <it/alpha/
</tag>
Get or set the alpha value.
<!-- NOTYET
<tag>
fog
</tag>
-->
Get or set the alpha value, in the range 0 to 1; it determines
the opacity of polygons.
<tag>
speed
......@@ -1040,7 +1063,8 @@ step [<it/timestep/]
</tag>
For time-varying data, sets current timestep number.
Real-valued times are meaningful for some kinds of data including those
from starlab; for others, times are rounded to nearest integer.
from Starlab/kira; for others, times are rounded to nearest integer.
If running, <tt/step/ also stops datatime animation. (See <tt/run/.)
<tag>
step [+|-]<it/deltatimestep/
......@@ -1054,63 +1078,10 @@ If preceded with a plus or minus sign, adds that amount to current time.
run
</tag>
<tag>
tfm
</tag>
<tag>
kiractl
tfm
</tag>
viewing control options for kira (starlab)
formatted data that have been read in with
the <tt/kira/ Data Command.
<descrip>
<tag> kira node {on|off|root} </tag>
Show or hide center-of-mass nodes for multiple stars.
With <tt/on/, show CM nodes for each level in a binary tree.
With <tt/root/, show only the top-level CM node for each multiple.
<tag> kira ring {on|off|root} </tag>
Show circles around multiple stars; <tt/on/ and <tt/root/ as above.
<tag> kira tree {on|off|cross|tick} [<it/tickscale/] </tag> <p>
Show lines connecting pairs of stars at each binary-tree level
in a multiple group. With <tt/cross/, also show a perpendicular
line -- a tick mark -- which crosses at the CM point,
and whose length is <tt/tickscale/ (default 0.5) times the
true separation of the pair.
With <tt/tick/, just show the tick-mark with no connecting line.
<tag> kira size [sep|semi] [<it/ringscalefactor/] </tag>
Determines 3-D size of circles when <tt/kira ring on/.
With <tt/kira size sep/, ring diameter is scalefactor * instanteous
separation. With <tt/kira size semi/, ring radius is scalefactor * a
(the semimajor axis of the two-body system, or <tt/|a|/ for
unbound orbits). Using <tt/semi/ gives typically more stable-looking
rings, though they will pop if they become marginally (un-)bound.
Default: <tt/kira size semi 1.5/.
<tag>kira scale <it/ringscalefactor/</tag>
Another way to set the scale factor for <tt/kira size/ above.
<tag> kira span <it/minpix/ <it/maxpix/ </tag>
Sets screen-space (pixel) size limits on rings.
They'll never get smaller than radius <it/minpix/ nor larger than
<it/maxpix/, regardless of true 3-D size. Thus even vanishingly
tight binaries can always be visibly marked.
Default: <tt/kira span 2 50/.
<tag> kira track <it/id/|on|off </tag>
As particle <it/id/ 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.
<tt/kira track off/ disables tracking, and <tt/kira track on/
re-enables it.
Use the <tt/p/ key or mouse button 2 to pick a particle
(or CM node if <tt/kira node on/) to see its numeric <it/id/.
Transient center-of-mass nodes (shown if <tt/kira node on/)
can be tracked while they exist.
</descrip>
<p>
......@@ -1120,12 +1091,6 @@ the <tt/kira/ Data Command.
move on|off
</tag>
<!-- DEPRECATED
<tag>
move-objects on|off
</tag>
-->
<tag>
fwd
......@@ -1415,6 +1380,76 @@ Draw a box, using any of the following formats:
</descrip>
<tt/level/ determines color.
<tag>
<tt/mesh/ [<tt/-t/ <it/txno/] [<tt/-c/ <it/cindex/] [<tt/-s/ <it/style/]
</tag>
Draw a quadrilateral mesh, optionally colored or textured.
Following the <bf/mesh/ line, provide a line with the mesh dimensions:
<verb><it/nu nv/</verb>
Following this comes the list of <it/nu/*<it/nv/ 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 <tt/-t/ texture was
specified, then two more fields give its u and v texture coordinates.
<p>
Options:
<descrip>
<tag> <tt/-t/ <it/txno/ </tag> Apply texture number <it/txno/ to surface.
In this case, each mesh vertex should also include
u and v texture coordinates.
<tag> <tt/-c/ <it/colorindex/ </tag> Color surface with color from
integer cmap entry <it/colorindex/.
<tag> <tt/-s/ <it/style/ </tag>
Drawing style: <descrip>
<tag> <it/solid/ </tag> filled polygonal surface (default)
<tag> <it/wire/ </tag> just edges
<tag> <it/point/ </tag> just points (one per mesh vertex)
</descrip>
</descrip>
<tag>
<it/Xcen Ycen Zcen/ ellipsoid <it/[options]... [transformation]/
</tag>
Draw an ellipsoid, specified by:
<descrip>
<tag> <tt/Xcen Ycen Zcen/ </tag> Center position in world coordinates
<tag> <tt/-c/ <it/colorindex/ </tag> Integer color index (default -1 => white)
<tag> <tt/-s/ <it/style/ </tag>
Drawing style: <descrip>
<tag> <it/solid/ </tag> filled polygonal surface (default)
<tag> <it/plane/ </tag> 3 ellipses: XY, XZ, YZ planes
<tag> <it/wire/ </tag> latitude/longitude ellipses
<tag> <it/point/ </tag> point cloud: one per lat/lon intersection
</descrip>
<tag> <tt/-r/ <it/Xradius/[,<it/Yradius/,<it/Zradius/] </tag>
Radius (for sphere) or semimajor axes (for ellipsoid)
<tag> <tt/-n/ <it/nlat[,nlon]/ </tag>
Number of latitude and longitude divisions.
Relevant even for <it/plane/ style, where they determine
how finely the polygonal curves approximate circles.
Default <it/nlon/ = <it/nlat//2 + 1.
<tag> <it/transformation/ </tag>
Sets the spatial orientation of the ellipsoid.
May take any of three forms:
<descrip>
<tag> (nothing) </tag> If absent, the ellipsoid's
coordinate axes are the same as the world axes
for the group it belongs to.
<tag> 9 blank-separated numbers </tag>
A 3x3 transformation matrix T from ellipsoid coordinates
to world coordinates, in the sense
Pworld = Pellipsoid * T + [Xcen, Ycen, Zcen].
<tag> 16 blank-separated numbers </tag>
A 4x4 transformation matrix, as above but for the
obvious changes.
</descrip>
</descrip>
<tag>
annot <it/[-t timestep] string .../
</tag>
......@@ -1446,12 +1481,12 @@ execute a Control Command.
<tag>
feed <it/command/
</tag>
Synonymous for <tt/eval/
Synonym for <tt/eval/.
<tag>
VIRDIR <it/command/
</tag>
Synonymous for <tt/eval/
Synonym for <tt/eval/.
<!-- DEPRECATED COMMAND
<tag>
......@@ -1482,43 +1517,50 @@ relevant if texturing is enabled.
Actually, unit vectors aren't essential; making them different lengths
yields non-circular polygonal disks.
<p>
If <tt/polyorivar/ is specified but some polygons should still lie in the
screen plane, use values <tt/9 9 9 9 9 9/.
If <tt/polyorivar/ is specified for the group, but some polygons should
still lie in the screen plane, use values <tt/9 9 9 9 9 9/ for those polygons.
<tag>
texture [-lmnMDB] <it/txno file.sgi/
texture [-aiAOlmnMDB] <it/txno file.sgi/
</tag>
<descrip>
<tag> -a(lpha) </tag>
A single-channel image would normally be used as luminance data.
With <tt/-a/, the image is taken as opacity data instead
(GL_ALPHA texture format).
<tag> -i(ntensity) </tag>
For 1- or 3-channel images, compute the intensity of each pixel
and use it to form an alpha (opacity) channel.
<tag> -A(dd) </tag>
Use additive blending. This texture will add to, not obscure,
the brightness of whatever lies behind it (i.e. whatever is drawn later).
<tag> -O(ver) </tag>
Use "over" compositing. This texture will obscure features lying
behind it according to alpha values at each point.
<!--
<tag> -l(inear) </tag> <p>
<tag> -m(ipmap) </tag> <p>
<tag> -n(earest) </tag> <p>
<tag> -M(odulate) </tag> <p>
-->
<tag> -M(odulate) </tag>
Multiply texture brightness/color values by the colormap-determined
color of each particle.
<tag> -D(ecal) </tag> <p>
The textured polygon's color is determined entirely by the texture,
suppressing any colormapped color.
<tag> -B(lend) </tag> <p>
Probably not very useful.
</descrip>
<tag>
texturevar <it/fieldno/
texturevar <it/field/
</tag>
To make polygons be textured:
<itemize>
<item>Use a series of <tt/texture/ data-commands to provide a table
of textures, each named by a small integer <it/texture-index/;
<item>Create a data field in each particle whose value is the
<it/texture-index/ for that particle's polygon
<item>Use data-command <tt/texturevar /<it/fieldno/ to specify which
data field that is.
<item>Use control commands (<tt/poly/, </polylumvar/, </polysize/)
to enable drawing polygons and textures,
and to give the polygons nonzero size.
<item>Possibly use control command <tt/polysides/ to specify
4-sided polygons -- a bit faster to draw than default 11-gons.
</itemize>
It doesn't matter whether the texture-index data field is given a datavar name.
<p>
If a particle's texture-index field's value doesn't correspond to anything
defined by a <tt/texture/ command, then its polygon is drawn as if
texturing were disabled.
If polygon-drawing and texturing are turned on, use the given
<it/field/ (datavar name or number) in each particle to select
which texture (if any) to draw on its polygon.
<tag>
coord <it/name ... 16 world-to-coord tfm floats (GL order)/
......@@ -1547,15 +1589,228 @@ Label subsequent data with this <it/time/ (a non-negative integer).
<it/Xpos Ypos Zpos Var0 .... /
</tag>
These lines, with XYZ positions in the first 3 columns, will make up the bulk
of the dataset. The 4th and subsequent columns contain the values of the
of a typical dataset. The 4th and subsequent columns contain the values of the
datavariables as named with the <bf/datavar/ commands. Note that
data variables are 0-based.
data variable (field) numbers are 0-based.
</descrip>
<!---------------------------------------------------------------------- -->
<sect1> Textures
<sect1> Kira/Starlab </>
To read Kira output, in human-readable or binary <bf/tdyn/ form, use the
``<tt/kira/ <it/kirafilename/'' data-command.
<p>
<sect2> Kira particle attributes </>
<p>
The particles read in have the following attributes:
<descrip>
<tag> id </>
positive integer worldline index for single stars
(matching the id in the kira stream).
For non-leaf (center-of-mass) tree nodes, <tt/id/ is a
negative integer.
<tag> mass </>
Mass, in solar mass units (see ``kira mscale'' control command).
<tag> nclump </>
Number of stars in this particle's subtree.
1 for isolated stars, 2 for binaries, etc.
<tag> Tlog </>
base-10 log of temperature (K)
<tag> Lum </>
Luminosity in solar-mass units. (Note this is linear, not log luminosity.)
<tag> stype </>
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.
<tag> rootid </>
id of root of subtree. For single stars, rootid = id.
<tag> treeaddr </>
bit-encoded location of star in subtree.
<tag> ringsize </>
0 for stars.
For nonleaf nodes, this is the semimajor axis or instantaneous
separation (according to ``<tt/kira sep/'').
This field isn't multiplied by the scale factor given in
<tt/kira sep/; it gives the actual distance in kira units.
<tag> sqrtmass </>
Square root of mass/Msun. Might be useful for luminosity scaling.
<tag> mu </>
Mass ratio for center-of-mass nodes. Zero for stars.
</descrip>
<p>
<sect2> Hertzsprung-Russell diagram </>
The H-R diagram can be invoked via the <tt/More.../ menu (upper left)
or by the <tt/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 <tt/kira hrdiag range/ command or with keystrokes.
<p>
Keystroke commands in the H-R window:
<descrip>
<tag> b/B </>
Adjust the (b)rightness (dot size) of the dots plotted for each star.
Small b brightens (enlarges); capital B shrinks.
<tag> a/A </>
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.
<tag> v/V </>
Zoom out (v) or in (V) by 33%. The point under the cursor
becomes the center of the view.
</descrip>
<sect2> kira control commands </>
<p>
Viewing control options for kira/Starlab
formatted data that have been read in with
the <tt/kira/ Data Command.
All control commands begin with <tt/kira/ too.
<descrip>
<tag> kira node {on|off|root} </tag>
Show or hide center-of-mass nodes for multiple stars.
With <tt/on/, show CM nodes for each level in a binary tree.
With <tt/root/, show only the top-level CM node for each multiple.
<tag> kira ring {on|off|root} </tag>
Show circles around multiple stars; <tt/on/ and <tt/root/ as above.
<tag> kira tree {on|off|cross|tick} [<it/tickscale/] </tag> <p>
Show lines connecting pairs of stars at each binary-tree level
in a multiple group. With <tt/cross/, also show a perpendicular
line -- a tick mark -- which crosses at the CM point,
and whose length is <tt/tickscale/ (default 0.5) times the
true separation of the pair.
With <tt/tick/, just show the tick-mark with no connecting line.
<tag> kira size [sep|semi] [<it/ringscalefactor/] </tag>
Determines 3-D size of circles when <tt/kira ring on/.
With <tt/kira size sep/, ring diameter is scalefactor * instanteous
separation. With <tt/kira size semi/, ring radius is scalefactor * a
(the semimajor axis of the two-body system, or <tt/|a|/ for
hyperbolic orbits). Using <tt/semi/ gives typically more stable-looking
rings, though they will pop if they become marginally (un-)bound.
Default: <tt/kira size semi 1.5/.
<tag>kira scale <it/ringscalefactor/</tag>
Synonym for <tt/kira size/ above.
<tag> kira span <it/minpix/ <it/maxpix/ </tag>
Sets screen-space (pixel) size limits on rings.
They'll never get smaller than radius <it/minpix/ nor larger than
<it/maxpix/, regardless of true 3-D size. Thus even vanishingly
tight binaries can always be visibly marked.
Default: <tt/kira span 2 50/.
<tag> kira track <it/id/|on|off </tag>
As particle <it/id/ 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.
<tt/kira track off/ disables tracking, and <tt/kira track on/
re-enables it.
Use the <tt/p/ key or mouse button 2 to pick a particle
(or CM node if <tt/kira node on/) to see its numeric <it/id/.
Transient center-of-mass nodes (shown if <tt/kira node on/)
can be tracked while they exist.
<tag> kira mscale <it/massscalefactor/[!] </tag>
Set/check the mass scale factor.
Starlab dynamical mass values are multiplied by this factor
for reporting to the user. Normally <it/massscalefactor/
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 <it/number/''
will be ignored unless <it/number/ ends with an exclamation point (!).
So with no <tt/!/, the user (or .cf script) provides a default value;
use <tt/!/ to override the original mass scale.
<tag> kira int <it/seldest/ [= <it/selsrc/] </tag>
Track interactions between particles.
As the cluster evolves, whenever any star matching
selection-expression <it/selsrc/ encounters (is a member of
the same kira tree as) another particle, then the other
particle is added to the <it/seldest/ set. If <it/seldest/
and <it/selsrc/ are the same (or if ``= <it/selsrc/'' is omitted),
then <tt/kira int/ computes the transitive closure of the
interaction set.
Otherwise, only stars that encounter members of the initial
<it/selsrc/ set become members of the <it/seldest/ set.
Example:
<descrip>
<tag> click on some star </tag>
The clicked-on star(s) become members of the <tt/pick/ set.
<tag> sel x = pick </tag>
Save a copy in the new set named <tt/x/.
<tag> kira int x </tag>
Accumulate encounters in the set <tt/x/.
<tag> emph x </tag>
Increase brightness of members of <tt/x/.
<tag> kira trail x </tag>
Extend trails from these set members.
</descrip>
<tag> kira trail <it/selexpression/|off </tag>
Leave trails behind particles selected by <it/selexpression/
(see the <tt/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:
<descrip>
<tag> kira trail all </tag>
Makes trails grow behind all particles
(including CM nodes, if they're displayed)
<tag> kira trail pick </tag>
Clicking on a star will make a trail grow behind it.
If several stars are within picking range,
trails will grow behind each of them.
<tag> thresh -s big mass >1.5 </tag>
<tag> kira trail big </tag>
These two commands (a) select all stars exceeding
1.5 solar masses and (b) extend trails behind them.
</descrip>
<tag> kira trail clear </tag>
Erase current trails, but let them continue to accumulate
as time passes.
<tag> kira maxtrail <it/nsamples/ </tag>
Set how many time-points are kept for each particle's trail,
initially 50.
<tag> kira hrdiag on|off </tag>
<tag> kira hrdiag range <it/logTleft logTright logLbottom logLtop/ </tag>
</descrip>
<!---------------------------------------------------------------------- -->
<sect1> Textures </>
<p>
To make polygons be textured:
<itemize>
<item>Use a series of <tt/texture/ data-commands to provide a table
of textures, each named by a small integer <it/texture-index/;
<item>Create a data field in each particle whose value is the
<it/texture-index/ for that particle's polygon
<item>Use data-command <tt/texturevar /<it/fieldno/ to specify which
data field that is.
<item>Use control commands (<tt/poly/, <tt/polylumvar/, <tt/polysize/)
to enable drawing polygons and textures,
and to give the polygons nonzero size.
<item>Possibly use control command <tt/polysides/ to specify
4-sided polygons -- a bit faster to draw than default 11-gons.
</itemize>
It doesn't matter whether the texture-index data field is given a datavar name.
<p>
For each particle, if the value of its <it/texturevar/'th field either
(a) doesn't match the value in some <tt/texture/ command or
(b) the file named in that <tt/texture/ command couldn't be read,
then its polygon is drawn as if texturing were disabled.
<!---------------------------------------------------------------------- -->
<sect1> Coordinates and Coordinate Transformations
......@@ -1591,18 +1846,18 @@ playmodes:
r,t playevery=0
Gview.cpp : Fl_Gview::handle()
w reset camera position
r ROTATE mode
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 ORBIT mode
O toggle perspective mode
v make field of view larger
V make field of view smaller
^v toggle debug output
@ dname [g1]
@ report viewpoint position
= show object-to-world, world-to-object 4x4 matrices
(precede by object name, e.g. "c=", "g3=")
ESC exit
......@@ -1615,7 +1870,6 @@ Gview.cpp : Fl_Gview::handle()
cycle between stop/forward/stop/backward/...
z Z Halve/double animation speed (dyn units/sec)
(numeric prefix sets animation speed)
(or by
</verb></tscreen>
......@@ -1657,6 +1911,8 @@ 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.
<p>
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.
......@@ -1668,13 +1924,19 @@ the other ('o', 'f') modes.
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.
<!--
<enum>
<item> in rotate mode, if you change the center of rotation with 'P',
item in rotate mode, if you change the center of rotation with 'P',
Button-1 works fine, but Button-3 does not rotate around the
new point correctly. It seems to remember the old (or 0,0,0)
origin.
No, this isn't true; not sure what you were seeing. It does
rotate about the center point with both button-1 and button-3.
In Orbit mode, button-3 translation still translates straight
forward; i.e. not toward the center point. Maybe that's what you mean?
-slevy.
</enum>
-->
<!--------------------------------------------------------------------------- -->
<sect1> Limitations w.r.t. VirDir:
......@@ -1688,5 +1950,4 @@ I was able to make a path (*.wf) file and load that though.
</enum>
</article>
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment

Contact help@ncsa.illinois.edu with questions regarding this site. | All rights reserved. ©2024 Board of Trustees of the University of Illinois. | Web Privacy Notice