-
Notifications
You must be signed in to change notification settings - Fork 417
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
Replacing local module BUILD_INTERVALS with nf-core mdule GAWK #1439
Replacing local module BUILD_INTERVALS with nf-core mdule GAWK #1439
Conversation
|
This PR scares me :D What are the output files now called? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
<3
Before merging, can you test on the full size test? I am worried that the output name changing of the bed file could have effects we don't see on a smaller dataset. in the earlier days of sarek 3, we had issues in that direction |
I don't think the bed-file is or were published, but the output-file in the work-folder is called
The following is the
|
no they are not published but they are used further in the pipeline. |
Sure I can run the full-test. Better safe than sorry. Anything, in particular, I should pay attention to in my run of the full-test or is it fine if it completes without crashing? EDIT: Shot! I just remembered the full-test is still broken in the dev-branch, and so it will also be broken on my branch :-/ What to do? |
I think if it runs through without crashing we are relatively save. |
Related to nf-core/modules#5132 (comment)
If approved, then similar a change should be done in the raredisease-pipeline.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).