Skip to main content

APB Catalog

Catalogues of what APB result fields mean, one set per kind of meaning, each stating its purpose and users, so the consumer asks for a meaning instead of vendor columns such as PEP, EG_PEP or Q_Value.

Documentation: anndata-omics-bridge.github.io/apb-catalog, built from docs/ with make docs; start with Get started.

Installation

pip install apb-catalog

Use

from apb_catalog.api import Catalog

confidence = Catalog(parsed, "identification_confidence")                     # parsed: apb2 ParsedLevels
confidence.layer("ion", concept="confidence")                 # ('pep', 'q_value') — kinds on offer, or None
pep = confidence.layer("ion", concept="confidence", kind="pep")  # MaxQuant PEP, Spectronaut EG_PEP, DIA-NN PEP

miape = Catalog(parsed, "miape")
miape.var("protein", concept="miape")                        # ('gene_name', 'protein_group')
genes = miape.var("protein", concept="miape", kind="gene_name")  # the column MIAPE-AnnData calls gene_name
  • Every entry of both sets
  • layer returns the apb2 layer table, var the column; None means the vendor has no such field
  • A level answers only for its own entity: ion for precursors, protein for protein groups
  • Confidence lookups mean identification unless stage="quantification" says otherwise
  • Two equally good fields, or a rule nobody reviewed, raise UnresolvedField naming the candidates
  • attach_snapshot(parsed, catalog.snapshot()) records bindings and lookups in metadata["catalog"][<catalogue>]

Catalogues

  • identification_confidence: how likely each identification is correct: per-run PEP and q-value layers, per-feature PEP and Sage's MS1-peak q-value; used by apb-aggregate's confidence-weighted rollups; 12 entries
  • miape: draft mapping onto the MIAPE-AnnData Schema 0.4.0 draft (HUPO-PSI AI Readiness Working Group): protein, peptide and peptidoform fields and the raw layer; ion levels have no MIAPE modality; 32 entries
  • Catalog(parsed, name).description: the set's purpose and users, also embedded in its snapshot
  • Each set lists every packaged APB2 rule level, so a vendor without a relevant field answers missing, never unknown
  • Entries bind to reviewed effective-rule fingerprints (SHA-256 of canonical rule_json); any APB2 rule change needs re-review, enforced by the drift tests
  • Vocabulary: confidence with kind (pep, q_value) and stage; miape with kind naming the MIAPE-AnnData field and its requirement level

Snapshot contract

attach_snapshot stores apb-catalog-resolution 0.2 as JSON at ParsedLevels.metadata["catalog"][<catalogue>]; APB2 persists it in every format, including AnnData uns from HDF5 result format 5. It embeds the set's description, concept definitions, level bindings, retained entries and every answer, so readers need neither this package nor its catalogues. The JSON Schema is published with the package; make schema regenerates it.

Development

uv sync --group dev
make check
.venv/bin/pre-commit install --hook-type pre-commit --hook-type pre-push

All Python commands run from the synchronized project .venv.

Metadata

Release files for apb-catalog 0.1.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for apb-catalog 0.1.1
File Size Uploaded
apb_catalog-0.1.1.tar.gz 24.4 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for apb-catalog 0.1.1
File Interpreter ABI Platform
apb_catalog-0.1.1-py3-none-any.whl Python 3 none any Details

Total release size: 73.6 kB

Release files / apb_catalog-0.1.1.tar.gz

Download URL apb_catalog-0.1.1.tar.gz
Size 24.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2777ea45e2c09c88d49724415e6b29df98ae7ff736ccc8d4db8fc7a641dbfdbe
BLAKE2b-256 checksum
How to use checksums
95e3d4affe907d0bfcc0eba7a936717ea40982dcb2225df9d504429694686e80
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 5, 2026.

Transparency log

Release files / apb_catalog-0.1.1-py3-none-any.whl

Download URL apb_catalog-0.1.1-py3-none-any.whl
Size 49.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
feb93b376c859f48e00da15ce58bfa35340814b3c096da9283725f52568cb452
BLAKE2b-256 checksum
How to use checksums
6edad26059d26a0030ba4aaee25d8859587becf8b52fbfa1aa6cec19becaecee
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Oct 5, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.1 This release

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page