Skip to content

New module : portello#11114

Open
sofiademmou wants to merge 4 commits intonf-core:masterfrom
sofiademmou:portello
Open

New module : portello#11114
sofiademmou wants to merge 4 commits intonf-core:masterfrom
sofiademmou:portello

Conversation

@sofiademmou
Copy link
Copy Markdown
Contributor

@sofiademmou sofiademmou commented Apr 2, 2026

PR checklist

Add new nf-core module Portello.

  • 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

@sofiademmou sofiademmou changed the title Add new portello module New module : portello Apr 2, 2026
@sofiademmou sofiademmou marked this pull request as ready for review April 2, 2026 08:31
Copy link
Copy Markdown
Contributor

@famosab famosab left a comment

Choose a reason for hiding this comment

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

Few things related to nf-test but looking good!

tag "samtools/index"
tag "find/concatenate"

setup {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

That is a really large setup for a test. I think its fine but I would argue that one could generate the input file once and store it in test-datasets so that we do not compute it all the time :)

Comment on lines +11 to +14
tuple val(meta), path(asm_to_ref_bam), path(asm_to_ref_bai), path(read_to_asm_bam), path(read_to_asm_bai)
tuple val(meta2), path(ref_fasta)
val(assembly_mode) // value : [ fully-phased | partially-phased ]
val(output_vcf) // value : [ true | false ]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we put all these inputs into one tuple? That will make sure you're sure that EVERY time everything comes together in the right combination.

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.

2 participants