1 |
|
.\" RCSid "$Id$" |
2 |
|
.TH RCOLLATE 1 7/8/97 RADIANCE |
3 |
|
.SH NAME |
4 |
< |
rcollate - resize or transpose matrix data |
4 |
> |
rcollate - resize or re-order matrix data |
5 |
|
.SH SYNOPSIS |
6 |
|
.B rcollate |
7 |
|
[ |
89 |
|
would all be equivalent. |
90 |
|
Note that the lack of row separators in binary files means that |
91 |
|
.I rcollate |
92 |
< |
does not actually do anything for binary files unless the transpose |
93 |
< |
option is given, also. |
92 |
> |
does not actually do anything for binary files unless the data is being |
93 |
> |
re-ordered. |
94 |
|
.PP |
95 |
|
If an input header is present, it may contain the format, number of components |
96 |
|
and matrix dimensions. |
105 |
|
The transpose option, |
106 |
|
.I \-t |
107 |
|
swaps rows and columns on the input. |
108 |
< |
For binary files, the user must specify at least one input or output |
109 |
< |
dimension to define the matrix size. |
108 |
> |
For binary files with no header information, the user must |
109 |
> |
specify at least one input or output dimension to define the matrix size. |
110 |
|
For ASCII files, |
111 |
|
.I rcollate |
112 |
|
will automatically determine the number of columns based on the |
113 |
|
position of the first EOL (end-of-line) character, and the number |
114 |
|
of rows based on the total count of records in the file. |
115 |
|
The user may override these determinations, allowing the matrix to |
116 |
< |
be resized as well as transposed. |
117 |
< |
If input and output dimensions are given, the number of input rows |
118 |
< |
must equal the number of output columns, |
116 |
> |
be resized or re-ordered as well as transposed. |
117 |
> |
If input and output dimensions are given and there is no block re-ordering, |
118 |
> |
the number of input rows must equal the number of output columns, |
119 |
|
and the number of input columns must equal the number of output rows. |
120 |
– |
For large transpose operations on Unix systems, it is most efficient |
121 |
– |
to specify the input file on the command line, rather than reading |
122 |
– |
from the standard input, since |
123 |
– |
.I rcollate |
124 |
– |
can map the file directly into virtual memory. |
120 |
|
If the |
121 |
|
.I \-o |
122 |
|
option is also given with multiple block levels, the transpose operation |
123 |
< |
will logically precede the reblocking operation, regardless of the order |
124 |
< |
they are given on the command line. |
123 |
> |
will logically precede the re-ordering operation, regardless of their |
124 |
> |
position on the command line. |
125 |
|
.SH EXAMPLES |
126 |
|
To change put 8760 color triplets per row in a matrix with no header: |
127 |
|
.IP "" .2i |
143 |
|
.SH AUTHOR |
144 |
|
Greg Ward |
145 |
|
.SH NOTES |
146 |
+ |
For large transpose or re-ordering operations on Unix systems, |
147 |
+ |
it is most efficient to specify the input file on the command line, |
148 |
+ |
rather than reading from the standard input, since |
149 |
+ |
.I rcollate |
150 |
+ |
can map the file directly into virtual memory. |
151 |
+ |
.PP |
152 |
|
The |
153 |
|
.I rcollate |
154 |
|
command is rather inflexible when it comes to output field and record |
159 |
|
Output row separtors will always be an EOL, which may differ between systems. |
160 |
|
.PP |
161 |
|
If no options are given on the command line, or a binary file is specified |
162 |
< |
without a transpose, |
162 |
> |
without a transpose or re-ordering, |
163 |
|
.I rcollate |
164 |
|
issues a warning and simply copies its input to its standard output. |
165 |
|
.SH "SEE ALSO" |