add new module: aardvark/compare

[kubranarci]

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

[kubranarci]

@georgiakes do you have more comments :D

[georgiakes]

I think that's it🫣

[kubranarci]

I think that's it🫣

Can I have an approve :D

[georgiakes]

Oh sorry for I thought you have seen those

[kubranarci]

did you push your commends? I think they are pending

[georgiakes]

Since the tools allows multi threading, should we use another label?

[kubranarci]

I think single is still good, maybe also low. but not medium.

[georgiakes]

For sure low. The only reason I'm saying it is because with single the task.cpu becomes useless.

[kubranarci]

changed to low now

[kubranarci]

thank youuu @georgiakes