-
Notifications
You must be signed in to change notification settings - Fork 27
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
Baysor segmentaion stain #216
Comments
Hello @lkmartin90, Baysor is not using any image for segmentation, it only uses the transcripts. Yet, Baysor can use a prior, e.g. we can run Cellpose on DAPI (or any other stain), and provide it to Baysor as a prior. Does this help? Which technology do you use? |
Ah - sorry, my misunderstanding; I read that Baysor also used the stain for segmentation and didn't realise it was in the prior! I'm using CosMx, and despite a fairly good prior segmentation, I am struggling to get the Baysor output to look nice, mainly due to overlapping cells, even when I force it to work in 2D. However, this may just be our data. |
Which Regarding the cells overlap, this happens mostly when using Baysor. I will soon improve this (once |
I'm using a prior confidence of 0.9. Thanks for the help, I'll also try ComSeg! |
Thanks for the great tool.
I have a question I can't find the answer to in the documentation. How do we know which stain Baysor is using to segment, and can we change this in the config file?
Sorry if I've missed this somewhere.
The text was updated successfully, but these errors were encountered: