Closed chapmanb closed 8 years ago
Hello Brad,
apologies for this. Could you please try version 2.0.62? It should fix this issue for bamsormadup. The bin field was computed wrongly for unmapped reads.
Please note that on the way to get this fixed I noticed that io_lib has similar issues, which means bin fields are still miscomputed for all the other tools (apart from bamsormadup, which does not use io_lib for SAM input) when inputformat=sam is set. I have notified the author of io_lib about this. Meanwhile setting inputformat=maussam (all tools but bamsormadup) may help, this will use libmaus2 SAM parsing instead of io_lib.
Best, German
German -- thanks so much for looking at this so quickly. The new version does resolve the issue. I updated the bioconda version we use in bcbio so it fixes the problems we were having there. Thanks also for the heads up on the more general io_lib issue. Thank you again.
German; We're running into an issue with using bamsormadup directly on SAM output from bwa. If you run with any htsjdk based tools you'll get errors/warnings about the BAM record:
The BAMs appear to work okay but generate a ton of messages and potentially will have slower look ups.
This appears to only happen when running from SAM input. This type of input generates the issue:
while first feeding to samtools does not:
This is a self-contained test case that demonstrates the issue using picard ValidateSamFile:
Let me know if I can provide any other details to help debug. Thanks as always for the awesome tools and all the help.