PASE
PASE estimates molecular associations within individual patients and summarizes them across a single-cell cohort.
Read the online documentation for installation, the API and the statistical meaning of each parameter.
Installation
Use Python 3.10 or later in a fresh environment. Install the published release from PyPI:
python -m venv .venv
# Windows: .venv\Scripts\activate
# macOS/Linux: source .venv/bin/activate
python -m pip install pase-framework==1.1.0
The distribution is named pase-framework, but the Python import is pase.
The unrelated audio package named pase on PyPI uses the same import name;
do not install both in one environment. The
v1.1.0 release
is also available on GitHub. For development, clone this repository and use
python -m pip install -e ".[test]".
Five-line example
import pase
adata = pase.datasets.load_gse234933_demo()
res = pase.associate(adata, anchor="LILRB4", target=["MMP14", "MMP9", "SPP1", "APOE"], patient_key="donor", covariates=["log_depth"], cell_mask="myeloid", aggregate="equal", min_cells=30)
print(res.summary())
res.plot_forest()
The bundled GSE234933 subset contains real cells and works without a download.
The four-gene target above illustrates the interface; it is not the current
manuscript's published 15-gene signature. The complete tutorial is
examples/gse234933_quickstart.ipynb.
Install the notebook tools with
python -m pip install "pase-framework[tutorial]==1.1.0". Download the notebook
or clone this repository, then run
jupyter lab examples/gse234933_quickstart.ipynb from the checkout.
Input format
Supply an AnnData object with cells in rows and unique gene names in
adata.var_names. adata.X, or the requested layer, must already contain
transformed expression. For count data, the tutorial uses
log1p(10000 * count / total_counts) with totals calculated before selecting
genes. associate does not normalize raw counts.
| Input | Meaning |
|---|---|
adata.obs["donor"] |
Independent patient ID, with no missing values. Repeated samples from one patient must share an ID. |
adata.obs["log_depth"] |
Numeric covariate; the tutorial uses log1p(total_counts) from the full matrix. |
adata.obs["myeloid"] |
Boolean cell-selection column. Patients with no selected cells remain in the output. |
anchor |
One gene name. |
target |
One gene name, or a list whose within-patient gene z scores are averaged. |
Covariates enter a separate least-squares model for each patient, with an
intercept. Numeric categorical encodings must be supplied explicitly.
Patients absent from the object can be retained using patient_ids.
See the input guide for missing values and eligibility rules.
Outputs and choice of summary
res.patients reports every patient, cell counts, observed correlation,
eligibility, exclusion reasons and, where applicable, weights or shrunken effects.
res.summary() returns one row with the selected method, target, estimate,
interval, P value and status. res.metadata records the analysis settings and
warnings. res.plot_forest() returns a Matplotlib Axes.
aggregate |
What it reports |
|---|---|
"equal" |
Arithmetic mean of eligible patients' observed correlations, with a t interval. Each eligible patient has equal weight. |
"re_hksj" |
REML random-effects mean on the Fisher-z scale, back-transformed for display, with a classical HKSJ interval. It has a different target from the arithmetic mean. |
"eb" |
Individual patient effects shrunk toward the fitted Fisher-z population mean. Conditional intervals exclude uncertainty in fitted population parameters; no cohort P value is returned. |
min_cells=30 is adjustable. Version 1.1.0 changes the default
min_patients from 2 to 6. Below the selected method's eligible-patient
threshold, PASE returns observed patient correlations, descriptive summaries
and exclusion reasons, but withholds inferential estimates, intervals and
P values. An explicit lower threshold is allowed and recorded as an override.
Reported inference receives a small-cohort warning below 20 eligible patients
and a precision warning when the full correlation-scale interval is wider
than max_ci_width=0.2. Warnings retain the interval. The patient boundaries
are result-informed reporting choices, and 0.2 is a configurable practical
tolerance; none guarantees calibrated coverage. See the
reporting policy and its evidence.
For the equal-patient mean, an externally specified planning_sd enables a
model-based minimum detectable effect (MDE). Record its origin with
planning_sd_source; set minimum_relevant_effect to compare the MDE with a
scientifically meaningful effect. This is a planning calculation, not achieved
power, and is not provided for Fisher or EB targets.
Citation
For this code, cite the authors, PASE software version 1.1.0, and its release URL. Machine-readable author information is in CITATION.cff. An earlier analysis archive is available at Zenodo v3; that DOI does not identify this 1.1.0 software release.
Code is distributed under the MIT License. The real-data example retains its source attribution and third-party terms; see THIRD_PARTY_DATA.md.
Metadata
Release files for pase-framework 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| pase_framework-1.1.0.tar.gz | 107.9 kB | With provenance | Details for pase_framework-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pase_framework-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for pase_framework-1.1.0-py3-none-any.whl |
Total release size: 184.4 kB
Release files / pase_framework-1.1.0.tar.gz
| Download URL | pase_framework-1.1.0.tar.gz |
|---|---|
| Size | 107.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3816b4d90a9fb9286b7447b83d822fec9024075205ee554552905ffa6bb67d46
|
|
BLAKE2b-256 checksum How to use checksums |
2e104771464d7dc69c1b99ea6834b36efa67ae5ba2e99f828c2f5b6f1df4c812
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logRelease files / pase_framework-1.1.0-py3-none-any.whl
| Download URL | pase_framework-1.1.0-py3-none-any.whl |
|---|---|
| Size | 76.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7aee42195f51b5bb19ff5437de29af28c3541ed458c670fc3cb45c7164582245
|
|
BLAKE2b-256 checksum How to use checksums |
c7ee2bd92ac1771a0d5ced57173c8620aabd8743cecd0f53d045d51507220573
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logSecurity for pase-framework 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pase_framework-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 6, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.