Actually, that message shows off a problem in error handling somewhere.
Something went wrong, was correctly detected and an error was set, but the
upper level didn't check it. DXBoundingBox is one of the few common calls
that happens to check the error status when it begins, so is often the
place this crops up. Fixing the error handling is usually easy in the
debugger, but thats not the point here. If I were you, the first thing I'd
do is put a Verify module above the module where the error occurs to make
sure the input is reasonable. First thing to do is determine for sure in
which module the error occurs. You can do that fairly easily by opening
the message window and, under the Commands pulldown, turn on Debug Tracing.
That'll first cause each module in the VPE to show an identifier, and then,
when you execute the program, will produce a message when each module
starts and finishes. I'd disconnect and reconnect prior to running it;
you want to make sure you are starting in a correct state. Once you have
the module where the error occurs, stick in the Verifys and see what
happens. I bet there's something wrong in the input, but I'd like the
error condition to be handled correctly.
Greg
Chris Pelkie
<[EMAIL PROTECTED]> To:
[email protected]
Sent by: cc:
[EMAIL PROTECTED] Subject: Re: [opendx-users] bug
or pb ?
son.ibm.com
09/05/2002 07:27 AM
Please respond to
opendx-users
At 09:48 AM 9/5/2002 +0200, you wrote:
>hi,
>
>i'm a bit new in dx use, but when trying to compute an isosurface on 2D
>data, it
>usually work fine but i sometime get a "Internal error : DXBoundingBox
>called with
>error code set" message and no isosurface is drawn.
>what does this mean : is my net bugged, or my data badly structured or may
>it be a bug
>in dx itself ?
>
That scary looking error usually just means no object was delivered to
Image to be rendered,
i.e., you probably chose a value for Isosurface for which no surface is
creatable.
My favorite trick is to ShowBox the original volume, then
Color(opacity=0.0) the box and
Collect it with the other objects you want to see (the isosurface). This
means there is always something
to render, but when rendered it is invisible so it doesn't get in your way.
Then if you get an empty Image and no error, you know you have a badly
chosen iso value.
Chris Pelkie
Managing Partner
Practical Video, LLC
30 West Meadow Drive, Ithaca, NY 14850
