1 |
greg |
1.2 |
.\" RCSid "$Id$" |
2 |
greg |
1.1 |
.TH MGF2RAD 1 4/12/95 RADIANCE |
3 |
|
|
.SH NAME |
4 |
|
|
mgf2rad - convert Materials and Geometry Format file to RADIANCE description |
5 |
|
|
.SH SYNOPSIS |
6 |
|
|
.B mgf2rad |
7 |
|
|
[ |
8 |
|
|
.B "\-m matfile" |
9 |
|
|
][ |
10 |
|
|
.B "\-e mult" |
11 |
|
|
][ |
12 |
|
|
.B "\-g dist" |
13 |
|
|
] |
14 |
|
|
[ |
15 |
|
|
.B input .. |
16 |
|
|
] |
17 |
|
|
.SH DESCRIPTION |
18 |
|
|
.I Mgf2rad |
19 |
|
|
converts one or more Materials and Geometry Format (MGF) |
20 |
|
|
files to a RADIANCE scene description. |
21 |
|
|
By definition, all output dimensions are in meters. |
22 |
|
|
The material names and properties |
23 |
|
|
for the surfaces will be those assigned in MGF. |
24 |
|
|
Any materials not defined in MGF will result in an error during |
25 |
|
|
translation. |
26 |
|
|
Light sources are described inline as IES luminaire files, and |
27 |
|
|
.I mgf2rad |
28 |
|
|
calls the program |
29 |
|
|
.I ies2rad(1) |
30 |
|
|
to translate these files. |
31 |
|
|
If an IES file in turn contains an MGF description of the local |
32 |
|
|
fixture geometry, this may result in a recursive call to |
33 |
|
|
.I mgf2rad, |
34 |
|
|
which is normal and should be transparent. |
35 |
|
|
The only side-effect of this additional translation is the |
36 |
|
|
appearance of other RADIANCE scene and data files produced |
37 |
|
|
automatically by |
38 |
|
|
.I ies2rad. |
39 |
|
|
.PP |
40 |
|
|
The |
41 |
|
|
.I \-m |
42 |
|
|
option may be used to put all the translated materials into a separate |
43 |
|
|
RADIANCE file. |
44 |
|
|
This is not always advisable, as any given material name may be |
45 |
|
|
reused at different points in the MGF description, and writing them |
46 |
|
|
to a separate file loses the contextual association between |
47 |
|
|
materials and surfaces. |
48 |
|
|
As long as unique material names are used throughout the MGF |
49 |
|
|
description and material properties are not redefined, there |
50 |
|
|
will be no problem. |
51 |
|
|
Note that this is the only way to get all the translated materials |
52 |
|
|
into a single file, since no output is produced for unreferenced |
53 |
|
|
materials; i.e. translating just the MGF materials does not work. |
54 |
|
|
.PP |
55 |
|
|
The |
56 |
|
|
.I \-e |
57 |
|
|
option may be used to multiply all the emission values by the |
58 |
|
|
given |
59 |
|
|
.I mult |
60 |
|
|
factor. |
61 |
|
|
The |
62 |
|
|
.I \-g |
63 |
|
|
option may be used to establish a glow distance (in meters) |
64 |
|
|
for all emitting surfaces. |
65 |
|
|
These two options are employed principally by |
66 |
|
|
.I ies2rad, |
67 |
|
|
and are not generally useful to most users. |
68 |
|
|
.SH EXAMPLE |
69 |
|
|
To translate two MGF files into one RADIANCE materials file and |
70 |
|
|
one geometry file: |
71 |
|
|
.IP "" .2i |
72 |
|
|
mgf2rad -m materials.rad building1.mgf building2.mgf > building1+2.rad |
73 |
|
|
.PP |
74 |
|
|
To create an octree directly from two MGF files and one RADIANCE |
75 |
|
|
file: |
76 |
|
|
.IP "" .2i |
77 |
|
|
oconv '\\!mgf2rad materials.mgf scene.mgf' source.rad > scene.oct |
78 |
|
|
.SH FILES |
79 |
|
|
tmesh.cal Used to smooth polygonal geometry |
80 |
|
|
.br |
81 |
|
|
*.rad RADIANCE source descriptions created by ies2rad |
82 |
|
|
.br |
83 |
|
|
*.dat RADIANCE source data created by ies2rad |
84 |
|
|
.br |
85 |
|
|
source.cal Used for IES source coordinates |
86 |
|
|
.SH AUTHOR |
87 |
|
|
Greg Ward |
88 |
|
|
.SH "SEE ALSO" |
89 |
|
|
ies2rad(1), mgf2meta(1), obj2rad(1), oconv(1), rad2mgf(1), xform(1) |
90 |
|
|
.PP |
91 |
|
|
MGF web site "http://radsite.lbl.gov/mgf/HOME.html" |