-
-
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
how to speed-up registration #850
Comments
Continued. Okay, here's an easy way to start finding a set of workable parameters. Try using the script |
|
the right way to optimize is by empirical validation study. you would optimize the number of levels / iterations / smoothing per level - while keeping the CC sampling dense - then proceed with limiting the CC sampling. that being said, I don't think that random sampling in CC will speed anything up. the implementation is optimized for dense sampling and random sampling will lose that additional speedup possibly to the point of actually making it slower. anyway, I would start with something like:
note that your default parameters are already very divergent from anything we would recommend. you would want to do the same type of thing for the affine step but keep the random sampling. |
Thank you for your fast reply :) I believe that I am fine with it for now, so I will close this task... |
Also, just an FYI, there are three B-spline registration algorithms: |
Is your feature request related to a problem? Please describe.
We are registering large microscopy images using this package with the following parameters which works fine meaning the alignment is reasonably good but it takes a very long time...
Describe the solution you'd like
Could you give some recommendations on what parameters could I change to gain some speed? I was thinking about
convergence
,smoothing-sigmas
,shrink-factors
Additional context
We are using ANTsPy for registering images from ANHIR dataset of average image size 12k x 10k and the resulting alignment is quite fine, but it takes horribly long, about 2hours per image pair.
The text was updated successfully, but these errors were encountered: