-
Notifications
You must be signed in to change notification settings - Fork 119
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
Adds --krona_db parameter to point at a local copy of the db needed for Krona. Suggested in Issue #404. #497
Conversation
|
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.
Looks good to me.
Is there a way to include that into tests? Potentially with files from the test of the nf-core module ktimporttaxonomy?
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.
Eventually it might be good to go to https://nf-co.re/modules/krona_ktimporttaxonomy (which seems to do the same), but I agree that --krona_db
parameter is in any case a good addition.
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 will look into how the test is implemented in https://nf-co.re/modules/krona_ktimporttaxonomy.
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.
Overall LGTM thanks @willros !
Just a question about the implementation with the file rather than a directory (containing the file). If there is an issue with symlinks 👍 I have an alternative suggestion
Co-authored-by: Daniel Straub <[email protected]>
Co-authored-by: James A. Fellows Yates <[email protected]>
Just running a little test, and then can merge |
Hm, auto download didn't work....
|
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.
The KRONA module received null
rather than the .getParent()
output for autodownloading...
Ah I think this is because what is literally given to the module is |
After thinking about it, my suggestion is to follow what is done in various Supply the whole directory containing the taxonomy files, then search for tab, and resolve the path that way. |
Looking deeper into the krona module of nf-core, why not use the process implemented there? https://github.com/nf-core/modules/blob/868d4c3dc7a3db39d36184173e4fe3484499396e/modules/nf-core/krona/ktimporttaxonomy/main.nf Anyways, I implemented the same solution in the local process for this 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.
All works for me now, thank you very much @willros this is VERY helpful (as I'm having to do a manual 'full test' of the AWS runs on my offline cluster 😅, which obiovusly wasn't working before...)
We also need to do a big pass through the pipeline replaceing local modules with now-official moduels... but this will requrie a big overhaul in the future! So thanks again for contribution and we hope you will keep contributing! |
closes #404
The user can now point at a local copy of the the taxonomy.tab file needed for running Krona.
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).