| 1 |
< |
.\" RCSid "$Id" |
| 1 |
> |
.\" RCSid "$Id$" |
| 2 |
|
.TH RHCOPY 1 1/15/99 RADIANCE |
| 3 |
|
.SH NAME |
| 4 |
< |
rhcopy - copy ray information into a holodeck |
| 4 |
> |
rhcopy - copy ray information to/from a holodeck |
| 5 |
|
.SH SYNOPSIS |
| 6 |
|
.B rhcopy |
| 7 |
|
.B dest_holo |
| 21 |
|
][ |
| 22 |
|
.B \-d |
| 23 |
|
] |
| 24 |
< |
.B "\-p src_pic src_zbf .." |
| 24 |
> |
.B "\-p src_hdr src_dpt .." |
| 25 |
> |
.br |
| 26 |
> |
or |
| 27 |
> |
.br |
| 28 |
> |
.B rhcopy |
| 29 |
> |
.B dest_holo |
| 30 |
> |
[ |
| 31 |
> |
.B \-f{a|f|d} |
| 32 |
> |
][ |
| 33 |
> |
.B \-u |
| 34 |
> |
][ |
| 35 |
> |
.B \-d |
| 36 |
> |
] |
| 37 |
> |
.B "\-i[odplLv] |
| 38 |
> |
.br |
| 39 |
> |
or |
| 40 |
> |
.br |
| 41 |
> |
.B rhcopy |
| 42 |
> |
.B src_holo |
| 43 |
> |
[ |
| 44 |
> |
.B \-f{a|f|d} |
| 45 |
> |
] |
| 46 |
> |
.B "\-o[odplLv] |
| 47 |
|
.SH DESCRIPTION |
| 48 |
|
.I Rhcopy |
| 49 |
< |
adds ray sample data to the existing holodeck |
| 28 |
< |
.I dest_holo. |
| 49 |
> |
typically adds ray sample data to an existing holodeck. |
| 50 |
|
In the first form, the ray samples are taken from one or more holodeck files |
| 51 |
|
given after the |
| 52 |
|
.I \-h |
| 53 |
|
option. |
| 54 |
|
In the second form, the ray samples are taken from one or more RADIANCE |
| 55 |
< |
picture files and their depth buffers, which must be paired on the |
| 56 |
< |
command line after the |
| 55 |
> |
picture files and their corresponding |
| 56 |
> |
depth buffers, which must be paired on the command line after the |
| 57 |
|
.I \-p |
| 58 |
|
option. |
| 59 |
+ |
In the third form, ray samples are read from the standard input |
| 60 |
+ |
based on parameters specified by the |
| 61 |
+ |
.I \-i |
| 62 |
+ |
option, which should match (for example) the corresponding |
| 63 |
+ |
.I \-o |
| 64 |
+ |
option of an |
| 65 |
+ |
.I rtrace(1) |
| 66 |
+ |
command. |
| 67 |
+ |
Note that a header is not expected on input, and some parameters |
| 68 |
+ |
are required for correct operation. |
| 69 |
+ |
A |
| 70 |
+ |
.I \-f |
| 71 |
+ |
option may be used to specify raw rather than ASCII data. |
| 72 |
|
.PP |
| 73 |
+ |
The final form reads rays from the given holodeck and writes |
| 74 |
+ |
them to the standard output according to the |
| 75 |
+ |
.I \-o |
| 76 |
+ |
specification. |
| 77 |
+ |
.PP |
| 78 |
|
The |
| 79 |
|
.I \-u |
| 80 |
|
option turns on duplicate ray checking. |
| 115 |
|
Whatever variables are set by |
| 116 |
|
.I rholo |
| 117 |
|
when the new holodeck is created |
| 118 |
< |
are the ones that will have effect when later rendering or viewing. |
| 118 |
> |
are the ones that will affect later rendering or viewing. |
| 119 |
|
Since the ray sample data may be taken from any source, |
| 120 |
|
.I rholo |
| 121 |
|
and |
| 127 |
|
.IP "" .2i |
| 128 |
|
rholo new.hdk new.hif |
| 129 |
|
.br |
| 130 |
< |
rhcopy new.hdk -h old.hdk |
| 130 |
> |
rhcopy new.hdk \-h old.hdk |
| 131 |
|
.PP |
| 132 |
+ |
A much less efficient way to copy the same data: |
| 133 |
+ |
.IP "" .2i |
| 134 |
+ |
rhcopy old.hdk -oodlv | rhcopy new.hdk -iodlv |
| 135 |
+ |
.PP |
| 136 |
|
To add ray samples from two pictures to the new holodeck: |
| 137 |
|
.IP "" .2i |
| 138 |
< |
rhcopy new.hdk -p view1.pic view1.zbf view2.pic view2.zbf |
| 138 |
> |
rhcopy new.hdk \-p view1.hdr view1.zbf view2.hdr view2.zbf |
| 139 |
|
.SH NOTES |
| 140 |
|
.I Rhcopy |
| 141 |
|
attempts to place the beams in the holodeck in a good |
| 147 |
|
.I rhcopy |
| 148 |
|
are through. |
| 149 |
|
.SH AUTHOR |
| 150 |
< |
Greg Ward Larson |
| 150 |
> |
Greg Ward |
| 151 |
|
.SH ACKNOWLEDGMENT |
| 152 |
|
This work was supported by Silicon Graphics, Inc. |
| 153 |
|
.SH "SEE ALSO" |
| 154 |
< |
getinfo(1), pfilt(1), psign(1), rhinfo(1), rholo(1), rhoptimize(1), rpict(1) |
| 154 |
> |
getinfo(1), pfilt(1), rcode_depth(1), rcontrib(1), |
| 155 |
> |
rhinfo(1), rholo(1), rhoptimize(1), rpict(1), rtrace(1), |
