nf-core/riboseq
Pipeline for the analysis of ribosome profiling, or Ribo-seq (also named ribosome footprinting) data.
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.
A CSV file describing sample contrasts
string^\S+\.(csv|tsv|txt)$This file is used to define groups of samples from 'input' to compare. It must contain at least the columns 'variable', 'reference' and 'target', and optionally a 'batch' column. 'variable' and 'batch' must be columns in the input sample sheet, 'reference' and 'target' are values in the column indicated by 'variable'.
The output directory where the results will be saved. You have to use absolute paths to storage on Cloud infrastructure.
stringEmail 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.
stringReference genome related files and options required for the workflow.
Name of iGenomes reference.
stringIf using a reference genome configured in the pipeline using iGenomes (not recommended), 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 the appropriate alignment index available this will be generated for you automatically. Combine with --save_reference to save alignment index for future runs.
Path to GTF annotation file.
string^\S+\.gtf(\.gz)?$This parameter is mandatory if --genome is not specified.
Path to GFF3 annotation file.
string^\S+\.gff(\.gz)?$This parameter must be specified if --genome or --gtf are not specified.
Path to FASTA transcriptome file.
string^\S+\.fn?a(sta)?(\.gz)?$FASTA file to concatenate to genome FASTA file e.g. containing spike-in sequences.
string^\S+\.fn?a(sta)?(\.gz)?$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.
Path to directory or tar.gz archive for pre-built STAR index.
stringPath to directory or tar.gz archive for pre-built Salmon index.
stringSpecify if your GTF annotation is in GENCODE format.
booleanBy default, the pipeline uses the gene_name field to obtain additional gene identifiers from the input GTF file when running Salmon.
stringgene_nameThis 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 when running Salmon.
stringgene_idDirectory / URL base for iGenomes references.
strings3://ngi-igenomes/igenomesDo not load the iGenomes reference config.
booleanDo 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.
Specifies the trimming tool to use - available options are 'trimgalore' and 'fastp'.
stringExtra arguments to pass to Trim Galore! command in addition to defaults defined by the pipeline.
stringExtra arguments to pass to fastp command in addition to defaults defined by the pipeline.
stringMinimum number of trimmed reads below which samples are removed from further processing. Some downstream steps in the pipeline will fail if this threshold is too low.
integer10000Options for filtering reads prior to alignment
Path to comma-separated file containing a list of reference genomes to filter reads against with BBSplit. You have to also explicitly set --skip_bbsplit false if you want to use BBSplit.
stringThe file should contain 2 columns: short name and full path to reference genome(s) e.g.
mm10,/path/to/mm10.fa
ecoli,/path/to/ecoli.fa
Path to directory or tar.gz archive for pre-built BBSplit index.
stringThe BBSplit index will have to be built at least once with this pipeline (see --save_reference to save index). It can then be provided via --bbsplit_index for future runs.
Path to directory or tar.gz archive for pre-built sortmerna index.
stringThe sortmerna index will have to be built at least once with this pipeline (see --save_reference to save index). It can then be provided via --sortmerna_index for future runs.
Enable the removal of reads derived from ribosomal RNA using SortMeRNA.
booleantrueAny 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.txtBy 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.
Options for processing reads with unique molecular identifiers
Enable UMI-based read deduplication.
booleanUMI pattern to use. Can be either 'string' (default) or 'regex'.
stringstringMore 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.
stringMore details can be found in the UMI-tools documentation.
The UMI barcode pattern to use if the UMI is located in read 2.
stringAfter UMI barcode extraction discard either R1 or R2 by setting this parameter to 1 or 2, respectively.
integerThe character that separates the UMI in the read name. Most likely a colon if you skipped the extraction with UMI-tools and used other software.
stringMethod to use to determine read groups by subsuming those with similar UMIs. All methods start by identifying the reads with the same mapping position, but treat similar yet nonidentical UMIs differently.
stringGenerate output stats when running "umi_tools dedup".
booleanIt can be quite time consuming generating these output stats - see #827.
Options to adjust parameters and filtering criteria for read alignments.
Specifies the alignment algorithm to use - available options are currently 'star'.
stringKmer length passed to indexing step of pseudoaligners
integer31Failure to set a good kmer size could cause issues with quantification with Kallisto or Salmon. This is mostly an issue for short reads (<50bp), where the default kmer size of 31 is an problem.
Create a CSI index for BAM files instead of the traditional BAI index. This will be required for genomes with larger chromosome sizes.
booleanWhen using pre-built STAR indices do not re-extract and use splice junctions from the GTF file.
booleanOverride Salmon library type inferred based on strandedness defined in meta object.
stringSee Salmon docs.
Minimum percentage of uniquely mapped reads below which samples are removed from further processing.
number5Some 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.
stringExtra arguments to pass to STAR alignment command in addition to defaults defined by the pipeline. Only available for the STAR-Salmon route.
stringExtra arguments to pass to Salmon quant command in addition to defaults defined by the pipeline.
stringOptions related to riboseq-specific analysis modules
Extra arguments to pass to the ribotish quality command in addition to defaults defined by the pipeline.
stringExtra arguments to pass to the ribotish predict command in addition to defaults defined by the pipeline.
stringExtra arguments to pass to the ribotricer prepare-orfs command in addition to defaults defined by the pipeline.
stringExtra arguments to pass to the ribotricer detect-orfs command in addition to defaults defined by the pipeline.
stringExtra arguments to pass to anota2seq in addition to defaults defined by the pipeline.
stringAdditional output files produces as intermediates that can be saved
Save FastQ files after merging re-sequenced libraries in the results directory.
booleanIf this option is specified, intermediate FastQ and BAM files produced by UMI-tools are also saved in the results directory.
booleanIf this option is specified, intermediate FastQ files containing non-rRNA reads will be saved in the results directory.
booleanIf this option is specified, FastQ files split by reference will be saved in the results directory.
booleanIf generated by the pipeline save the STAR index in the results directory.
booleanIf an alignment 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.
Save the trimmed FastQ files in the results directory.
booleanBy 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.
Save the intermediate BAM files from the alignment step.
booleantrueBy 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.
Where possible, save unaligned reads from either STAR, HISAT2 or Salmon to the results directory.
booleanThis may either be in the form of FastQ or BAM files depending on the options available for that particular tool.
Options to skip various steps within the workflow.
Skip filtering of GTF for valid scaffolds and/ or transcript IDs.
booleanIf you're confident on the validity of the GTF with respect to the genome fasta file, or wish to disregard failures thriggered by the filtering module, activate this option.
Skip the 'transcript_id' checking component of the GTF filtering script used in the pipeline.
booleanSkip BBSplit for removal of non-reference genome reads.
booleantrueSkip the UMI extraction from the read in case the UMIs have been moved to the headers in advance of the pipeline run.
booleanSkip the adapter trimming step.
booleanUse 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.
Skip all of the alignment-based processes within the pipeline.
booleanSkip picard MarkDuplicates step.
booleanSkip FastQC.
booleanSkip MultiQC.
booleanSkip all QC steps except for MultiQC.
booleanSkip Ribo-TISH.
booleanSkip Riboricer.
booleanParameters used to describe centralised config profiles. These should not be edited.
Git commit id for Institutional configs.
stringmasterBase directory for Institutional configs.
stringhttps://raw.githubusercontent.com/nf-core/configs/masterIf 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.
stringInstitutional config description.
stringInstitutional config contact information.
stringInstitutional config URL link.
stringBase path / URL for data used in the test profiles
stringhttps://raw.githubusercontent.com/nf-core/test-datasets/riboseq/testdata/Warning: The -profile test samplesheet file itself contains remote paths. Setting this parameter does not alter the contents of that file.
Set the top limit for requested resources for any single job.
Maximum number of CPUs that can be requested for any single job.
integer16Use 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.
string128.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.
string240.h^(\d+\.?\s*(s|m|h|d|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.
booleanDisplay version and exit.
booleanMethod used to save pipeline results to output directory.
stringThe 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.
booleanFile size limit when attaching MultiQC reports to summary emails.
string25.MBDo not use coloured log outputs.
booleanIncoming hook URL for messaging service
stringIncoming hook URL for messaging service. Currently, MS Teams and Slack are supported.
Custom config file to supply to MultiQC.
stringCustom logo file to supply to MultiQC. File name must also be set in the MultiQC config file
stringCustom MultiQC yaml file containing HTML including a methods description.
stringBoolean whether to validate parameters against the schema at runtime
booleantrueShow all params when using --help
booleanBy default, parameters set as hidden in the schema are not shown on the command line when a user runs with --help. Specifying this option will tell the pipeline to show all parameters.
Validation of parameters fails when an unrecognised parameter is found.
booleanBy default, when an unrecognised parameter is found, it returns a warinig.
Validation of parameters in lenient more.
booleanAllows string values that are parseable as numbers or booleans. For further information see JSONSchema docs.