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
- Developing
- Overview
- Containers
- Documentation
- External use
- Institutional profiles
- Migration guides
- Testing
- Contributing
- Overview
- How to contribute
- Components
- Contributor types
- Contributor's list
- Documentation
- Existing pipelines
- New pipelines
- Project proposals
- Reviewing pull requests
- nf-core bot
- Review checklists
- Specifications
- Community
- nf-core/tools
- API
- Cli
- Installation
- Test datasets
- TUI