-
Notifications
You must be signed in to change notification settings - Fork 2
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
Release 0.7 #116
base: main
Are you sure you want to change the base?
Release 0.7 #116
Conversation
Use small 1.2G for base nextflow job
Use the org level variable TOWER_COMPUTE_ENV which point to small actually with 1.2G memory.
Use small tower compute env
This will save a lot of space
Support for grid view (and a few other things)
|
Indeed, 85.9% of jobs complete within 4 hours, 98% within 47 hours, and 99.7% within 167 hours
There will need to be another change in this release. Damon reported that the instructions for setting up the UniProt diamond database don't work. |
Misc fixes before release
I don't think it is immediately necessary, but we might want to manually insert something into the small test dataset that won't be caught in blastx, so the blastn subworkflow will be triggered in the tests? |
That would be very good, yes. |
Trigger blastn subworkflow in test profile
The sum of #113, #114, and #117
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,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).