man/man1/mgf2rad.1

.\" RCSid "$Id: mgf2rad.1,v 1.3 2007/09/04 17:36:40 greg Exp $"
.TH MGF2RAD 1 4/12/95 RADIANCE
.SH NAME
mgf2rad - convert Materials and Geometry Format file to RADIANCE description
.SH SYNOPSIS
.B mgf2rad
[
.B \-s
][
.B "\-m matfile"
][
.B "\-e mult"
][
.B "\-g dist"
]
[
.B input ..
]
.SH DESCRIPTION
.I Mgf2rad
converts one or more Materials and Geometry Format (MGF)
files to a RADIANCE scene description.
By definition, all output dimensions are in meters.
The material names and properties
for the surfaces will be those assigned in MGF.
Any materials not defined in MGF will result in an error during
translation.
Light sources are described inline as IES luminaire files, and
.I mgf2rad
calls the program
.I ies2rad(1)
to translate these files.
If an IES file in turn contains an MGF description of the local
fixture geometry, this may result in a recursive call to
.I mgf2rad,
which is normal and should be transparent.
The only side-effect of this additional translation is the
appearance of other RADIANCE scene and data files produced
automatically by
.I ies2rad.
.PP
The
.I \-m
option may be used to put all the translated materials into a separate
RADIANCE file.
This is not always advisable, as any given material name may be
reused at different points in the MGF description, and writing them
to a separate file loses the contextual association between
materials and surfaces.
As long as unique material names are used throughout the MGF
description and material properties are not redefined, there
will be no problem.
Note that this is the only way to get all the translated materials
into a single file, since no output is produced for unreferenced
materials; i.e. translating just the MGF materials does not work.
.PP
The
.I \-s
option turns on spectral data conversion, producing "spectrum"
modifiers in the output as supported by RADIANCE 6.0 and later.
If you do not plan to employ spectral rendering, then it is
better to have
.I mgf2rad
convert to RGB colors, which is the default.
.PP
The
.I \-e
option may be used to multiply all the emission values by the
given
.I mult
factor.
The
.I \-g
option may be used to establish a glow distance (in meters)
for all emitting surfaces.
These two options are employed principally by
.I ies2rad,
and are not generally useful to most users.
.SH EXAMPLE
To translate two MGF files into one RADIANCE materials file and
one geometry file:
.IP "" .2i
mgf2rad -m materials.rad building1.mgf building2.mgf > building1+2.rad
.PP
To create an octree directly from two MGF files and one RADIANCE
file, including spectra:
.IP "" .2i
oconv '!mgf2rad -s materials.mgf scene.mgf' source.rad > scene.oct
.SH FILES
tmesh.cal       Used to smooth polygonal geometry
.br
*.rad           RADIANCE source descriptions created by ies2rad
.br
*.dat           RADIANCE source data created by ies2rad
.br
source.cal      Used for IES source coordinates
.SH AUTHOR
Greg Ward
.SH "SEE ALSO"
ies2rad(1), mgf2meta(1), obj2rad(1), oconv(1), rad2mgf(1), xform(1)
.PP
MGF web site "http://radsite.lbl.gov/mgf/HOME.html"
Revision:	1.4
Committed:	Wed Jan 17 00:43:45 2024 UTC (16 months ago) by greg
Branch:	MAIN
CVS Tags:	HEAD
Changes since 1.3:	+15 -4 lines
Log Message:	feat(mgf2rad): Made spectra conversion optional with -s command-line flag
#	User	Rev	Content
1	greg	1.4	.\" RCSid "$Id: mgf2rad.1,v 1.3 2007/09/04 17:36:40 greg Exp $"
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	greg	1.4	.B \-s
9			][
10	greg	1.1	.B "\-m matfile"
11			][
12			.B "\-e mult"
13			][
14			.B "\-g dist"
15			]
16			[
17			.B input ..
18			]
19			.SH DESCRIPTION
20			.I Mgf2rad
21			converts one or more Materials and Geometry Format (MGF)
22			files to a RADIANCE scene description.
23			By definition, all output dimensions are in meters.
24			The material names and properties
25			for the surfaces will be those assigned in MGF.
26			Any materials not defined in MGF will result in an error during
27			translation.
28			Light sources are described inline as IES luminaire files, and
29			.I mgf2rad
30			calls the program
31			.I ies2rad(1)
32			to translate these files.
33			If an IES file in turn contains an MGF description of the local
34			fixture geometry, this may result in a recursive call to
35			.I mgf2rad,
36			which is normal and should be transparent.
37			The only side-effect of this additional translation is the
38			appearance of other RADIANCE scene and data files produced
39			automatically by
40			.I ies2rad.
41			.PP
42			The
43			.I \-m
44			option may be used to put all the translated materials into a separate
45			RADIANCE file.
46			This is not always advisable, as any given material name may be
47			reused at different points in the MGF description, and writing them
48			to a separate file loses the contextual association between
49			materials and surfaces.
50			As long as unique material names are used throughout the MGF
51			description and material properties are not redefined, there
52			will be no problem.
53			Note that this is the only way to get all the translated materials
54			into a single file, since no output is produced for unreferenced
55			materials; i.e. translating just the MGF materials does not work.
56			.PP
57			The
58	greg	1.4	.I \-s
59			option turns on spectral data conversion, producing "spectrum"
60			modifiers in the output as supported by RADIANCE 6.0 and later.
61			If you do not plan to employ spectral rendering, then it is
62			better to have
63			.I mgf2rad
64			convert to RGB colors, which is the default.
65			.PP
66			The
67	greg	1.1	.I \-e
68			option may be used to multiply all the emission values by the
69			given
70			.I mult
71			factor.
72			The
73			.I \-g
74			option may be used to establish a glow distance (in meters)
75			for all emitting surfaces.
76			These two options are employed principally by
77			.I ies2rad,
78			and are not generally useful to most users.
79			.SH EXAMPLE
80			To translate two MGF files into one RADIANCE materials file and
81			one geometry file:
82			.IP "" .2i
83	greg	1.4	mgf2rad -m materials.rad building1.mgf building2.mgf > building1+2.rad
84	greg	1.1	.PP
85			To create an octree directly from two MGF files and one RADIANCE
86	greg	1.4	file, including spectra:
87	greg	1.1	.IP "" .2i
88	greg	1.4	oconv '!mgf2rad -s materials.mgf scene.mgf' source.rad > scene.oct
89	greg	1.1	.SH FILES
90			tmesh.cal Used to smooth polygonal geometry
91			.br
92			*.rad RADIANCE source descriptions created by ies2rad
93			.br
94			*.dat RADIANCE source data created by ies2rad
95			.br
96			source.cal Used for IES source coordinates
97			.SH AUTHOR
98			Greg Ward
99			.SH "SEE ALSO"
100			ies2rad(1), mgf2meta(1), obj2rad(1), oconv(1), rad2mgf(1), xform(1)
101			.PP
102			MGF web site "http://radsite.lbl.gov/mgf/HOME.html"