- Nextflow
- Docker
NOTE If you plan to setup a basic server, then you can refer minimal-nextflow-setup
nextflow run https://github.com/nf-modules-hub/tb-profiler
file_pattern
By default, the process assumes the files to follow the *_{R1,R2}.fastq.gz
pattern, which could be customized using this option
nextflow run https://github.com/nf-modules-hub/tb-profiler --file_pattern './*_{1,2}.fastq.gz'
outdir
By default, it stores the result files locally inside the results
directory.
nextflow run https://github.com/nf-modules-hub/tb-profiler --outdir /path/to/custom/resultsDir
publish_dir_mode
By default, the pipeline publishes the results in the outdir
by copying the relevant output.
You can update this behavior by simply specifying the alternative such as move
or link
etc.
nextflow run https://github.com/nf-modules-hub/tb-profiler --publish_dir_mode move
For more information please refer Nextflow documentation
The sole purpose of process wrappers in nf-modules-hub
is to keep the code small, clean and hackable with some basic knowledge of nextflow
scripting.
If you have specific requirements, you are encouraged to fork/clone and update your version to accomodate your needs.
Contribution, in all forms, is most welcome!