nf-core/spatialvi
Pipeline for processing spatially-resolved gene counts with spatial coordinates and image data. Designed for 10x Genomics Visium transcriptomics.
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.
stringOptions related to Space Ranger execution and raw spatial data processing
Location of Space Ranger probeset file.
string^\S+\.csv$Location of Space Ranger reference directory. May be packed as tar.gz file.
stringhttps://cf.10xgenomics.com/supp/spatial-exp/refdata-gex-GRCh38-2020-A.tar.gzOptions specific to the analysis of Visium HD data.
Bin size for Visium HD data. Allowed values: 2, 8, 16.
integerFiltering settings and thresholds used by the pipeline
The minimum number of UMIs needed in a spot for that spot to pass the filtering.
integer500The minimum number of expressed genes in a spot needed for that spot to pass the filtering.
integer250The minimum number of spots in which a gene is expressed for that gene to pass the filtering.
integer1The maximum proportion of mitochondrial content that a spot is allowed to have to pass the filtering.
number20The minimum percentage of ribosomal content that a spot needs to have to pass the filtering (no filtering is done by default).
numberThe maximum proportion of haemoglobin content that a spot is allowed to have to pass the filtering (no filtering is done by default).
number100Normalization options used by the pipeline.
Target sum for normalization of counts per cell.
integerOptions for calculating highly variable genes.
The number of top highly variable genes to use for the analyses.
integer2000The method for identifying highly variable genes
stringOptions for principal component analyses used in the pipeline.
The number of principal components to use for downstream analyses.
integer50Whether to use highly variable genes only for principal component analyses.
booleanOptions for nearest neighbors calculations.
The number of nearest neighbors to use for the neighborhood graph calculation.
integer15The number of principal components to use for the nearest neighbors calculation.
integer50Options for the dimensionality reductions performed by the pipeline.
Minimium distance between points in the UMAP embedding, where lower values produces tigher clusters.
number0.5Scale of the UMAP embedding, where larger values spread points further away from each other.
number1Options for the clustering performed by the pipeline.
The resolution for the clustering of the spots.
number1Options for determinig spatially variable genes.
Statistical method to use for differential expression testing.
stringOptions for the various spatial analyses performed by the pipeline.
The coordinate type to use for spatial neighborhood enrichment.
stringNumber of neighborhoods to use for spatial neighborhood enrichment.
integer6The method to use for spatially variable gene autocorrelation.
stringThe number of top spatially variable genes to plot.
integer15Options related to aggregation of final data objects
Skip integration of per-sample objects into one and the associated report.
booleanThe integration method to use
stringThe resolution for the clustering of the spots after integration of samples.
number1Additional intermediate output files that can be optionally saved.
Save the extracted tar archive of the Space Ranger reference.
booleanSave extracted tar archives of input data.
booleanSkip downstream analyses.
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/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 colored 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.
stringDisplay the help message.
boolean,stringDisplay the full detailed help message.
booleanDisplay hidden parameters in the help message (only works when —help or —help_full are provided).
boolean