Subworkflow parameters
The key words “MUST”, “MUST NOT”, “SHOULD”, etc. are to be interpreted as described in RFC 2119.
Usage of parameters
Subworkflows MUST NOT assume that named params defined in the parent workflow will be passed to the subworkflow.
This allows developers to name their parameters as needed.
Use additional input value channels for such scenarios.
- Get started
- Running
- Reference genomes
- Running pipelines offline
- Configuration
- Advanced topics
- Developing
- Containers
- Institutional profiles
- Migration guides
- Documentation
-
- Contributing
- How to contribute
- Project proposals
- Reviewing pull requests
- nf-core bot
- Review checklists
- Documentation
- Components
- Contribution types
- Contributor's list
- Deprecating modules
- Existing pipelines
- New pipelines
- Reviewing pipeline releases
- Specifications
- Community
- Governance
- Advisories
- Terminology
-
- nf-core/tools
- CLI
- Installation
- Test datasets
- TUI
- API
-