[Insight-users] B-Splines registration with fixed points

[M.Staring at lumc.nl]

Hi Albert,

If you have the coordinates of the sternum in both fixed and moving image you can add a term to the registration framework that penalizes deviation away from alignment of that point (or multiple points). We have done something similar:

http://elastix.isi.uu.nl/marius/publications/2011_c_MICCAIb.html

code of which can be found in elastix, which you can use freely.

But it all depends on whether you have corresponding pointsets.

Marius

From: insight-users-bounces at itk.org [mailto:insight-users-bounces at itk.org] On Behalf Of Albert Gubern Mérida
Sent: maandag 25 juli 2011 15:41
To: insight-users at itk.org
Subject: [Insight-users] B-Splines registration with fixed points

Hi all,

I am currently working in Breast MRI registration between different patients, especially interested in the alignment of body area (thorax + pectoral muscles). The first step of my registration consist of a translation to align the sternum, which gives a good initial alignment of the pectoral muscles. In the following link you can see an example of one slice with the sternum indicated with a white cross: http://imageshack.us/photo/my-images/220/breastmristernum.png/. After the translation step with the pectorals already "rigidly" aligned I apply non-rigid b-splines registration to the whole volumes. It works well in some cases, but in others, especially of course when the differences are high between fixed and moving images, the non-rigid registration move the sternum point and the pectorals are not aligned anymore.

I have thought that not allowing the non-registration the move of the sternum point and the ones close to it could be a good solution for such problem. However, I have taken a look to the classes and the mailing list but I have not found any direct/easy example to how to do that.

Could anyone give me some advice? Does a easy way to do it exist or I should modify the classes involved in the registration framework? Which ones should I take a look?

Thanks in advance,

Albert
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/pipermail/insight-users/attachments/20110725/21979622/attachment.htm>