-
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
Move BUSCO bash code a script #444
Conversation
|
Hi, isn't the output env variable most_spec_db missing? |
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.
Other than the missing output env variable, it looks good to me! One could add a proper handling of the input arguments with getopts
, but not necessary in my opinion ...
Suggestions for BUSCO script
If you felt like doing that go ahead, I was trying simply for a one-to-one conversion here as I assumed the 'script' wouldn't really b e used outside of the pipeline 😬 |
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.
LGTM :D
I just couldn't cope anymore with trying to debug pipelines during tests and having 100xs of a 300 line error msesage...
I've tested with
-profile test
and it produces output and no errors.Resolves #393
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).