nf-core/nanostring
An analysis pipeline for Nanostring nCounter expression data.
See the advisory entry for more information.
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$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})$MultiQC report title. Printed as page header, used for filename if not otherwise specified.
stringDefine how the pipeline should process the data.
The column used for heatmap generation, specifying the rows. The values in this column have to be unique.
stringSAMPLE_IDPath to YAML file (list, one item per line) to specify which genes should be used for the gene-count heatmap.
stringParameters that influence normalization outcome
The method to use for normalization of nCounter data.
stringGEOConfiguration to define how to compute gene scores
This selects the algorithm for computing the respective gene score. Default is ‘plage.dir’.
stringplage.dirThis sets the YAML to be used for computing the gene scores. Needs both a name for each set of genes and respective genes to be selected.
stringAllows to specify options to skip parts of the pipeline
Skip creating the heatmap
booleanReference genome related files and options required for the workflow.
Name of iGenomes reference.
stringDo not load the iGenomes reference config.
booleanThe base path to the igenomes reference files
strings3://ngi-igenomes/igenomes/Parameters 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/masterInstitutional config name.
stringInstitutional config description.
stringInstitutional config contact information.
stringInstitutional config URL link.
stringLess common options for the pipeline, typically set in a config file.
Display version and exit.
booleanMethod used to save pipeline results to output directory.
stringEmail address for completion summary, only when pipeline fails.
string^([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})$Send plain-text email instead of HTML.
booleanFile size limit when attaching MultiQC reports to summary emails.
string25.MB^\d+(\.\d+)?\.?\s*(K|M|G|T)?B$Do not use coloured log outputs.
booleanIncoming hook URL for messaging service
stringCustom 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
booleantrueBase URL or local path to location of pipeline test dataset files
stringhttps://raw.githubusercontent.com/nf-core/test-datasets/Suffix to add to the trace report filename. Default is the date and time in the format yyyy-MM-dd_HH-mm-ss.
string