Nuclei mask slightly overlap, causing btrack to assign them the same ID #322
Replies: 5 comments
-
Hi @HaoranYueRyan - this looks like an issue with your segmentation. https://scikit-image.org/docs/stable/auto_examples/segmentation/plot_watershed.html |
Beta Was this translation helpful? Give feedback.
-
Hi @quantumjot I utilized Cellpose for the segmentation, which generall produces separeated masks for individual nuclei. However, as shown in the images below, there are still a few cases where slight overlaps occur between nuclei in the original images, leading to connect regions in the segmenated mask Considering that the overlap in the segmented masks is relatively minor, would it's still necessary to apply watershed segmentation, or are there any btrack parameters adjustments that can handle such slight overlaps ? Additionally, would you recommend providing btrack with the original multi-colored segmented masks (labeled mask) from Cellpose instead of the binary masks to improve tracking? I would greatly appreciate any guidance you can offer on managing these minor overlaps and attaining more accurate tracking results with btrack. Thank you! |
Beta Was this translation helpful? Give feedback.
-
Ah -- OK! That clarifies things a lot, thanks. You should just be able to pass the cellpose output (labeled mask; with the unique labels) directly to btrack. |
Beta Was this translation helpful? Give feedback.
-
Hi @quantumjot Thank you for providing the guidance on this issue. Your method was indeed helpful! |
Beta Was this translation helpful? Give feedback.
-
Great! I will convert this issue to a discussion so that others can see the solution, even if the issue gets closed. |
Beta Was this translation helpful? Give feedback.
-
Hi author,
Thank you for providing the amazing tracking algorithms. I was trying to run btrack with my image data (1080, 1024, 1024) and encountered an issue where cells slightly overlap, causing btrack to assign them the same ID. Subsequently, when cells move to different areas, their IDs change to different ones.
For example, ID 1 overlaps with ID 7, they are assigned the same ID, and then ID 1 becomes ID 126.
To address this issue, I tried adjusting the maximum search radius from 50 to 25 and 16, and also used more features in the feature list:
tracker.features=["area", "perimeter", "solidity", "major_axis_length", "minor_axis_length", "orientation", 'intensity_max', 'intensity_mean', 'intensity_min']
Additionally, I doubled the values of lambda_dist, lambda_time, theta_dist, and theta_time in the hypothesis parameters.
If you have any suggestions on how to resolve this error, please let me know.
Beta Was this translation helpful? Give feedback.
All reactions