Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

rhoptimize(1) [posix man page]

RHOPTIMIZE(1)						      General Commands Manual						     RHOPTIMIZE(1)

NAME
rhoptimize - optimize beam locations in holodeck file SYNOPSIS
rhoptimize [ -u ] src_holo [ dest_holo ] DESCRIPTION
Rhoptimize optimizes beam positions and eliminates fragment waste in the holodeck file src_holo, writing the result to dest_holo, or back into src_holo if only one argument is given. This may improve rendering speed on large holodecks, which tend to have widely dispersed beam positions that cause delays due to long file seeks. It may also reduce the size of the file, since large holodecks become fragmented as they fill up with new ray samples. (Use the rhinfo(1) program to determine holodeck file fragmentation.) The -u option adds a check to make sure that each ray sample is unique, i.e., the same sample is never given twice. This check is usually unnecessary, but may eliminate redundant samples from some holodeck files. EXAMPLE
To optimize the beam order in old.hdk and write the results to new.hdk: rhoptimize old.hdk new.hdk To optimize beam order in scene.hdk: rhoptimize scene.hdk NOTES
If rhoptimize is given only one file argument, it creates a temporary file in the same directory, and moves it onto the original file once it has successfully completed its operation. If the operation fails for some reason, the temporary file is removed and the original holodeck is left unchanged. This program generally takes several minutes to run and offers no progress reports. FILES
rho????.hdk temporary file to hold new holodeck AUTHOR
Greg Ward Larson ACKNOWLEDGMENT
This work was supported by Silicon Graphics, Inc. SEE ALSO
getinfo(1), pfilt(1), psign(1), rhcopy(1), rhinfo(1), rholo(1), rpict(1) RADIANCE
1/25/99 RHOPTIMIZE(1)

Check Out this Related Man Page

RHCOPY(1)						      General Commands Manual							 RHCOPY(1)

NAME
rhcopy - copy ray information into a holodeck SYNOPSIS
rhcopy dest_holo [ -u ][ -d ] -h src_holo .. or rhcopy dest_holo [ -u ][ -d ] -p src_pic src_zbf .. DESCRIPTION
Rhcopy adds ray sample data to the existing holodeck dest_holo. 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, rhcopy does not check for duplicates, because it takes extra time, and in many invocations is not neces- sary, as when copying into an empty holodeck. The -d option turns off depth checking. Normally, rhcopy 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 rhcopy makes sure that any contributing rays end outside each section. If OBSTRUCTIONS is not set, then this option has no effect. (See the rholo(1) man page for a definition of the OBSTRUCTIONS variable.) Rcopy cannot be used to create a holodeck -- use rholo for this purpose. For example, to create an empty holodeck, run rholo without either the -n or -o option. Whatever variables are set by rholo 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, rholo and rhcopy may be used together to change cer- tain unalterable holodeck parameters, such as the section grid geometry. EXAMPLE
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 NOTES
Rhcopy 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 rhoptimize(1) program once all runs of rhcopy are through. AUTHOR
Greg Ward Larson ACKNOWLEDGMENT
This work was supported by Silicon Graphics, Inc. SEE ALSO
getinfo(1), pfilt(1), psign(1), rhinfo(1), rholo(1), rhoptimize(1), rpict(1) RADIANCE
1/15/99 RHCOPY(1)
Man Page