man/man1/rfluxmtx.1

.\" RCSid "$Id: rfluxmtx.1,v 1.15 2025/03/27 01:26:55 greg Exp $"
.TH RFLUXMTX 1 07/22/14 RADIANCE
.SH NAME
rfluxmtx - compute flux transfer matrix(es) for RADIANCE scene
.SH SYNOPSIS
.B rfluxmtx
[
.B \-v
][
.B "rcontrib options"
]
.B "{ sender.rad | - }"
.B receivers.rad
.B "[ -i system.oct ]"
.B "[ system.rad .. ]"
.SH DESCRIPTION
.I Rfluxmtx
samples rays uniformly over the surface given in
.I sender.rad
and records rays arriving at surfaces in the file
.I receivers.rad,
producing a flux transfer matrix per receiver.
A system octree to which the receivers will be appended may be given with a
.I \-i
option following the receiver file.
Additional system surfaces may be given in one or more
.I system.rad
files, which are compiled before the receiver file into an octree sent to the
.I rcontrib(1)
program to do the actual work.
If a single hyphen ('-') is given in place of the sender file, then
.I rfluxmtx
passes ray samples from its standard input directly to
.I rcontrib
without interpretation.
By default, all resulting matrix data are interleaved and sent to the standard output
in ASCII format, but this behavior is typically overridden using inline options
as described below.
.PP
The
.I \-v
option turns on verbose reporting for the number of samples and the executed
.I rcontrib
command.
All other supported options are passed on to
.I rcontrib(1).
However, the
.I \-fo,
.I \-p,
.I \-b,
.I \-bn,
.I \-m,
and
.I \-M
options are controlled by
.I rfluxmtx
and may not be set by the user.
(Recovery mode is not supported, and existing output is always overwritten.)\0
Further, the
.I \-x,
.I \-y,
and
.I \-ld
options are ignored unless
.I rfluxmtx
is invoked in the pass-through mode,
in which case they may be needed to generate RADIANCE views from
.I vwrays(1).
The sample count, unless set by the
.I \-c
option, defaults to 10000 when a sender file is given, or to 1 for pass-through mode.
.SH VARIABLES
The sender and receiver scene files given to
.I rfluxmtx
contain controlling parameters in special comments of the form:
.nf

        #@rfluxmtx variable=value ..

.fi
At minimum, both sender and receiver must specify one of the
hemisphere sampling types, and there must be at least
one surface in each file.
.TP 10n
.BI h =u
Set hemisphere sampling to "uniform," meaning a single bin
of (cosine-distributed) samples.
In the case of distant "source" primitives, this is the only
sampling method that supports arbitrary receiver sizes.
The other methods below require a full hemispherical source.
.TP
.BI h =kf
Divide the hemisphere using the LBNL/Klems "full" sampling basis.
(Use "h=-kf" for left-handed coordinates.)
.TP
.BI h =kh
Divide the hemisphere using the LBNL/Klems "half" sampling basis.
(Use "h=-kh" for left-handed coordinates.)
.TP
.BI h =kq
Divide the hemisphere using the LBNL/Klems "quarter" sampling basis.
(Use "h=-kq" for left-handed coordinates.)
.TP
.BI h =rN
Divide the hemisphere using Reinhart's substructuring of the Tregenza
sky pattern with
.I N
divisions in each dimension.
If it is not given,
.I N
defaults to 1, which is just the Tregenza sky.
(Use "h=-rN" for left-handed coordinates.)
.TP
.BI h =cie
Divide the hemisphere into CIE sky scanner directions, which is
similar to Tregenza but with different starting azimuths and
reversing row direction at each new altitude.
(Use "h=-cie" for left-handed coordinates.)
.TP
.BI h =scN
Subdivide the hemisphere using the Shirley-Chiu square-to-disk mapping with an
.I NxN
grid over the square.
(Use "h=-scN" for left-handed coordinates.)
.TP
.BI u =[-]{X|Y|Z|ux,uy,uz}
Orient the "up" direction for the hemisphere using the indicated axis or direction
vector.
.TP
.BI o =output_spec
Send the matrix data for this receiver to the indicated file or command.
Single or double quotes may be used to contain strings with spaces, and
commands must begin with an exclamation mark ('!').
The file format will be determined by the command-line
.I \-fio
option and will include an information header unless the
.I \-h
option was used to turn headers off.
(The input format specification is ignored for senders.)\0
.PP
In normal execution, only a single sender surface is sampled, but it may be
comprised of any number of subsurfaces, as in a triangle mesh or similar.
The surface normal will be computed as the average of all the constituent
subsurfaces.
The subsurfaces themselves must be planar, thus only
.I polygon
and
.I ring
surface primitives are supported.
Other primitives will be silently ignored and will have no effect on the calculation.
.PP
In the receiver file, the
.I source
primitive is supported as well, and multiple receivers (and multiple output
matrices) may be identified by different modifier names.
(Make sure that surfaces using the same modifier are grouped together,
and that the modifiers are unique and not used elsewhere in the
scene description.)\0
Though it may be counter-intuitive, receivers are often light sources,
since samples end up there in a backwards ray-tracing system such as RADIANCE.
When using local geometry, the overall aperture shape should be close to flat.
Large displacements may give rise to errors due to a convex receiver's
larger profile at low angles of incidence.
.PP
Rays always emanate from the back side of the sender surface and arrive at the
front side of receiver surfaces.
In this way, a receiver surface may be reused as a sender in a subsequent
.I rfluxmtx
calculation and the resulting matrices will concatenate properly.
(Note that it is important to keep receiver surfaces together, otherwise a
"duplicate modifier" error will result.)\0
.SH EXAMPLES
To generate a flux transfer matrix connecting input and output apertures
on a light pipe:
.IP "" .2i
rfluxmtx int_aperture.rad ext_aperture.rad lpipe.rad > lpipe.mtx
.SH AUTHOR
Greg Ward
.SH "SEE ALSO"
genBSDF(1), getinfo(1), pvsum(1), rcalc(1), rcollate(1), rcomb(1), rcontrib(1),
rcrop(1), rmtxop(1), rxfluxmtx(1), vwrays(1), wrapBSDF(1)
Revision:	1.16
Committed:	Thu Oct 23 23:34:59 2025 UTC (7 days, 21 hours ago) by greg
Branch:	MAIN
CVS Tags:	HEAD
Changes since 1.15:	+7 -7 lines
Log Message:	docs: Added rxfluxmtx man page and updated others accordingly
#	Content
1	.\" RCSid "$Id: rfluxmtx.1,v 1.15 2025/03/27 01:26:55 greg Exp $"
2	.TH RFLUXMTX 1 07/22/14 RADIANCE
3	.SH NAME
4	rfluxmtx - compute flux transfer matrix(es) for RADIANCE scene
5	.SH SYNOPSIS
6	.B rfluxmtx
7	[
8	.B \-v
9	][
10	.B "rcontrib options"
11	]
12	.B "{ sender.rad \| - }"
13	.B receivers.rad
14	.B "[ -i system.oct ]"
15	.B "[ system.rad .. ]"
16	.SH DESCRIPTION
17	.I Rfluxmtx
18	samples rays uniformly over the surface given in
19	.I sender.rad
20	and records rays arriving at surfaces in the file
21	.I receivers.rad,
22	producing a flux transfer matrix per receiver.
23	A system octree to which the receivers will be appended may be given with a
24	.I \-i
25	option following the receiver file.
26	Additional system surfaces may be given in one or more
27	.I system.rad
28	files, which are compiled before the receiver file into an octree sent to the
29	.I rcontrib(1)
30	program to do the actual work.
31	If a single hyphen ('-') is given in place of the sender file, then
32	.I rfluxmtx
33	passes ray samples from its standard input directly to
34	.I rcontrib
35	without interpretation.
36	By default, all resulting matrix data are interleaved and sent to the standard output
37	in ASCII format, but this behavior is typically overridden using inline options
38	as described below.
39	.PP
40	The
41	.I \-v
42	option turns on verbose reporting for the number of samples and the executed
43	.I rcontrib
44	command.
45	All other supported options are passed on to
46	.I rcontrib(1).
47	However, the
48	.I \-fo,
49	.I \-p,
50	.I \-b,
51	.I \-bn,
52	.I \-m,
53	and
54	.I \-M
55	options are controlled by
56	.I rfluxmtx
57	and may not be set by the user.
58	(Recovery mode is not supported, and existing output is always overwritten.)\0
59	Further, the
60	.I \-x,
61	.I \-y,
62	and
63	.I \-ld
64	options are ignored unless
65	.I rfluxmtx
66	is invoked in the pass-through mode,
67	in which case they may be needed to generate RADIANCE views from
68	.I vwrays(1).
69	The sample count, unless set by the
70	.I \-c
71	option, defaults to 10000 when a sender file is given, or to 1 for pass-through mode.
72	.SH VARIABLES
73	The sender and receiver scene files given to
74	.I rfluxmtx
75	contain controlling parameters in special comments of the form:
76	.nf
77
78	#@rfluxmtx variable=value ..
79
80	.fi
81	At minimum, both sender and receiver must specify one of the
82	hemisphere sampling types, and there must be at least
83	one surface in each file.
84	.TP 10n
85	.BI h =u
86	Set hemisphere sampling to "uniform," meaning a single bin
87	of (cosine-distributed) samples.
88	In the case of distant "source" primitives, this is the only
89	sampling method that supports arbitrary receiver sizes.
90	The other methods below require a full hemispherical source.
91	.TP
92	.BI h =kf
93	Divide the hemisphere using the LBNL/Klems "full" sampling basis.
94	(Use "h=-kf" for left-handed coordinates.)
95	.TP
96	.BI h =kh
97	Divide the hemisphere using the LBNL/Klems "half" sampling basis.
98	(Use "h=-kh" for left-handed coordinates.)
99	.TP
100	.BI h =kq
101	Divide the hemisphere using the LBNL/Klems "quarter" sampling basis.
102	(Use "h=-kq" for left-handed coordinates.)
103	.TP
104	.BI h =rN
105	Divide the hemisphere using Reinhart's substructuring of the Tregenza
106	sky pattern with
107	.I N
108	divisions in each dimension.
109	If it is not given,
110	.I N
111	defaults to 1, which is just the Tregenza sky.
112	(Use "h=-rN" for left-handed coordinates.)
113	.TP
114	.BI h =cie
115	Divide the hemisphere into CIE sky scanner directions, which is
116	similar to Tregenza but with different starting azimuths and
117	reversing row direction at each new altitude.
118	(Use "h=-cie" for left-handed coordinates.)
119	.TP
120	.BI h =scN
121	Subdivide the hemisphere using the Shirley-Chiu square-to-disk mapping with an
122	.I NxN
123	grid over the square.
124	(Use "h=-scN" for left-handed coordinates.)
125	.TP
126	.BI u =[-]{X\|Y\|Z\|ux,uy,uz}
127	Orient the "up" direction for the hemisphere using the indicated axis or direction
128	vector.
129	.TP
130	.BI o =output_spec
131	Send the matrix data for this receiver to the indicated file or command.
132	Single or double quotes may be used to contain strings with spaces, and
133	commands must begin with an exclamation mark ('!').
134	The file format will be determined by the command-line
135	.I \-fio
136	option and will include an information header unless the
137	.I \-h
138	option was used to turn headers off.
139	(The input format specification is ignored for senders.)\0
140	.PP
141	In normal execution, only a single sender surface is sampled, but it may be
142	comprised of any number of subsurfaces, as in a triangle mesh or similar.
143	The surface normal will be computed as the average of all the constituent
144	subsurfaces.
145	The subsurfaces themselves must be planar, thus only
146	.I polygon
147	and
148	.I ring
149	surface primitives are supported.
150	Other primitives will be silently ignored and will have no effect on the calculation.
151	.PP
152	In the receiver file, the
153	.I source
154	primitive is supported as well, and multiple receivers (and multiple output
155	matrices) may be identified by different modifier names.
156	(Make sure that surfaces using the same modifier are grouped together,
157	and that the modifiers are unique and not used elsewhere in the
158	scene description.)\0
159	Though it may be counter-intuitive, receivers are often light sources,
160	since samples end up there in a backwards ray-tracing system such as RADIANCE.
161	When using local geometry, the overall aperture shape should be close to flat.
162	Large displacements may give rise to errors due to a convex receiver's
163	larger profile at low angles of incidence.
164	.PP
165	Rays always emanate from the back side of the sender surface and arrive at the
166	front side of receiver surfaces.
167	In this way, a receiver surface may be reused as a sender in a subsequent
168	.I rfluxmtx
169	calculation and the resulting matrices will concatenate properly.
170	(Note that it is important to keep receiver surfaces together, otherwise a
171	"duplicate modifier" error will result.)\0
172	.SH EXAMPLES
173	To generate a flux transfer matrix connecting input and output apertures
174	on a light pipe:
175	.IP "" .2i
176	rfluxmtx int_aperture.rad ext_aperture.rad lpipe.rad > lpipe.mtx
177	.SH AUTHOR
178	Greg Ward
179	.SH "SEE ALSO"
180	genBSDF(1), getinfo(1), pvsum(1), rcalc(1), rcollate(1), rcomb(1), rcontrib(1),
181	rcrop(1), rmtxop(1), rxfluxmtx(1), vwrays(1), wrapBSDF(1)