I just discovered a nasty invisible bug in intersectBed.
I did
intersectBed -abam A.bam -b B.bed > C.bam
Now, if you do
samtools view C.bam | head
outputting to screen, it will all look normal and successful but it
you try to catch that text output and repack it into BAM, it will
complain:
"missing colon in auxiliary data"
If I do
samtools view C.bam | head > ten_records.txt
I can open the txt and see the nasty tabs at the end of every line.
Basically, intersectBed works but the output BAM is not usable.
No matter how nasty you consider this bug, BEDTools is still
outstanding.
Big thanks to Aaron.
Ivan
I haven't really done what Ivan is reporting here but I routinely use subset of bam file generated by intersectBed for viewing in IGV or pileups and they seem to work fine.
-Abhi
This is worrisome...
Aaron
Aaron Quinlan, Ph.D.
NRSA Postdoctoral Fellow
Hall Laboratory
University of Virginia
Biochem. & Mol. Genetics
aaronq...@gmail.com
Aaron
On Mar 3, 2010, at 5:23 PM, Ivan wrote:
Thanks so much for bringing this up and sorry for doubting you!
Aaron
On Mar 3, 2010, at 5:23 PM, Ivan wrote: