[ViewVC] Diff of: Development/ray/doc/man/man1/rtrace.1

Comparing ray/doc/man/man1/rtrace.1 (file contents):
Revision 1.7 by greg, Tue Apr 19 01:15:06 2005 UTC vs.
Revision 1.21 by greg, Sun Sep 26 15:49:39 2010 UTC

+.IP
+v       value (radiance)
+.IP
-+
+V       contribution (radiance)
-+
+.IP
+w       weight
+.IP
-<
+W       contribution
->
+W       color coefficient
+.IP
+l       effective length of ray
+.IP
+.IP
+M       material name
+.IP
-+
+~       tilde (end of trace marker)
-+
+.IP
+If the letter 't' appears in
+.I spec,
+then the fields following will be printed for every ray traced,
+If the capital letter 'T' is given instead of 't', then all rays will
+be reported, including shadow testing rays to light sources.
+Spawned rays are indented one tab for each level.
-+
+The tilde marker ('~') is a handy way of differentiating the final ray
-+
+value from daughter values in a traced ray tree, and usually appears
-+
+right before the 't' or 'T' output flags.
-+
+E.g.,
-+
+.I \-ov~TmW
-+
+will emit a tilde followed by a tab at the end of each trace,
-+
+which can be easily distinguished even in binary output.
+.IP
+Note that there is no space between this option and its argument.
+.TP
+Add
+.I mod
+to the trace include list,
-<
+so that it will be considered during the indirect calculation.
->
+so that it will be reported by the trace option.
+The program can use either an include list or an exclude
+list, but not both.
+.TP
+This option is especially useful in
+conjunction with ximage(1) for computing illuminance at scene points.
+.TP
-+
+.BR \-u
-+
+Boolean switch to control uncorrelated random sampling.
-+
+When "off", a low-discrepancy sequence is used, which reduces
-+
+variance but can result in a brushed appearance in specular highlights.
-+
+When "on", pure Monte Carlo sampling is used in all calculations.
-+
+.TP
+.BR \-I
+Boolean switch to compute irradiance rather than radiance,
+with the input origin and direction interpreted instead
+.I res.
+The output will be flushed after every
+.I res
-<
+input rays.
->
+input rays if
->
+.I \-y
->
+is set to zero.
->
+A value of one means that every ray will be flushed, whatever
->
+the setting of
->
+.I \-y.
+A value of zero means that no output flushing will take place.
+.TP
+.BI -y \ res
+.I \-f
+option, above.)
+.TP
-+
+.BI -n \ nproc
-+
+Execute in parallel on
-+
+.I nproc
-+
+local processes.
-+
+This option is incompatible with the
-+
+.I \-P
-+
+and
-+
+.I \-PP,
-+
+options.
-+
+Multiple processes also do not work properly with ray tree output
-+
+using any of the
-+
+.I \-o*t*
-+
+options.
-+
+There is no benefit from specifying more processes than there are
-+
+cores available on the system or the
-+
+.I \-x
-+
+setting, which forces a wait at each flush.
-+
+.TP
+.BI -dj \ frac
+Set the direct jittering to
+.I frac.
+.TP
+.BI -lr \ N
+Limit reflections to a maximum of
-<
+.I N.
->
+.I N,
->
+if N is a positive integer.
->
+If
->
+.I N
->
+is zero or negative, then Russian roulette is used for ray
->
+termination, and the
->
+.I -lw
->
+setting (below) must be positive.
->
+If N is a negative integer, then this sets the upper limit
->
+of reflections past which Russian roulette will be used.
->
+In scenes with dielectrics and total internal reflection,
->
+a setting of 0 (no limit) may cause a stack overflow.
+.TP
+.BI -lw \ frac
+Limit the weight of each ray to a minimum of
+.I frac.
-<
+During ray-tracing, a record is kept of the final contribution
-<
+a ray would have to the image.
-<
+If it is less then the specified minimum, the ray is not traced.
->
+During ray-tracing, a record is kept of the estimated contribution
->
+(weight) a ray would have in the image.
->
+If this weight is less than the specified minimum and the
->
+.I -lr
->
+setting (above) is positive, the ray is not traced.
->
+Otherwise, Russian roulette is used to
->
+continue rays with a probability equal to the ray weight
->
+divided by the given
->
+.I frac.
+.TP
+.BR -ld
+Boolean switch to limit ray distance.
+.SH EXAMPLES
+To compute radiance values for the rays listed in samples.inp:
+.IP "" .2i
-<
+rtrace -ov scene.oct < samples.inp > radiance.out
->
+rtrace \-ov scene.oct < samples.inp > radiance.out
+.PP
+To compute illuminance values at locations selected with the 't'
+command of
+.I ximage(1):
+.IP "" .2i
-<
+ximage scene.pic | rtrace -h -x 1 -i scene.oct | rcalc -e '$1=47.4*$1+120*$2+11.6*$3'
->
+ximage scene.hdr | rtrace \-h \-x 1 \-i scene.oct | rcalc \-e '$1=47.4*$1+120*$2+11.6*$3'
+.PP
+To record the object identifier corresponding to each pixel in an image:
+.IP "" .2i
-<
+vwrays -fd scene.pic | rtrace -fda `vwrays -d scene.pic` -os scene.oct
->
+vwrays \-fd scene.hdr | rtrace \-fda `vwrays \-d scene.hdr` \-os scene.oct
+.PP
+To compute an image with an unusual view mapping:
+.IP "" .2i
-<
+cnt 640 480 | rcalc -e 'xr:640;yr:480' -f unusual_view.cal | rtrace
-<
+-x 640 -y 480 -fac scene.oct > unusual.pic
->
+cnt 480 640 | rcalc \-e 'xr:640;yr:480' \-f unusual_view.cal | rtrace
->
+\-x 640 \-y 480 \-fac scene.oct > unusual.hdr
+.SH ENVIRONMENT
+RAYPATH         the directories to check for auxiliary files.
+.SH FILES
+Greg Ward
+.SH "SEE ALSO"
+getinfo(1), lookamb(1), oconv(1), pfilt(1), pinterp(1),
-<
+pvalue(1), rpict(1), rvu(1), vwrays(1), ximage(1)
->
+pvalue(1), rpict(1), rtcontrib(1), rvu(1), vwrays(1), ximage(1)

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines (old)
->
+Changed lines (new)

Comparing ray/doc/man/man1/rtrace.1 (file contents): Revision 1.7 by greg, Tue Apr 19 01:15:06 2005 UTC vs. Revision 1.21 by greg, Sun Sep 26 15:49:39 2010 UTC

Diff Legend

Comparing ray/doc/man/man1/rtrace.1 (file contents):
Revision 1.7 by greg, Tue Apr 19 01:15:06 2005 UTC vs.
Revision 1.21 by greg, Sun Sep 26 15:49:39 2010 UTC