Service notice: Several of our team members are on vacation so service will be slow through at least July 13th, possibly longer depending on how much backlog accumulates during that time. This means that for a while it may take us more time than usual to answer your questions. Thank you for your patience.

The doctor is in: diagnosing sick SAM/BAM files

deklingdekling Broad InstituteMember
edited May 2016 in Announcements

Ever find yourself happily going about your day, using Picard and/or GATK when all of sudden a dreaded ERROR message is output instead of your tidy SAM/BAM or VCF file? Even worse, you try to diagnose the errors using Picard's ValidateSamFile tool and the command-line output is... shall we say, "incomplete"? Well, take comfort because we have just the right medicine for you... new documentation for Picard's ValidateSamFile tool!

image

This document will guide even the most novice of users through the steps of diagnosing problems lurking within their SAM/BAM files. Not only that, for the first time in the history of the world, we present tables listing and explaining all of the WARNING and ERROR message outputs of this program! Woohoo!!! Now you can effectively troubleshoot your WARNING and ERROR messages by running ValidateSamFile prior to feeding your SAM/BAM file into Picard and/or GATK.

Post edited by dekling on
Sign In or Register to comment.