However, I noticed that some Slicer RegistrationQA tutorial data is corrupted. I am not sure if this issue comes from my OS(mac os 12.2.1) or the uploaded data is actually corrupted. (i.e., I cannot load image2). Could someone confirm that?
All the data sets load fine for me. Make sure you drag-and-drop the individual files and not the folder (if you load a folder then I think the file will attempted to be loaded as an image sequence).
@lassoan Thank you for your speedy response, I really appreciate it. It works like a charm.
I have a few follow-up questions that I’m not totally clear about.
I am not entirely sure what units of those measures/metrics. I wonder if there is a way to report the fiducial pair distance in physical units such as mm?
in the case where I use fiducial registration wizard to generate a transformation.
how do I save the given transformation into a vector field, specifically what should I pick as the reference volume.
in the case where I use fiducial registration wizard and it gives an RMS error. What should I do to find the TRE in the physical unit given the RMS error is unitless
Thank you so much for reading all those questions and your help.
All lengths and distances are reported in world coordinate system unit, which is millimeter by default.
You can choose any volume as reference volume. You can make the region smaller, larger, or make the resolution finer or coarser by using Crop volume module.
Both TRE (target regitration error) and RMS (root mean square) are in millimeters. RMS just specifies how a single error value is computed from multiple samples, and so RMS can be used to characterize TRE. However, to compute TRE you need to know the ground truth target locations, which in practice is usually unavailable. So the RMS value that a landmark registration algorithm can give you is the FRE (fiducial registration error).
@lassoan Thanks once again for your speedy and in-depth answers. I truly appreciate that. If I recall correctly from one of the slicer tutorials, the RMS error could be used to quantify TRE, but RMS is a mixture of unknown precision and accuracy.
The issue I’m trying into when saving transformation and visualizing is that the visualized transformation doesn’t seem to be on the correct plane.
I also wonder, in the case where landmarks registration is used, what is the preferred approach for quantifying the accuracy? i.e step (1) visual confirmation of overlays step(2) calculation of the RMS ?
If the transform contains a large rigid translation&rotation component then the visualization using a grid is not that helpful. For fiducial registration result visualization it may be more informative if you use Glyph visualization mode and in Advanced → Source Points you select the point list that the transform should move to the correct position (but don’t apply the transform to the point list; if you want to visualize the transformed positions as well then clone the point list and apply the transform to the clone).
@lassoan Thank you so much for your advice again. However, I still have trouble with visualizing the transformation shown here
Here is what I did,
step 1: clone From points
step 2: generate a transform from Fiducial registration wizard