| 60 |
|
with |
| 61 |
|
.I rcontrib |
| 62 |
|
in a separate run for each window or skylight orientation. |
| 63 |
< |
The final input is the sky contribution vector or matrix, |
| 64 |
< |
usually computed by |
| 65 |
< |
.I genskyvec(1), |
| 66 |
< |
which may be passed on the standard input. |
| 67 |
< |
This data is expected to be in ASCII format, whereas the |
| 68 |
< |
View and Daylight matrices |
| 69 |
< |
are more efficiently represented as binary float data if machine |
| 70 |
< |
byte-order is not an issue. |
| 63 |
> |
The last file is the sky contribution vector or matrix, |
| 64 |
> |
typically computed by |
| 65 |
> |
.I genskyvec(1) |
| 66 |
> |
or |
| 67 |
> |
.I gendaymtx(1), |
| 68 |
> |
and may be passed on the standard input. |
| 69 |
> |
This data is assumed by default to be in ASCII format, whereas the |
| 70 |
> |
formats of the View and Daylight matrices |
| 71 |
> |
are detected automatically if given as binary data. |
| 72 |
|
The |
| 73 |
|
.I \-if |
| 74 |
|
or |
| 75 |
|
.I \-id |
| 76 |
|
option may be used to specify that sky data is in float or double |
| 77 |
< |
format, instead. |
| 77 |
> |
format, respectively, which is more efficient for large matrices. |
| 78 |
|
(Note that binary double data may not be read from stdin.)\0 |
| 79 |
|
.PP |
| 80 |
|
Sent to the standard output of |
| 98 |
|
single invocation. |
| 99 |
|
The sky input file must contain the number of |
| 100 |
|
columns specified in each sky patch row, whether it is read |
| 101 |
< |
from the standard input or from an ASCII file. |
| 101 |
> |
from the standard input or from a file. |
| 102 |
|
The columns do not need to be given on the same |
| 103 |
|
line, so long as the number of values totals 3*Nsteps*Npatches. |
| 104 |
|
Input starts from the first patch at the first time step, then the |
| 111 |
|
If the given specification contains a '%d' format string, this |
| 112 |
|
will be replaced by the time step index, starting from 1. |
| 113 |
|
In this way, multiple output pictures may be produced, |
| 114 |
< |
or separate results vector (one per time step). |
| 114 |
> |
or separate result vectors (one per time step). |
| 115 |
|
.SH EXAMPLES |
| 116 |
|
To compute workplane illuminances at 3:30pm on Feb 10th: |
| 117 |
|
.IP "" .2i |
| 119 |
|
.PP |
| 120 |
|
To compute an image at 10am on the equinox from a set of component images: |
| 121 |
|
.IP "" .2i |
| 122 |
< |
gensky 3 21 10 | genskyvec | dctimestep viewc%03d.hdr > view_03-21-10.hdr |
| 122 |
> |
gensky 3 21 10 | genskyvec | dctimestep dcomp%03d.hdr > view_03-21-10.hdr |
| 123 |
|
.PP |
| 124 |
|
To compute a set of illuminance contributions for Window 1 on |
| 125 |
|
the Winter solstice at 2pm: |
| 128 |
|
.PP |
| 129 |
|
To compute Window2's contribution to an interior view at 12 noon on the Summer solstice: |
| 130 |
|
.IP "" .2i |
| 131 |
< |
gensky 6 21 12 | genskyvec | dctimestep view%03d.hdr Blinds30.xml Window2.dmx > view_6-21-12.hdr |
| 131 |
> |
gensky 6 21 12 | genskyvec | dctimestep view%03d.hdr Blinds30.xml |
| 132 |
> |
Window2.dmx > view_6-21-12.hdr |
| 133 |
> |
.PP |
| 134 |
> |
To generate an hourly matrix of sensor value contributions from Skylight3 |
| 135 |
> |
using a 3-phase calculation, where output columns are time steps: |
| 136 |
> |
.IP "" .2i |
| 137 |
> |
gendaymtx -of Tampa.wea | dctimestep -if -n 8760 WPpts.vmx |
| 138 |
> |
shade3.xml Skylight3.dmx > wp_win3.dat |
| 139 |
> |
.IP "" .2i |
| 140 |
> |
.PP |
| 141 |
> |
Generate a series of pictures corresponding to timesteps |
| 142 |
> |
in an annual simulation: |
| 143 |
> |
.IP "" .2i |
| 144 |
> |
gendaymtx NYCity.wea | dctimestep -n 8760 -o tstep%04d.hdr dcomp%03d.hdr |
| 145 |
|
.SH AUTHOR |
| 146 |
|
Greg Ward |
| 147 |
|
.SH "SEE ALSO" |
| 148 |
< |
genklemsamp(1), genskyvec(1), mkillum(1), rcontrib(1), rtrace(1), vwrays(1) |
| 148 |
> |
gendaymtx(1), genklemsamp(1), genskyvec(1), |
| 149 |
> |
mkillum(1), rcontrib(1), rtrace(1), vwrays(1) |
