You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
Maybe this is a silly question, but I recently found that bedtools intersect (v2.19.0) behaves weird when 0bp (those with identical start and end coordinates) features are compared. For example, an intersect of: A.bed containing chr1 2 2 B.bed containing chr1 3 3
would actually return: C.bed containing chr1 3 3
instead of returning nothing, which is a bit confusing and also complicates matters in some uses.
Attached is an example screenshot from IGV.
The text was updated successfully, but these errors were encountered:
Hi
Maybe this is a silly question, but I recently found that
bedtools intersect
(v2.19.0) behaves weird when 0bp (those with identical start and end coordinates) features are compared. For example, anintersect
of:A.bed
containingchr1 2 2
B.bed
containingchr1 3 3
would actually return:
C.bed
containingchr1 3 3
instead of returning nothing, which is a bit confusing and also complicates matters in some uses.
Attached is an example screenshot from IGV.
The text was updated successfully, but these errors were encountered: