-
Notifications
You must be signed in to change notification settings - Fork 6
Update to include tmpdir #200
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
Conversation
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.2.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
muffato
left a comment
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.
Our convention is to control this via a parameter named use_work_dir_as_temp. We have that in readmapping and genomenote.
|
Ok, no problem. How's this instead? |
muffato
left a comment
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.
I think you can simplify the two main.nf by always doing mkdir blastp_tmp. It's the only tmpdir value that the pipeline allows anyway.
And please register use_work_dir_as_temp as the other params: nextflow.config, nextflow_schema.json, CHANGELOG.md
That's how I have it for production at the minute, but didn't think it was enough for this. mkdir is in there now. Does it want to just be hardcoded for
What do you mean by this bit? |
I mean hardcode
Exactly. Make it an official pipeline arg |
|
Cool, |
|
Ah there's a typo ! |
Addition of /tmpdir to Diamond blast modules.