Skip to content
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

update meta map guidelines for reference file inputs #1987

Open
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

ramprasadn
Copy link

As discussed in the nf-core maintainers meeting, I have updated the guidelines for creating new modules to add a meta map to channel definitions that carry reference file inputs.

@netlify
Copy link

netlify bot commented Sep 21, 2023

Deploy Preview for nf-core failed.

Name Link
🔨 Latest commit
🔍 Latest deploy log https://app.netlify.com/sites/nf-core/deploys/650daeadca7e8f0c064e4096

@maxulysse
Copy link
Member

@ramprasadn there are some conflicts.
If you could solve them that would be fabulous, and we could finally merge that one

@edmundmiller edmundmiller requested a review from a team as a code owner August 20, 2024 21:43
@edmundmiller edmundmiller requested a review from cmatKhan August 20, 2024 21:43

3. All _non-mandatory_ command-line tool _non-file_ arguments MUST be provided as a string via the `$task.ext.args` variable.
3. Non-file mandatory arguments or arguments needed to modify the command to make the module run with no error, SHOULD be provided as value channels (for example `lib_type` in [salmon/quant](https://github.com/nf-core/modules/blob/master/modules/nf-core/salmon/quant/main.nf)) - see 'Input/output options' below.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think rather than referring to 'non-file' in the current points 3. and 4. ... It would be better to separate that into its own bullet point. eg,

  1. file arguments, whether or not they are mandatory, should be provided as input channels (for example, the fai argument in samtools faidx)

I'm torn as to whether that should come before or after the current point 3.

On the one hand, it seems like mandatory arguments are more important, and hence addressed first.

On the other, it is probably a more necessary reminder to include non-mandatory file arguments, which the author themselves may never use, as module input.

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.

3 participants