If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!

Test-drive the GATK tools and Best Practices pipelines on Terra

Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.

Cannot construct fragment from more than two reads

micknudsenmicknudsen DenmarkMember ✭✭


I am running a Best Practices Mutect2 workflow, and after having upgraded to GATK from, I am starting to see this error:

17:35:39.809 INFO  PairHMM - Using the OpenMP multi-threaded AVX-accelerated native PairHMM implementation
17:35:39.942 INFO  ProgressMeter - Starting traversal
17:35:39.943 INFO  ProgressMeter -        Current Locus  Elapsed Minutes     Regions Processed   Regions/Minute
17:35:50.272 INFO  ProgressMeter -       chr22:10938027              0.2                 36510         212082.5
17:36:00.317 INFO  ProgressMeter -       chr22:12587748              0.3                 42160         124158.2
17:36:10.409 INFO  ProgressMeter -       chr22:16564638              0.5                 55550         109400.6
17:36:20.431 INFO  ProgressMeter -       chr22:18088679              0.7                 60790          90086.0
17:36:30.395 INFO  VectorLoglessPairHMM - Time spent in setup for JNI call : 0.022855297
17:36:30.395 INFO  PairHMM - Total compute time in PairHMM computeLogLikelihoods() : 7.454791689
17:36:30.395 INFO  SmithWatermanAligner - Total compute time in java Smith-Waterman : 11.04 sec
17:36:30.516 INFO  Mutect2 - Shutting down engine
[October 9, 2019 5:36:30 PM CEST] done. Elapsed time: 0.86 minutes.
java.lang.IllegalArgumentException: Cannot construct fragment from more than two reads
        at org.broadinstitute.hellbender.utils.Utils.validateArg(
        at java.util.ArrayList$ArrayListSpliterator.forEachRemaining(
        at org.broadinstitute.hellbender.utils.genotyper.AlleleLikelihoods.groupEvidence(
        at org.broadinstitute.hellbender.engine.AssemblyRegionWalker.processReadShard(
        at org.broadinstitute.hellbender.engine.AssemblyRegionWalker.traverse(
        at org.broadinstitute.hellbender.engine.GATKTool.doWork(
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.runTool(
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMainPostParseArgs(
        at org.broadinstitute.hellbender.cmdline.CommandLineProgram.instanceMain(
        at org.broadinstitute.hellbender.Main.runCommandLineProgram(
        at org.broadinstitute.hellbender.Main.mainEntry(
        at org.broadinstitute.hellbender.Main.main(
Using GATK jar /home/michaelk/miniconda3/envs/moma-somatic-pipeline-gatk-
    java -Dsamjdk.use_async_io_read_samtools=false -Dsamjdk.use_async_io_write_samtools=true -Dsamjdk.use_async_io_write_tribble=false -Dsamjdk.compression_level=2 -Xmx8g -jar /home/michaelk/miniconda3/envs/moma-somatic-pipeline-gatk- Mutect2 -R /faststorage/project/MomaRAWfiles/BACKUP/reference/hg38/reference_hg38/GCA_000001405.15_GRCh38_no_alt_analysis_set.fna -I output/raw_output/alignments/TUMOR.recalibrated.markdup.sorted.bam -tumor TUMOR -I output/raw_output/alignments/NORMAL.recalibrated.markdup.sorted.bam -normal NORMAL --bam-output /scratch/2114474/TUMOR_chr22.mutect.somatic.assembled.haplotypes.bam --f1r2-tar-gz /scratch/2114474/TUMOR_chr22.mutect.somatic.f1r2.tar.gz -pon /faststorage/project/MomaRAWfiles/BACKUP/reference/hg38/broad_bundle_hg38/1000g_pon.hg38.vcf.gz -L chr22 -O /scratch/2114474/TUMOR_chr22.mutect.somatic.vcf.gz

Both VCF file and BAM-out are produced and seem to be OK. If I run the exact same pipeline with GATK, the error does not occur.

I have not seen others report this error neither here nor as a GitHub issue. Any clue what could be going on?




Sign In or Register to comment.