Add Severus

[fellen31]

Closes #5797

PR checklist

Closes #XXX

• 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.
• Emit the versions.yml file.
• 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
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[matthdsm]

Does the tool also support cram inputs?

[fellen31]

Yes!

[SPPearce]

Maybe change to something like target_input?
We really need a good word that covers bam and cram files...

[fellen31]

In this case I chose target_bam because the program argument is --target-bam. But I can change it to target_input & control_input.

[fellen31]

Updated meta.yml to also include cram, csi and crai @matthdsm

[SPPearce]

Maybe change to something like target_input?
We really need a good word that covers bam and cram files...

[fellen31]

The VCF contained a date, changed the snapshot to store the lines around it.