Text archives Help
- From: Tim Holy <holy@wustl.edu>
- To: iv3d-users@sci.utah.edu
- Subject: [IV3D-USERS] Re: Re: Re: Re: NRRD import
- Date: Thu, 21 Jan 2010 13:28:11 -0600
Dear Tom,
On Thursday 21 January 2010 12:43:58 pm tom fogal wrote:
>
It should be RGBA, RGBA, RGBA, etc.
>
>
Here's a QVis format header that I use to load up an RGBA dataset into
>
ImageVis3D:
[snip]
Many thanks! The "UCHAR4" part of this header was a particularly helpful tip.
I have verified that I can load a "scalar" qvis file just fine (using UCHAR
for
the format in the header). However, if I try to load an RGBA, I get a crash
with this message on the command line:
terminate called after throwing an instance of 'std::length_error'
what(): basic_string::resize
Here is my header file:
ObjectFileName: qvistest.raw
TaggedFileName: ---
Resolution: 4 5 10
SliceThickness: 0.5 2 3
Format: UCHAR4
NbrTags: 0
ObjectType: TEXTURE_VOLUME_OBJECT
ObjectModel: RGBA
GridType: EQUIDISTANT
and note that the .raw file is of the correct size (4*5*10*4):
$ ls -l qvistest*
-rw-r--r-- 1 tim holy 194 2010-01-21 13:07 qvistest.dat
-rw-r--r-- 1 tim holy 800 2010-01-21 13:07 qvistest.raw
Like I said, if I just edit the Format tag, changing it to "UCHAR" (even if I
don't shorten the .raw file), then this works fine (though the image looks
messed up, obviously).
This is using a freshly-downloaded version of iv3d (.tar.gz format).
Any thoughts? I can send my .raw file (not attaching it because I don't know
if
you like attachments on this list, but note it's only 800 bytes). It just
contains values that are either 0 or 255.
Best,
--Tim
>
You should hopefully be able to just change the filename and use that
>
file. Place it in a .dat file so that ImageVis3D will recognize it as
>
QVis format.
>
>
-tom
>
>
> > Am 21.01.2010 um 17:40 schrieb Tim Holy:
>
> > > Hi again,
>
> > >
>
> > > In experimenting further with NRRD import, it also appears that the
>
> > > NRRD importer does not make use of the "space directions" tag.
>
> > > Consequently, the user has to manually enter the spacing along each
>
> > > coordinate axis. There are a number of other NRRD0004 features that
>
> > > could also be of potential interest.
>
> > >
>
> > > If I'm not barking up the wrong tree in terms of choosing NRRD as a
>
> > > data interchange format (i.e., with respect to my previous post re
>
> > > RGBA support), there's a chance I can help with simple
>
> > > bugfixes/extensions (obviously, in consultation with those who have
>
> > > developed iv3d in the first place!).
>
> > >
>
> > > Best,
>
> > > --Tim
>
Archive powered by MHonArc 2.6.16.