nf-core/rnaseq
RNA sequencing analysis pipeline using STAR, RSEM, HISAT2 or Salmon with gene/isoform counts and extensive quality control.
3.0
). The latest
stable release is
3.15.0
.
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
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 5 columns, and a header row. See usage docs.
Path to the output directory where the results will be saved.
string
./results
File containing SRA/ENA/GEO identifiers one per line in order to download their associated FastQ files.
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
Only download metadata for public data database ids and don't download the FastQ files.
boolean
Save FastQ files after merging re-sequenced libraries in the results directory.
boolean
Options for processing reads with unique molecular identifiers
Enable UMI-based read deduplication.
boolean
UMI pattern to use. Can be either 'string' (default) or 'regex'.
string
string
More details can be found in the UMI-tools documentation.
The UMI barcode pattern to use e.g. 'NNNNNN' indicates that the first 6 nucleotides of the read are from the UMI.
string
More details can be found in the UMI-tools documentation.
If this option is specified, intermediate FastQ and BAM files produced by UMI-tools are also saved in the results directory.
boolean
Options for filtering reads prior to alignment
Enable the removal of reads derived from ribosomal RNA using SortMeRNA.
boolean
Any patterns found in the sequences defined by the '--ribo_database_manifest' parameter will be used.
Text file containing paths to fasta files (one per line) that will be used to create the database for SortMeRNA.
string
${projectDir}/assets/rrna-db-defaults.txt
By default, rRNA databases defined in the SortMeRNA GitHub repo are used. You can see an example in the pipeline Github repository in assets/rrna-default-dbs.txt
.
Please note that commercial/non-academic entities require licensing for SILVA
for these default databases.
If this option is specified, intermediate FastQ files containing non-rRNA reads will be saved in the results directory.
boolean
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
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 annotation file.
string
This parameter is mandatory if --genome
is not specified.
Path to GFF3 annotation file.
string
This parameter must be specified if --genome
or --gtf
are not specified.
Path to BED file containing gene intervals. This will be created from the GTF file if not specified.
string
Path to FASTA transcriptome file.
string
FASTA file to concatenate to genome FASTA file e.g. containing spike-in sequences.
string
If provided, the sequences in this file will get concatenated to the existing genome FASTA file, a GTF file will be automatically created using the entire sequence as the gene, transcript, and exon features, and any alignment index will get created from the combined FASTA and GTF. It is recommended to save the reference with --save_reference
to re-use the index for future runs so you do not need to create it again.
Splice sites file required for HISAT2.
string
Path to directory or tar.gz archive for pre-built STAR index.
string
Path to directory or tar.gz archive for pre-built HISAT2 index.
string
Path to directory or tar.gz archive for pre-built RSEM index.
string
Path to directory or tar.gz archive for pre-built Salmon index.
string
Memory passed to HISAT2 build process.
integer
200
Specify if your GTF annotation is in GENCODE format.
boolean
If your GTF file is in GENCODE format and you would like to run Salmon i.e. --pseudo_aligner salmon
, you will need to provide this parameter in order to build the Salmon index appropriately.
By default, the pipeline uses the gene_name
field to obtain additional gene identifiers from the input GTF file.
string
gene_name
This behaviour can be modified by specifying --gtf_extra_attributes
when running the pipeline. Note that you can also specify more than one desired value, separated by a comma e.g. --gtf_extra_attributes gene_id,...
.
Define the attribute type used to group features in the GTF file.
string
gene_id
Define the attribute type used to group feature types in the GTF file.
string
gene_biotype
By default, the pipeline assigns reads based on the 'exon' attribute within the GTF file.
string
exon
You can change this parameter for example, for nuclear RNA-seq where you may want to count reads in introns as well as exons using '--gtf_count_type transcript'.
If generated by the pipeline save the BWA index in the results directory.
boolean
If the BWA index is generated by the pipeline use this parameter to save it to your results folder. These can then be used for future pipeline runs, reducing processing times.
Directory / URL base for iGenomes references.
string
s3://ngi-igenomes/igenomes/
Do not load the iGenomes reference config.
boolean
Do not load igenomes.config
when running the pipeline. You may choose this option if you observe clashes between custom parameters and those supplied in igenomes.config
.
Options to adjust read trimming criteria.
Instructs Trim Galore to remove bp from the 5' end of read 1 (or single-end reads).
integer
Instructs Trim Galore to remove bp from the 5' end of read 2 (paired-end reads only).
integer
Instructs Trim Galore to remove bp from the 3' end of read 1 AFTER adapter/quality trimming has been performed.
integer
Instructs Trim Galore to remove bp from the 3' end of read 2 AFTER adapter/quality trimming has been performed.
integer
Instructs Trim Galore to apply the --nextseq=X option, to trim based on quality after removing poly-G tails.
integer
This enables the option Cutadapt --nextseq-trim=3'CUTOFF
option via Trim Galore, which will set a quality cutoff (that is normally given with -q instead), but qualities of G bases are ignored. This trimming is in common for the NextSeq- and NovaSeq-platforms, where basecalls without any signal are called as high-quality G bases.
Skip the adapter trimming step.
boolean
Use this if your input FastQ files have already been trimmed outside of the workflow or if you're very confident that there is no adapter contamination in your data.
Save the trimmed FastQ files in the results directory.
boolean
By default, trimmed FastQ files will not be saved to the results directory. Specify this flag (or set to true in your config file) to copy these files to the results directory when complete.
Options to adjust parameters and filtering criteria for read alignments.
Specifies the alignment algorithm to use - available options are 'star_salmon', 'star_rsem' and 'hisat2'.
string
Specifies the pseudo aligner to use - available options are 'salmon'. Runs in addition to '--aligner'.
string
When using pre-built STAR indices do not re-extract and use splice junctions from the GTF file.
boolean
Minimum percentage of uniquely mapped reads below which samples are removed from further processing.
integer
5
Some downstream steps in the pipeline will fail if this threshold is too low.
Sequencing center information to be added to read group of BAM files.
string
Perform reference-guided de novo assembly of transcripts using StringTie i.e. dont restrict to those in GTF file.
boolean
Where possible, save unaligned reads from either STAR, HISAT2 or Salmon to the results directory.
boolean
This may either be in the form of FastQ or BAM files depending on the options available for that particular tool.
Save the intermediate BAM files from the alignment step.
boolean
By default, intermediate BAM files will not be saved. The final BAM files created after the appropriate filtering step are always saved to limit storage usage. Set this parameter to also save other intermediate BAM files.
Skip picard MarkDuplicates step.
boolean
Skip all of the alignment-based processes within the pipeline.
boolean
Options to skip various steps within the workflow.
Specify the RSeQC modules to run.
string
bam_stat,inner_distance,infer_experiment,junction_annotation,junction_saturation,read_distribution,read_duplication
Skip bigWig file creation.
boolean
Skip StringTie.
boolean
Skip FastQC.
boolean
Skip Preseq.
boolean
Skip dupRadar.
boolean
Skip Qualimap.
boolean
Skip RSeQC.
boolean
Skip additional featureCounts process for biotype QC.
boolean
Skip DESeq2 PCA and heatmap plotting.
boolean
Skip MultiQC.
boolean
Skip all QC steps except for MultiQC.
boolean
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 configs hostname.
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
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
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
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
Arguments passed to Nextflow clusterOptions.
string
Instead of directly downloading Singularity images for use with Singularity, force the workflow to pull and convert Docker containers instead.
boolean
This may be useful for example if you are unable to directly pull Singularity containers to run the pipeline due to http/https proxy issues.
Run this workflow with Conda. You can also use '-profile conda' instead of providing this parameter.
boolean