nf-core/rnafusion
RNA-seq analysis pipeline for detection of gene-fusions
2.0.0
). The latest
stable release is
3.0.2
.
Skip analysis steps
Skip QC steps
boolean
Skip visualisation steps
boolean
Define where the pipeline should find input data and save output data.
Path to comma-separated file containing information about the samples in the experiment.
string
^\S+\.csv$
You will need to create a design file with information about the samples in your experiment before running the pipeline. Use this parameter to specify its location. It has to be a comma-separated file with 3 columns, and a header row. See usage docs.
The output directory where the results will be saved. You have to use absolute paths to storage on Cloud infrastructure.
string
Email address for completion summary.
string
^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$
Set this parameter to your e-mail address to get a summary e-mail with details of the run sent to you when the workflow exits. If set in your user config file (~/.nextflow/config
) then you don't need to specify this on the command line for every run.
MultiQC report title. Printed as page header, used for filename if not otherwise specified.
string
Specifies which analysis type for the pipeline - either build references or analyse data
boolean
Path to reference folder
string
ensembl version
integer
105
If set, starfusion references are built from scratch instead of downloaded (default)
boolean
Read length
integer
100
Build or run all references/analyses
boolean
Build or run arriba references/analyses
boolean
Path to arriba references
string
Path to arriba reference blacklist
string
Path to arriba reference protein domain
string
Path to arriba output
string
Path to ensembl references
string
Build or run fusioncatcher references/analyses
boolean
Path to fusioncatcher output
string
Path to fusioncatcher references
string
Feed filtered fusionreport fusions to fusioninspector
boolean
Build fusionreport references
boolean
Path to fusionreport references
string
Build or run pizzly references/analyses
boolean
Path to pizzly output
string
Path to pizzly references
string
Build or run squid references/analyses
boolean
Path to squid output
string
Path to squid references
string
Build or run starfusion references/analyses
boolean
Path to starfusion output
string
Path to starfusion references
string
Build or run starindex references/analyses
boolean
Path to starindex references
string
COSMIC username
string
COSMIC password
string
Reference genome related files and options required for the workflow.
Name of iGenomes reference.
string
If using a reference genome configured in the pipeline using iGenomes, use this parameter to give the ID for the reference. This is then used to build the full paths for all required reference genome files e.g. --genome GRCh38
.
See the nf-core website docs for more details.
Path to FASTA genome file.
string
^\S+\.fn?a(sta)?(\.gz)?$
This parameter is mandatory if --genome
is not specified. If you don't have a BWA index available this will be generated for you automatically. Combine with --save_reference
to save BWA index for future runs.
Path to GTF genome file.
string
^\S+\.gtf?(\.gz)?$
Path to GTF genome file.
string
^\S+\.gtf?(\.gz)?$
Path to GTF genome file.
string
^\S+\.fn?a(sta)?(\.gz)?$
Path to GTF genome file.
string
^\S+\.refflat?$
Parameters used to describe centralised config profiles. These should not be edited.
Git commit id for Institutional configs.
string
master
Base directory for Institutional configs.
string
https://raw.githubusercontent.com/nf-core/configs/master
If you're running offline, Nextflow will not be able to fetch the institutional config files from the internet. If you don't need them, then this is not a problem. If you do need them, you should download the files from the repo and tell Nextflow where to find them with this parameter.
Institutional config name.
string
Institutional config description.
string
Institutional config contact information.
string
Institutional config URL link.
string
Set the top limit for requested resources for any single job.
Maximum number of CPUs that can be requested for any single job.
integer
16
Use to set an upper-limit for the CPU requirement for each process. Should be an integer e.g. --max_cpus 1
Maximum amount of memory that can be requested for any single job.
string
128.GB
^\d+(\.\d+)?\.?\s*(K|M|G|T)?B$
Use to set an upper-limit for the memory requirement for each process. Should be a string in the format integer-unit e.g. --max_memory '8.GB'
Maximum amount of time that can be requested for any single job.
string
240.h
^(\d+\.?\s*(s|m|h|day)\s*)+$
Use to set an upper-limit for the time requirement for each process. Should be a string in the format integer-unit e.g. --max_time '2.h'
Less common options for the pipeline, typically set in a config file.
Display help text.
boolean
Method used to save pipeline results to output directory.
string
The Nextflow publishDir
option specifies which intermediate files should be saved to the output directory. This option tells the pipeline what method should be used to move these files. See Nextflow docs for details.
Email address for completion summary, only when pipeline fails.
string
^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$
An email address to send a summary email to when the pipeline is completed - ONLY sent if the pipeline does not exit successfully.
Send plain-text email instead of HTML.
boolean
File size limit when attaching MultiQC reports to summary emails.
string
25.MB
^\d+(\.\d+)?\.?\s*(K|M|G|T)?B$
Do not use coloured log outputs.
boolean
Custom config file to supply to MultiQC.
string
Directory to keep pipeline Nextflow logs and reports.
string
${params.outdir}/pipeline_info
Boolean whether to validate parameters against the schema at runtime
boolean
true
Show all params when using --help
boolean
Run this workflow with Conda. You can also use '-profile conda' instead of providing this parameter.
boolean
Use to pull docker containers to run with singularity
boolean
Sequencing center
boolean
This will reported in the BAM header as CN
Sequencing platform
boolean
This will reported in the BAM header as PL.
Whether to ignore the GTF in STAR alignment
boolean
Setting false will use GTF file for STAR alignment