<LinkableSection id={"overview"} title={"Hardware"}>

Xenium Ranger pipelines run on Linux systems that meet these minimum requirements:

- 8-core Intel or AMD processor (32 cores recommended) with `avx2`
- 64GB RAM (128GB recommended)
- 1TB free disk space
- 64-bit CentOS 7 and later/RedHat 7.4 or Ubuntu 16.04 and later. See the [10x Genomics OS Support](/support/software/cell-ranger/latest/miscellaneous/cr-os-requirements) page on the Cell Ranger support site for additional details.

Running `xeniumranger import-segmentation` with the following tissue area and input data have higher minimum memory requirements:

| Tissue area                                              | Input                                                 | Minimum memory |
| -------------------------------------------------------- | ----------------------------------------------------- | -------------- |
| 1cm<sup>2</sup> dataset (e.g., full coronal mouse brain) | Nucleus and cell label mask (e.g., from Cellpose)     | 64GB RAM       |
| Entire well                                              | Nucleus and cell label mask                           | 256GB RAM      |
| Entire well                                              | Nucleus and cell boundary (e.g., GeoJSON from QuPath) | 128GB RAM      |

The pipeline can also run on clusters that meet these additional minimum requirements:

- Shared filesystem (e.g. NFS)
- Slurm batch scheduling system

</LinkableSection>

<LinkableSection id={"resource-limits"} title={"Resource limits"}>

- Xenium Ranger runs with `--jobmode=local` by default, using 90% of available memory and all available cores. To restrict resource usage, please see the `--localcores` and `--localmem` arguments for `xeniumranger` subcommands.
- In-house Xenium Ranger testing uses the following settings and we recommend customers do the same: `--localcores=32` and `--localmem=128`.
- Many Linux systems have default user limits (ulimits) for maximum open files and maximum user processes as low as 1024 or 4096. Because Xenium Ranger spawns multiple processes per core, jobs that use a large number of cores can exceed these limits. 10x Genomics recommends higher limits.

| **Limit**        | **Recommendation**                        |
| ---------------- | ----------------------------------------- |
| user open files  | 16k                                       |
| system max files | 10k per GB RAM available to Xenium Ranger |
| user processes   | 64 per core available to Xenium Ranger    |

</LinkableSection>

<LinkableSection id={"computing-options"} title={"Computing options"}>

There are three primary ways to run Xenium Ranger:

1. **Single server**: Xenium Ranger can run directly on a dedicated server. This is the most straightforward approach and the easiest to troubleshoot. The majority of the information on this website uses the single server approach.
2. **[Job submission mode](/support/software/xenium-ranger/2.0/advanced/XR-job-submission-mode)**: Xenium Ranger can run using a _single_ node on the cluster. Less cluster coordination is required since all work is done on the same node. This method works well even with job schedulers that are not officially supported.
3. **[Cluster mode](/support/software/xenium-ranger/2.0/advanced/XR-cluster-mode)**: Xenium Ranger can run using _multiple_ nodes on the cluster. This method provides high performance, but is difficult to troubleshoot since cluster setup varies among institutions.

Recommendations and requirements, in order of computational speed (left to right):
| | Cluster Mode | Job Submission Mode | Single Server |
|---|---|---|----|
| **Recommended for** | Organizations using an HPC with SLURM for job scheduling | Organizations using an HPC | Users without access to an HPC |
| **Compute details** | Splits each analysis across multiple compute nodes to decrease run time | Runs each analysis on a single compute node | Runs each analysis directly on a dedicated server |
| **Requirements** | HPC with SLURM for job scheduling | HPC with most job schedulers |Linux computer with minimum 8 cores & 64 GB RAM (but see [above](#overview)) |

</LinkableSection>

<LinkableSection id={"time-trials"} title={"How memory affects runtime"}>

These plots are based on time trials using [Amazon EC2 instances](https://aws.amazon.com/ec2/instance-types) and Xenium Ranger v2.0.0.

<SupportCallout level={"info"}>The plots will be updated for subsequent releases of Xenium Ranger if pipeline performance changes significantly.</SupportCallout>
<br />

Shown below is a `xeniumranger resegment` analysis for a 140 FOV Xenium In Situ Gene Expression dataset:

- Wall time as a function of memory

<Image src={"https://cdn.10xgenomics.com/image/upload/v1713894429/software-support/Xenium-Ranger/xr2.0-final-resegment-140-walltime-as-memory.png"} />

- Wall time as a function of threads

<Image src={"https://cdn.10xgenomics.com/image/upload/v1713894429/software-support/Xenium-Ranger/xr2.0-final-resegment-140-walltime-as-threads.png"} />

Shown below is a `xeniumranger resegment` analysis for a 97 FOV Xenium In Situ Gene Expression with Cell Segmentation Staining dataset:

- Wall time as a function of memory

<Image src={"https://cdn.10xgenomics.com/image/upload/v1713894430/software-support/Xenium-Ranger/xr2.0-final-resegment-97-walltime-as-memory.png"} />

- Wall time as a function of threads

<Image src={"https://cdn.10xgenomics.com/image/upload/v1713894428/software-support/Xenium-Ranger/xr2.0-final-resegment-97-walltime-as-threads.png"} />

</LinkableSection>


Hardware

Resource limits

Computing options

How memory affects runtime

Xenium Ranger

Gene Expression

Analyze Xenium In Situ Gene Expression data with a set of easy-to-use analysis pipelines.

System Requirements

<LinkableSection id={"v-2-0-1"} title={"v2.0.1 (June 10, 2024)"}>

- Fixed a bug that caused `cell_ids` to be misassigned in `transcripts.csv.gz` and `transcripts.parquet` when importing transcript assignments (e.g. from Baysor) with `import-segmentation`. This bug also resulted in erroneous cell-feature matrix files and erroneous counts in `cells.csv.gz`. Any datasets that were segmented with _transcript-based methods_, such as Baysor or Proseg, and _used Xenium Ranger v2.0_ to import transcript assignments, should re-run the analysis using Xenium Ranger v2.0.1.
- Fixed a bug to ensure interior stain-based expansion extends all the way to the neighboring cell's boundary in `resegment`.

</LinkableSection>

<LinkableSection id={"v-2-0-0"} title={"v2.0 (April 25, 2024)"}>

- The expansion-distance parameter default is now 5 &micro;m instead of 15 &micro;m for the `resegment` and `import-segmentation` pipelines.
- Segmentation algorithm updates for the `resegment` pipeline:
  - Reanalyze cell segmentation staining workflow data by adjusting the nuclear expansion distance and/or boundary or interior stain used for multimodal cell segmentation, the cell segmentation algorithm introduced in [XOA v2.0](/support/software/xenium-onboard-analysis/latest/release-notes/release-notes-for-xoa). Suboptimal or unsuitable stains can be excluded from the segmentation algorithm by specifying the `interior-stain` or `boundary-stain` arguments.
  - Updated nucleus segmentation ML model to match update in XOA v2.0.
- Updates for `import-segmentation` pipeline:
  - The `xeniumranger resegment --resegment-nuclei` option is deprecated and will be removed in future releases. `resegment` will always resegment nuclei from the input DAPI image. To use the nucleus segmentation from input data and adjust expansion distance, the preferred method is to run `xeniumranger import-segmentation` with `--expansion-distance` and `--nuclei=cells.zarr.zip`, which will use the nucleus segmentation masks from `cells.zarr.zip` file.
  - The `--nuclei` argument no longer needs to be used with `--cells`.
  - The `--cells` and `--nuclei` arguments support `cells.zarr.zip` format and will use the cell and nucleus masks for transcript assignment.
  - New metrics provided in `metrics_summary.csv`: "Number of cell non-simple polygons", "Number of cell multipolygons", "Number of nucleus non-simple polygons", "Number of nucleus multipolygons", "Segmented cell imported fraction", and "Segmented cell imported count". The "Number of cells from imported segmentation" is also reported in the `analysis_summary.html` Segmentation Methods table.
  - The "Percentage of cells without a nucleus" metric has been removed.
- Interrupted runs can be resumed. Issuing the same `xeniumranger` command will now resume execution of the pipestance from the stage that originally failed. See [troubleshooting](/support/software/xenium-ranger/2.0/resources/troubleshooting#resume) page.
- Fixed a bug where Xenium Ranger `import-segmentation` errored if GeoJSON inputs had the `MultiPolygon` type or `Polygon` type with holes. If Xenium Ranger encounters a polygon with a hole, it will remove the hole and retain only the exterior of the polygons (interior edges/segments are removed.) If type `MultiPolygon` is present, they will be ignored and will not be included in the analysis.

</LinkableSection>

<LinkableSection id={"v-1-7-1"} title={"v1.7.1 (January 23, 2024)"}>

- Fixed a bug to improve the method to import segmentation results generated from large image files (i.e., from IF or H&E images).
- Fixed a bug to enable importing segmentation results for smaller regions of the original image data.

</LinkableSection>

<LinkableSection id={"v-1-7"} title={"v1.7.0 (October 9, 2023)"}>

- Supports reanalysis of Xenium Onboard Analysis data up to latest version (see [version compatibility table](/support/software/xenium-ranger/2.0/getting-started/XR-getting-started-with-xenium-ranger#compatibility)).
- The image-based `import-segmentation --coordinate-transform` [option](/support/software/xenium-ranger/2.0/analysis/running-pipelines/XR-import-segmentation#xr-matrix) is now compatible with segmentation masks (previously limited to polygons).
- Improved memory usage in the `import-segmentation` pipeline (see updated [system requirements page](/support/software/xenium-ranger/2.0/release-notes/XR-system-requirements)).
- Fixed bug where input masks with discontinuous cells or nuclei caused Xenium Ranger to occasionally crash. An analysis summary alert was introduced to flag rare scenarios where discontinuities may lead to splitting of imported cells or nuclei.
- Several minor bug fixes in the analysis summary user interface.
- Improved preflight checks.
- Miscellaneous bug fixes.

</LinkableSection>

<LinkableSection id={"v-1-6"} title={"v1.6 (August 17, 2023)"}>

- Initial release.
- Resegment Xenium data with customizable nucleus expansion distance and the latest 10x cell segmentation algorithm.
- Import community-developed nucleus and cell segmentations in multiple popular formats (i.e., Baysor).
- Selected the wrong gene panel when you started the Xenium Analyzer run? Simply fix the mistake by using relabel.
- All pipelines produce the same output bundle as Xenium Onboard Analysis v1.6, so they are compatible with the same downstream visualization and analysis softwares (e.g., Xenium Explorer).
- Backwards compatible with all previous Xenium Onboard Analysis versions.

</LinkableSection>


v2.0.1 (June 10, 2024)

v2.0 (April 25, 2024)

v1.7.1 (January 23, 2024)

v1.7.0 (October 9, 2023)

v1.6 (August 17, 2023)

Release Notes for Xenium Ranger

Overview

Getting Started

Download Center

Xenium Ranger Commands

Analysis

Algorithms

Advanced

Troubleshooting

Release Notes

Xenium Onboard Analysis

Xenium Explorer

Example Datasets

Analysis Guides

Xenium Ranger 2.0

We provide resources from protocols, user guides, and free-to-use analysis tools.

Learn more about input files required for Xenium Ranger

Inputs

Input Overview

Segmentation Inputs

Learn how to run Xenium Ranger subcommands.

Running Pipelines

Guidance for choosing a Xenium Ranger pipeline.

Choosing a pipeline

Choosing a Pipeline

Relabel

Modify the Xenium Onboard Analysis cell segmentation results.

Resegment

Import segmentation results from community-developed tools.

Import-segmentation

Learn more about output files generated by Xenium Ranger

Outputs

The Xenium In Situ software suite is a set of software applications for analyzing and visualizing in situ gene expression data produced by the Xenium Analyzer. Xenium Ranger provides flexible off-instrument reanalysis of Xenium In Situ data. Relabel transcripts, resegment cells with the latest 10x segmentation algorithms, or import your own segmentation data to assign transcripts to cells.

What is Xenium Ranger?

View the latest updates to Xenium Ranger algorithms.

View the latest updates to Xenium Ranger.

Learn more about Xenium In Situ instrument analysis software.

Visualize data from Xenium In Situ solutions.

Browse Q&As from the 10x Genomics support team.

Access free, publicly available data generated with Xenium In Situ solutions.

A collection of introductions, tutorials, and blogs for data analysis beyond 10x Genomics software.