-
Notifications
You must be signed in to change notification settings - Fork 29
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
Difference in number of calls: CRAM vs BAM #344
Comments
Hi Nicole, Would you be able to show us the variant differences of the replicates you have. At least we want to know where the different variants are at. |
Sure, these are the variant differences that were seen in the replicates: Replicate 1
Replicate 2
Replicate 3
Replicate 4
Replicate 5
Replicate 6
Looking in IGV many of these calls appear to be at the start of or within repetitive regions. |
Thank you for the details, we will start investigating. |
Sounds good, thanks a lot! |
Hi there,
I’m currently comparing the results of Clair3 v1.0.5 when alignments are stored within a BAM file vs CRAM. I am using HG002 replicates, and CRAM files were converted from the BAM file.
When comparing total number of variants called from the BAM file vs converted CRAM, I am seeing a 1-5 variant difference for 6 out of 8 HG002 replicates (out of on average 6 million variants called per replicate). Another thing I found interesting is that once the CRAM is converted back to BAM and is processed through Clair3, the total number of variant calls from the converted BAM matches the calls from original BAM.
Here is an example of what I am seeing:
Would you know why this might be happening?
Clair3 command used:
Kind regards,
Nicole
The text was updated successfully, but these errors were encountered: