Input/output options
The key words “MUST”, “MUST NOT”, “SHOULD”, etc. are to be interpreted as described in RFC 2119.
Required input channels
Input channel declarations MUST be defined for all possible input files that the subworkflow requires (i.e., both required and optional files) within the take block.
Required output channels
Named file extensions MUST be emitted for ALL output channels (e.g., path "*.txt", emit: txt).
Optional inputs
Nextflow does not currently support optional inputs.
Pass an empty list ([]) instead of a file as a subworkflow parameter to work around this limitation.
- 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