ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/radiance/ray/doc/man/man1/rtrace.1
(Generate patch)

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.22 by greg, Fri Oct 8 22:08:26 2010 UTC

# Line 87 | Line 87 | d      direction (normalized)
87   .IP
88   v       value (radiance)
89   .IP
90 + V       contribution (radiance)
91 + .IP
92   w       weight
93   .IP
94 < W       contribution
94 > W       color coefficient
95   .IP
96   l       effective length of ray
97   .IP
# Line 109 | Line 111 | m      modifier name
111   .IP
112   M       material name
113   .IP
114 + ~       tilde (end of trace marker)
115 + .IP
116   If the letter 't' appears in
117   .I spec,
118   then the fields following will be printed for every ray traced,
# Line 116 | Line 120 | not just the final result.
120   If the capital letter 'T' is given instead of 't', then all rays will
121   be reported, including shadow testing rays to light sources.
122   Spawned rays are indented one tab for each level.
123 + The tilde marker ('~') is a handy way of differentiating the final ray
124 + value from daughter values in a traced ray tree, and usually appears
125 + right before the 't' or 'T' output flags.
126 + E.g.,
127 + .I \-ov~TmW
128 + will emit a tilde followed by a tab at the end of each trace,
129 + which can be easily distinguished even in binary output.
130   .IP
131   Note that there is no space between this option and its argument.
132   .TP
# Line 138 | Line 149 | must appear in a separate option.
149   Add
150   .I mod
151   to the trace include list,
152 < so that it will be considered during the indirect calculation.
152 > so that it will be reported by the trace option.
153   The program can use either an include list or an exclude
154   list, but not both.
155   .TP
# Line 169 | Line 180 | option (below) may be used to override this.
180   This option is especially useful in
181   conjunction with ximage(1) for computing illuminance at scene points.
182   .TP
183 + .BR \-u
184 + Boolean switch to control uncorrelated random sampling.
185 + When "off", a low-discrepancy sequence is used, which reduces
186 + variance but can result in a brushed appearance in specular highlights.
187 + When "on", pure Monte Carlo sampling is used in all calculations.
188 + .TP
189   .BR \-I
190   Boolean switch to compute irradiance rather than radiance,
191   with the input origin and direction interpreted instead
# Line 182 | Line 199 | Set the x resolution to
199   .I res.
200   The output will be flushed after every
201   .I res
202 < input rays.
202 > input rays if
203 > .I \-y
204 > is set to zero.
205 > A value of one means that every ray will be flushed, whatever
206 > the setting of
207 > .I \-y.
208   A value of zero means that no output flushing will take place.
209   .TP
210   .BI -y \ res
# Line 213 | Line 235 | format.
235   .I \-f
236   option, above.)
237   .TP
238 + .BI -n \ nproc
239 + Execute in parallel on
240 + .I nproc
241 + local processes.
242 + This option is incompatible with the
243 + .I \-P
244 + and
245 + .I \-PP,
246 + options.
247 + Multiple processes also do not work properly with ray tree output
248 + using any of the
249 + .I \-o*t*
250 + options.
251 + There is no benefit from specifying more processes than there are
252 + cores available on the system or the
253 + .I \-x
254 + setting, which forces a wait at each flush.
255 + .TP
256   .BI -dj \ frac
257   Set the direct jittering to
258   .I frac.
# Line 295 | Line 335 | may also be desirable in conjunction with the
335   .I \-i
336   option.
337   .TP
338 < .BI -sj \ frac
339 < Set the specular sampling jitter to
340 < .I frac.
341 < This is the degree to which the highlights are sampled
342 < for rough specular materials.
343 < A value of one means that all highlights will be fully sampled
344 < using distributed ray tracing.
338 > .BI -ss \ samp
339 > Set the specular sampling to
340 > .I samp.
341 > For values less than 1, this is the degree to which the highlights
342 > are sampled for rough specular materials.
343 > A value greater than one causes multiple ray samples to be sent
344 > to reduce noise at a commmesurate cost.
345   A value of zero means that no jittering will take place, and all
346   reflections will appear sharp even when they should be diffuse.
347   .TP
# Line 508 | Line 548 | source within a given scattering volume.
548   .TP
549   .BI -lr \ N
550   Limit reflections to a maximum of
551 < .I N.
551 > .I N,
552 > if N is a positive integer.
553 > If
554 > .I N
555 > is zero or negative, then Russian roulette is used for ray
556 > termination, and the
557 > .I -lw
558 > setting (below) must be positive.
559 > If N is a negative integer, then this sets the upper limit
560 > of reflections past which Russian roulette will be used.
561 > In scenes with dielectrics and total internal reflection,
562 > a setting of 0 (no limit) may cause a stack overflow.
563   .TP
564   .BI -lw \ frac
565   Limit the weight of each ray to a minimum of
566   .I frac.
567 < During ray-tracing, a record is kept of the final contribution
568 < a ray would have to the image.
569 < If it is less then the specified minimum, the ray is not traced.
567 > During ray-tracing, a record is kept of the estimated contribution
568 > (weight) a ray would have in the image.
569 > If this weight is less than the specified minimum and the
570 > .I -lr
571 > setting (above) is positive, the ray is not traced.
572 > Otherwise, Russian roulette is used to
573 > continue rays with a probability equal to the ray weight
574 > divided by the given
575 > .I frac.
576   .TP
577   .BR -ld
578   Boolean switch to limit ray distance.
# Line 579 | Line 636 | system call will share memory on a copy-on-write basis
636   .SH EXAMPLES
637   To compute radiance values for the rays listed in samples.inp:
638   .IP "" .2i
639 < rtrace -ov scene.oct < samples.inp > radiance.out
639 > rtrace \-ov scene.oct < samples.inp > radiance.out
640   .PP
641   To compute illuminance values at locations selected with the 't'
642   command of
643   .I ximage(1):
644   .IP "" .2i
645 < ximage scene.pic | rtrace -h -x 1 -i scene.oct | rcalc -e '$1=47.4*$1+120*$2+11.6*$3'
645 > ximage scene.hdr | rtrace \-h \-x 1 \-i scene.oct | rcalc \-e '$1=47.4*$1+120*$2+11.6*$3'
646   .PP
647   To record the object identifier corresponding to each pixel in an image:
648   .IP "" .2i
649 < vwrays -fd scene.pic | rtrace -fda `vwrays -d scene.pic` -os scene.oct
649 > vwrays \-fd scene.hdr | rtrace \-fda `vwrays \-d scene.hdr` \-os scene.oct
650   .PP
651   To compute an image with an unusual view mapping:
652   .IP "" .2i
653 < cnt 640 480 | rcalc -e 'xr:640;yr:480' -f unusual_view.cal | rtrace
654 < -x 640 -y 480 -fac scene.oct > unusual.pic
653 > cnt 480 640 | rcalc \-e 'xr:640;yr:480' \-f unusual_view.cal | rtrace
654 > \-x 640 \-y 480 \-fac scene.oct > unusual.hdr
655   .SH ENVIRONMENT
656   RAYPATH         the directories to check for auxiliary files.
657   .SH FILES
# Line 613 | Line 670 | option.
670   Greg Ward
671   .SH "SEE ALSO"
672   getinfo(1), lookamb(1), oconv(1), pfilt(1), pinterp(1),
673 < pvalue(1), rpict(1), rvu(1), vwrays(1), ximage(1)
673 > pvalue(1), rpict(1), rtcontrib(1), rvu(1), vwrays(1), ximage(1)

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines