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 |
|
[ |
34 |
|
][ |
35 |
|
.B "\-i{f|d} |
36 |
|
][ |
37 |
< |
.B "\-o{f|d} |
37 |
> |
.B "\-o{f|d|c} |
38 |
|
] |
39 |
|
.B Vspec |
40 |
|
.B Tbsdf |
51 |
|
vector or matrix, which may be read from the standard input if unspecified. |
52 |
|
The daylight coefficients are multiplied against these sky values |
53 |
|
and the results are written to the standard output. |
54 |
< |
This may be a list of color values or a combined Radiance image, |
54 |
> |
This may be a list of color values or a combined Radiance picture, |
55 |
|
as explained below. |
56 |
|
.PP |
57 |
|
In the second form, |
58 |
|
.I dctimestep |
59 |
|
takes four input files, forming a matrix expression. |
60 |
< |
The first argument is the View matrix file that specifies how window output |
60 |
> |
The first argument is the View matrix that specifies how window output |
61 |
|
directions are related to some set of measured values, such as an array of |
62 |
< |
illuminance points or images. |
62 |
> |
illuminance points or pictures. |
63 |
|
This matrix is usually computed by |
64 |
|
.I rfluxmtx(1) |
65 |
|
or |
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 |
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 |
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 |
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 pictures, the |
130 |
+ |
.I \-x |
131 |
+ |
and/or |
132 |
+ |
.I \-y |
133 |
+ |
options may be necessary to set the output picture 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 |
+ |
Default output format is ASCII text. |
141 |
|
The |
142 |
< |
.I \-of |
142 |
> |
.I \-of, |
143 |
> |
.I \-od, |
144 |
|
or |
145 |
< |
.I \-od |
146 |
< |
option may be used to specify IEEE float or double binary output |
145 |
> |
.I \-oc |
146 |
> |
option may be used to specify IEEE float, double, or RGBE (picture) output |
147 |
|
data, respectively. |
148 |
+ |
The |
149 |
+ |
.I \-oc |
150 |
+ |
option is set automatically if input is a collection of RGBE or XYZE pictures. |
151 |
|
.SH EXAMPLES |
152 |
|
To compute workplane illuminances at 3:30pm on Feb 10th: |
153 |
|
.IP "" .2i |
154 |
|
gensky 2 10 15:30 | genskyvec | dctimestep workplaneDC.dmx > Ill_02-10-1530.dat |
155 |
|
.PP |
156 |
< |
To compute an image at 10am on the equinox from a set of component images: |
156 |
> |
To compute a picture at 10am on the equinox from a set of component pictures: |
157 |
|
.IP "" .2i |
158 |
|
gensky 3 21 10 | genskyvec | dctimestep dcomp%03d.hdr > view_03-21-10.hdr |
159 |
|
.PP |
186 |
|
To multiply two matrices into a IEEE-float result with header: |
187 |
|
.IP "" .2i |
188 |
|
dctimestep -of Inp1.fmx Inp2.fmx > Inp1xInp2.fmx |
189 |
+ |
.SH NOTES |
190 |
+ |
.I Dctimestep |
191 |
+ |
optimizes its matrix concatenation by checking for all-zero rows |
192 |
+ |
or columns, thus avoiding unnecessary vector multiplications. |
193 |
+ |
This can improve performance when a daylight matrix contains |
194 |
+ |
zero-filled column vectors corresponding to hours of darkness. |
195 |
+ |
.PP |
196 |
+ |
It rarely makes sense to specify the |
197 |
+ |
.I \-od |
198 |
+ |
output option with |
199 |
+ |
.I dctimestep, |
200 |
+ |
since matrix operations are carried out using 32-bit "float" values. |
201 |
+ |
This take less memory, but can also be less accurate than an |
202 |
+ |
equivalent invocation of |
203 |
+ |
.I rmtxop(1) |
204 |
+ |
or |
205 |
+ |
.I rcomb(1), |
206 |
+ |
which perform all operations on 64-bit "double" values. |
207 |
|
.SH AUTHOR |
208 |
|
Greg Ward |
209 |
|
.SH "SEE ALSO" |
210 |
|
gendaymtx(1), genskyvec(1), getinfo(1), |
211 |
< |
mkillum(1), rcollate(1), rcontrib(1), |
211 |
> |
mkillum(1), rcollate(1), rcomb(1), rcontrib(1), rcrop(1), |
212 |
|
rfluxmtx(1), rmtxop(1), rtrace(1), vwrays(1) |