-
Notifications
You must be signed in to change notification settings - Fork 8
Use nf-core interproscan instead of local version #67
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
base: dev
Are you sure you want to change the base?
Conversation
… and funcscan-like interproscan subworkflow, updated test configs with new-moved test dataset paths,
…nfig updated, test samplesheet paths fixed
|
Warning Newer version of the nf-core template is available. Your pipeline is using an old version of the nf-core template: 3.5.1. For more documentation on how to update your pipeline, please see the nf-core documentation and Synchronisation documentation. |
|
erikrikarddaniel
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.
Looks good. One small comment and an even smaller suggestion.
I was a bit surprised to see that on the interproscan module is nf-core while the download and swf are local. I suppose you have a reason for this but having an nf-core swf would make it easier for other pipelines.
Co-authored-by: Daniel Lundin <erik.rikard.daniel@gmail.com>
I just copy-pasted from nf-core/funcscan. But to be honest it's better if I move to |
Closes #3
PR checklist
nf-core pipelines lint).nf-test test */local --profile=~test,dockerfor all new local tests).nf-test test */local --profile=~test,docker,debug).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).