Projects:SlicerFAQ:RegistrationRerun - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

2017-07-10T17:01:52Z

Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Meier at 20:23, 11 November 2010

2010-11-11T20:23:49Z

Meier: /* Automated Registration Result is Insufficient */

2010-11-11T20:23:23Z

Automated Registration Result is Insufficient

Meier: /* Automated Registration Result is Insufficient */

2010-11-11T20:22:55Z

Automated Registration Result is Insufficient

Meier at 20:21, 11 November 2010

2010-11-11T20:21:25Z

Meier at 20:19, 11 November 2010

2010-11-11T20:19:22Z

Meier: Created page with ''''Rerun Automated Registration''': *most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and th…'

2010-11-11T20:16:42Z

Created page with '**'''Rerun Automated Registration''': ***most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and th…'

New page

**'''Rerun Automated Registration''':
***most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and the remedy:
***too much initial misalignment: particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] or [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [http://www.slicer.org/slicerWiki/index.php/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
***insufficient detail: consider increasing the number of sample points used for the registration, depending on time/speed constraints, increase to 5-10% of image size.
***insufficient contrast: consider adjusting the ''Histogram Bins'' (where avail.) to tune the algorithm to weigh small intensity variations more or less heavily
***strong anisotropy: if one or both of the images have strong voxel anisotropy of ratios 5 or more, rotational alignment may become increasingly difficult for an automated method. Consider increasing the sample points and reducing the ''Histogram Bins''. In extreme cases you may need to switch to a manual or fiducial-based approach
***distracting image content: pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
***too many/too few DOF: the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned. Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
***inapropriate algorithm: there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration ''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.

@@ Line 5: / Line 5: @@
 *'''Explanation:''' The automated registration algorithms (except for  fiducial and surface registration) in Slicer operate on image intensity and try to move images so that similar image content is aligned. This is influenced by many factors such as image contrast, resolution, voxel anisotropy, artifacts such as motion or intensity inhomogeneity, pathology etc, the initial misalignment and the parameters selected for the registration.
 *'''Fix:'''  Your first try however should be to obtain a better automated registration by changing some of to re-run the automated registration, while changing either initial position, initialization method, parameters or the method/module used. Most helpful to determine a good secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and the remedies:
-**'''too much initial misalignment:''' particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] or [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [http://www.slicer.org/slicerWiki/index.php/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
+**'''too much initial misalignment:''' particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [https://www.slicer.org/wiki/Modules:BRAINSFit BRAINSfit] or [https://www.slicer.org/wiki/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [https://www.slicer.org/wiki/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
 **'''insufficient detail:''' consider increasing the number of sample points used for the registration, depending on time/speed constraints, increase to 5-10% of image size.
 **'''insufficient contrast:''' consider adjusting the ''Histogram Bins'' (where avail.) to tune the algorithm to weigh small intensity variations more or less heavily
 **'''strong anisotropy:''' if one or both of the images have strong voxel anisotropy of ratios 5 or more, rotational alignment may become increasingly difficult for an automated method. Consider increasing the sample points and reducing the ''Histogram Bins''.  In extreme cases you may need to switch to a manual or fiducial-based approach
-**'''distracting image content:''' pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
+**'''distracting image content:''' pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [https://www.slicer.org/wiki/Modules:BRAINSFit BRAINSFit], [https://www.slicer.org/wiki/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [https://www.slicer.org/wiki/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
-**'''too many/too few DOF''': the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
+**'''too many/too few DOF''': the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [https://www.slicer.org/wiki/Modules:BRAINSFit BRAINSfit] and [https://www.slicer.org/wiki/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [https://www.slicer.org/wiki/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
-**'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration '''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
+**'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [https://www.slicer.org/wiki/Slicer3:Registration '''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
 **you can adjust/correct an obtained registration manually, within limits, as outlined [[Projects:SlicerFAQ:RegistrationAdjust|here]].

@@ Line 12: / Line 12: @@
 **'''too many/too few DOF''': the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
 **'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration '''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
-**you can adjust/correct an obtained registration manually, within limits, as outlined [[Projects:SlicerFAQ:RegistrationAdjust here]].
+**you can adjust/correct an obtained registration manually, within limits, as outlined [[Projects:SlicerFAQ:RegistrationAdjust|here]].

@@ Line 11: / Line 11: @@
 **'''distracting image content:''' pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
 **'''too many/too few DOF''': the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
-**'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration ''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
+**'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration '''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
 **you can adjust/correct an obtained registration manually, within limits, as outlined [[Projects:SlicerFAQ:RegistrationAdjust here]].

@@ Line 4: / Line 4: @@
 *'''Problem:''' automated registration provides an alignment that is insufficient, possibly worse than the initial position
 *'''Explanation:''' The automated registration algorithms (except for  fiducial and surface registration) in Slicer operate on image intensity and try to move images so that similar image content is aligned. This is influenced by many factors such as image contrast, resolution, voxel anisotropy, artifacts such as motion or intensity inhomogeneity, pathology etc, the initial misalignment and the parameters selected for the registration.
-*'''Fix:'''  Your first try however should be to obtain a better automated registration by changing some of to re-run the automated registration, while changing either initial position, initialization method, parameters or the method/module used. Some guidelines for modification:
+*'''Fix:'''  Your first try however should be to obtain a better automated registration by changing some of to re-run the automated registration, while changing either initial position, initialization method, parameters or the method/module used. Most helpful to determine a good secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and the remedies:
-**most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and the remedy:
+**'''too much initial misalignment:''' particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] or [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [http://www.slicer.org/slicerWiki/index.php/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
-**too much initial misalignment: particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] or [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [http://www.slicer.org/slicerWiki/index.php/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
+**'''insufficient detail:''' consider increasing the number of sample points used for the registration, depending on time/speed constraints, increase to 5-10% of image size.
-**insufficient detail: consider increasing the number of sample points used for the registration, depending on time/speed constraints, increase to 5-10% of image size.
+**'''insufficient contrast:''' consider adjusting the ''Histogram Bins'' (where avail.) to tune the algorithm to weigh small intensity variations more or less heavily
-**insufficient contrast: consider adjusting the ''Histogram Bins'' (where avail.) to tune the algorithm to weigh small intensity variations more or less heavily
+**'''strong anisotropy:''' if one or both of the images have strong voxel anisotropy of ratios 5 or more, rotational alignment may become increasingly difficult for an automated method. Consider increasing the sample points and reducing the ''Histogram Bins''.  In extreme cases you may need to switch to a manual or fiducial-based approach
-**strong anisotropy: if one or both of the images have strong voxel anisotropy of ratios 5 or more, rotational alignment may become increasingly difficult for an automated method. Consider increasing the sample points and reducing the ''Histogram Bins''.  In extreme cases you may need to switch to a manual or fiducial-based approach
+**'''distracting image content:''' pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
-**distracting image content: pathology, strong edges, clipped FOV with image content at the border of the image can easily dominate the cost function driving the registration algorithm. '''Masking''' is a powerful remedy for this problem: create a mask (binary labelmap/segmentation) that excludes the distracting parts and includes only those areas of the image where matching content exists. This requires one of the modules that supports masking input, such as: [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSFit], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 ExpertAutomated], [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Multi Resolution]. Next best thing to use with modules that do not support masking is to mask the image manually and create a temporary masked image where the excluded content is set to 0 intensity; the ''Mask Volume'' module performs this task
+**'''too many/too few DOF''': the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
-**too many/too few DOF: the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
+**'''inappropriate algorithm:''' there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration ''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.
 **you can adjust/correct an obtained registration manually, within limits, as outlined [[Projects:SlicerFAQ:RegistrationAdjust here]].

@@ Line 1: / Line 1: @@
-**'''Rerun Automated Registration''':
+*[[Projects:SlicerFAQ|back to Slicer FAQ]]
 ***most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and the remedy:
 ***too much initial misalignment: particularly rotation can be difficult for automated registration to capture. If the two images have strong rotational misalignment, consider A) one of the initialization options (e.g. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] or [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated]), B) a manual initial alignment using the [http://www.slicer.org/slicerWiki/index.php/Modules:Transforms-Documentation-3.6 Transforms module] and then use this as initialization input
@@ Line 8: / Line 13: @@
 ***too many/too few DOF: the degrees of freedom (DOF) determine how much motion is allowed for the image to be registered. Too few DOF results in suboptimal alignment; too many DOF can result in overfitting or the algorithm getting stuck in local extrema, or a bad fit with some local detail matched but the rest misaligned.  Consider a stepwise approach where the DOF are gradually increased. [http://www.slicer.org/slicerWiki/index.php/Modules:BRAINSFit BRAINSfit] and [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImages-Documentation-3.6 Expert Automated] provide such pipelines; or you can nest the transforms manually. A multi-resolution approach can also greatly benefit difficult registration challenges: this scheme runs multiple registrations at increasing amounts of image detail. The [http://www.slicer.org/slicerWiki/index.php/Modules:RegisterImagesMultiRes-Documentation-3.6 Robust Multiresolution module] performs this task.
 ***inapropriate algorithm: there are many different registration methods available in Slicer. Have a look at the [http://www.slicer.org/slicerWiki/index.php/Slicer3:Registration ''Registration Method Overview'''] and consider one of the alternatives. Also review the [http://na-mic.org/Wiki/index.php/Projects:RegistrationDocumentation:RegLibTable '''sortable table''' in the Registration Case Library] to see which methods were successfully used on cases matching your own.

Projects:SlicerFAQ:RegistrationRerun - Revision history

Grundlett: Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/"

Meier at 20:23, 11 November 2010

Meier: /* Automated Registration Result is Insufficient */

Meier: /* Automated Registration Result is Insufficient */

Meier at 20:21, 11 November 2010

Meier at 20:19, 11 November 2010

Meier: Created page with '**'''Rerun Automated Registration''': ***most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and th…'

Meier: Created page with ''''Rerun Automated Registration''': *most helpful to determine the secondary approach is to know why the first one was likely to fail. Below a list of possible reasons and th…'