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.
We will be out of the office on November 11th and 13th 2019, due to the U.S. holiday(Veteran's day) and due to a team event(Nov 13th). We will return to monitoring the GATK forum on November 12th and 14th respectively. Thank you for your patience.

BWA and fastqtosam failing with read names do not match errors

I'm using the GATK best practices to call public exome data. Out of over 600 exomes, most of the samples did fine with BWA mem alignment and fastqtosam. About 100 samples failed both steps (the same samples failed both). For fastqtosam an empty file is created. For BWA a very small file is created. The input for both these steps is paired end FASTQ files from a public repository. The error messages from both processes mention read names not matching, for instance this is from fastqtosam:

Exception in thread "main" picard.PicardException: In paired mode, read name 1 (SRR221230.sra.ncbi_enc.1) does not match read name 2 (SRR221230.sra.ncbi_enc.4)

Can anyone tell me what is causing this and if there is a way to recover the data for these samples?


  • bhanuGandhambhanuGandham Cambridge MAMember, Administrator, Broadie, Moderator admin

    Hi @nparmalee

    We are experiencing a high volume of questions at the moment, so we are focusing on answering GATK error/bug related questions at this time. This is about BWA question which do not support. This might be better suited for or

Sign In or Register to comment.