-
Notifications
You must be signed in to change notification settings - Fork 7
Remove Cellpose ROI overlap check #889
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
@tcompa 2 brief CI questions:
|
This is the issue which hit us during the ngio-task PR: coverage is counting a bunch of internal modules, see https://htmlpreview.github.io/?https://github.com/fractal-analytics-platform/fractal-tasks-core/blob/python-coverage-comment-action-data/htmlcov/index.html: It's the same as #881. I'll have to debug it again, cause the first round was not successful. |
This reverts commit 084e47c.
It is used in https://github.com/fmi-basel/gliberal-scMultipleX/blob/1413c909588508d0a2d9bf3d423a5e4d3c3cb8f2/src/scmultiplex/fractal/surface_mesh_multiscale.py#L27, thus we cannot remove it. I can quickly add a test, if it's useful. |
This obviously change if we plan to also propose a PR that removes that feature from scmultiplex (and if we think nobody else is using it). |
Hmm, multiple tasks use Cellpose as a template. Besides scmultiplex, it's also the private rdcnet task that is also using this function. I think we should not remove the function before the fractal-tasks-core 2.0 update, as it would break multiple other packages. But we should stop using it ourselves in the cellpose task. |
If we have a good setup to add a basic test, nothing against that. But given that we may deprecate it anyway later, let's not spend too much time on that |
The test is now in-place. The coverage message is obviously wrong, but this is due to my other activities (outside this PR). In principle you can already merge this PR, since I only added a (passing) test to the previous PR state. I'm still working on fixing the coverage issue, but that's unrelated. |
Thanks a lot @tcompa ! |
Closes #779
I decided against a detailed further review of this performance. Given that it is often a bottleneck in performance and its only value is a warning, I suggest we remove the check completely. We can reintroduce more relevant checks later if needed.
Checklist before merging
CHANGELOG.md