Text archives Help
- From: tom fogal <tfogal@sci.utah.edu>
- To: James J Cook <james.j.cook@duke.edu>
- Cc: iv3d-users@sci.utah.edu
- Subject: [IV3D-USERS] Re: Loading Label volumes
- Date: Fri, 13 May 2011 14:55:28 -0600
James J Cook <james.j.cook@duke.edu> writes:
[snip]
>
Can i turn off that trilinear interpolation for rendering? That
>
might be just what i want to do.
Yep, the part I've snipped guarantees that this is the issue.
>
If i build from svn will this option be available?
You can't disable it (in any version) yet, but I'm working on it.
I need to release 2.0.1 first, though. Nearest neighbor (i.e.
uninterpolated) will make it into 2.1.0. I'll send you a private mail
when it's available in svn / the devbuilds.
Cheers,
-tom
>
tom fogal <tfogal@sci.utah.edu>
>
05/13/11 04:25 PM
>
>
To
>
James J Cook <james.j.cook@duke.edu>
>
cc
>
iv3d-users@sci.utah.edu
>
Subject
>
Re: [IV3D-USERS] Loading Label volumes
>
>
>
Hi,
>
>
James J Cook <james.j.cook@duke.edu> writes:
>
> I am loading a 3d analyze format image volume of labels.
>
> I have 37 descrete levels.
>
> When i load this data imagevis seems to add other levels to the
>
> dataset between my labeled regions.
>
> Is there any way to stop this?
>
>
Is this version 2.0.0 or are you building from svn by any chance?
>
This juuust just changed. Also, what type are your data (floating
>
point?)? [1]
>
>
Some things of note, regardless of version:
>
>
. if your data are > 16bit, they are quantized to 16bit
>
>
. for large data, we produce a multiresolution hierarchy via a
>
downsampling approach which includes averaging. The averaging can of
>
course 'smear' out your flags, especially if they are close together
>
>
. the (visible) histogram behind the transfer functions is computed
>
on the lowest resolution data, for performance reasons, but we're
>
still doing the correct thing with the higher resolution data,
>
despite appearances.
>
>
. We utilize trilinear interpolation during rendering. This is just
>
plain wrong for flag data...
>
>
We've heard complaints about that last one before... should really be
>
fixed. Gimme a min..
>
>
HTH,
>
>
-tom
>
>
[1] If you have no idea, you can open up ImageVis3D's debug window
>
(under "Help"), check the 'message' channel, and then try to convert
>
your dataset. There will be a message "n-bit XxYxZ data", and then the
>
message after that will describe the data type.
Archive powered by MHonArc 2.6.16.