9 |
|
][ |
10 |
|
.B "\-o ospec" |
11 |
|
][ |
12 |
< |
.B "\-i{f|d} |
12 |
> |
.B "\-i{f|d|h} |
13 |
|
][ |
14 |
|
.B "\-o{f|d} |
15 |
|
] |
24 |
|
][ |
25 |
|
.B "\-o ospec" |
26 |
|
][ |
27 |
< |
.B "\-i{f|d} |
27 |
> |
.B "\-i{f|d|h} |
28 |
|
][ |
29 |
|
.B "\-o{f|d} |
30 |
|
] |
79 |
|
.I \-id |
80 |
|
option may be used to specify that sky data is in float or double |
81 |
|
format, respectively, which is more efficient for large matrices. |
82 |
< |
(Note that binary double data may not be read from stdin.)\0 |
82 |
> |
The |
83 |
> |
.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 |
86 |
|
.PP |
87 |
< |
Sent to the standard output of |
87 |
> |
The standard output of |
88 |
|
.I dctimestep |
89 |
|
is either a color vector with as many RGB triplets |
90 |
|
as there are rows in the View matrix, or a combined |
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 |
118 |
|
.I \-o |