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 false positive namecheck warning #648

Open
mdkeehan opened this issue Jul 19, 2018 · 0 comments
Open

bedtools intersect false positive namecheck warning #648

mdkeehan opened this issue Jul 19, 2018 · 0 comments

Comments

@mdkeehan
Copy link

Thanks for bedtools it is just so handy!

Here is a small issue I have encountered with bedtools.
I am working with a genome which has successfully assembled chromosomes and also unlocalized scaffolds which we are working with. We have combined them into one big reference. The naming convention for the chromosomes is lowercase "chr" as the prefix while the unlocalized have names like "Leftover_ScbfJmS_1".
Mixing the convention in one bed file generates the namecheck warning. Here is a cut'n'paste test to generate the warning.

bedtools version

someone@somemachine:/somedir$ bedtools -version
bedtools v2.27.1-2-ge5ad7e4

False positive scary warning

someone@somemachine:/somedir$ bedtools intersect  -a tiny.chrNametest.bed -b tiny.chrNametest.bed -f 0.9 -r 
***** WARNING: File tiny.chrNametest.bed has inconsistent naming convention for record:
Leftover_ScbfJmS_1	0	25561

chrX	0	139009144
chrY	0	43300181
chrM	0	16340
Leftover_ScbfJmS_1	0	25561
Leftover_ScbfJmS_10	0	5566
Leftover_ScbfJmS_100	0	24335
Leftover_ScbfJmS_1000	0	41467
***** WARNING: File tiny.chrNametest.bed has inconsistent naming convention for record:
Leftover_ScbfJmS_1	0	25561

Remove warning with nonamecheck

someone@somemachine:/somedir$ bedtools intersect  -a tiny.chrNametest.bed -b tiny.chrNametest.bed -f 0.9 -r -nonamecheck
chrX	0	139009144
chrY	0	43300181
chrM	0	16340
Leftover_ScbfJmS_1	0	25561
Leftover_ScbfJmS_10	0	5566
Leftover_ScbfJmS_100	0	24335
Leftover_ScbfJmS_1000	0	41467

Tiny sample data to replicate the issue and use as a test case

someone@somemachine:/somedir$ cat tiny.chrNametest.bed 
chrX	0	139009144
chrY	0	43300181
chrM	0	16340
Leftover_ScbfJmS_1	0	25561
Leftover_ScbfJmS_10	0	5566
Leftover_ScbfJmS_100	0	24335
Leftover_ScbfJmS_1000	0	41467
someone@somemachine:/somedir

I think the namecheck logic needs to be improved.
The -nonamecheck makes the problem go away but ideally it wouldn't have happened in this circumstance.
It's not a big problem but the warning is worrisome and I hope the feedback makes bedtools better.
Mike

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