-
Notifications
You must be signed in to change notification settings - Fork 1
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
Identify a threshold without reprocessing all data? #4
Comments
Hello @liz-is , Thanks for your question. For now BgeeCall has only been used to generate present/absent expression calls for bulk RNASeq and full length single-cell RNASeq. We are currently investigating the best approach to make it compatible to target base single-cell RNASeq. For now in BgeeCall we are using Kallisto for both mapping and quantification steps. The use case you are talking about (bam file + seurat object) is one of the approach we investigate but is not compatible with Kallisto. In this scenario you already have the mapping. So we need to use a different tool taking into consideration the mapping and the barcodes for the quantification step. Please let us know if you have name of other tools in mind. |
Hello,
I think the BgeeCall approach to using intergenic regions to select a reasonable threshold to call a gene "expressed" is an excellent idea, and I'm keen to try it out. However it's not clear to me from the README/vignette whether I can run this approach using BgeeCall without re-analysing all my data from fastq files.
I have human scRNA-seq data (10x), as a Seurat object. I also have .bam files with alignments to the genome, which should enable extraction of expression for the human reference intergenic regions. Is it possible to use this processed data as input into your workflow?
This seems like it would be a pretty common use case, so it would be really helpful if you could add some guidance to the vignette/README about how to use your approach on already-processed data.
Thanks in advance for your help!
The text was updated successfully, but these errors were encountered: