| 11 |
|
][ |
| 12 |
|
.B "\-o ospec" |
| 13 |
|
][ |
| 14 |
+ |
.B "\-x xres" |
| 15 |
+ |
][ |
| 16 |
+ |
.B "\-y yres" |
| 17 |
+ |
][ |
| 18 |
|
.B "\-i{f|d} |
| 19 |
|
][ |
| 20 |
< |
.B "\-o{f|d} |
| 20 |
> |
.B "\-o{f|d|c} |
| 21 |
|
] |
| 22 |
|
.B DCspec |
| 23 |
|
[ |
| 37 |
|
.B "\-o{f|d} |
| 38 |
|
] |
| 39 |
|
.B Vspec |
| 40 |
< |
.B Tbsdf.xml |
| 40 |
> |
.B Tbsdf |
| 41 |
|
.B Dmat.dat |
| 42 |
|
[ |
| 43 |
|
.B skyf |
| 61 |
|
directions are related to some set of measured values, such as an array of |
| 62 |
|
illuminance points or images. |
| 63 |
|
This matrix is usually computed by |
| 64 |
+ |
.I rfluxmtx(1) |
| 65 |
+ |
or |
| 66 |
|
.I rcontrib(1) |
| 67 |
|
for a particular set of windows or skylight openings. |
| 68 |
|
The second argument is the window transmission matrix, or BSDF, given as |
| 69 |
< |
a standard XML description. |
| 69 |
> |
a matrix or a standard XML description. |
| 70 |
|
The third argument is the Daylight matrix file that defines how sky patches |
| 71 |
|
relate to input directions on the same opening. |
| 72 |
|
This is usually computed using |
| 73 |
< |
.I genklemsamp(1) |
| 74 |
< |
with |
| 69 |
< |
.I rcontrib |
| 70 |
< |
in a separate run for each window or skylight orientation. |
| 73 |
> |
.I rfluxmtx |
| 74 |
> |
with separate runs for each window or skylight orientation. |
| 75 |
|
The last file is the sky contribution vector or matrix, |
| 76 |
|
typically computed by |
| 77 |
|
.I genskyvec(1) |
| 78 |
|
or |
| 79 |
|
.I gendaymtx(1), |
| 80 |
|
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. |
| 81 |
|
.PP |
| 82 |
|
If the input sky data lacks a header, the |
| 83 |
|
.I \-n |
| 84 |
|
option may be used to indicate the number of time steps, which |
| 85 |
|
will be 1 for a sky vector. |
| 86 |
< |
The sky input file must contain the number of |
| 87 |
< |
columns specified in each sky patch row, whether it is read |
| 88 |
< |
from the standard input or from a file. |
| 86 |
> |
The sky input file must otherwise contain the number of |
| 87 |
> |
columns (time steps) specified in each sky patch row, |
| 88 |
> |
whether it is read from the standard input or from a file. |
| 89 |
|
Input starts from the first patch at the first time step, then the |
| 90 |
|
first patch at the second time step, and so on. |
| 91 |
+ |
Note that all matrix elements are RGB triplets, so the actual size |
| 92 |
+ |
of the sky vector or matrix is three times the number of steps times |
| 93 |
+ |
the number of sky patches. |
| 94 |
|
The |
| 95 |
|
.I \-if |
| 96 |
|
or |
| 97 |
|
.I \-id |
| 98 |
|
option may be used to specify that sky data is in float or double |
| 99 |
|
format, respectively, which is more efficient for large matrices. |
| 100 |
< |
These options are unnecessary in the when the sky |
| 97 |
< |
input has a header. |
| 100 |
> |
These options are unnecessary when the sky input includes a header. |
| 101 |
|
.PP |
| 102 |
+ |
Any of the matrix or vector files may be read from a command |
| 103 |
+ |
instead of a file by |
| 104 |
+ |
using quotes and a beginning exclamation point ('!'). |
| 105 |
+ |
.PP |
| 106 |
|
The standard output of |
| 107 |
|
.I dctimestep |
| 108 |
|
is either a color vector with as many RGB triplets |
| 123 |
|
option may be used to specify a file or a set of output files |
| 124 |
|
to use rather than the standard output. |
| 125 |
|
If the given specification contains a '%d' format string, this |
| 126 |
< |
will be replaced by the time step index, starting from 1. |
| 126 |
> |
will be replaced by the time step index, starting from 0. |
| 127 |
|
In this way, multiple output pictures may be produced, |
| 128 |
|
or separate result vectors (one per time step). |
| 129 |
+ |
If input is a matrix rather than a set of images, the |
| 130 |
+ |
.I \-x |
| 131 |
+ |
and/or |
| 132 |
+ |
.I \-y |
| 133 |
+ |
options may be necessary to set the output image size. |
| 134 |
+ |
If only one dimension is specified, the other is computed based |
| 135 |
+ |
on the number of rows in the result vectors. |
| 136 |
|
.PP |
| 137 |
|
A header will normally be produced on the output, unless the |
| 138 |
|
.I \-h |
| 139 |
|
option is specified. |
| 140 |
|
The |
| 141 |
< |
.I \-of |
| 141 |
> |
.I \-of, |
| 142 |
> |
.I \-od, |
| 143 |
|
or |
| 144 |
< |
.I \-od |
| 145 |
< |
option may be used to specify IEEE float or double binary output |
| 144 |
> |
.I \-oc |
| 145 |
> |
option may be used to specify IEEE float, double, or RGBE (picture) output |
| 146 |
|
data, respectively. |
| 147 |
|
.SH EXAMPLES |
| 148 |
|
To compute workplane illuminances at 3:30pm on Feb 10th: |
| 168 |
|
.IP "" .2i |
| 169 |
|
gendaymtx -of Tampa.wea | dctimestep WPpts.vmx |
| 170 |
|
shade3.xml Skylight3.dmx > wp_win3.dat |
| 156 |
– |
.IP "" .2i |
| 171 |
|
.PP |
| 172 |
|
Generate a series of pictures corresponding to timesteps |
| 173 |
|
in an annual simulation: |
| 174 |
|
.IP "" .2i |
| 175 |
|
gendaymtx NYCity.wea | dctimestep -o tstep%04d.hdr dcomp%03d.hdr |
| 176 |
|
.PP |
| 177 |
+ |
To multiply an irradiance view matrix through a pair of XML window layers using |
| 178 |
+ |
a given exterior daylight matrix and sky vector: |
| 179 |
+ |
.IP "" .2i |
| 180 |
+ |
dctimestep Illum.vmx "!rmtxop -ff Blinds1.xml Windo1.xml" Exter.dmx Jan20.sky |
| 181 |
+ |
.PP |
| 182 |
|
To multiply two matrices into a IEEE-float result with header: |
| 183 |
|
.IP "" .2i |
| 184 |
|
dctimestep -of Inp1.fmx Inp2.fmx > Inp1xInp2.fmx |
| 185 |
|
.SH AUTHOR |
| 186 |
|
Greg Ward |
| 187 |
|
.SH "SEE ALSO" |
| 188 |
< |
gendaymtx(1), genklemsamp(1), genskyvec(1), getinfo(1), |
| 189 |
< |
mkillum(1), rcollate(1), rcontrib(1), rmtxop(1), rtrace(1), vwrays(1) |
| 188 |
> |
gendaymtx(1), genskyvec(1), getinfo(1), |
| 189 |
> |
mkillum(1), rcollate(1), rcontrib(1), |
| 190 |
> |
rfluxmtx(1), rmtxop(1), rtrace(1), vwrays(1) |
