Robert Grzeszczuk (rg)
Wed, 30 Jun 1999 11:03:13 -0700 (PDT)
What are the eaxact arguments you are specifying for voglRaw? Are they
sometging like:
voglRaw 0 68 68 68 ubyte IronProt1.ima IronProt2 ... IronProt67.ima
Keep in mind that you cannot simply say:
voglRaw 0 68 68 68 ubyte IronProt*
as the shell-expanded list will not be sorted (IronProt15.ima proceeds
IronProt2.ima in lexicographic order). Other than renaming your files you may
want to create an explicit list of files (by hand editing the list generated
with 'ls -0' or with some crafty sed script) and try:
voglRaw 0 68 68 68 ubyte `cat list`
If you do use shell wildcarts, are you sure that they do expand to the correct
number of files? What is the result of 'ls IronProt* | wc'
Finally, keep in mind that Volumizer does not try to adress the very complex
problem of dealing with any file format out there, but merely provides examples
on how to write your own readers. Simply provide a routine myReadBrickRaw()
that will decode your proprietary format and read a subvolume starting at
(x,y,z) with dimensions of (sizeX,sizeY,sizeZ).
Hope that helps.
-rg
On Jun 30, 10:11am, Kimberly Nucifora wrote:
> Subject: dataset formats
> I'm looking for some information regarding image file formats. It appears
> that Volumizer only comes with code to read two formats: Tiff files and
> "Raw" or sliced datafiles. I've run VoglRaw from the demos program which
> reads in data slices using the lung data which came with Volumizer.
> However, when I try to reference my own dataset, the program fails. The
> files are named ironProt0.ima, ironProt1.ima...ironProt67.ima, similar to
> the naming convention of the lung data. When I run the program, I get the
> error
>
> "Error: the length of the file list does not match zVolumeSize"
>
> I've stated the size of the dataset as being 68 68 68 and set the path
> variable to the folder containing the data files. The preceding code to
> this error statement is
> if (argc - 6 != zVolumeSize) so it seems that the program is expecting
> an input argument for each file. To run the demo, I was able to set the
> DATAPATH and type $DATAPATH/lung*ima for the filesnames. Is there a reason
> why this wouldn't work with my files?
>
> I've also been trying to track down a spec for a 3D Tiff, unsuccessfully.
> Is this format described in any Volumizer documentation? I've read the spec
> for Tiff V.6 but haven't found any references to 3D.
>
> I can either convert my data to Raw 2D files or to 3D Tiffs (if I can find
> out what the format is) but if there are any other readers that have been
> written for structured datasets, I'd love to get my hands on them.
>
> Thanks!
>
> Kim Nucifora
>
>
>-- End of excerpt from Kimberly Nucifora
This archive was generated by hypermail 2.0b2 on Mon Nov 01 1999 - 14:02:51 PST