[Insight-users] using 3d registration on a 2d stack of images .

[Li, George (NIH/NCI)]

Mark,

Switching from 2d to 3d is not just setting the dimension differently. The
image reader has to read 3d data and transform has to be capable of handling
3d. That is all I can think of. I am not an expert in itk, but only have a
few experiences with it. Others might provide you more information. 

Attention should also be paid to the center of rotation, as well, making
sure it is kept the same throughout the entire 3d registration.

You should also read some of the examples in /examples/registration/ and in
/examples/IO/, as well as the chapter 8 in the itk user manual for detailed
information.

Good luck.

George



-----Original Message-----
From: Mark Wyszomierski [mailto:markww at gmail.com] 
Sent: Tuesday, March 29, 2005 5:03 PM
To: Luis Ibanez; Insight-users at itk.org
Subject: [Insight-users] using 3d registration on a 2d stack of images.


Hello all,

I have a stack of 2d slices that I have been using with 2d motion
registration. I have read it is possible to use a 3d registration method on
this stack, which may produce a better result.

All the registration examples have the image dimensions set at 2. I also
have this setup. I loop through each slice in my moving stack, load its
pixel data into a buffer, and register each buffer with the corresponding
stationary buffer from my stationary image stack.

If I were to switch this to 3d, should I simply change my dimensions to 3?
Then create a 3d array and load all my moving images into that 3d array? Do
the same for the stationary images? Then just have one registration step
where I hand the method both volumes?

After it's done, can I peel my moving slices out of the registered 3d array
and consider them done?

Any general guidelines would be great, thanks!

Mark
_______________________________________________
Insight-users mailing list
Insight-users at itk.org http://www.itk.org/mailman/listinfo/insight-users