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

How to call SNV from scRNA-seq data using GATK #4

Open
kangjiajinlong opened this issue May 18, 2023 · 0 comments
Open

How to call SNV from scRNA-seq data using GATK #4

kangjiajinlong opened this issue May 18, 2023 · 0 comments

Comments

@kangjiajinlong
Copy link

kangjiajinlong commented May 18, 2023

Hi CAISC team,

CAISC requires SNV profiles of scRNA-seq data as input. As far as I know GATK is designed for bulk RNA-seq samples and I assume there has to be some adaptions for GATK to be used for scRNA-seq data. However, after reading through this github repository and the CAISC paper, I did not find a specific instruction on how we should call SNV from scRNA-seq data using GATK.

My current understanding is that we treat each single cell as a sample and jointly call SNVs using the GATK joint variant calling pipeline (https://gatk.broadinstitute.org/hc/en-us/articles/360035890411-Calling-variants-on-cohorts-of-samples-using-the-HaplotypeCaller-in-GVCF-mode). I assume the process should to similar as follows: we first obtain fastq files for each single cell and convert them into unmapped bam files. We run GATK RNA-seq variant calling pipeline on each cell individually in GVCF mode, generating one vcf file per cell. Then we combine all these vcf files into one using the CombineGVCFs tool. Finally, we use the VariantFiltration tool to generate one filtered vcf containing SNV information across all cells. This filtered vcf can be then used as input for CAISC.

Is what I described above the correct approach for generating the SNV input?

Thanks,
Jack

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

1 participant