I have two volumes. One is axial (fixed), the other one is sagittal(moving). I am wondering the behavior of ‘General Registration’, if I give these two volumes as they are.
Does General Registration (BRAINS) extract axial orientation from sagittal and register it into the original axial?
Or, does it perform registration as they are given.
Volumes are registered to each other based on the image content, regardless of how the slices are oriented.
“General registration (BAINS)” module usually requires some parameter tuning. I would recommend “General registration (Elastix)” module instead, which usually works well with the default parameter set. It is available in SlicerElastix extension.
Thank you so much!
We will be working on that.
**Description: itk::ERROR: RandomCoordinateSampler(000000000303E580): ERROR: in your parameter file you selected**
**SampleRegionSize[ 2 ] = 50 mm,**
**while the fixed image size at dim = 2 is 10 voxels or 10 mm.**
**Please select a smaller SampleRegionSize!**
**It is recommended to be not larger than 1/3 of the image size in mm.**
It is a registration problem using Elastix, Monomodel MRI. Error message is copied above in bold.
Where can I modify SampleRegionSize to tackle this error? Well, more significantly can any of us share a manual link that reviews parameter adjusting for registration?
I would recommend to use “generic (all)” or “generic rigid (all)” preset for all kind of registration. These worked well for me for any registration problems.
If you choose any other preset then you may need to tune those.
Thank you Andras. We are working on that.
I recall my question that solicits what to do if we have two stacks that are orthogonal to each other. As Andras mentioned, Slicer does not predict their geometric relation(here orthogonality) and takes them as input as they are. I would like to emphasize that orthogonal slices are severely varied from each other. If one does not know they are two different orientations of same anatomy in advance, he/she will term sagittal ‘camel’ and the other ‘thorn’. Therefore, this is a challenging registration problem.
Essentially I wish to know what I should theoretically do. I afraid this forum may not be the place to ask this question. But if any suggests a work done before in line with my question, I will be glad.
Andras, we are exploring Slicer. Again many thanks for your replies!
Note: [(1) Extracting the fixed orientation from the moving orientation, (2) let us name it ‘pseudo fixed’, **(3) and perform registration with the fixed and the pseudo fixed ] ** comes to my mind, but not sure whether it is a null cheating.
Slice orientation is irrelevant. The registration algorithm does not care how the voxels are organized in memory. However, it helps the image registration algorithm if the content of the images are already somewhat aligned when you start the registration process. Initial translation can be often computed automatically (for example aligning center of gravity). However, for a successful registration, initial orientation difference of image content (again, slice orientation does not matter) often needs to be under a few ten degrees.