Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bedtools intersect behaviour when crossing 0bp features #141

Open
Marmach opened this issue Jan 17, 2019 · 0 comments
Open

Bedtools intersect behaviour when crossing 0bp features #141

Marmach opened this issue Jan 17, 2019 · 0 comments

Comments

@Marmach
Copy link

Marmach commented Jan 17, 2019

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.

intersect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant