Skip to content

New module: mobster #8647

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 8 commits into
base: master
Choose a base branch
from
Open

Conversation

elena-buscaroli
Copy link

@elena-buscaroli elena-buscaroli commented Jun 16, 2025

PR checklist

Closes #8689

  • 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

Copy link
Contributor

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, thanks for the contribution. The module is already quite solid. I've left a few technical comments for your consideration.

label "process_high"

conda "${moduleDir}/environment.yml"
container "${ workflow.containerEngine == 'singularity' && !task.ext.singularity_pull_docker_container ?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you make a Seqera container with the tools? They are more reliable than Biocontainers

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! thank your for your comment. My lab and I are developing an nf-core pipeline (https://nf-co.re/tumourevo/dev/) and after the first release comments, some of your collegues suggested to use biocontainers for our modules, that's why we proceeded with those. Is it ok or should I update the containers to sequera ones?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For a single module, biocontainers should be fine (although I recall some issues with Singularity). However, with multiple, it is much more reliable and convenient to use Seqera Containers instead of mulled biocontainers.

@elena-buscaroli
Copy link
Author

Hi @itrujnara! thank you for your comments, I should've addressed all of them (I've left a comment for the Docker/Singularity containers).
I'm currently waiting for the test datastes to be accepted in the nf-core/test-datasets repository. After that (if everything else is now correct) I can create a snapshot and test the module

Copy link
Contributor

@itrujnara itrujnara left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You can consider switching to Seqera Containers for convenience. Otherwise, the module looks fine now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

new module: mobster
2 participants