i fixed up my subscription and think i'm able to post
again.  i just realized this post didn't ever appear.
it's a bit tardy, but if anyone is still interested,
here is is...   n.

-------- Original Message --------
Subject: Re: Collect & 3D set
Date: Fri, 20 Oct 2000 18:11:44 +0200
From: nancy collins <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [email protected]

here's one other idea for this situation:

     Hi, all:
     I have two questions -
     (1) Modules Collect & CollectSeries can take in a max of
     21 objects. Now, if I have over 100 slices of 2D images
     (each obtained separately as individual files), does
     that mean I cannot view all of them as a volume?
     Do I need to merge them into one single 3D file before
     - -hand?  will this get around the problem?

if the 2D images are already in .dx format, or can easily be described
in .dx format instead of the .general format, then you can make a single
.dx file which defines each image as a member of a series group.
then you import the single dx file, which will in turn recursively import
each slice and assemble the group.  the resulting object will be
ready to put into Stack() directly to go to a 3D volume.

see the manual section on the dx format.  you'd probably want to
write a small program in C or perl to make the file.  it will need to
define a regular grid of positions and connections which can be
reused for each slice, and then for the data, in the place where you
say exactly where the data for an array is located, you reference
the file where the data is, and optionally a byte offset in that file.
(if the filenames change each time, there are many magic things
that can be done with an awk or sed script to automate this...)

this won't work if you are using some of the options in the
.general format which deal with interleave, or column numbers,
or some of the other niceties that it handles.  but if it's just a
raw block of numbers, either ascii or binary, then this might be
a workable option.

it's also possible for any object in a .dx file to be a reference to
another full .dx file, so if you'd rather make each 2D slice a
stand-alone dx file, then you can make a single file which just
contains a series group object, and each member is simply a
reference to each file in turn, and optionally to a specific object
inside that file.

nancy

Reply via email to