-
Notifications
You must be signed in to change notification settings - Fork 111
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
Segfault from bedtools in prepare_results.R #40
Comments
this is pretty odd. Every time I've run prepare_results.R with the hg19 bed files I get two warnings about inconsistent records but I've never had a seg fault. Have you updated to the latest version of bedtools? If these weird chromosome names are the case then maybe we could get rid of them when creating the bed files? |
That warning may just be a coincidence, not sure. I'll try updating and see if it helps! |
Hmm so upgrading bedtools from v2.25.0 to v2.26.0 didn't fix this. |
I removed the "weird" chromosome names from |
I tried with a new |
So I'm starting to think this is a bug in |
I've reworked prepare_results.R to use dplyr joins instead of bedtools now so we avoid these issues. I've also changed the CLI to be a bit simpler to document. |
I'm trying to run prepare_results.R on the YRI vs EU example in /worked_out_example. At the line
bedtools is segfaulting:
I think the
has inconsistent naming convention for record
is todo with checking for e.g. chr1 vs 1 naming of chromosomes, but nothing like that is going on there. Maybe bedtools doesn't like the GL000220.1 chromosome name for some reason? This is my all_junctions.bed:https://www.dropbox.com/s/43eq0zdtv27owh7/all_junctions.bed?dl=0
and gencode_hg19_all_introns.bed.gz is here:
https://www.dropbox.com/s/pt1pbh5r40pjjs8/gencode_hg19_all_introns.bed.gz?dl=0
The text was updated successfully, but these errors were encountered: