1 |
|
.\" RCSid "$Id$" |
2 |
< |
.TH RPIECE 1 5/25/05 RADIANCE |
2 |
> |
.TH RTCONTRIB 1 5/25/05 RADIANCE |
3 |
|
.SH NAME |
4 |
< |
rtcontrib - compute contributions in a RADIANCE scene |
4 |
> |
rtcontrib - compute contribution coefficients in a RADIANCE scene |
5 |
|
.SH SYNOPSIS |
6 |
|
.B rtcontrib |
7 |
|
[ |
26 |
|
rtrace options |
27 |
|
] |
28 |
|
.B octree |
29 |
+ |
.br |
30 |
+ |
.B "rtcontrib [ options ] \-defaults" |
31 |
|
.SH DESCRIPTION |
32 |
|
.I Rtcontrib |
33 |
|
computes ray contributions (i.e., color coefficients) |
37 |
|
These modifiers are usually materials associated with |
38 |
|
light sources or sky domes, and must directly modify some geometric |
39 |
|
primitives to be considered in the output. |
40 |
< |
The computed contributions can then be used in linear combination to |
40 |
> |
The output of |
41 |
> |
.I rtcontrib |
42 |
> |
has many potential uses. |
43 |
> |
Source contributions can be used as components in linear combination to |
44 |
|
reproduce any desired variation, e.g., simulating lighting controls or |
45 |
|
changing sky conditions via daylight coefficients. |
46 |
|
More generally, |
47 |
|
.I rtcontrib |
48 |
< |
may be used to compute input-output relationships in optical |
49 |
< |
systems, such as light pipes and shading devices. |
48 |
> |
can be used to compute arbitrary input-output relationships in optical |
49 |
> |
systems, such as luminaires, light pipes, and shading devices. |
50 |
|
.PP |
51 |
|
.I Rtcontrib |
52 |
|
calls |
53 |
|
.I rtrace(1) |
54 |
< |
to calculate the contributions for each input ray, |
55 |
< |
and the output tallies are sent to one or more files according to the |
54 |
> |
with the -oTW option to calculate the daughter ray |
55 |
> |
contributions for each input ray, and the output tallies |
56 |
> |
are sent to one or more files according to the given |
57 |
|
.I \-o |
58 |
|
specification. |
59 |
|
If an output specification contains a "%s" format, this will be |
64 |
|
a "bin number" within each object if finer resolution is needed, and |
65 |
|
this will be applied to a "%d" format in the output file |
66 |
|
specification if present. |
67 |
< |
(The actual bin number is computed at run time based on ray direction |
68 |
< |
and surface intersection, as described below.)\0 |
67 |
> |
The actual bin number is computed at run time based on ray direction |
68 |
> |
and surface intersection, as described below. |
69 |
|
The most recent |
70 |
|
.I \-b |
71 |
|
and |
86 |
|
will be assigned to Dx, Dy, and Dz. |
87 |
|
These parameters may be combined with definitions given in |
88 |
|
.I \-e |
89 |
< |
options and files read in |
89 |
> |
arguments and files read using the |
90 |
|
.I \-f |
91 |
< |
options, to compute the bin, which will be |
91 |
> |
option. |
92 |
> |
The computed bin value will be |
93 |
|
rounded to the nearest whole number. |
94 |
|
This mechanism allows the user to define precise regions or directions |
95 |
|
they wish to accumulate, such as the Tregenza sky discretization, |
96 |
|
which would be otherwise impossible to specify |
97 |
|
as a set of RADIANCE primitives. |
98 |
+ |
The rules and predefined functions available for these expressions are |
99 |
+ |
described in the |
100 |
+ |
.I rcalc(1) |
101 |
+ |
man page. |
102 |
+ |
Unlike |
103 |
+ |
.I rcalc, |
104 |
+ |
.I rtcontrib |
105 |
+ |
will search the RADIANCE library directories for each file given in a |
106 |
+ |
.I \-f |
107 |
+ |
option. |
108 |
+ |
(No search takes place if a file name begins with a '.', '/' or '~' |
109 |
+ |
character.)\0 |
110 |
|
.PP |
111 |
|
If no |
112 |
|
.I \-o |
189 |
|
.IP "" .2i |
190 |
|
rtcontrib -b tbin -o sky.dat -m skyglow -b 0 -o ground.dat -m groundglow |
191 |
|
@render.opt -f tregenza.cal scene.oct < test.dat |
192 |
+ |
.SH ENVIRONMENT |
193 |
+ |
RAYPATH path to search for -f files |
194 |
|
.SH AUTHOR |
195 |
|
Greg Ward |
196 |
|
.SH "SEE ALSO" |