Hi!
Is it possible to control the output in the holodeck file to be able to see the
actual values? I already tried to add the following line to the .hif-file:
render= -faa, but unfortunately the output (=holodeck file) was not readable at
all. Basicly it was the same as without the mentioned line or with -fdd instead
of -faa. Maybe I am using the wrong command or just the wrong place for the
right command? Or is the holodeck file not supposed to be viewable at all?
regards,
Olga
Hi Olga,
There is no method provided for looking at the ray values in a holodeck in ASCII format, as I never found this useful even for debugging purposes. The data is organized in a very hard-to-understand way, and the individual ray values are so many that I'm not sure what you would do with them if you had them. However, there are a couple of useful utilities for holodecks that you might enjoy:
rhinfo - prints the header and grid information from a holodeck file
rhcopy - copies information from one holodeck to another, or from a picture to a holodeck
rhoptimize - optimizes beam placements in a holodeck for more efficient rendering
rhpict - reconstructs a picture from beams stored in a holodeck
What purpose did you have in mind for recovering ray values?
-Greg
From: O Graf <[email protected]>
Date: June 20, 2004 3:48:04 PM CESTHi!
Is it possible to control the output in the holodeck file to be able to see the
actual values? I already tried to add the following line to the .hif-file:
render= -faa, but unfortunately the output (=holodeck file) was not readable at
all. Basicly it was the same as without the mentioned line or with -fdd instead
of -faa. Maybe I am using the wrong command or just the wrong place for the
right command? Or is the holodeck file not supposed to be viewable at all?regards,
Olga
Thanks for your reply, Greg!
The purpose is to try to manipulate a holodeck file in terms of inserting an
artificial object (like a mirrored shpere) into a laser scan of a room. Of
course it is possible to do so in the appropriate .rad file (or in the octree),
but I was just wondering if it's also possible to do it directly by changing
the actual holodeck file. This is why I wanted to see the actual values.
-Olga
Hi Olga,
There is no method provided for looking at the ray values in a holodeck
in ASCII format, as I never found this useful even for debugging
purposes. The data is organized in a very hard-to-understand way, and
the individual ray values are so many that I'm not sure what you would
do with them if you had them. However, there are a couple of useful
utilities for holodecks that you might enjoy:rhinfo - prints the header and grid information from a holodeck file
rhcopy - copies information from one holodeck to another, or from a
picture to a holodeck
rhoptimize - optimizes beam placements in a holodeck for more efficient
rendering
rhpict - reconstructs a picture from beams stored in a holodeckWhat purpose did you have in mind for recovering ray values?
-Greg> From: O Graf <[email protected]>
> Date: June 20, 2004 3:48:04 PM CEST
>
> Hi!
>
> Is it possible to control the output in the holodeck file to be able
> to see the
> actual values? I already tried to add the following line to the
> .hif-file:
> render= -faa, but unfortunately the output (=holodeck file) was not
> readable at
> all. Basicly it was the same as without the mentioned line or with
> -fdd instead
> of -faa. Maybe I am using the wrong command or just the wrong place
> for the
> right command? Or is the holodeck file not supposed to be viewable at
> all?
>
> regards,
>
> Olga
Hi Olga,
The purpose is to try to manipulate a holodeck file in terms of inserting an
artificial object (like a mirrored shpere) into a laser scan of a room. Of
course it is possible to do so in the appropriate .rad file (or in the octree),
but I was just wondering if it's also possible to do it directly by changing
the actual holodeck file. This is why I wanted to see the actual values.
I don't recommend inserting samples into a holodeck for this purpose, but you could create one or more rpict pictures and use rhcopy to add these to the holodeck manually. Adding the object to the octree is a much more robust solution, however. If you were to insert samples using rhcopy, you could end up with some odd reconstruction errors in rholo.
-Greg