ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/radiance/ray/doc/man/man1/dctimestep.1
(Generate patch)

Comparing ray/doc/man/man1/dctimestep.1 (file contents):
Revision 1.9 by greg, Fri May 30 00:00:54 2014 UTC vs.
Revision 1.10 by greg, Wed Sep 17 22:40:49 2014 UTC

# Line 7 | Line 7 | dctimestep - compute annual simulation time-step(s) vi
7   [
8   .B "\-n nsteps"
9   ][
10 + .B "\-h"
11 + ][
12   .B "\-o ospec"
13   ][
14 < .B "\-i{f|d|h}
14 > .B "\-i{f|d}
15   ][
16   .B "\-o{f|d}
17   ]
# Line 22 | Line 24 | dctimestep - compute annual simulation time-step(s) vi
24   [
25   .B "\-n nsteps"
26   ][
27 + .B "\-h"
28 + ][
29   .B "\-o ospec"
30   ][
31 < .B "\-i{f|d|h}
31 > .B "\-i{f|d}
32   ][
33   .B "\-o{f|d}
34   ]
# Line 73 | Line 77 | 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.
80 + .PP
81 + If the input sky data lacks a header, the
82 + .I \-n
83 + option may be used to indicate the number of time steps, which
84 + will be 1 for a sky vector.
85 + The sky input file must contain the number of
86 + columns specified in each sky patch row, whether it is read
87 + from the standard input or from a file.
88 + Input starts from the first patch at the first time step, then the
89 + first patch at the second time step, and so on.
90   The
91   .I \-if
92   or
93   .I \-id
94   option may be used to specify that sky data is in float or double
95   format, respectively, which is more efficient for large matrices.
96 < The
97 < .I \-ih
84 < option says to check the header to determine the data type.
85 < (Note that binary double data may not be read from stdin without a header.)\0
96 > These options are unnecessary in the when the sky
97 > input has a header.
98   .PP
99   The standard output of
100   .I dctimestep
# Line 100 | Line 112 | component pictures, which will be summed according to
112   vector.
113   .PP
114   The
103 – .I \-n
104 – option may be used to compute multiple time steps in a
105 – single invocation.
106 – The sky input file must contain the number of
107 – columns specified in each sky patch row, whether it is read
108 – from the standard input or from a file.
109 – The columns do not need to be given on the same
110 – line, so long as the number of values totals 3*Nsteps*Npatches.
111 – Input starts from the first patch at the first time step, then the
112 – first patch at the second time step, and so on.
113 – If the input matrix has a header, then you may use
114 – .I \-n 0
115 – to get the number of columns from the header rather than specifying it.
116 – .PP
117 – The
115   .I \-o
116   option may be used to specify a file or a set of output files
117   to use rather than the standard output.
# Line 122 | Line 119 | If the given specification contains a '%d' format stri
119   will be replaced by the time step index, starting from 1.
120   In this way, multiple output pictures may be produced,
121   or separate result vectors (one per time step).
125 – If the standard output is used or the
126 – .I \-o
127 – option specifies a single output file, then an information header
128 – will precede the output.
129 – This can be removed if desired using the
130 – .I getinfo\(1\)
131 – command with a single hyphen ('-') argument.
122   .PP
123 + A header will normally be produced on the output, unless the
124 + .I \-h
125 + option is specified.
126   The
127   .I \-of
128   or
129   .I \-od
130   option may be used to specify IEEE float or double binary output
131   data, respectively.
139 – This enables
140 – .I dctimestep
141 – to be used as a pure matrix multiplier, as the output file with
142 – header specifying the format is suitable for subsequent calls.
132   .SH EXAMPLES
133   To compute workplane illuminances at 3:30pm on Feb 10th:
134   .IP "" .2i
# Line 162 | Line 151 | Window2.dmx > view_6-21-12.hdr
151   To generate an hourly matrix of sensor value contributions from Skylight3
152   using a 3-phase calculation, where output columns are time steps:
153   .IP "" .2i
154 < gendaymtx -of Tampa.wea | dctimestep -if -n 8760 WPpts.vmx
154 > gendaymtx -of Tampa.wea | dctimestep WPpts.vmx
155   shade3.xml Skylight3.dmx > wp_win3.dat
156   .IP "" .2i
157   .PP
158   Generate a series of pictures corresponding to timesteps
159   in an annual simulation:
160   .IP "" .2i
161 < gendaymtx NYCity.wea | dctimestep -n 8760 -o tstep%04d.hdr dcomp%03d.hdr
161 > gendaymtx NYCity.wea | dctimestep -o tstep%04d.hdr dcomp%03d.hdr
162   .PP
163 < To multiply two color matrices (second matrix is IEEE-float with
175 < 145 RGB columns) into a IEEE-double result (also 145 RGB columns):
163 > To multiply two matrices into a IEEE-float result with header:
164   .IP "" .2i
165 < getinfo - < Inp2.fmx | dctimestep -n 145 -if -od Inp1.fmx > Inp1xInp2.dmx
165 > dctimestep -of Inp1.fmx Inp2.fmx > Inp1xInp2.fmx
166   .SH AUTHOR
167   Greg Ward
168   .SH "SEE ALSO"
169   gendaymtx(1), genklemsamp(1), genskyvec(1), getinfo(1),
170 < mkillum(1), rcollate(1), rcontrib(1), rtrace(1), vwrays(1)
170 > mkillum(1), rcollate(1), rcontrib(1), rmtxop(1), rtrace(1), vwrays(1)

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines