Add functionality to parse run dir metadata#106
Conversation
|
…n the multiqc report generation, make function take output name as cmd parameter
… the outfile accordingly, for proper downstream grouping
|
Ties into nf-core/test-datasets#1559 |
Did I mention you again when I meant to tag @matthdsm |
|
So I think there's a huge overlap between this module and what we're trying to achieve with MultiQC_SAV. |
Oh interesting, I have to check it out! If we can avoid a local module that is definitely interesting. Unfortunately I have been swamped with other work duties so have had no time to work with this PR. |
I'm on it 🚀 |
I fully rewrote the tests, and they're now working. Now trying to figure out what's the problem with the rest of the tests |
| */ | ||
|
|
||
| // Enable use of module binaries for e.g. module specific Python scripts | ||
| nextflow.enable.moduleBinaries = true |
There was a problem hiding this comment.
why are you using module binaries? Just wondering since we have typically been using templates in nf-core
There was a problem hiding this comment.
I just followed along what was already done to be honest.
There was a problem hiding this comment.
ok will approve as i assume there will be clean up before v1
There was a problem hiding this comment.
Module binaries require wave to run on cloud if I remember correctly
|
FYI, a new version of MultiQC_SAV was just released |
PR checklist
nf-core lint).nf-test test main.nf.test -profile test,docker).nextflow run . -profile debug,test,docker --outdir <OUTDIR>).docs/usage.mdis updated.docs/output.mdis updated.CHANGELOG.mdis updated.README.mdis updated (including new tool citations and authors/contributors).