8000 Update motile_toolbox version to v0.4.0 by cmalinmayor · Pull Request #117 · funkelab/motile_tracker · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Update motile_toolbox version to v0.4.0 #117

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

Merged
merged 10 commits into from
Jan 2, 2025
Merged

Update motile_toolbox version to v0.4.0 #117

merged 10 commits into from
Jan 2, 2025

Conversation

cmalinmayor
Copy link
Collaborator
@cmalinmayor cmalinmayor commented Dec 19, 2024

This is a minimal working update for our new toolbox version (no hypothesis dimension, unique segmentation IDs and int node ids). I did not actually update the visualization code to use the unique seg ids - it still relabels the segmentation before viewing. All the backend tests pass (in fact, most of the code changes were updating the tests to use the new integer node ids). I tested the UI components, but only a little.

I still want to implement a function that will check if the input labels layer has repeat IDs across time and relabels them (with the already implemented function in the toolbox), to make sure we can still input e.g. cellpose labels that have been predicted independently for each time point.

Edit: I added the function, and a function that will check if there are duplicate labels across time. Right now that lives in the RunEditor and just compares the labels of the first two frames of the segmentation, to avoid looping over the whole time series.

@cmalinmayor cmalinmayor marked this pull request as ready for review December 19, 2024 22:17
Copy link
Collaborator
@AnniekStok AnniekStok left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It worked well on my computer! If the same label value was used at different time points, IDs were still assigned correctly (whereas it failed when I disabled the _has_duplicate_ids check). I quickly tried assigning the node id as label values and it looked as expected, so we can just make a colormap that maps the id to a track (or optionally, lineage) specific color.

@cmalinmayor cmalinmayor merged commit a040068 into main Jan 2, 2025
4 checks passed
@cmalinmayor cmalinmayor deleted the toolbox_update branch January 2, 2025 17:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0