Closed parlar closed 8 years ago
Pär; Thanks for checking in on BAM correctness. Are you noticing problems processing the BAM downstream? I've always found ValidateSamFile to be too stringent so don't work with it regularly. With test datasets I can replicate getting CIGAR string reports when using bwa on pretty vanilla inputs but not issues with both mates being marked as first.
If it's worth digging into more, I'd likely need to know more about your setup to try and replicate: what type of inputs do you have (standard fastq files, previously aligned BAMs, how long are the reads), what does your configuration look like (are you doing split alignments, recalibration/realignment?), what genome are you aligning against (hg19 versus hg38). Happy to try and help more if this is causing problems.
As far as I know there are no problems, I just though I should inform you if the results would be a reason for concern. But of course you already knew about this..
Pär; Thanks much. If you run into anything or identify issues happy to try and debug more. Closing for now but re-open if anything comes up.
Running
$ picard ValidateSamFile INPUT=xxxxx-ready.bam
(bam file produced by bcbio-nextgen) gives the error listed below. Is this due to bam files being merged? Any potential problems from this, reason to worry?Adam Ewing, who makes BamSurgeon pointed this out.