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.18 by greg, Wed Mar 23 01:52:51 2022 UTC vs.
Revision 1.23 by greg, Thu Mar 27 01:26:55 2025 UTC

# Line 15 | Line 15 | dctimestep - compute annual simulation time-step(s) vi
15   ][
16   .B "\-y yres"
17   ][
18 < .B "\-i{f|d}
18 > .B "\-i{a|f|d}
19   ][
20 < .B "\-o{f|d|c}
20 > .B "\-o{a|f|d|c}
21   ]
22   .B DCspec
23   [
# Line 34 | Line 34 | dctimestep - compute annual simulation time-step(s) vi
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
# Line 106 | Line 106 | using quotes and a beginning exclamation point ('!').
106   The standard output of
107   .I dctimestep
108   is either a color vector with as many RGB triplets
109 < as there are rows in the View matrix, or a combined
110 < .I Radiance
109 > as there are rows in the View matrix, or a combined Radiance
110   picture.
111   Which output is produced depends on the first argument.
112   A regular file name will be loaded and interpreted as a matrix to
113   generate a color results vector.
114   A file specification containing a '%d' format string will be
115 < interpreted as a list of
117 < .I Radiance
115 > interpreted as a list of Radiance
116   component pictures, which will be summed according to the computed
117   vector.
118   .PP
# Line 137 | Line 135 | on the number of rows in the result vectors.
135   A header will normally be produced on the output, unless the
136   .I \-h
137   option is specified.
138 + Default output format is ASCII text.
139   The
140   .I \-of,
141   .I \-od,
# Line 144 | Line 143 | or
143   .I \-oc
144   option may be used to specify IEEE float, double, or RGBE (picture) output
145   data, respectively.
146 + The
147 + .I \-oc
148 + option is set automatically if input is a collection of RGBE or XYZE pictures.
149   .SH EXAMPLES
150   To compute workplane illuminances at 3:30pm on Feb 10th:
151   .IP "" .2i
# Line 158 | Line 160 | the Winter solstice at 2pm:
160   .IP "" .2i
161   gensky 12 21 14 | genskyvec | dctimestep IllPts.vmx Blinds20.xml Window1.dmx > Ill_12-21-14.dat
162   .PP
163 < To compute Window2's contribution to an interior view at 12 noon on the Summer solstice:
163 > To compute Window2's contribution to an interior view at 12 noon on the summer solstice:
164   .IP "" .2i
165   gensky 6 21 12 | genskyvec | dctimestep view%03d.hdr Blinds30.xml
166   Window2.dmx > view_6-21-12.hdr
# Line 196 | Line 198 | output option with
198   since matrix operations are carried out using 32-bit "float" values.
199   This take less memory, but can also be less accurate than an
200   equivalent invocation of
201 < .I rmtxop(1),
202 < which performs all operations on 64-bit "double" values.
201 > .I rmtxop(1)
202 > or
203 > .I rcomb(1),
204 > which perform all operations on 64-bit "double" values.
205 > .PP
206 > .I Dctimestep
207 > does not accept on input or produce on output Radiance
208 > spectral pictures.
209 > This is a limitation of the implementation and its underlying
210 > data representation.
211 > Use instead the similar
212 > .I pvsum(1)
213 > tool for spectral input and output.
214   .SH AUTHOR
215   Greg Ward
216   .SH "SEE ALSO"
217 < gendaymtx(1), genskyvec(1), getinfo(1),
218 < mkillum(1), rcollate(1), rcontrib(1), rcrop(1),
217 > dcglare(1), gendaymtx(1), genskyvec(1), getinfo(1), mkillum(1),
218 > pvsum(1), ra_rgbe(1), rcollate(1), rcomb(1), rcontrib(1), rcrop(1),
219   rfluxmtx(1), rmtxop(1), rtrace(1), vwrays(1)

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines