Text archives Help
- From: Jens Krüger <jens@sci.utah.edu>
- To: iv3d-users@sci.utah.edu
- Subject: [IV3D-USERS] Re: Re: Loading Label volumes
- Date: Fri, 13 May 2011 22:52:57 +0200
| Hi James,
turning of the trilinear interpolation is exactly what you want to do, Tom and just discussed this a minute ago. What we will do now is release ImageVis3D 2.0.1 today (contains a lot of bugfixes from 2.0 so you should definitely upgrade to that version) and then we will work on 2.1 and that will include a switch to turn of trilinear interpolation. We will release 2.1 very soon but even before that we will point you to a pre-release so you should be able to render your tag volumes properly early next week.
Cheers Jens Am 13.05.2011 um 22:49 schrieb James J Cook:
Sorry i forgot version, i'm using v2.0
download from website, 2 days old.
My data started as 8 bit values from
0 to 37 with 0 as background.
I tried a few things, including converting to 16bit and scaling my values
to fit between 0-32768.
This problem occured for an 8 or 16-bit
volume. Scaled and not scaled.
Can i turn off that trilinear interpolation
for rendering? That might be just what i want to do.
If i build from svn will this option
be available?
James Cook
CIVM, Duke University
Office: (919) 684-7672
Cell: (919) 768-3293
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.
