| 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 |
|
[ |
| 8 |
|
.B "\-n nprocs" |
| 9 |
|
][ |
| 10 |
+ |
.B \-r |
| 11 |
+ |
][ |
| 12 |
|
.B "\-e expr" |
| 13 |
|
][ |
| 14 |
|
.B "\-f source" |
| 15 |
|
][ |
| 16 |
< |
.B "\-o fspec" |
| 16 |
> |
.B "\-o ospec" |
| 17 |
|
][ |
| 18 |
|
.B "\-b binv" |
| 19 |
|
] |
| 20 |
+ |
{ |
| 21 |
+ |
.B "\-m mod | \-M file" |
| 22 |
+ |
} |
| 23 |
+ |
.. |
| 24 |
|
[ |
| 25 |
|
.B $EVAR |
| 26 |
|
] |
| 30 |
|
[ |
| 31 |
|
rtrace options |
| 32 |
|
] |
| 27 |
– |
.B "\-m mod .." |
| 33 |
|
.B octree |
| 34 |
+ |
.br |
| 35 |
+ |
.B "rtcontrib [ options ] \-defaults" |
| 36 |
|
.SH DESCRIPTION |
| 37 |
|
.I Rtcontrib |
| 38 |
|
computes ray contributions (i.e., color coefficients) |
| 39 |
|
for objects whose modifiers are named in one or more |
| 40 |
|
.I \-m |
| 41 |
|
settings. |
| 42 |
< |
These modifiers are usually materials associated with specific |
| 43 |
< |
light sources, though they could correspond to intermediate objects as well. |
| 44 |
< |
The resulting contributions may then be used in linear combination to |
| 42 |
> |
These modifiers are usually materials associated with |
| 43 |
> |
light sources or sky domes, and must directly modify some geometric |
| 44 |
> |
primitives to be considered in the output. |
| 45 |
> |
A modifier list may also be read from a file using the |
| 46 |
> |
.I \-M |
| 47 |
> |
option. |
| 48 |
> |
.PP |
| 49 |
> |
The output of |
| 50 |
> |
.I rtcontrib |
| 51 |
> |
has many potential uses. |
| 52 |
> |
Source contributions can be used as components in linear combination to |
| 53 |
|
reproduce any desired variation, e.g., simulating lighting controls or |
| 54 |
|
changing sky conditions via daylight coefficients. |
| 55 |
|
More generally, |
| 56 |
|
.I rtcontrib |
| 57 |
< |
can compute general input-output relationships in optical |
| 58 |
< |
systems, such as light pipes and shading devices. |
| 57 |
> |
can be used to compute arbitrary input-output relationships in optical |
| 58 |
> |
systems, such as luminaires, light pipes, and shading devices. |
| 59 |
|
.PP |
| 60 |
< |
.I Rtrace(1) |
| 61 |
< |
is called to calculate the contributions for each input ray, |
| 62 |
< |
and the output tallies are sent to one or more files according to the |
| 60 |
> |
.I Rtcontrib |
| 61 |
> |
calls |
| 62 |
> |
.I rtrace(1) |
| 63 |
> |
with the -oTW option to calculate the daughter ray |
| 64 |
> |
contributions for each input ray, and the output tallies |
| 65 |
> |
are sent to one or more destinations according to the given |
| 66 |
|
.I \-o |
| 67 |
|
specification. |
| 68 |
< |
If the output file specification contains a "%s" format, this will be |
| 68 |
> |
If a destination begins with an exclamation mark ('!'), then |
| 69 |
> |
a pipe is opened to a command and data is sent to its standard input. |
| 70 |
> |
Otherwise, the destination is treated as a file. |
| 71 |
> |
An existing file of the same name is clobbered, unless the |
| 72 |
> |
.I \-r |
| 73 |
> |
option is specified, in which case data recovery is attempted. |
| 74 |
> |
If an output specification contains a "%s" format, this will be |
| 75 |
|
replaced by the modifier name. |
| 76 |
|
The |
| 77 |
|
.I \-b |
| 78 |
|
option may be used to further define |
| 79 |
< |
a "bin number" within each object if finer resolution is desired, and |
| 80 |
< |
will be applied to a "%d" format in the output file |
| 79 |
> |
a "bin number" within each object if finer resolution is needed, and |
| 80 |
> |
this will be applied to a "%d" format in the output file |
| 81 |
|
specification if present. |
| 82 |
< |
(The actual bin number is computed at run time based on ray direction |
| 83 |
< |
and surface intersection, as described below.)\0 |
| 82 |
> |
The actual bin number is computed at run time based on ray direction |
| 83 |
> |
and surface intersection, as described below. |
| 84 |
|
The most recent |
| 85 |
|
.I \-b |
| 86 |
|
and |
| 87 |
|
.I \-o |
| 88 |
< |
options (to the left) of each |
| 88 |
> |
options to the left of each |
| 89 |
|
.I \-m |
| 90 |
< |
setting affect only that modifier, and the ordering |
| 91 |
< |
of other options is unimportant. |
| 90 |
> |
setting affect only that modifier. |
| 91 |
> |
(The ordering of other options is unimportant.)\0 |
| 92 |
|
.PP |
| 93 |
< |
Input and output format defaults to plain text, where each ray's |
| 94 |
< |
origin and direction (6 real values) must appear together per |
| 95 |
< |
line of input, and one line of output is produced per output file |
| 96 |
< |
file per ray. |
| 97 |
< |
Alternative input and output formats may be specified using the |
| 98 |
< |
.I \-f[io] |
| 99 |
< |
option, which is explained in the |
| 100 |
< |
.I rtrace |
| 101 |
< |
man page along with the associated |
| 102 |
< |
.I \-x |
| 103 |
< |
and |
| 104 |
< |
.I \-y |
| 105 |
< |
resolution settings. |
| 106 |
< |
In particular, the 'c' output setting |
| 107 |
< |
together with positive dimensions for |
| 108 |
< |
.I \-x |
| 109 |
< |
and |
| 110 |
< |
.I \-y |
| 111 |
< |
will produce an uncompressed RADIANCE picture, |
| 112 |
< |
suitable for manipulation with |
| 113 |
< |
.I pcomb(1) |
| 114 |
< |
and related tools. |
| 93 |
> |
If a |
| 94 |
> |
.I \-b |
| 95 |
> |
expression is defined for a particular modifier, |
| 96 |
> |
the bin number will be evaluated at run time for each |
| 97 |
> |
ray contribution from |
| 98 |
> |
.I rtrace. |
| 99 |
> |
Specifically, each ray's world intersection point will be assigned to |
| 100 |
> |
the variables Px, Py, and Pz, and the normalized ray direction |
| 101 |
> |
will be assigned to Dx, Dy, and Dz. |
| 102 |
> |
These parameters may be combined with definitions given in |
| 103 |
> |
.I \-e |
| 104 |
> |
arguments and files read using the |
| 105 |
> |
.I \-f |
| 106 |
> |
option. |
| 107 |
> |
The computed bin value will be |
| 108 |
> |
rounded to the nearest whole number. |
| 109 |
> |
This mechanism allows the user to define precise regions or directions |
| 110 |
> |
they wish to accumulate, such as the Tregenza sky discretization, |
| 111 |
> |
which would be otherwise impossible to specify |
| 112 |
> |
as a set of RADIANCE primitives. |
| 113 |
> |
The rules and predefined functions available for these expressions are |
| 114 |
> |
described in the |
| 115 |
> |
.I rcalc(1) |
| 116 |
> |
man page. |
| 117 |
> |
Unlike |
| 118 |
> |
.I rcalc, |
| 119 |
> |
.I rtcontrib |
| 120 |
> |
will search the RADIANCE library directories for each file given in a |
| 121 |
> |
.I \-f |
| 122 |
> |
option. |
| 123 |
> |
(No search takes place if a file name begins with a '.', '/' or '~' |
| 124 |
> |
character.)\0 |
| 125 |
|
.PP |
| 126 |
|
If no |
| 127 |
|
.I \-o |
| 128 |
|
specification is given, results are written on the standard output in order |
| 129 |
|
of modifier (as given on the command line) then bin number. |
| 130 |
< |
The same format is used for a simple file name specification |
| 131 |
< |
without any embedded "%s" or "%d" formats. |
| 130 |
> |
Concatenated data is also sent to a single destination (i.e., an initial |
| 131 |
> |
.I \-o |
| 132 |
> |
specification without formatting strings). |
| 133 |
|
If a "%s" format appears but no "%d" in the |
| 134 |
|
.I \-o |
| 135 |
|
specification, then each modifier will have its own output file, with |
| 143 |
|
For binary output formats, there is no such delimiter to mark |
| 144 |
|
the end of each record. |
| 145 |
|
.PP |
| 146 |
< |
If a |
| 147 |
< |
.I \-b |
| 148 |
< |
expression is defined for a particular modifier, |
| 149 |
< |
the bin number will be evaluated at run time for each |
| 150 |
< |
ray contribution from |
| 151 |
< |
.I rtrace. |
| 152 |
< |
Specifically, each ray's world intersection point will be assigned to |
| 153 |
< |
the variables Px, Py, and Pz, and the normalized ray direction |
| 154 |
< |
will be assigned to Dx, Dy, and Dz. |
| 155 |
< |
These ray parameters may be combined with any definitions given in |
| 156 |
< |
.I \-e |
| 157 |
< |
options, or any files read in from |
| 158 |
< |
.I \-f |
| 159 |
< |
options, to compute the bin, which will be |
| 160 |
< |
rounded to the closest whole number. |
| 161 |
< |
This mechanism allows the user to define precise regions (or directions) |
| 162 |
< |
they wish to accumulate, such as the Tregenza sky grid, which would be |
| 163 |
< |
otherwise impossible to specify as a set of RADIANCE primitives. |
| 146 |
> |
Input and output format defaults to plain text, where each ray's |
| 147 |
> |
origin and direction (6 real values) are given on input, |
| 148 |
> |
and one line is produced per output file per ray. |
| 149 |
> |
Alternative data representations may be specified by the |
| 150 |
> |
.I \-f[io] |
| 151 |
> |
option, which is described in the |
| 152 |
> |
.I rtrace |
| 153 |
> |
man page along with the associated |
| 154 |
> |
.I \-x |
| 155 |
> |
and |
| 156 |
> |
.I \-y |
| 157 |
> |
resolution settings. |
| 158 |
> |
In particular, the color ('c') output data representation |
| 159 |
> |
together with positive dimensions for |
| 160 |
> |
.I \-x |
| 161 |
> |
and |
| 162 |
> |
.I \-y |
| 163 |
> |
will produce an uncompressed RADIANCE picture, |
| 164 |
> |
suitable for manipulation with |
| 165 |
> |
.I pcomb(1) |
| 166 |
> |
and related tools. |
| 167 |
|
.PP |
| 168 |
|
If the |
| 169 |
|
.I \-n |
| 170 |
|
option is specified with a value greater than 1, multiple |
| 171 |
< |
.I rtrace(1) |
| 171 |
> |
.I rtrace |
| 172 |
|
processes will be used to accelerate computation on a shared |
| 173 |
|
memory machine. |
| 174 |
|
Note that there is no benefit to using more processes |
| 175 |
< |
than there are local CPUs available to do the work. |
| 175 |
> |
than there are local CPUs available to do the work, and the |
| 176 |
> |
.I rtcontrib |
| 177 |
> |
process itself may use a considerable amount of CPU time. |
| 178 |
|
.PP |
| 179 |
|
Options may be given on the command line and/or read from the |
| 180 |
|
environment and/or read from a file. |
| 182 |
|
replaced by the contents of the given environment variable. |
| 183 |
|
A command argument beginning with an at sign ('@') is immediately |
| 184 |
|
replaced by the contents of the given file. |
| 185 |
< |
.SH EXAMPLE |
| 186 |
< |
First |
| 187 |
< |
.I rpiece |
| 148 |
< |
process is started on the machine "goober": |
| 185 |
> |
.SH EXAMPLES |
| 186 |
> |
To compute the proportional contributions from sources modified |
| 187 |
> |
by "light1" vs. "light2" on a set of illuminance values: |
| 188 |
|
.IP "" .2i |
| 189 |
< |
goober% echo 1 8 > syncfile |
| 151 |
< |
.br |
| 152 |
< |
goober% echo -F syncfile -x 1024 -y 1024 -vf view -o picture octree > args |
| 153 |
< |
.br |
| 154 |
< |
goober% rpiece @args & |
| 189 |
> |
rtcontrib -I+ @render.opt -o c_%s.dat -m light1 -m light2 scene.oct < test.dat |
| 190 |
|
.PP |
| 191 |
< |
Second |
| 192 |
< |
.I rpiece |
| 158 |
< |
processes is started on the machine "sucker": |
| 191 |
> |
To generate a pair of images corresponding to these two lights' |
| 192 |
> |
contributions: |
| 193 |
|
.IP "" .2i |
| 194 |
< |
sucker% rpiece @args & |
| 195 |
< |
.SH NOTES |
| 196 |
< |
Due to NFS file buffering, the network lock manager is employed to |
| 163 |
< |
guarantee consistency in the output file even though non-overlapping |
| 164 |
< |
writes are used. |
| 165 |
< |
This would tend to slow the process down if |
| 166 |
< |
.I rpiece |
| 167 |
< |
were to wait for this I/O to complete before starting on the next |
| 168 |
< |
piece, so |
| 169 |
< |
.I rpiece |
| 170 |
< |
forks separate processes to hang around waiting for I/O completion. |
| 171 |
< |
The number of processes thus designated is set by the MAXFORK macro |
| 172 |
< |
in the program (compiled in the src/util directory). |
| 173 |
< |
If the fork call is slow on a system, it may actually be better to |
| 174 |
< |
set MAXFORK to zero. |
| 175 |
< |
In other cases, the network lock manager may be so slow that this |
| 176 |
< |
value should be increased to get the best utilization. |
| 194 |
> |
vwrays -ff -x 1024 -y 1024 -vf best.vf | |
| 195 |
> |
rtcontrib -ffc `vwrays -d -x 1024 -y 1024 -vf best.vf` |
| 196 |
> |
@render.opt -o c_%s.pic -m light1 -m light2 scene.oct |
| 197 |
|
.PP |
| 198 |
< |
The output picture is not run-length encoded, and can be quite |
| 199 |
< |
large. |
| 180 |
< |
The approximate size (in kilobytes) can be computed by the simple |
| 181 |
< |
formula: |
| 198 |
> |
These images may then be recombined using the desired outputs |
| 199 |
> |
of light1 and light2: |
| 200 |
|
.IP "" .2i |
| 201 |
< |
filesize = xres*yres/256 |
| 201 |
> |
pcomb -c 100 90 75 c_light1.pic -c 50 55 57 c_light2.pic > combined.pic |
| 202 |
|
.PP |
| 203 |
< |
Make sure that there is enough space on the filesystem to hold the |
| 204 |
< |
entire picture before beginning. |
| 205 |
< |
Once the picture is finished, the |
| 206 |
< |
.I ra_rgbe(1) |
| 207 |
< |
program with the -r option may be used to convert to a run-length |
| 208 |
< |
encoded picture for more efficient storage, although |
| 191 |
< |
.I pfilt(1) |
| 192 |
< |
or any of the other Radiance picture filters will do the same |
| 193 |
< |
thing. |
| 194 |
< |
.PP |
| 195 |
< |
The ALRM signal may be used to gracefully terminate an |
| 196 |
< |
.I rpiece |
| 197 |
< |
process after it finishes the current piece. |
| 198 |
< |
This permits other currently running or subsequently started |
| 199 |
< |
.I rpiece |
| 200 |
< |
process(es) to continue rendering the picture without loss. |
| 201 |
< |
The |
| 202 |
< |
.I \-T |
| 203 |
< |
option will send the ALRM signal to |
| 204 |
< |
.I rpiece |
| 205 |
< |
after the specified number of (decimal) hours. |
| 206 |
< |
This is the best way to force a time limit on the computation, |
| 207 |
< |
since information will not be lost, though the process may continue |
| 208 |
< |
for some time afterwards to finish its current piece. |
| 209 |
< |
.SH BUGS |
| 210 |
< |
This program may not work on some systems whose NFS lock manager is |
| 211 |
< |
unreliable. |
| 212 |
< |
In particular, some System V derivative UNIX systems often have |
| 213 |
< |
problems with the network lock manager. |
| 214 |
< |
If the output is scrambled or rpict aborts with some ambient file |
| 215 |
< |
related problem, you should just remove the ambient file and go |
| 216 |
< |
back to normal rendering. |
| 203 |
> |
To compute an array of illuminance contributions according to a Tregenza sky: |
| 204 |
> |
.IP "" .2i |
| 205 |
> |
rtcontrib -b tbin -o sky.dat -m skyglow -b 0 -o ground.dat -m groundglow |
| 206 |
> |
@render.opt -f tregenza.cal scene.oct < test.dat |
| 207 |
> |
.SH ENVIRONMENT |
| 208 |
> |
RAYPATH path to search for -f files |
| 209 |
|
.SH AUTHOR |
| 210 |
|
Greg Ward |
| 211 |
|
.SH "SEE ALSO" |
