For a list of subcommands, run xeniumranger --help.
The Martian runtime options are available for Xenium Ranger relabel, resegment, and import-segmentation subcommands.
Argument option names and values should be separated by either a space or equal sign (i.e., --id=demo or --id demo). Arguments that specify files or paths may use either absolute or relative paths.
If a pipeline analysis is interrupted or throws an error, enter the command with a new --id, or delete the pipestance directory (named after --id) and the invocation .mro file to use the identical command.
Usage:
xeniumranger relabel --help
# Argument option names and values can be separated by a space or =
xeniumranger relabel [OPTIONS] --id=<ID> --xenium-bundle=<XENIUM_BUNDLE> \
--panel=<PANEL>
| Argument | Description |
|---|---|
--xenium-bundle | Required. File path to directory containing all required Xenium Onboard Analysis output files. |
--id | Required. Unique string to specify the name of the relabel output folder. May only include ASCII characters (alphanumeric, underscore, dash, period) and must not use whitespace, slash, quote, or comma characters. |
--panel | Required. New gene panel JSON file to use for relabeling transcripts with the correct gene. |
Usage:
xeniumranger resegment --help
# Argument option names and values can be separated by a space or =
xeniumranger resegment [OPTIONS] --id=<ID> --xenium-bundle=<XENIUM_BUNDLE>
| Argument | Description |
|---|---|
--xenium-bundle | Required. File path to directory containing all required Xenium Onboard Analysis output files. |
--id | Required. Unique string to specify the name of the resegment output folder. May only include ASCII characters (alphanumeric, underscore, dash, period) and must not use whitespace, slash, quote, or comma characters. |
--boundary-stain | Specify the name of the boundary stain to use or disable. Supported for cell segmentation staining workflow output bundles. Possible options are: "ATP1A1/CD45/E-Cadherin" (default) or "disable". |
--interior-stain | Specify the name of the interior stain to use or disable. Supported for cell segmentation staining workflow output bundles. Possible options are: "18S" (default) or "disable". |
--expansion-distance | Nuclei boundary expansion distance in µm. Default: 5 (Min: 0, Max: 15 if either --boundary-stain or --interior-stain are enabled and 100 if nucleus-expansion only). |
--dapi-filter | Minimum intensity in photoelectrons (pe) to filter nuclei. Default: 100 (appropriate range of values is 0 to 99th percentile of image stack or 1000, whichever is larger). |
--resegment-nuclei | Boolean to specify whether to rerun the latest Xenium Onboard Analysis nucleus segmentation algorithm (true) or to use existing nucleus segmentation masks in the cells.zarr file (false). Default: true. This parameter is deprecated and will be removed in a future release, see import-segmentation example for preferred method. |
Usage:
xeniumranger import-segmentation --help
# Argument option names and values can be separated by a space or =
xeniumranger import-segmentation [OPTIONS] --id=<ID> --xenium-bundle=<XENIUM_BUNDLE>
These import-segmentation arguments are specific to image-based segmentation inputs (i.e., polygons, masks).
| Argument | Description |
|---|---|
--xenium-bundle | Required. File path to directory containing all required Xenium Onboard Analysis output files. |
--id | Required. Unique string to specify the name of the import-segmentation output folder. May only include ASCII characters (alphanumeric, underscore, dash, period) and must not use whitespace, slash, quote, or comma characters. |
--expansion-distance | Nuclei boundary expansion distance in µm. Only for use when nucleus segmentation provided as input. Default: 5 (accepted range: 0 - 100). |
--nuclei | Label mask (TIFF or NPY), polygons of nucleus segmentations (GeoJSON FeatureCollection), or Xenium Onboard Analysis cells.zarr.zip (the nucleus masks as input). --nuclei will use nucleusGeometry polygon if it exists in the GeoJSON (i.e., for QuPath-like GeoJSON files), or geometry if it does not. Error if --transcript-assignment argument is used. |
--cells | Label mask (TIFF or NPY), polygons of cell segmentations (GeoJSON FeatureCollection), or Xenium Onboard Analysis cells.zarr.zip (the cell masks as input). Features with a non-cell objectType will be ignored. Error if --transcript-assignment argument is used. In Xenium Ranger v2.0, --nuclei no longer needs to be used with --cells. |
--coordinate-transform | Image alignment file containing similarity transform matrix (e.g., the _imagealignment.csv file exported from Xenium Explorer; read about the algorithm here). Works with segmentation results in polygon or label mask format. |
--units | Indicates whether segmentation results are in physical space ("microns") or pixel space ("pixel"). Default: "pixel". Must be set as "microns" if --coordinate-transform is used. |
These import-segmentation arguments are specific to transcript-based segmentation inputs. For example, Xenium Ranger supports a transcript CSV with cell assignments as input formatted like the segmentation.csv output from Baysor v0.6.
| Argument | Description |
|---|---|
--xenium-bundle | Required. File path to directory containing all required Xenium Onboard Analysis output files. |
--id | Required. Unique string to specify the name of the import-segmentation output folder. May only include ASCII characters (alphanumeric, underscore, dash, period) and must not use whitespace, slash, quote, or comma characters. |
--viz-polygons | Cell boundary polygons (GeoJSON) for visualization from Baysor. Required if --transcript-assignment argument used. Error if --cells or --nuclei arguments used. |
--transcript-assignment | Transcript CSV with cell assignment from Baysor. Error if --cells or --nuclei arguments are used. |
--units | Indicates whether segmentation results are in physical space ("microns") or pixel space ("pixel"). Default: "pixel". Must be set as "microns" for Baysor inputs. |
The Martian runtime options are available for Xenium Ranger relabel, resegment, and import-segmentation subcommands.
The Martian commands work the same as for other 10x Genomics pipelines (i.e., Cell Ranger, Space Ranger). For more information about certain parameters, please see these pages for job submission mode, cluster mode, and pipeline monitoring UI guidance.
Usage example with relabel:
xeniumranger relabel --id=example --xenium-bundle=/path/to/outputs \
--panel=/path/to/panel --jobmode=local \
--localcores=8 --localmem=32
| Argument | Description |
|---|---|
--jobmode | Job manager to use. Valid options: local (default), a cluster job mode (i.e., sge, lsf, slurm), or the path to a <jobmode>.template file. |
--localcores | Set max cores the pipeline may request at one time. Only applies to local jobs. |
--localmem | Set max GB the pipeline may request at one time. Only applies to local jobs. |
--localvmem | Set max virtual address space in GB for the pipeline. Only applies to local jobs. |
--mempercore | Reserve enough threads for each job to ensure enough memory will be available, assuming each core on your cluster has at least this much memory available. Only applies to cluster jobmodes. |
--maxjobs | Set max jobs submitted to the cluster at one time. Only applies in cluster jobmodes. |
--jobinterval | Set delay between submitting jobs to cluster, in ms. Only applies in cluster jobmodes. |
--overrides | The path to a JSON file that specifies stage-level overrides for cores and memory. Finer-grained than --localcores, --mempercore and --localmem. Contact support for an example override file. |
--uiport | The port to serve web UI at: http://localhost:PORT |
--disable-ui | Boolean to determine whether to serve the web UI (true, false). |
--noexit | Boolean to keep web UI running after pipestance completes or fails (true, false). |
--nopreflight | Boolean to skip all preflight checks. |
| Flag | Description |
|---|---|
--dry | Do not execute the pipeline. Generate a pipeline invocation (.mro) file and stop. |
Check your system’s compatibility with Xenium Ranger system requirements.
Usage: xeniumranger sitecheck > sitecheck.txt
| Flag | Description |
|---|---|
-h, --help | Show help message. |
--version | Show version. |
To use tarmri to generate a .mri.tgz file for a failed run, call tarmri and give it the path to the failed pipestance (run name specified by --id).
The .mri.tgz file contains a number of logs (including error messages, status reports, and information about the system) that are useful for troubleshooting failures. The .mri.tgz file does not contain sample data or analysis outputs.
Usage:
# Generate mri.tgz file for example analysis --id run1
xeniumranger-xenium1.6/external/cellranger/bin/tenkit/tarmri <path to>/run1
# Share mri.tgz file with 10x Support
xeniumranger upload <your email> <path to log.mri.tgz>
Upload a file to the 10x Genomics support team.
Usage: xeniumranger upload <your email> <file>