Heads up:
We’re moving the GATK website, docs and forum to a new platform. Read the full story and breakdown of key changes on this blog.
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.

ReduceReads - No real operator (M|I|D|N) in CIGAR

Hi. When I reduce my BAM files with ReduceReads and then run HaplotypeCaller I get this warning:

Ignoring SAM validation error: ERROR: Read name 1060, No real operator (M|I|D|N) in CIGAR

Why is this? Is it OK to inore it?


  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    This sounds like the aligner was sleeping on the job... If it's just a few reads, I'd ignore it, or maybe use -rf BadCigar to filter them out so we don't risk choking on them later on. If it's more than a few, by all means check the alignments throughout the file.

  • Dear Geraldine,
    I encountered the same problem when running AddOrReplaceReadGroups tools from picard.Since the software exited when it met the first bad formatted read,I had no idea about the total number of such reads.Would you please explain more about the aligner was sleeping on the job?
    Thanks and regards.

  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    Hi @taojinsheng,

    "sleeping on the job" is a colloquial phrase that means "doing something wrong". In this case it means that the aligner produced invalid output.

    One easy way of knowing how many reads are affected is to run the CountReads tool with the BadCigar filter enabled, like this:

    java -jar GATK.jar -T CountReads -R ref.fasta -I reads.bam -rf BadCigar

    When the run finishes, there will be a line in the console output that tells you how many reads were filtered out by BadCigar.

    If the percentage of bad reads is high, then you may need to do additional QC on your data and possibly realign them from the original FastQ.

  • I got it.Thanks a bunch,Geraldine.

Sign In or Register to comment.