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
- Overview
- Advanced topics
- Configuration
- Reference genomes
- Running pipelines offline
- Developing
- Overview
- Containers
- Documentation
- Institutional profiles
- Migration guides
- Testing
- Contributing
- Overview
- Components
- Contribution types
- Contributor's list
- Deprecating modules
- Documentation
- Existing pipelines
- New pipelines
- Project proposals
- Reviewing pull requests
- nf-core bot
- Review checklists
- Reviewing pipeline releases
- Specifications
- Community
- Advisories
- Governance
- Terminology
- nf-core/tools
- API
- CLI
- Installation
- Test datasets
- TUI