Open dbolser opened 7 months ago
I don't want to do this:
time bedtools genomecov \
-i <(echo -n '#' && bgzcat Data3/PWM/multiinter.bed.gz)
-g ../../ENCFF792NJK.tsv \
> genomecov-multiinter.tsv # hashtag sad face
Also tabix
doesn't like the header without a preceding #, e.g. although tabix -S 1 -p bed multiinter.bed.gz
works, tabix -H multiinter.bed.gz
doesn't (it does when you have the #) and as an extension, Python's pysam.TabixFile("multiinter.bed.gz").header
also 'fails'.
So although nothing in BED formally requires a # for the header, it seems a lot of tooling has adopted that convention.
Hi, Thanks for creating bedtools @arq5x !
When I use:
bedtools multiinter -header -i a.bed b.bed
the resulting output looks like this:
Note that this is not bed format, which should be:
At least I think that's what it should be ... I'm actually not sure now I check the BED specification...
HOWEVER, the lack of the
#
DOES break your own tools, e.g.multiinter
itself expects the BED file header to start with #, and so doesgenomecov
(and so does LiftOver from UCSC...)So perhaps this bug is better described as "multiinter and genomecov fall over when given a valid bed header...", with a separate bug for LiftOver?
THx