| 33 |
|
.B "\-o{f|d} |
| 34 |
|
] |
| 35 |
|
.B Vspec |
| 36 |
< |
.B Tbsdf.xml |
| 36 |
> |
.B Tbsdf |
| 37 |
|
.B Dmat.dat |
| 38 |
|
[ |
| 39 |
|
.B skyf |
| 57 |
|
directions are related to some set of measured values, such as an array of |
| 58 |
|
illuminance points or images. |
| 59 |
|
This matrix is usually computed by |
| 60 |
+ |
.I rfluxmtx(1) |
| 61 |
+ |
or |
| 62 |
|
.I rcontrib(1) |
| 63 |
|
for a particular set of windows or skylight openings. |
| 64 |
|
The second argument is the window transmission matrix, or BSDF, given as |
| 65 |
< |
a standard XML description. |
| 65 |
> |
a matrix or a standard XML description. |
| 66 |
|
The third argument is the Daylight matrix file that defines how sky patches |
| 67 |
|
relate to input directions on the same opening. |
| 68 |
|
This is usually computed using |
| 69 |
< |
.I genklemsamp(1) |
| 70 |
< |
with |
| 69 |
< |
.I rcontrib |
| 70 |
< |
in a separate run for each window or skylight orientation. |
| 69 |
> |
.I rfluxmtx |
| 70 |
> |
with separate runs for each window or skylight orientation. |
| 71 |
|
The last file is the sky contribution vector or matrix, |
| 72 |
|
typically computed by |
| 73 |
|
.I genskyvec(1) |
| 74 |
|
or |
| 75 |
|
.I gendaymtx(1), |
| 76 |
|
and may be passed on the standard input. |
| 77 |
– |
This data is assumed by default to be in ASCII format, whereas the |
| 78 |
– |
formats of the View and Daylight matrices |
| 79 |
– |
are detected automatically if given as binary data. |
| 77 |
|
.PP |
| 78 |
|
If the input sky data lacks a header, the |
| 79 |
|
.I \-n |
| 80 |
|
option may be used to indicate the number of time steps, which |
| 81 |
|
will be 1 for a sky vector. |
| 82 |
|
The sky input file must contain the number of |
| 83 |
< |
columns specified in each sky patch row, whether it is read |
| 84 |
< |
from the standard input or from a file. |
| 83 |
> |
columns (time steps) specified in each sky patch row, |
| 84 |
> |
whether it is read from the standard input or from a file. |
| 85 |
|
Input starts from the first patch at the first time step, then the |
| 86 |
|
first patch at the second time step, and so on. |
| 87 |
+ |
Note that all matrix elements are RGB triplets, so the actual size |
| 88 |
+ |
of the sky vector or matrix is three times the number of steps times |
| 89 |
+ |
the number of sky patches. |
| 90 |
|
The |
| 91 |
|
.I \-if |
| 92 |
|
or |
| 157 |
|
.IP "" .2i |
| 158 |
|
gendaymtx -of Tampa.wea | dctimestep WPpts.vmx |
| 159 |
|
shade3.xml Skylight3.dmx > wp_win3.dat |
| 160 |
– |
.IP "" .2i |
| 160 |
|
.PP |
| 161 |
|
Generate a series of pictures corresponding to timesteps |
| 162 |
|
in an annual simulation: |
| 163 |
|
.IP "" .2i |
| 164 |
|
gendaymtx NYCity.wea | dctimestep -o tstep%04d.hdr dcomp%03d.hdr |
| 165 |
|
.PP |
| 166 |
+ |
To multiply an irradiance view matrix through a pair of XML window layers using |
| 167 |
+ |
a given exterior daylight matrix and sky vector: |
| 168 |
+ |
.IP "" .2i |
| 169 |
+ |
dctimestep Illum.vmx "!rmtxop -ff Blinds1.xml Windo1.xml" Exter.dmx Jan20.sky |
| 170 |
+ |
.PP |
| 171 |
|
To multiply two matrices into a IEEE-float result with header: |
| 172 |
|
.IP "" .2i |
| 173 |
|
dctimestep -of Inp1.fmx Inp2.fmx > Inp1xInp2.fmx |
| 174 |
|
.SH AUTHOR |
| 175 |
|
Greg Ward |
| 176 |
|
.SH "SEE ALSO" |
| 177 |
< |
gendaymtx(1), genklemsamp(1), genskyvec(1), getinfo(1), |
| 178 |
< |
mkillum(1), rcollate(1), rcontrib(1), rmtxop(1), rtrace(1), vwrays(1) |
| 177 |
> |
gendaymtx(1), genskyvec(1), getinfo(1), |
| 178 |
> |
mkillum(1), rcollate(1), rcontrib(1), |
| 179 |
> |
rfluxmtx(1), rmtxop(1), rtrace(1), vwrays(1) |
