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 warning #516

Closed
yassineS opened this issue Jul 17, 2020 · 3 comments · Fixed by #518
Closed

bedtools warning #516

yassineS opened this issue Jul 17, 2020 · 3 comments · Fixed by #518
Assignees
Labels
bug Something isn't working

Comments

@yassineS
Copy link

Bedtools occasionally issues a warning like this when using GRCh38:


***** WARNING: File merged_bams/initial/A14937_libmerged_rg_rmdup.bam has inconsistent naming convention for record:
HLA-A*01:01:01:01	47	100	M_ST-E00180:295:H7JNVCCXY:7:2220:15229:45699	0	+

Bedtools continues running and produces a complete output. However, the error 137 results in the process being identified as "failed" by nextflow. It just requires an exception.

jfy133 added a commit that referenced this issue Jul 17, 2020
@jfy133
Copy link
Member

jfy133 commented Jul 17, 2020

Thanks for the report @yassineS !

Could you maybe run a manual test, and see if the following solution works?

arq5x/bedtools2#628 (-noname)

If so I would prefer for that to work than 'ignoring' the error code, but in case it doesn't work, please can you test the fix on this branch: https://github.com/nf-core/eager/tree/bedtools-fix/

@jfy133 jfy133 added the bug Something isn't working label Jul 17, 2020
@jfy133 jfy133 self-assigned this Jul 17, 2020
@yassineS
Copy link
Author

Thanks, @jfy133 Just for the record, there are no mismatches between chromosome names in the bed file, the reference and the bam file.

I tried the -nonamecheck option and it seems to have fixed the issue.

@jfy133 jfy133 mentioned this issue Jul 20, 2020
8 tasks
@jfy133 jfy133 linked a pull request Jul 20, 2020 that will close this issue
8 tasks
@jfy133
Copy link
Member

jfy133 commented Jul 20, 2020

Should be addressed inthe above!

@jfy133 jfy133 closed this as completed Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants