38 |
|
.fi |
39 |
|
.sp |
40 |
|
The number of components indicates that each matrix element is actually |
41 |
< |
composed of multiple elements, most commonly an RGB triple. |
41 |
> |
composed of multiple channels, most commonly an RGB triple. |
42 |
|
This is essentially dividing the matrix into planes, where each component |
43 |
|
participates in a separate calculation. |
44 |
|
If an appropriate header is not present, it may be added with a call to |
127 |
|
Note that conversion from a float or RGBE color space applies a conversion |
128 |
|
of 179 lumens/watt (for CIE or melanopic output) or 412 (for scotopic output), |
129 |
|
and the reverse happens for conversion from XYZE input to RGB or RGBE output. |
130 |
+ |
Lower case versions of all these components are also supported, the only |
131 |
+ |
difference is that the aforementioned efficacy factors |
132 |
+ |
will be left out of the conversion. |
133 |
|
.PP |
134 |
|
If a matrix or picture file path is given to the |
135 |
|
.I \-c |
224 |
|
option turns on verbose reporting, which announces each operation. |
225 |
|
.SH EXAMPLES |
226 |
|
To concatenate two matrix files with a BTDF between them and write |
227 |
< |
the result as binary double: |
227 |
> |
the result as binary float: |
228 |
|
.IP "" .2i |
229 |
< |
rmtxop -fd view.vmx blinds.xml exterior.dmx > dcoef.dmx |
229 |
> |
rmtxop -ff view.vmx blinds.xml exterior.dmx > dcoef.dmx |
230 |
|
.PP |
231 |
|
To convert a BTDF matrix into a Radiance picture: |
232 |
|
.IP "" .2i |
273 |
|
Note that this only applies to concatenation; |
274 |
|
element-wise addition, multiplication, and division are always |
275 |
|
evaluated from left to right. |
276 |
+ |
.PP |
277 |
+ |
All calculations are peformed internally using 32-bit floating-point, |
278 |
+ |
so there is little benefit in either reading or writing 64-bit double |
279 |
+ |
data. |
280 |
+ |
This may be overridden at compile time using the macro |
281 |
+ |
"-DDTrmx_native=DTdouble". |
282 |
+ |
.SH BUGS |
283 |
+ |
The |
284 |
+ |
.I rmtxop |
285 |
+ |
command currently ignores the "PRIMARIES" setting in input |
286 |
+ |
headers, and does not produce any on output, even in |
287 |
+ |
circumstances where it would make sense to. |
288 |
|
.SH AUTHOR |
289 |
|
Greg Ward |
290 |
|
.SH "SEE ALSO" |
291 |
|
cnt(1), dctimestep(1), getinfo(1), pcomb(1), pfilt(1), |
292 |
< |
ra_xyze(1), rcalc(1), |
293 |
< |
rcollate(1), rcontrib(1), rcrop(1), rfluxmtx(1), |
294 |
< |
rmtxcomb(1), rtpict(1), rtrace(1), vwrays(1), wrapBSDF(1) |
292 |
> |
pvsum(1), ra_xyze(1), rcalc(1), |
293 |
> |
rcollate(1), rcomb(1), rcontrib(1), rcrop(1), rfluxmtx(1), |
294 |
> |
rtpict(1), rtrace(1), vwrays(1), wrapBSDF(1) |