New module: octopusv/merge

[manascripts]

PR checklist

Closes #11516

• 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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Broadcast software version numbers to topic: versions - See version_topics
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda

[SPPearce]

You can put the valid list back into the module code if you like

[SPPearce]

You can put the valid list back into the module code if you like

[SPPearce]

(sorry, just accidentally closed the PR!)

[manascripts]

I was thinking of adding this: def strategy_flags = ['union', 'intersect', 'specific', 'min-support', 'exact-support', 'max-support', 'expression'] and if (!strategy_flags.contains(merge_strategy)) { error("OCTOPUSV_MERGE: invalid merge strategy '${merge_strategy}'. Allowed: ${strategy_flags.join(', ')}") }

But I think it is fine as is, since some flags also require an INT or a string after. For such cases one needs to refer to the tool documentation anyway. Do you think I should add this?

[SPPearce]

Ok, particularly if some strategies require an extra value as well, validation isn't as simple.
I'm happy as is.

[manascripts]

Cool thanks, I added an optional output (an upset plot) which I found later on. and bumped the version to 0.3.3 (new recipe came out only 8 hours ago).