REVISE Documentation ==================== .. raw:: html

REconstruction via Vision-integrated Spatial Estimation

Spatially inferred virtual cells from ST, histology, and scRNA-seq.

REVISE reconstructs Spatially-inferred Virtual Cells (SVCs) by routing each dataset through a config-driven topology-aware optimal transport pipeline. The documentation is organized around the decisions users make first: which SVC mode to run, which platform/confounding route applies, and how outputs flow into benchmark or application notebooks.

Start with a route Understand SVCs See the architecture
Resources --------- - Package: `revise-svc on PyPI `_ - Code: `GitHub repository `_ - Data and reproduced results: `Zenodo `_ - Documented package version: ``0.0.32`` .. figure:: ../png/REVISE_overview.png :alt: Overview of the REVISE framework :align: center REVISE combines spatial transcriptomics, histology, and single-cell reference information to reconstruct SVCs for benchmark and real-data application workflows. Choose Your Path ---------------- .. raw:: html Two SVC Modes ------------- .. list-table:: :header-rows: 1 :widths: 1 2 2 2 * - Mode - Best for - Typical platforms - Primary outputs * - ``sp-SVC`` - Spatial refinement when high-definition ST is affected by segmentation or bin-to-cell assignment artifacts. - hST such as Visium HD; Sim2Real-ST segmentation and bin2cell benchmarks. - ``sp_SVC.h5ad`` and canonical ``artifacts/sp_svc.h5ad``. * - ``sc-SVC`` - Molecular completion and cell-state refinement when ST measures limited genes or spot-level mixtures. - iST/sST such as Xenium and Visium; super-resolution and imputation benchmarks. - ``sc_SVC_expr.h5ad``, ``sc_SVC_spatial.h5ad``, and canonical artifacts. Core Execution Model -------------------- All modern execution flows through one public engine: 1. ``revise.framework.REVISEPipeline.run()`` 2. ``revise/revise.yaml`` profiles and runtime/io overrides 3. ``revise.recon.pipeline.UnifiedReconstructionPipeline`` 4. backend strategy and plugin registries in ``revise/backend/`` The fixed lifecycle is documented in :doc:`source/architecture`; practical profile and override examples are documented in :doc:`source/configuration`. .. toctree:: :caption: Start Here :maxdepth: 2 :hidden: source/concepts source/quickstart source/installation .. toctree:: :caption: Run REVISE :maxdepth: 2 :hidden: Application mode Benchmark mode source/configuration .. toctree:: :caption: Gallery :maxdepth: 2 :hidden: Application cases .. toctree:: :caption: Reference :maxdepth: 2 :hidden: source/architecture source/api/index