I adjusted the used labels for the process specific resource requests.
In the end I just applied minor modifications and kept the labels for the most processes as they were although the memory usages was drastically reduced. I am a bit unsure how much would be needed for reasonable big real datasets, but thought retrying with increased memory values is also not efficient.
We can still reduce some of the values in the future if needed.
PR checklist
[x] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/metapep branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).
I adjusted the used labels for the process specific resource requests.
In the end I just applied minor modifications and kept the labels for the most processes as they were although the memory usages was drastically reduced. I am a bit unsure how much would be needed for reasonable big real datasets, but thought retrying with increased memory values is also not efficient.
We can still reduce some of the values in the future if needed.
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).