| 1 |
.\" RCSid "$Id: rad2mgf.1,v 1.3 2007/09/04 17:36:41 greg Exp $" |
| 2 |
.TH RAD2MGF 1 5/15/95 RADIANCE |
| 3 |
.SH NAME |
| 4 |
rad2mgf - convert RADIANCE scene description to Materials and Geometry Format |
| 5 |
.SH SYNOPSIS |
| 6 |
.B rad2mgf |
| 7 |
[ |
| 8 |
.B \-dU |
| 9 |
] |
| 10 |
[ |
| 11 |
.B input .. |
| 12 |
] |
| 13 |
.SH DESCRIPTION |
| 14 |
.I Rad2mgf |
| 15 |
converts one or more RADIANCE scene files |
| 16 |
to the Materials and Geometry Format (MGF). |
| 17 |
Input units are specified with the |
| 18 |
.I \-mU |
| 19 |
option, where |
| 20 |
.I U |
| 21 |
is one of 'm' (meters), 'c' (centimeters), 'f' (feet) or 'i' |
| 22 |
(inches). |
| 23 |
The assumed unit is meters, which is the required output unit for |
| 24 |
MGF (thus the need to know). |
| 25 |
If the input dimensions are in none of these units, then the user |
| 26 |
should apply |
| 27 |
.I xform(1) |
| 28 |
with the |
| 29 |
.I \-s |
| 30 |
option to bring the units into line prior to translation. |
| 31 |
.PP |
| 32 |
The MGF material names and properties |
| 33 |
for the surfaces will be those assigned in RADIANCE. |
| 34 |
If a referenced material has not been defined, then its name will |
| 35 |
be invoked in the MGF output without definition, and the description |
| 36 |
will be incomplete. |
| 37 |
.SH LIMITATIONS |
| 38 |
Although MGF supports all of the geometric types and the most |
| 39 |
common material types used in RADIANCE, there is currently no |
| 40 |
support for advanced BRDF materials, patterns, textures or mixtures. |
| 41 |
Also, the special types "source" and "antimatter" are not supported, |
| 42 |
and all light source materials are converted to simple diffuse emitters |
| 43 |
(except "illum" materials, which are converted to their alternates). |
| 44 |
These primitives are reproduced as comments in the output and |
| 45 |
must be replaced manually if necessary. |
| 46 |
.PP |
| 47 |
The RADIANCE "instance" and "mesh" types aretreated specially. |
| 48 |
.I Rad2mgf |
| 49 |
converts each instance or mesh to an MGF include statement, |
| 50 |
using the corresponding |
| 51 |
transformation and a file name derived from the octree or mesh name. |
| 52 |
(The original octree/mesh suffix is replaced by ".mgf".)\0 |
| 53 |
For this to work, the user must separately create the referenced |
| 54 |
MGF files from the original RADIANCE descriptions. |
| 55 |
The description file names can usually be determined using the |
| 56 |
.I getinfo(1) |
| 57 |
command run on the octrees in question. |
| 58 |
.SH EXAMPLE |
| 59 |
To convert three RADIANCE files (in feet) to one MGF file: |
| 60 |
.IP "" .2i |
| 61 |
rad2mgf \-df file1.rad file2.rad file3.rad > scene.mgf |
| 62 |
.PP |
| 63 |
To translate a RADIANCE materials file to MGF: |
| 64 |
.IP "" .2i |
| 65 |
rad2mgf materials.rad > materials.mgf |
| 66 |
.SH AUTHOR |
| 67 |
Greg Ward |
| 68 |
.SH "SEE ALSO" |
| 69 |
getinfo(1), ies2rad(1), mgf2meta(1), mgf2rad(1), obj2rad(1), oconv(1), xform(1) |
| 70 |
.PP |
| 71 |
MGF web site "http://radsite.lbl.gov/mgf/HOME.html" |
