Does GATK BaseRecalibrator work with solid Lifescope Bam files?

WimSWimS Posts: 25Member

Does GATK BaseRecalibrator work with Bam files produces with the SOLID Lifescope mapper?

You show in the a base quality recalibration presentation that recalibration also should work on SOLID data. But you don't mention if it also works for Bam files produced with lifescope. BWA mapping quality is from 0-37 , Lifescope mapping quality is from 0 - 95.

I get an ArrayIndexOutOfBoundsException on the lifescope Bam files.

`##### ERROR ------------------------------------------------------------------------------------------

ERROR stack trace

java.lang.ArrayIndexOutOfBoundsException: -92
at org.broadinstitute.sting.utils.baq.BAQ.calcEpsilon(BAQ.java:158)
at org.broadinstitute.sting.utils.baq.BAQ.hmm_glocal(BAQ.java:225)
at org.broadinstitute.sting.utils.baq.BAQ.calcBAQFromHMM(BAQ.java:542)
at org.broadinstitute.sting.utils.baq.BAQ.calcBAQFromHMM(BAQ.java:595)
at org.broadinstitute.sting.utils.baq.BAQ.calcBAQFromHMM(BAQ.java:530)
at org.broadinstitute.sting.utils.baq.BAQ.baqRead(BAQ.java:663)
at org.broadinstitute.sting.gatk.walkers.bqsr.BaseRecalibrator.calculateBAQArray(BaseRecalibrator.java:428)
at org.broadinstitute.sting.gatk.walkers.bqsr.BaseRecalibrator.map(BaseRecalibrator.java:243)
at org.broadinstitute.sting.gatk.walkers.bqsr.BaseRecalibrator.map(BaseRecalibrator.java:112)
at org.broadinstitute.sting.gatk.traversals.TraverseReadsNano$TraverseReadsMap.apply(TraverseReadsNano.java:203)
at org.broadinstitute.sting.gatk.traversals.TraverseReadsNano$TraverseReadsMap.apply(TraverseReadsNano.java:191)
at org.broadinstitute.sting.utils.nanoScheduler.NanoScheduler.executeSingleThreaded(NanoScheduler.java:248)
at org.broadinstitute.sting.utils.nanoScheduler.NanoScheduler.execute(NanoScheduler.java:219)
at org.broadinstitute.sting.gatk.traversals.TraverseReadsNano.traverse(TraverseReadsNano.java:91)
at org.broadinstitute.sting.gatk.traversals.TraverseReadsNano.traverse(TraverseReadsNano.java:55)
at org.broadinstitute.sting.gatk.executive.LinearMicroScheduler.execute(LinearMicroScheduler.java:83)
at org.broadinstitute.sting.gatk.GenomeAnalysisEngine.execute(GenomeAnalysisEngine.java:281)
at org.broadinstitute.sting.gatk.CommandLineExecutable.execute(CommandLineExecutable.java:113)
at org.broadinstitute.sting.commandline.CommandLineProgram.start(CommandLineProgram.java:237)
at org.broadinstitute.sting.commandline.CommandLineProgram.start(CommandLineProgram.java:147)
at org.broadinstitute.sting.gatk.CommandLineGATK.main(CommandLineGATK.java:91)

ERROR ----------------------------------------------`

Answers

  • Geraldine_VdAuweraGeraldine_VdAuwera Posts: 7,369Administrator, GATK Developer admin

    Hi there,

    The error you're getting is unrelated to its origin, it's due to a bug that is fixed in the latest version of GATK. Just upgrade your version and it will work fine.

    Geraldine Van der Auwera, PhD

  • WimSWimS Posts: 25Member

    The version I am using is
    The Genome Analysis Toolkit (GATK) v2.3-9-ge5ebf34, Compiled 2013/01/11 22:43:14

    which is fairly recent. So there is already a newer 2.3.9 build online? Or will it be fixed in 2.4?

  • Geraldine_VdAuweraGeraldine_VdAuwera Posts: 7,369Administrator, GATK Developer admin

    Oh that's weird, that is our latest version. Let me check if the fix is still pending.

    Geraldine Van der Auwera, PhD

  • WimSWimS Posts: 25Member

    Ok I am interested in the answer. To check for other problems I also ran Picard validate bam.
    I get a lot of NM tag missing errors:

    WARNING: Record 1, Read name 1212_1948_428, NM tag (nucleotide differences) is missing

    And just some mate related errors:

    ERROR: Record 20985168, Read name 164_312_583, Mate alignment does not match alignment start of mate
    ERROR: Record 20985168, Read name 164_312_583, Mate negative strand flag does not match read negative strand flag of mat

  • Geraldine_VdAuweraGeraldine_VdAuwera Posts: 7,369Administrator, GATK Developer admin

    OK, we believe this is fixed in our current development version. The fix will be in the next release (2.4) which will be out next week.

    Geraldine Van der Auwera, PhD

  • LisaLattaruloLisaLattarulo Posts: 9Member

    Hi - quick follow up @WimS. Did you ever figure out what do do with the all WARNING: ....NM tag (nucleotide differences) is missing? Did you have to fix these or did they run through anyhow? If you did fix them, how did you? I am currently running into this issue and haven't been able to find resolution yet. Thank you!!

Sign In or Register to comment.