1 |
.\" RCSid $Id$ |
2 |
.TH PKGBSDF 1 6/23/2011 RADIANCE |
3 |
.SH NAME |
4 |
pkgBSDF - package BSDFs provided as XML for Radiance |
5 |
.SH SYNOPSIS |
6 |
.B pkgBSDF |
7 |
[ |
8 |
.B \-i |
9 |
][ |
10 |
.B \-s |
11 |
] |
12 |
.B "bsdf.xml .." |
13 |
.SH DESCRIPTION |
14 |
.I PkgBSDF |
15 |
takes one or more XML files, each describing the bidirectional scattering |
16 |
distribution function of a surface or geometric system, and packages |
17 |
them into RADIANCE scene descriptions. |
18 |
One rectangle is produced for each BSDF that has |
19 |
no detail geometry and/or no rear-side reflectance distribution. |
20 |
If both front and back reflectance distributions are present with |
21 |
detail geometry, then two rectangles will be used to sandwich |
22 |
the geometry extracted from the BSDF file. |
23 |
.PP |
24 |
The |
25 |
.I \-i |
26 |
option causes |
27 |
.I pkgBSDF |
28 |
to produce frozen octree instances for any detail geometry, |
29 |
which may reduce memory requirements in scenes with many |
30 |
references to the same complex BSDF object. |
31 |
.PP |
32 |
Normally, |
33 |
.I pkgBSDF |
34 |
produces one RADIANCE scene file for each XML input, replacing |
35 |
the required '.xml' suffix with '.rad' in the same directory. |
36 |
The |
37 |
.I \-s |
38 |
option sends the RADIANCE scene description to the standard |
39 |
output rather than writing it to a file, but only works |
40 |
for a single XML input. |
41 |
Any instance octree is still written out to a file generated |
42 |
by replacing the '.xml' suffix with '.oct' in the same directory. |
43 |
.SH EXAMPLE |
44 |
Package all the XML files in the current directory as Radiance |
45 |
scene files, employing frozen octree instances for any |
46 |
detail geometry: |
47 |
.IP "" .2i |
48 |
pkgBSDF -i *.xml |
49 |
.SH AUTHOR |
50 |
Greg Ward |
51 |
.SH "SEE ALSO" |
52 |
genBSDF(1), oconv(1), xform(1) |