Meryl count and meryl histogram migration to nf-test

[mahesh-panchal]

PR checklist

• Adds k-value as mandatory parameter to meryl/count and meryl/histogram
• Migrates pytest to nf-test
• Adds kvalue to genomescope2 nf-test

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

[rodtheo]

Outstanding! Thanks for updating these modules and corresponding tests.

[GallVp]

Hey guys!

Thanks for this module. Is there a reason the memory= parameter (marbl/meryl#24 (comment)) wasn't added? Should I add it and create a PR?

[mahesh-panchal]

Oversight perhaps, but is there a need to limit memory? Is it behaving badly on your systems? If it's not an issue I would just let it use what it can get a hold of, but if you see a need for it, make a PR

[GallVp]

It can be an issue because by default it uses all the available system memory.