-
-
Notifications
You must be signed in to change notification settings - Fork 381
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Determining optimal hyperparameter settings for abdominal CT image registration #1654
Comments
This isn't descriptive enough to diagnose the problem. For example, we would also need to understand how you're assessing "optimal registration results" and to actually see the data and results ourselves, or at least a few examples. |
Thank you very much for your response. We segmented images of multiple organs, including spleen, kidney, gallbladder, liver, pancreas, adrenal glands, blood vessels, and bones. After using specific hyperparameters for registration, the average dice coefficient of multiple organs is calculated, and the corresponding hyperparameter when reaching the maximum value is regarded as the optimal hyperparameter. I put the relevant NIfTI files of the registration results of the default hyperparameters and optimal hyperparameters on Google Drive. You can download them using the following link: In addition, I put the calculation results of these two examples in the figure below. |
I don’t have access to your data but I can provide some advice even before looking at the images. Given the large number of parameters to be optimized during image registration, it’s no surprise that individual subjects (and organs) will exhibit a wide range of values for a given evaluation metric. That’s why image registration competitions and other evaluations tend to look at a variety of evaluation metrics over several subjects. And even then, those evaluation metrics might not be sufficient to capture what is actually needed for a specific study. My advice would be to, starting with the default settings in “antsRegistrationSyN.sh” or “antsRegistrationSyNQuick.sh”, actually look at the images and determine where alignment needs systematic improvement over several images for your particular study starting with the default settings. You can then ask follow-up questions here for further guidance. This is much a more principled approach than doing a brute-force grid search where some of the parameters that you’ve included don’t make sense, from an experienced developer’s perspective. |
Thank you for your advice. I apologize for any inconvenience caused by my unfamiliarity with the sharing process. I can confirm that access has now been successfully granted. Here is the link. I appreciate your insightful advice and the inspiration you've provided. I'll take some time to carefully consider your suggestions and will provide a detailed response later. Thank you for your understanding, and I'll get back to you as soon as possible. |
Dear ANTs developers and experts,
I'm currently working on enhanced abdominal CT image registration and have found that the default parameters do not yield optimal registration results. Although the registration can be improved via key parameters tuning, the optimal configuration for specific cases varies and I found no clue to infer the optimal configuration from image pairs intuitively other than performing a grid search.
Here's the keys parameters that affect the registration:
-Registration Method: antsRegistrationSyN
-Key Parameters:
-r: radius for cross correlation metric used during SyN stage (default = 4), varied from 0 to 8 in my cases
-s: spline distance for deformable B-spline SyN transform (default = 26) , varied from 20 to 80 in my cases
If any professionals have experience in abdominal CT image registration and parameter tuning, could you offer insights or suggestions on refining the parameters? Any advice on key parameters or general strategies for improvement would be greatly appreciated.
Thank you for considering my question.
The text was updated successfully, but these errors were encountered: