| 61 |
|
If the |
| 62 |
|
.I \-n |
| 63 |
|
option is specified with a value greater than 1, multiple |
| 64 |
– |
.I rtrace |
| 64 |
|
processes will be used to accelerate computation on a shared |
| 65 |
|
memory machine. |
| 66 |
|
Note that there is no benefit to using more processes |
| 101 |
|
option tells |
| 102 |
|
.I rcontrib |
| 103 |
|
how many rays to accumulate for each record. |
| 104 |
< |
The default value is 1, meaning a full record will be produced for |
| 104 |
> |
The default value is one, meaning a full record will be produced for |
| 105 |
|
each input ray. |
| 106 |
< |
For values greater than 1, contributions will be averaged together |
| 106 |
> |
For values greater than one, contributions will be averaged together |
| 107 |
|
over the given number of input rays. |
| 108 |
|
If set to zero, only a single record will be produced at the very |
| 109 |
|
end, corresponding to the sum of all rays given on the input |
| 113 |
|
to sum RGB values together, but is much more efficient. |
| 114 |
|
Using this option, it is possible to reverse sampling, sending rays from |
| 115 |
|
a parallel source such as the sun to a diffuse surface, for example. |
| 116 |
< |
Note that output flushing via zero-direction rays is disabled |
| 117 |
< |
for accumulated evaluations. |
| 116 |
> |
Note that output flushing via zero-direction rays is disabled with |
| 117 |
> |
.I \-c |
| 118 |
> |
set to zero. |
| 119 |
|
.PP |
| 120 |
|
The output of |
| 121 |
|
.I rcontrib |
| 129 |
|
systems, such as luminaires, light pipes, and shading devices. |
| 130 |
|
.PP |
| 131 |
|
.I Rcontrib |
| 132 |
< |
calls |
| 133 |
< |
.I rtrace(1) |
| 134 |
< |
with the \-oTW (or \-oTV) option to calculate the daughter ray |
| 135 |
< |
contributions for each input ray, and the output tallies |
| 136 |
< |
are sent to one or more destinations according to the given |
| 132 |
> |
sends the accumulated rays tallies |
| 133 |
> |
to one or more destinations according to the given |
| 134 |
|
.I \-o |
| 135 |
|
specification. |
| 136 |
|
If a destination begins with an exclamation mark ('!'), then |
| 159 |
|
specification if present. |
| 160 |
|
The actual bin number is computed at run time based on ray direction |
| 161 |
|
and surface intersection, as described below. |
| 162 |
< |
If the number of bins is known in advance, it should be specified with the |
| 162 |
> |
The number of bins must be specified in advance with the |
| 163 |
|
.I \-bn |
| 164 |
|
option, and this is critical for output files containing multiple values |
| 165 |
|
per record. |
| 169 |
|
or |
| 170 |
|
.I \-e |
| 171 |
|
option. |
| 172 |
< |
Since bin numbers start from 0, the bin count is always equal to |
| 173 |
< |
the last bin plus 1. |
| 177 |
< |
Set the this value to 0 if the bin count is unknown (the default). |
| 172 |
> |
Since bin numbers start from zero, the bin count is always equal to |
| 173 |
> |
the last bin plus one. |
| 174 |
|
The most recent |
| 175 |
|
.I \-b, |
| 176 |
|
.I \-bn |
| 185 |
|
.I \-y |
| 186 |
|
if the |
| 187 |
|
.I \-c |
| 188 |
< |
is 0, when they control the resolution string |
| 188 |
> |
is zero, when they control the resolution string |
| 189 |
|
produced in the corresponding output. |
| 190 |
|
.PP |
| 191 |
|
If a |
| 192 |
|
.I \-b |
| 193 |
|
expression is defined for a particular modifier, |
| 194 |
|
the bin number will be evaluated at run time for each |
| 195 |
< |
ray contribution from |
| 200 |
< |
.I rtrace. |
| 195 |
> |
ray contribution. |
| 196 |
|
Specifically, each ray's world intersection point will be assigned to |
| 197 |
|
the variables Px, Py, and Pz, and the normalized ray direction |
| 198 |
|
will be assigned to Dx, Dy, and Dz. |
| 203 |
|
option. |
| 204 |
|
The computed bin value will be |
| 205 |
|
rounded to the nearest whole number. |
| 206 |
+ |
(Negative bin values will be silently ignored.)\0 |
| 207 |
+ |
For a single bin, you may specify |
| 208 |
+ |
.I "\-b 0", |
| 209 |
+ |
which is the default. |
| 210 |
|
This mechanism allows the user to define precise regions or directions |
| 211 |
|
they wish to accumulate, such as the Tregenza sky discretization, |
| 212 |
|
which would be otherwise impossible to specify |
| 215 |
|
described in the |
| 216 |
|
.I rcalc(1) |
| 217 |
|
man page. |
| 218 |
< |
Unlike |
| 218 |
> |
Like |
| 219 |
|
.I rcalc, |
| 220 |
|
.I rcontrib |
| 221 |
|
will search the RADIANCE library directories for each file given in a |
| 290 |
|
.PP |
| 291 |
|
To compute an array of illuminance contributions according to a Tregenza sky: |
| 292 |
|
.IP "" .2i |
| 293 |
< |
rcontrib \-I+ \-b tbin \-o sky.dat \-m skyglow \-b 0 \-o ground.dat \-m groundglow |
| 294 |
< |
@render.opt \-f tregenza.cal scene.oct < test.dat |
| 293 |
> |
rcontrib \-I+ \-f tregenza.cal \-b tbin \-bn Ntbins \-o sky.dat \-m skyglow |
| 294 |
> |
\-b 0 \-o ground.dat \-m groundglow @render.opt scene.oct < test.dat |
| 295 |
|
.SH ENVIRONMENT |
| 296 |
|
RAYPATH path to search for \-f and \-M files |
| 297 |
|
.SH AUTHOR |