RHCOPY(1)                                                            RHCOPY(1)



NNAAMMEE
       rhcopy - copy ray information into a holodeck

SSYYNNOOPPSSIISS
       rrhhccooppyy ddeesstt__hhoolloo [ --uu ][ --dd ] --hh ssrrcc__hhoolloo ....
       or
       rrhhccooppyy ddeesstt__hhoolloo [ --uu ][ --dd ] --pp ssrrcc__ppiicc ssrrcc__zzbbff ....

DDEESSCCRRIIPPTTIIOONN
       _R_h_c_o_p_y adds ray sample data to the existing holodeck _d_e_s_t___h_o_l_o_.  In the
       first form, the ray samples are taken from one or more  holodeck  files
       given  after  the  _-_h  option.  In the second form, the ray samples are
       taken from one or more RADIANCE picture files and their depth  buffers,
       which must be paired on the command line after the _-_p option.

       The _-_u option turns on duplicate ray checking.  In some cases, the same
       ray may already exist in the destination  holodeck,  and  it  would  be
       redundant to add it.  By default, _r_h_c_o_p_y does not check for duplicates,
       because it takes extra time, and in many invocations is not  necessary,
       as when copying into an empty holodeck.

       The  _-_d  option  turns off depth checking.  Normally, _r_h_c_o_p_y checks the
       OBSTRUCTIONS variable of the destination holodeck, and if it is set  to
       True, makes sure that all contributing rays start outside each section.
       If OBSTRUCTIONS is set to False, then _r_h_c_o_p_y makes sure that  any  con-
       tributing  rays  end outside each section.  If OBSTRUCTIONS is not set,
       then this option has no effect.  (See the _r_h_o_l_o_(_1_) man page for a defi-
       nition of the OBSTRUCTIONS variable.)

       _R_c_o_p_y  cannot  be  used to create a holodeck -- use _r_h_o_l_o for this pur-
       pose.  For example, to create an  empty  holodeck,  run  _r_h_o_l_o  without
       either  the  _-_n or _-_o option.  Whatever variables are set by _r_h_o_l_o when
       the new holodeck is created are the ones that  will  have  effect  when
       later  rendering  or  viewing.   Since the ray sample data may be taken
       from any source, _r_h_o_l_o and _r_h_c_o_p_y may be used together to  change  cer-
       tain  unalterable  holodeck parameters, such as the section grid geome-
       try.

EEXXAAMMPPLLEE
       To take data from an existing holodeck after changing the section grid:

         rholo new.hdk new.hif
         rhcopy new.hdk -h old.hdk

       To add ray samples from two pictures to the new holodeck:

         rhcopy new.hdk -p view1.hdr view1.zbf view2.hdr view2.zbf

NNOOTTEESS
       _R_h_c_o_p_y  attempts to place the beams in the holodeck in a good order for
       quick access, but if the data comes from multiple sources, the  results
       may not be optimal.  For large holodecks, it is sometimes useful to run
       the _r_h_o_p_t_i_m_i_z_e_(_1_) program once all runs of _r_h_c_o_p_y are through.

AAUUTTHHOORR
       Greg Ward Larson

AACCKKNNOOWWLLEEDDGGMMEENNTT
       This work was supported by Silicon Graphics, Inc.

SSEEEE AALLSSOO
       getinfo(1), pfilt(1),  psign(1),  rhinfo(1),  rholo(1),  rhoptimize(1),
       rpict(1)



RADIANCE                            1/15/99                          RHCOPY(1)
