CSDE: Corrected Spatial Differential Expression

Automated pipelines for spatial transcriptomics produce cell quantifications (cell-by-gene expression matrices and label assignments) that contain systematic errors, e.g., due to mis-segmentation of cell boundaries. These errors can propagate into downstream analyses of differential expression, leading to false discoveries or missed signals

CSDE corrects for these errors by combining the large automated dataset with a small set of manually validated cells, using prediction-powered inference to recover unbiased estimates with valid confidence intervals.

The current codebase focuses on the comparison of a given cell type across two spatial regions. It allows users to

1. export per-cell annotation panels for a small subset of cells (e.g. 600)
2. manually validate the segmentation and type assignment for these cells
3. run the CSDE model to get corrected DE estimates for all genes

Refer to the preprint for details on the method. Reproducibility code is available here.

Input requirements

The workflow takes a SpatialData zarr as input.

Its "table" AnnData must contain:

• raw expression counts in .X or a named layer
• the following obs columns:

obs column	content
cell_type (configurable)	cell-type label for each cell
spatial_group (configurable)	spatial region label with two values to compare (e.g. 0/1, or "out_of_tumor"/"in_tumor"). Which value is the target is chosen in Step 3 with --spatial-group-target / --spatial-group-reference, defaulting to 1 / 0
center_x, center_y	cell centroid in microns

The zarr must also expose the following SpatialData elements, used to render the per-cell annotation panels (Step 1):

element	requirement
images	at least one image with a named fluorescence channel (e.g. "DAPI", "Cellbound2")
shapes	at least one element holding the cell-boundary polygons
points	at least one element holding transcript locations, with a gene column

The cell-boundary shapes must carry a transformation to the global coordinate system: it converts the micron center_x/center_y centroids into the image's pixel space. This conversion assumes a pure scale-and-translation transform (as produced for MERSCOPE); transforms with rotation or shear are not handled.

Installation

pip install csde
pip install "csde[cuda12]"# GPU (CUDA 12)
pip install "csde[annotate]"# annotation UI (Step 2, requires streamlit)
pip install "csde[cuda12,annotate]"# both

Workflow overview

CSDE runs as three scripts executed in sequence, each consuming the previous one's output: export.py samples a small set of cells and renders an annotation panel for each, annotate.py lets you manually mark those cells as correct or incorrect, and differential_expression.py feeds those validated labels into the CSDE model to produce corrected DE estimates. All three share a single annotation directory.

SpatialData zarr
│
▼
1. Export annotation panels ←─ scripts/export.py
(importance-sampled cells,
one image per cell)
│
▼
2. Manual validation ←─ scripts/annotate.py
(annotator marks each cell
as correctly / incorrectly labelled)
│
▼
3. Run CSDE ←─ scripts/differential_expression.py
(corrected DE estimates)

---

Step 1 — Export annotation panels (scripts/export.py)

Before running the statistical model, a small subset of cells must be manually validated. csde provides tooling to generate the per-cell images needed for that step.

python scripts/export.py \
--sdata /path/to/region.zarr \
--out /path/to/annotation_dir \
--cell-type-key cell_type \
--cell-type-of-interest macrophages \
--target-proportion 0.4 \
--gene-colors scripts/gene_colors_file.json \
--image-channel Cellbound2 \
--n-cells 600 \
--layer counts

--annotation-mode selects the actions offered in Step 2, and defaults to accept_correct_reject. Use --annotation-mode accept_reject to drop the relabelling option. The value is saved to config.json; because the cell-type vocabulary is written there too (always, whatever the mode), you can switch modes afterwards by editing config.json, without re-exporting the panels.

--target-proportion controls the fraction of cells of interest in the subsample. Cells of interest are upweighted accordingly (importance sampling); the unnormalized weight for each sampled cell is stored in metadata.csv for downstream use.

--layer selects which expression matrix to read: the named .layers entry holding the raw counts (e.g. counts), or .X when omitted. The value is saved to config.json and reused throughout the workflow — the same layer feeds the top-gene panels here in Step 1 and the CSDE model in Step 3, so set it once at export time. It must point at raw counts, since the noise model (Poisson / negative binomial) assumes integer counts; pointing it at normalised or log-transformed values will produce invalid results.

The script writes:

/path/to/annotation_dir/
├── images/
│ ├── cell_<id>.png # one panel per cell
│ └── ...
├── config.json # export arguments + cell_type_vocabulary (read by annotate.py)
├── metadata.csv # cell_id, cell_type, image_path, sampling_weight, center_x, center_y
└── annotations.json # {cell_id: {action, label}} — written by annotate.py

Each panel contains:

• Left — fluorescence image crop + cell boundaries + transcript dots for genes listed in gene_colors
• Right — top expressed genes (bar chart); genes in gene_colors use their assigned colour, others are grey

Gene color file

A simple JSON mapping gene names to colours:

{
"CD68": "#e41a1c",
"MRC1": "#377eb8",
"C1QA": "#4daf4a",
"FCGR3A": "#ff7f00"
}

---

Step 2 — Manual validation (scripts/annotate.py)

For each exported image, the annotator runs two checks in order:

1. Segmentation — is the cell boundary (left panel) consistent with the nuclei / membrane staining, or does it merge two cells or clip part of one?
2. Cell-type label — are the top expressed genes (right panel) consistent with the assigned label?

which lead to one of three actions:

action	when	effect
accept	segmentation fine, label fine	the cell keeps its automated label
correct	segmentation fine, label wrong	the annotator picks the right cell type
reject	segmentation inadequate	the cell is excluded from both compared groups

Correcting a cell revises only its cell type; its spatial region is treated as reliable and is always taken from the automated pipeline. So correcting a cell into the cell type of interest is what places it in the target or reference group, according to the region it already sits in — this is the case an accept/reject workflow cannot express.

Segmentation is never edited: an accepted or corrected cell keeps the automated expression counts. Rejection therefore doubles as a quality-control filter for cells whose quantification cannot be trusted at all.

streamlit run scripts/annotate.py -- --dir /path/to/annotation_dir

The -- is required: it tells Streamlit to pass everything after it to the script rather than interpreting it as Streamlit's own options.

VS Code Remote forwards the Streamlit port automatically. Open the URL printed in the terminal, then use:

key	accept_correct_reject (default)	accept_reject
1	accept	accept
2	correct	reject
3	reject	—

Pressing 2 in accept_correct_reject mode opens a cell-type selector below the panel — type a few characters to filter, then pick the label. Nothing is written until you choose one, so pressing 2 by mistake is harmless: hit Cancel and the cell stays unannotated.

Progress is saved after every keypress to annotations.json, as {cell_id: {"action": ..., "label": ...}} (label is set only for corrections). Re-running the command resumes from where you left off. You can also start annotating while export.py is still running — the UI picks up newly exported cells automatically.

---

Step 3 — Differential expression (scripts/differential_expression.py)

python scripts/differential_expression.py --dir /path/to/annotation_dir

Reads all export settings from config.json and writes gene-level results to <dir>/results.csv.

The three-way comparison is built here: cells of interest in spatial group 0 (reference) and group 1 (target) form the two compared populations, and everything else — including rejected cells — is collapsed into a third group. Both the automated labels and the manual ones are built the same way; only the cell type differs between them. The script prints a summary of the annotations first (counts per action, plus how many cells the curation moved into and out of the compared groups), which is the quickest check that the annotations were read as intended.

If your region column is not encoded as 1 / 0, set --spatial-group-target and --spatial-group-reference to the two values you want to compare; the script reports the values it found if they don't match. The target region is the one positive log-fold changes refer to, so swapping the two flips the sign of every result — this is deliberately not inferred for you, even when the column has exactly two values.

option	default	description
--dir	(required)	annotation directory (output of steps 1 & 2)
--out	<dir>/results.csv	output CSV path
--spatial-group-key	spatial_group	obs column encoding the two spatial populations
--spatial-group-target	1	value of that column identifying the target region (group 1)
--spatial-group-reference	0	value of that column identifying the reference region (group 0)
--n-cells-expressed-threshold	10	min annotated cells expressing a gene for it to be tested
--noise-model	poisson	poisson or nb (negative binomial)

Output columns

column	description
log_fold_change	estimated LFC (positive = upregulated in target population)
p_value	raw two-sided p-value
p_value_adj	Benjamini-Hochberg adjusted p-value