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.

required
type: string
pattern: ^\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.

Path to comma-separated file containing information about the BAM files in the experiment.

type: string
pattern: ^\S+\.csv$

You will need to create a design file with information about the BAM files in your experiment before running the pipeline. Use this parameter to specify its location. It has to be a comma-separated file with 4 columns, and a header row. See usage docs.

Path to comma-separated file containing the counts for the samples in the experiment. Can also be a file containing just gene identifiers. In this case, count values need to be referenced in the counts_design file.

type: string
pattern: ^\S+\.(csv|txt)$

You will need to create a counts file with the counts for 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 a header row. See usage docs.

Path to comma-separated file containing information about the counts file.

type: string
pattern: ^\S+\.csv$

You will need to create a counts design file with information about the counts file 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.

required
type: string

Email address for completion summary.

type: string
pattern: ^([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.

type: string

Options for the pipeline itself.

Merge samples with the same condition and assay.

type: boolean

If you have multiple samples with the same condition and assay, you can set this parameter to true to merge them into a single sample. This is useful if you have technical replicates and want to combine them into a single sample for analysis.

Minimum number of samples that a peak has to occur in to keep it while merging.

type: integer
default: 1

If you have multiple samples with the same condition and assay and use the --merge_samples parameter, you can set this parameter to the minimum number of samples that a peak has to occur in to keep it while merging.

Size of the window to search for binding sites.

type: integer
default: 50000

Size of the window to search for binding sites. The default value is 50000.

Use decay in STARE

type: boolean
default: true

Use decay in STARE. The default value is true.

Method to aggregate expression values.

type: string
default: mean

Method to aggregate expression values. The default value is mean.

Method to aggregate affinity values.

type: string
default: max

Method to aggregate affinity values. The default value is max.

Number of ChromHMM states.

type: integer
default: 10

Number of ChromHMM states. The default value is 10.

Minimum number of total counts to keep a gene in the analysis.

type: integer
default: 50

Minimum number of total counts to keep a gene in the analysis. The default value is 50.

Minimum TPM to keep a gene in the analysis.

type: number
default: 1

Minimum TPM to keep a gene in the analysis. The default value is 1.

Minimum number of total counts to keep a transcription factor in the analysis.

type: integer
default: 50

Minimum number of total counts to keep a transcription factor in the analysis. The default value is 50.

Minimum TPM to keep a transcription factor in the analysis.

type: number
default: 1

Minimum TPM to keep a transcription factor in the analysis. The default value is 1.

Number of outer folds for dynamite.

type: integer
default: 3

Number of outer folds for dynamite. The default value is 3.

Number of inner folds for dynamite.

type: integer
default: 6

Number of inner folds for dynamite. The default value is 6.

Alpha value for dynamite.

type: number
default: 0.1

Alpha value for dynamite. The default value is 0.1.

Randomize the data for dynamite.

type: boolean
default: false

Randomize the data for dynamite. The default value is false.

Minimum regression value for dynamite.

type: number
default: 0.1

Minimum regression value for dynamite. The default value is 0.1.

Alpha value for the Mann-Whitney U test.

type: number
default: 0.05

Alpha value for the Mann-Whitney U test. The default value is 0.05.

Reference genome related files and options required for the workflow.

Name of iGenomes reference.

type: 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.

type: string
pattern: ^\S+\.fn?a(sta)?(\.gz)?$

This parameter is mandatory if --genome is not specified.

Path to GTF gene annotation file.

type: string
pattern: ^\S+\.gtf(\.gz)?$

This parameter is mandatory if --genome is not specified.

Path to blacklist regions file.

type: string
pattern: ^\S+\.bed(\.gz)?$

This parameter is mandatory if --genome is not specified.

Path to PWMs file.

type: string
pattern: ^\S+\.txt(\.gz)?$

This parameter is mandatory if --genome is not specified.

Path to ROSE UCSC file.

type: string
pattern: ^\S+\.ucsc$

This parameter is mandatory if --genome is not specified and input_bam is defined.

Do not load the iGenomes reference config.

hidden
type: 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.

Parameters used to describe centralised config profiles. These should not be edited.

Git commit id for Institutional configs.

hidden
type: string
default: master

Base directory for Institutional configs.

hidden
type: string
default: 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.

hidden
type: string

Institutional config description.

hidden
type: string

Institutional config contact information.

hidden
type: string

Institutional config URL link.

hidden
type: string

Set the top limit for requested resources for any single job.

Maximum number of CPUs that can be requested for any single job.

hidden
type: integer
default: 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.

hidden
type: string
default: 128.GB
pattern: ^\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.

hidden
type: string
default: 240.h
pattern: ^(\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.

hidden
type: boolean

Display version and exit.

hidden
type: boolean

Method used to save pipeline results to output directory.

hidden
type: 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.

hidden
type: string
pattern: ^([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.

hidden
type: boolean

File size limit when attaching MultiQC reports to summary emails.

hidden
type: string
default: 25.MB
pattern: ^\d+(\.\d+)?\.?\s*(K|M|G|T)?B$

Do not use coloured log outputs.

hidden
type: boolean

Incoming hook URL for messaging service

hidden
type: string

Incoming hook URL for messaging service. Currently, MS Teams and Slack are supported.

Custom config file to supply to MultiQC.

hidden
type: string

Custom logo file to supply to MultiQC. File name must also be set in the MultiQC config file

hidden
type: string

Custom MultiQC yaml file containing HTML including a methods description.

type: string

Boolean whether to validate parameters against the schema at runtime

hidden
type: boolean
default: true

Show all params when using --help

hidden
type: boolean

By 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.

hidden
type: boolean

By default, when an unrecognised parameter is found, it returns a warinig.

Validation of parameters in lenient more.

hidden
type: boolean

Allows string values that are parseable as numbers or booleans. For further information see JSONSchema docs.