Slicer 3 contains a number of different ways to register two images. In this document we will examine the results of these modules on three different cases. The convention used will be (moving image) -> (fixed image) = (resulting moved image). The cases are:
- Registering a t2 weighted image to an arbitrary t1, then registering this transformed image back to the original t2. Ideally this will produce a identical image.
- Registering a DTI baseline image to the corresponding realigned t2 weighted image, and vice-versa. This is a realistic test of one of our (the PNL) everyday uses of registration.
- Registering a realigned t2 weighted image to another t2.
All cases were completed using the nightly build of SLicer 3 provided on 3-31-09. No settings were changed, the parameters were left at Slicer3 defaults.
Talk to Andrew Rausch, email@example.com for more info. I'm no expert on registration, but I can tell you exactly how each of these were performed and provide mrmls and nrrds.
A concise comparison of FSL and slicer registrations can be found here.
The data set used for testing can be downloaded here.
- 1 There and back registration
- 2 T2 to DTI baseline registration
- 2.1 Freesurfer parcellation overlay
- 2.2 Slicer modules
- 2.3 Register Images Module
- 3 Different subject registration
- 4 Special case: Anna's data registration
There and back registration
In this case we take the 01053-t2w nrrd as our moving image and the 01031-t1 nrrd as our fixed, register them and save the result, then move that result to the fixed 01053-t2w image. Not all of these transformations are totally reversible, but for the most part if they can be registered one way, they should be able to be registered back to exactly the same spot. It never works quite perfectly though, so the errors/distortions are detailed below.
- 53-t2 -> 31-t1 = aff1
- aff1 -> 53-t2 = aff2
The image shows these side by side. The are nearly the same except for the loss of fine detail.
- 53-t2 -> 31-t1 = lin1
- lin1 -> 53-t2 = lin2
The image shows lin2 and 53-t2 side by side. The image shows there appears to be some change beyond loss of detail, possibly a L-R shift in the front.
- 53-t2 -> 31-t1 = rig1
- rig1 -> 53-t2 = rig2
Significant blurring, but every feature is in it's proper place.
- 53-t2 -> 31-t1 = Bspline1
- Bspline1 -> 53-t2 = Bspline2
Superior frontal enlargement, odd upward shifting in rear of brain, distortions everywhere.
- 53-t2 -> 31-t1 = Demons1
- Demons1 -> 52-t2 = Demons2
Multiple deformations. Much larger ventricles. Small errors everywhere, expansions, contractions, shifts. Roughly in the same place overall.
Register Images Module
- 53-t2 -> 31-t1 = init1
- init1 -> 53-t2 = init2
Significant shift in count values, rigid translation down ~4 pixels, left ~1 pixel.
- 53-t2 -> 31-t1 = rigid1
- rigid1 -> 53-t2 = rigid2
Shift in grey values. Few other problems.
- 53-t2 -> 31-t1 = affine1
- affine1 -> 53-t2 = affine2
Again, shift in grey values, mostly okay otherwise. Slight posterior shift.
- 53-t2 -> 31-t1 = Bspline1
- Bspline1 -> 53-t2 = Bspline2
Again grey values shift. Minor distortion in frontal lobe and cerebellum.
- 53-t2 -> 31-t1 = piperigid1
- piperigid1 -> 53-t2 = piperigid2
The brain appears to be shifted slightly leftward, as the contours around the edges do not perfectly match. There also is a tilt forward around the L-R axis. Grey value shift.
- 53-t2 -> 31-t1 = pipeaffine1
- pipeaffine1 -> 53-t2 = pipeaffine2
Elongation along the superior frontal to cerebellum axis. Grey value shift. Otherwise ok.
- 53-t2 -> 31-t2 = pipebspline1
- pipebspline1 -> 53-t2 = pipebspline2
There is pinching towards the corpus callosum, strange distortions near the cerebellum, many distortions around the skull, very poor overall.
T2 to DTI baseline registration
Freesurfer parcellation overlay
Only linear methods produce transforms that can be used to register a label map. Unfortunately, a linear registration can never account for the distortions of a DTI image, and as such there is no way to get a good registration of structural label maps to DTI space. In Slicer 2, I can create a transform node and do an automatic registration between two already created nrrds based on intensity via diff. demons or bspline, and then apply that transform to a label map, but I don't know of any way to get a similar transform in Slicer3.
*Note: actually need to apply a transform volume, not a transform node to make this work in slicer 2. Still don't know how to accomplish this (or get a transform node) in Slicer 3.
The overlay has only a few places where it is usable, only in the center of ROIs you'll probably be in the same region on the DTI.
The overlay is useful in roughly the middle third of the brain, distortion of DTI means linear transform cannot match in the front or back of brain.
Archana is an MIT grad student working on fMRI -> DTI registration. She used an affine transformation of some sort (I'm pretty sure it wasn't Slicer) to register a masked T2 to the masked DTI baseline, and transformed the freesurfer aseg the same way. You can see her registration has the same problems in the back of the brain, going beyond the borders of our image, but there is better registration in the front, matching up to the DTI distortion.
At first, I attempted to do whole volume registration, but it quickly became clear that masked volumes would be needed to perform even semi-accurate registrations. A few examples of non-masked registrations will be left, but all other transforms will be done with skull-striped masked volumes.
- DTI-baseline -> 53-t2 = Bspline3
Fits the cortex on the baseline to the skull on the t2. Retry with a skull stripped t2.
- DTI-baseline -> 53-t2 = Demons3
Brain tilted to appropriate angle, but DTI strecthing clear in frontal and parietal lobes. Cerebellum okay, middle quarter of rest of brain roughly matches.
Brain tilted properly, matches in pretty much the same places as a Rigid transformation. It looks even blurrier now that it has gone through two registrations.
Clearly completely unusable. Bright ventricle of structural appears to be aligned with ventricles and bright region of cerebellum.
Similar problems and matches to previous methods.
For the middle of the brain, this is acceptable, near front and rear registration can be off by whole gyri. Looking at axial view, clearly not turned the same direction as the DTI baseline.
This matches the two brain's borders very well. The structural expands to fill most of the DTI image's distortions. In the process, the gyrii in the frontal lobe are thrown all over the place, off by large margins. The middle is closer, and the rear of the brain is again poorly matched, though it has expanded to fill the DTI image distortion.
Relatively close, compared to other transformations. Minor areas of frontal lobe are mismatched, especially near the bottom, and a small section of the occipital lobe is off, but overall gyri and sulci are matched well.
Demons Registration clearly has some problems. I can't get even a viewable image to result.
Register Images Module
While the T2 has been moved, it really isn't accurate at any part. None of the image can be properly matched to the corresponding part of the DTI.
Might there be some problem with the way I'm setting this up? Image does not match. Is not rotated, is shifted to roughly the same area, unclear why it is stretched where it is.
None of these registrations seem to be getting even close to accurate results, so until I get advice on what settings to use to correct this, I'm going to hold off on further testing of this section.
Different subject registration
In this, I'll be moving images like so:
- 01053-t2 -> 01031-t2 = Result. All the images shown have the moving image on the left, the resultant image in the middle, and the target image on the right.
01053>01031rigid.png = not bad... different brains of different sizes, but seem to be aligned in the ventricles so output seems okay. output slightly blurry. bad initial leveling displays.
01053>01031linear.png = not bad... different brains of different sizes, but seem to be aligned in the ventricles so output seems okay.output slightly blurry. bad initial leveling displays.
01053>01031_affine.png = looks good in terms of size. odd warping of frontal lobe and cerebellum area, but otherwise good coregistration.
01053>01031_bspline.png = looks good in terms of size. odd warping of frontal/temporal lobe and cerebellum area, but otherwise good coregistration.
01053>01031_demons.png = 10 minutes. Window/leveling initially off. Otherwise, it looks really good. Not much distortion.
Register Images module
01053>01031_RI_initial.png - looks like the original 01053 image, but shifted, which is expected. resolultion a little worse.
01053>01031_RI_rigid.png - center ventricles are mostly aligned, but not perfectly. in axial view, brain is more crooked than in initial scan... especially in frontal lobe.
01053>01031_RI_affine.png - ventricles aligned well. sizing decent. looks how one would expect affine to look. not perfect subcortically. some distortion, esp in temporal lobe.
01053>01031_RI_bspline.png - good result. ventricles aligned well, but temporal lobe size is not the same as the target image.
01053>01031_RI_pipe_rigid.png - shifted version of the original image. decent registration in the ventricles.
01053>01031_RI_pipe_affine.png - decent coreg. a bit of distortion in the frontal and temporal lobes, esp around the corpus collosum.
01053>01031_RI_pipe_bspline.png - good coregistration, but pretty blurred. also, I would have expected the temporal lobe to be coregistered better.
Special case: Anna's data registration
At Marek's request, Doug has attempted to register the t1 structural images to the dwi-baseline images of Anna's data. Being different types of images, they do not register well. Examples follow.
Though it has been recommended to always go through a pipeline before using a non-linear registration, We've given a B-spline only registration a try. This is Slicer 3's separate Bspline module. Unsurprisingly, it works extremely poorly. The brain is barely recognizable any longer, with strange curvatures at the top, gross enlargement of the middle third (S-I) and unclear registration along the very bottom, stretching out along the entire image.
The image has been expanded radially outward, not clearly matching to any features of the DTI baseline.
Linear to Affine to Bspline
As suggested, in this test we registered the image via linear, then affine, then bspline modules in Slicer 3. Again the registration is largely incomprehensible.
Curved crazily, still doesn't appropriately fit.