Added new module arcane/express

[LeonHornich]

Added new module supporting arcane/express subcommand.

Quick things to add/consider:

process {
    withName: 'ARCANE_FILTER' {
        ext.args = '--kmersize 12'
    }
    withName: 'ARCANE_INDEX' {
        ext.args = '--kmersize 12'
    }
    withName: 'ARCANE_EXPRESS' {
        ext.args = { params.express_args ?: '' }
    }
} 

• i tried defining the --kmersize 12 parameter in the setup block directly for the /filter and /index subcommands. With that the tools /filter and /index was not able to access the parameter and did not run. Therefore these are defined directly in the config. If you have alternative options or ideas why this happens please let me know.

• 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

[famosab]

I think this looks good :)

[famosab]

I think it might be related to the fact that the config needs to be supplied differently to the setup block. But I would say it is ok to leave it like that.

[LeonHornich]

That would explain it. Is there some documentation regarding how to handle this? I haven't been able to find anything in the official docs. Just so that i know for the future :)