A typical xeniumranger analysis will display the following after completion (here the --id=tiny-test):

Copy
...

Outputs:
- metrics_summary:                            /tiny-test/outs/metrics_summary.csv
- transcripts:                                /tiny-test/outs/transcripts.zarr.zip
- Transcript info CSV:                        /tiny-test/outs/transcripts.csv.gz
- Transcript info parquet:                    /tiny-test/outs/transcripts.parquet
- Cell info CSV:                              /tiny-test/outs/cells.csv.gz
- Cell info parquet:                          /tiny-test/outs/cells.parquet
- Cell segmentation result:                   /tiny-test/outs/cells.zarr.zip
- Cell segmentation nucleus polygons CSV:     /tiny-test/outs/nucleus_boundaries.csv.gz
- Cell segmentation cell polygons CSV:        /tiny-test/outs/cell_boundaries.csv.gz
- Cell segmentation nucleus polygons parquet: /tiny-test/outs/nucleus_boundaries.parquet
- Cell segmentation cell polygons parquet:    /tiny-test/outs/cell_boundaries.parquet
- Clustering result in zarr.zip format:       /tiny-test/outs/analysis.zarr.zip
- Cell-feature matrix in zarr.zip format:     /tiny-test/outs/cell_feature_matrix.zarr.zip
- Cell-feature matrix in h5 format:           /tiny-test/outs/cell_feature_matrix.h5
- morphology:                                 /tiny-test/outs/morphology.ome.tif
- CS multi-file OME-TIFF (AUTOFOCUS):         /tiny-test/outs/morphology_focus
- Metadata for Xenium Explorer:               /tiny-test/outs/experiment.xenium
- Customer-facing web summary:                /tiny-test/outs/analysis_summary.html
- Cell-feature matrix in MEX format:          /tiny-test/outs/cell_feature_matrix
- Clustering result in csv format:            /tiny-test/outs/analysis
- Auxiliary output files:
    morphology_fov_locations:    null
    overview_scan:               null
    overview_scan_fov_locations: null
    per_cycle_channel_images:    null
- Gene panel JSON:                            /tiny-test/outs/gene_panel.json

Pipestance completed successfully!

The /outs directory contains all the output files. Xenium Ranger v4.0 output structure matches the outputs from XOA v4.0:

Copy
├── analysis
│   ├── clustering
│   ├── diffexp
│   ├── pca
│   └── umap
├── analysis.zarr.zip
├── analysis_summary.html
├── aux_outputs
├── cell_boundaries.csv.gz
├── cell_boundaries.parquet
├── cell_feature_matrix
│   ├── barcodes.tsv.gz
│   ├── features.tsv.gz
│   └── matrix.mtx.gz
├── cell_feature_matrix.h5
├── cell_feature_matrix.zarr.zip
├── cells.csv.gz
├── cells.parquet
├── cells.zarr.zip
├── experiment.xenium
├── gene_panel.json
├── metrics_summary.csv
├── morphology.ome.tif
├── morphology_focus/
│   ├── ch0000_dapi.ome.tif
│   ├── ch0001_atp1a1_cd45_e-cadherin.ome.tif # (0001-0003 for cell segmentation staining workflow data)
│   ├── ch0002_18s.ome.tif
│   └── ch0003_alphasma_vimentin.ome.tif
├── nucleus_boundaries.csv.gz
├── nucleus_boundaries.parquet
├── transcripts.csv.gz
├── transcripts.parquet
└── transcripts.zarr.zip

For every Xenium Ranger analysis, the following file modifications will be made to the input XOA files:

• In the experiment.xenium file, a new analysis_uuid will be generated (other UUIDs generated by the original XOA pipeline will remain the same).
• A xenium_ranger field will be appended to the experiment.xenium file. It provides the analysis run ID, Xenium Ranger version, and xeniumranger command(s).
• The analysis_summary.html will display similar Xenium Ranger metadata as above in a new panel on the Summary tab. It provides the analysis run ID, run timestamp, Xenium Ranger version, and xeniumranger command(s). If the same input dataset was rerun sequentially with Xenium Ranger multiple times, the commands will all be displayed in this panel.
• The import-segmentation pipeline generates new metrics in the metrics_summary.csv and the analysis_summary.html. Starting in Xenium Ranger v4.0, this pipeline also generates a cell_id_map.csv.gz file with the mapping of Xenium Ranger's cell IDs to the imported file's cell IDs for downstream analysis. Learn more about use cases for this CSV file here.

Files that are not modified by a given Xenium Ranger subcommand will be copied from the original Xenium bundle directory (specified by --xenium-bundle).