1 |
.\" RCSid "$Id" |
2 |
.TH RHCOPY 1 1/15/99 RADIANCE |
3 |
.SH NAME |
4 |
rhcopy - copy ray information into a holodeck |
5 |
.SH SYNOPSIS |
6 |
.B rhcopy |
7 |
.B dest_holo |
8 |
[ |
9 |
.B \-u |
10 |
][ |
11 |
.B \-d |
12 |
] |
13 |
.B "\-h src_holo .." |
14 |
.br |
15 |
or |
16 |
.br |
17 |
.B rhcopy |
18 |
.B dest_holo |
19 |
[ |
20 |
.B \-u |
21 |
][ |
22 |
.B \-d |
23 |
] |
24 |
.B "\-p src_pic src_zbf .." |
25 |
.SH DESCRIPTION |
26 |
.I Rhcopy |
27 |
adds ray sample data to the existing holodeck |
28 |
.I dest_holo. |
29 |
In the first form, the ray samples are taken from one or more holodeck files |
30 |
given after the |
31 |
.I \-h |
32 |
option. |
33 |
In the second form, the ray samples are taken from one or more RADIANCE |
34 |
picture files and their depth buffers, which must be paired on the |
35 |
command line after the |
36 |
.I \-p |
37 |
option. |
38 |
.PP |
39 |
The |
40 |
.I \-u |
41 |
option turns on duplicate ray checking. |
42 |
In some cases, the same ray may already exist in the destination holodeck, |
43 |
and it would be redundant to add it. |
44 |
By default, |
45 |
.I rhcopy |
46 |
does not check for duplicates, because it takes extra time, and in many |
47 |
invocations is not necessary, as when copying into an empty holodeck. |
48 |
.PP |
49 |
The |
50 |
.I \-d |
51 |
option turns off depth checking. |
52 |
Normally, |
53 |
.I rhcopy |
54 |
checks the OBSTRUCTIONS variable of the destination holodeck, and if it is |
55 |
set to True, makes sure that all contributing rays start outside each |
56 |
section. |
57 |
If OBSTRUCTIONS is set to False, then |
58 |
.I rhcopy |
59 |
makes sure that any contributing rays end outside each section. |
60 |
If OBSTRUCTIONS is not set, then this option has no effect. |
61 |
(See the |
62 |
.I rholo(1) |
63 |
man page for a definition of the OBSTRUCTIONS variable.)\0 |
64 |
.PP |
65 |
.I Rcopy |
66 |
cannot be used to create a holodeck -- use |
67 |
.I rholo |
68 |
for this purpose. |
69 |
For example, to create an empty holodeck, run |
70 |
.I rholo |
71 |
without either the |
72 |
.I \-n |
73 |
or |
74 |
.I \-o |
75 |
option. |
76 |
Whatever variables are set by |
77 |
.I rholo |
78 |
when the new holodeck is created |
79 |
are the ones that will have effect when later rendering or viewing. |
80 |
Since the ray sample data may be taken from any source, |
81 |
.I rholo |
82 |
and |
83 |
.I rhcopy |
84 |
may be used together to change certain unalterable holodeck parameters, |
85 |
such as the section grid geometry. |
86 |
.SH EXAMPLE |
87 |
To take data from an existing holodeck after changing the section grid: |
88 |
.IP "" .2i |
89 |
rholo new.hdk new.hif |
90 |
.br |
91 |
rhcopy new.hdk -h old.hdk |
92 |
.PP |
93 |
To add ray samples from two pictures to the new holodeck: |
94 |
.IP "" .2i |
95 |
rhcopy new.hdk -p view1.pic view1.zbf view2.pic view2.zbf |
96 |
.SH NOTES |
97 |
.I Rhcopy |
98 |
attempts to place the beams in the holodeck in a good |
99 |
order for quick access, but if the data comes from multiple sources, |
100 |
the results may not be optimal. |
101 |
For large holodecks, it is sometimes useful to run the |
102 |
.I rhoptimize(1) |
103 |
program once all runs of |
104 |
.I rhcopy |
105 |
are through. |
106 |
.SH AUTHOR |
107 |
Greg Ward Larson |
108 |
.SH ACKNOWLEDGMENT |
109 |
This work was supported by Silicon Graphics, Inc. |
110 |
.SH "SEE ALSO" |
111 |
getinfo(1), pfilt(1), psign(1), rhinfo(1), rholo(1), rhoptimize(1), rpict(1) |