-
Notifications
You must be signed in to change notification settings - Fork 17
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
Possible issue with mate CIGAR string #18
Comments
here is an example of a MISMATCH_MATE_CIGAR_STRING: output given by Picard ValidateSamFile:
|
Hi @TDDB-limagrain, As for the It would be interesting to see what an example of As for the error in haplotype caller, I do not know. Do you think you could post an issue with the developers? (even though it is likely some misreporting in strobealign). Maybe they know what will cause this error. Looks like there is an issue that has to do with sorting of some kind. |
Which program do you use to add on the fields |
I am piping those following commands:
The new fields probably came from the mark duplicate step http://www.htslib.org/doc/samtools-markdup.html. These are the same commands I piped to bwa-mem and here are the same reads:
That looks quite weird they are located on different chromosome! Bwa mem mapped it on Chr11 while strobealign mapped it on Chr1. I had a look at this issue on the GATK github broadinstitute/gatk#7199 (comment), but no response from the developer so far. |
So as for the As for the map location: Both mates within the read pair are mapped with the same 'fit' (m1 perfect match and m2 perfect except 4 softclipps). They even have the same insert distance (template length 147). This is likely because of a perfect repeat where the location is assigned "at random", so I also don't see a potential issue here. |
regarding the
with the following details from the strobealign-related bam file:
|
Ok thanks for the anwser! |
Ah, I see. This is also an error caused by the program adding the attributes to the bam file. For some reason, picard does not like that the cigar of the mate |
ok, seems that samtools command I add are introducing some confusing fields! |
Hi, I’m going through some open strobealign issues and was wondering whether this one can be closed. Note that in version 0.10.0, strobealign has switched to outputting |
Hi @ksahlin !
sorry for bothering you again!
I am trying to run GATK haplotypecaller on reads mapped with Strobealign. The Haplotypecaller ends with an error:
java.lang.IllegalArgumentException: Sequence [VC HC @ Chr02:1-49670989 Q. of type=SYMBOLIC alleles=[C*, <NON_REF>] attr={END=49670989} GT=[[CB10 C*/C* GQ 0 DP 0 PL 0,0,0 {MIN_DP=0}]] filters= added out of order currentReferenceIndex: 0, referenceIndex:6
Besides I aligned the same reads with bwa mem and successfully ran the Haplotycaller. Therefore, I wondered whether something could have happened with the alignment formats.
I ran the Picard tool ValidateSamFile, giving me:
Strobealign:
Bwa mem:
I still need to dive into the details, especially to look for this kind of error: MISMATCH_MATE_CIGAR_STRING.
That might also be a GATK-related issue... so I will keep you in touch with additional information.
(I finally succeeded in running Strelka on the same reads, thanks for adjusting alignment formatting! compared to array-based genotyping data, the combination strobealign+strelka performed very similarly to bwa mem + strelka, but of course at much higher speed for the mapping!).
The text was updated successfully, but these errors were encountered: