-
Notifications
You must be signed in to change notification settings - Fork 7
Set ROI origin to match well origin #524
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
Conversation
Coverage reportThe coverage rate went from None of the new lines are part of the tested code. Therefore, there is no coverage data about them. |
This is mostly ready on my side, and it should streamline the understanding of ROIs from now on. I also fixed some slightly unrelated ROI issues (notably the bounding-box ROIs when running cellpose over FOVs), see full list in the first post above. @jluethi a review would be useful. I don't have a full understanding of what parts of registration tasks are tested, and then I am not sure of whether there remain open issues related to the ROI origins. Some notes:
|
Great, will review!
If all tables already come with a reset origin, then this is not necessary anymore. We only needed to run reset_origins because FOV & well ROIs had non-0 origins. |
This makes sense, thanks. I just removed it with f15863d.
|
Hmm, good question. I think the tests would catch it if it calculates the registration wrong (because I have some checks on the amount of 0-padded pixels and such). But I'll run it on example 03 as part of the review and verify the results visually as well, just to be sure :) |
The changes look good to me. Great that you updated docstrings @tcompa ! I added a few minor points to where we could clarify them further, but that's about it. I'll also run some tests on example 03, will report results :) |
In local tests, I keep running into this error (both for example 01 and example 03):
I do have Python 3.9.0 on that machine though. Given that our CI is fine, I'll have to look into updating python & retrying tomorrow |
The obvious comment is that you may be missing Other than that, we can debug it further - but I don't see any connection with the current PR. |
Ah, that was it! 🤦🏻♂️ Downside of trying to do testing on a rush. Interesting though to see that this is how the issue pops up if someone forgets to include the extras! Retrying now :) |
Thanks for the review. I fixed the minor points and I don't have anything more to add.
This would be the last check, and then I think we could merge this. |
Ok, I can now confirm that the multiplexing examples still work as expected. PR approved :) |
zenodo_zarr
fixture to "fix" current zenodo datasets, and open issue about update (ref Update new datasets to Zenodo #526)reset_origin=True
implementation inconvert_ROI_table_to_indices
#507reset_origin
should not modify its input #525prepare_FOV_ROI_table
andprepare_well_ROI_table
#527Close #339
Close #460
Close #525
Close #507
Close #527
Checklist before merging
CHANGELOG.md