-
Notifications
You must be signed in to change notification settings - Fork 21
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
global RANSAC affine -- insufficient fixed spots found #20
Comments
I'm so sorry to answer this so late Fangming - I think maybe we talked about it over email or in a call - but in case we never covered it and also to document it at least somewhere, here is guidance to obtain more spot detections for ransac alignments: The Step (1) itself happens by calling: Each of these three functions take a few parameters. You can specify any of them when you call The best thing to change to get a lot more spots detected is the affine = feature_point_ransac_affine_align(
fix, mov, fix_spacing, mov_spacing,
blob_sizes=blob_sizes,
...
fix_spot_detection_kwargs={
'threshold':1e-3,
'threshold_rel':None,
},
mov_spot_detection_kwargs={
'threshold':1e-3,
'threshold_rel':None,
},
) will find many more spots than the default settings. Read the |
Please let me know if you're still stuck on this or any similar issue. Or if you think this explanation is sufficient to guide you (or a future user) to using the spot detection part of the ransac alignment more effectively, let me know so I can close the issue. |
Thank you @GFleishman! This explanation is super clear and I now got a much better understanding, and am able to better control these parameters. I think you can close this issue now! |
The images I am working with is a 3D sample imaged by cyto-DAPI. Individual cells were clearly visible in both moving and fixed images. We wanted to match those cells from two imaging rounds.
I have a question about the first step of the registration -- global RANSAC affine. I often get “insufficient fixed spots found”. To deal with it,
Any suggestions / directions would be appreciated.
The text was updated successfully, but these errors were encountered: