-
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
No genotype information after variant calling using both single and multiple bam files. #10
Comments
The genotype information was obtained from the reference vcf file (the one we are comparing the scAllele output to) which is the GIAB HG001 vcf. |
Can I use the GIAB HG001 vcf file for my analysis? If yes, please share the location of the vcf file. |
Hi Giovanni, |
scAllele takes a very conservative approach of not genotyping because allele-specific expression/bias can occur in the RNA-seq data resulting in wrong genotype calls. Currently, genotyping is out of the scope of scAllele but, since the allelic read counts and ratio values are given in the file, you could estimate the 'observed' genotypes. |
Thanks for the swift reply, @giovanniquinones. |
Hello, I used the following command for variant calling: Below, I have attached the output vcf for your reference. Could you able to help me in this. Thanks. |
I met the same mistake, wondering how to sovle it |
Dear Giovanni,
Thank you for your nice software. I am using scAllele for the detection and analysis of variants using scRNA-seq. I wonder how you get the information about 0/1 or 1/1 in Figure 2E of your paper. I checked your deposited results in Zenodo (https://doi.org/10.5281/ zenodo.6558451), where I found no genotype information. Moreover, I have also analyzed my data and have yet to get genotype information. I have followed all QC processes and scAllele protocols to analyze my data. I am stuck at this point. Please kindly give your explanation about it.
Advance thanks for your response.
Best Regards,
Alamin
Email: [email protected]
The text was updated successfully, but these errors were encountered: