Skip to content
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

Coupling CellBender w/ other preprocessing tools--doublet detection, demultiplexing #381

Open
lhoranportelance opened this issue Sep 3, 2024 · 1 comment

Comments

@lhoranportelance
Copy link

Hello! Thank you for creating this great tool. I have gotten CellBender to run successfully on my data. Now, I'm wondering what your recommended pipeline would look like for integrating the outputs with those from other preprocessing softwares. Basically, I'm not sure what is your recommended order of operations. I am running Demuxafy with several doublet detection and demultiplexing tools and CellBender. There are several options I see as being possible to integrate these--which (if any) would you recommend?

  1. Run Demuxafy on filtered CellRanger output, get doublet barcodes. Run CellBender on raw CellRanger output, get the adjusted counts matrix, and filter down to only non-doublet barcodes identified by Demuxafy. (this is what I am leaning towards)
  2. Run CellBender on raw CellRanger output, then use the filtered CellBender .h5 as an input to Demuxafy for doublet detection and demultiplexing. (my worry with this approach is that 1) certain softwares may not accept the CellBender .h5 given the changes with v0.3, and 2) that using the adjusted counts matrix may mess with demultiplexing and doublet detection).

If there's an approach you already use, please let me know--otherwise, any advice is welcome!

@onurcanbektas
Copy link

onurcanbektas commented Sep 15, 2024

I'm also curious about this, but intuitively, I would expect running Demuxafy on the cellbender's output would make more sense. Afterall a droplet can be classified as doublet if a) it has a lot of background (false-positive) b) it is a true doublet. By running Demuxafy on the backround-removed data would give more statistical power, I think.

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

No branches or pull requests

2 participants