pedigree-graph
Sparse-matrix pedigree relationship extraction and kinship computation.
Builds parent→child CSR adjacency matrices and extracts relationship
categories using sparse matrix algebra (A @ A.T for siblings,
A² @ A²ᵀ for cousins, etc.). Each relationship type is parameterised
by (up, down, n_ancestors):
up: meioses from the first member (the junior role: offspring, descendant, niece_nephew, junior_cousin) up to the common ancestor(s); collateral categories are storedup ≥ downdown: meioses from common ancestor(s) down to individual Bn_ancestors: 1 (half/lineal) or 2 (full, i.e. mated pair)kinship = n_ancestors × (1/2)^(up + down + 1)
Install
pip install pedigree-graph
Binary wheels cover manylinux x86-64 and AArch64, macOS x86-64 and Apple
Silicon, and Windows x86-64 (one abi3 wheel per platform for CPython >= 3.13).
Elsewhere pip builds the sdist, which needs a Rust toolchain (rustc >= 1.85).
For development the locked pixi environment carries Python, Rust, and maturin
and installs the package editable (the extension module is rebuilt with
pixi run maturin develop --release after a Rust change):
git clone https://github.com/rwaples/pedigree-graph.git
cd pedigree-graph
pixi install --locked
pixi run pytest -m "not slow" # inner loop, about 2.5 minutes
pixi run pytest # before a commit, about 13 minutes
pixi run cargo test --release # the Rust core
Five of the nine slow tests are the random_30k integration gates. Each runs
the pair-kinship kernel over the whole 30,300-row pedigree, and a single kernel
call there costs 30 to 250 seconds regardless of how many pairs it is asked for,
so the full suite is dominated by a handful of tests. The other four are the
N=2000 effective-size scaling tests in tests/test_effective_size_scaling.py,
which touch neither random_30k nor the pair-kinship kernel.
Requires Python ≥ 3.13. Runtime deps: numpy and scipy. Construction,
relationships, topology, pairwise kinship, the kinship matrices, the
generation kinship summary, inbreeding, the lineage counts and the Ne
prerequisites are compiled Rust (pedigree_graph._native, sources under
crates/). numba is only a test extra, for the retired kernels the test
suite keeps as oracles.
Pandas is optional and only needed if you pass DataFrames to the
constructors.
Usage
import numpy as np
from pedigree_graph import RELATIONSHIPS, PedigreeGraph
# Construct from arrays (no pandas needed)
pg = PedigreeGraph.from_arrays(
ids=np.array([0, 1, 2, 3, 4]),
mother_ids=np.array([-1, -1, 0, 0, 0]),
father_ids=np.array([-1, -1, 1, 1, 1]),
)
# Or from a table: a dict of columns (pandas-free), or any pandas/polars frame
pg = PedigreeGraph.from_frame(
{
"id": np.array([0, 1, 2, 3]),
"mother": np.array([-1, -1, 0, 0]),
"father": np.array([-1, -1, 1, 1]),
"twin": np.array([-1, -1, -1, -1]),
"sex": np.array([0, 1, 0, 1], dtype=np.int8),
"generation": np.array([0, 0, 1, 1], dtype=np.int32),
}
)
# pg = PedigreeGraph.from_frame(df)
# Pairs by relationship category, up to a given degree; each block holds
# read-only int32 first_rows / second_rows in the category's role orientation.
# execution="memory" returns the same blocks at the lowest peak memory
# (the result plus engine state) for about twice the wall time.
pairs = pg.relationship_pairs(max_degree=3)
first, second = pairs["FS"] # full sibs
print(len(pairs["1C"])) # 1st cousins (degree 3)
print(RELATIONSHIPS["FS"].nominal_kinship) # 0.25
# Pedigree-expected kinship for those pairs, or for any two row arrays
kin = pg.pair_kinship(pairs) # {code: float32 array}
kin_fs = pg.pair_kinship(first, second)
# Exact counts in O(N) memory (no pair lists), and the three kinship-matrix families
counts = pg.relationship_counts(max_degree=3)
K = pg.kinship_matrix() # complete, CSC float32
# Scalar counts for MZ, MO, FO, FS, MHS and PHS only, also exact
close = pg.close_relative_counts() # no degree/category selector
assert close["FS"] == counts["FS"]
assert close["GP"] is None # not computed, not zero
Absent optional columns read as absent: there is no sex default and no
generation fallback. Effective-size estimators live in
pedigree_graph.effective_size; the FrameLike protocol in
pedigree_graph.typing. Migrating from 0.7.1: see the old-to-new table in
CHANGELOG.md.
close_relative_counts() is full-graph only. Its requested and exact
sets contain the six codes above; all other registry keys map to None.
It counts parent edges and sibling groups without pair lists or adjacency
powers. For grandparents, avuncular pairs, cousins, or a pedigree view, use
relationship_counts() instead. The former estimate_relationship_counts
method and the result fields approximate and clamped have been removed.
Relationship registry
Codes follow the convention up_down_n_anc:
| Code | Label | up | down | n_anc | Kinship | Degree |
|---|---|---|---|---|---|---|
MZ |
MZ twin | 0 | 0 | 0 | 0.5 | 0 |
MO |
Mother–offspring | 1 | 0 | 1 | 0.25 | 1 |
FO |
Father–offspring | 1 | 0 | 1 | 0.25 | 1 |
FS |
Full sib | 1 | 1 | 2 | 0.25 | 1 |
MHS |
Maternal half sib | 1 | 1 | 1 | 0.125 | 2 |
PHS |
Paternal half sib | 1 | 1 | 1 | 0.125 | 2 |
GP |
Grandparent | 2 | 0 | 1 | 0.125 | 2 |
Av |
Avuncular | 2 | 1 | 2 | 0.125 | 2 |
1C |
1st cousin | 2 | 2 | 2 | 0.0625 | 3 |
| ... | (full registry up to 2nd cousin / kinship 1/64) |
See RELATIONSHIPS for the complete list; each RelationshipCategory
carries code, label, degree, nominal_kinship, up, down,
ancestor_count, and the two positional roles.
Architecture
For contributors: docs/architecture.md maps the
module layout and the hidden contracts (coordinate space, exact count
coverage, sparse-ID handling, default sex), each with its source
of truth and regression test.
The relationship/coordinate vocabulary is in CONTEXT.md;
design decisions are in docs/adr/.
License
MIT — see LICENSE.
Metadata
Release files for pedigree-graph 0.9.4
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 | |
|---|---|---|---|---|
| pedigree_graph-0.9.4.tar.gz | 621.3 kB | With provenance | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| pedigree_graph-0.9.4-cp313-abi3-win_amd64.whl | CPython 3.13 | abi3 | Windows x86-64 | Details |
| pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.13 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.13 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| pedigree_graph-0.9.4-cp313-abi3-macosx_11_0_arm64.whl | CPython 3.13 | abi3 | macOS 11.0+ ARM64 | Details |
| pedigree_graph-0.9.4-cp313-abi3-macosx_10_12_x86_64.whl | CPython 3.13 | abi3 | macOS 10.12+ x86-64 | Details |
Total release size: 3.3 MB
Release files / pedigree_graph-0.9.4.tar.gz
| Download URL | pedigree_graph-0.9.4.tar.gz |
|---|---|
| Size | 621.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3503750e53339263261528169e6eb88de9e15cee711845b1e02ccff607e0dba5
|
|
BLAKE2b-256 checksum How to use checksums |
37cccbd722a1a4d7a82634e2c1435f0b8ae78df74d7ff3c10db4becdfe8efd93
|
| 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 Sep 23, 2026.
Transparency logRelease files / pedigree_graph-0.9.4-cp313-abi3-win_amd64.whl
| Download URL | pedigree_graph-0.9.4-cp313-abi3-win_amd64.whl |
|---|---|
| Size | 485.5 kB |
| Tags | CPython 3.13 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d7ba1cd1db8656bac237a61a0bc74b4df397c3e83b80b325c6af172414df4915
|
|
BLAKE2b-256 checksum How to use checksums |
bd4e3eceeeffc2f1be62c63e151318d598bdf1f567c0d4a97fff4eb53b1fd247
|
| 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 Sep 23, 2026.
Transparency logRelease files / pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 589.6 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
d94d0cb8437530159d2674921a0158e05cb6f061ce5659b22e31ef497ebdedcd
|
|
BLAKE2b-256 checksum How to use checksums |
37101e94ae57f89df8bc4c4c96ce9300ddfdc322d21498ea3e41a086b9a9d2bf
|
| 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 Sep 23, 2026.
Transparency logRelease files / pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | pedigree_graph-0.9.4-cp313-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 561.9 kB |
| Tags | CPython 3.13 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
a117829bd9923dc044d68cf4bdb96314ac4487fd159db4d437dc5b5fb4606e56
|
|
BLAKE2b-256 checksum How to use checksums |
84e3c3e8dc4e3d8cdd141e87286254563fb3978b32649f6814ace8f2440d4d51
|
| 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 Sep 23, 2026.
Transparency logRelease files / pedigree_graph-0.9.4-cp313-abi3-macosx_11_0_arm64.whl
| Download URL | pedigree_graph-0.9.4-cp313-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 532.2 kB |
| Tags | CPython 3.13 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
8cbf1d03c9ed6a2b342111c2799ab6c423eec25c7c758760a69d67ca3817c7f4
|
|
BLAKE2b-256 checksum How to use checksums |
9d454360a5c43293476aba4b27e1e203329cb06e1e35693252af6d21d1c55fd7
|
| 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 Sep 23, 2026.
Transparency logRelease files / pedigree_graph-0.9.4-cp313-abi3-macosx_10_12_x86_64.whl
| Download URL | pedigree_graph-0.9.4-cp313-abi3-macosx_10_12_x86_64.whl |
|---|---|
| Size | 552.0 kB |
| Tags | CPython 3.13 abi3 macOS 10.12+ x86-64 |
|
SHA-256 checksum How to use checksums |
503223212f6d94f12e681c41448ed2e63151cfc379707100c5425131644f7512
|
|
BLAKE2b-256 checksum How to use checksums |
991fbef2f009a7b3d75cbdcb6d0c0ece21e37dc1c405e064f3b6cbca9c8908c3
|
| 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 Sep 23, 2026.
Transparency logSecurity for pedigree-graph 0.9.4
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
All 6 files in this release have been uploaded with provenance metadata.
Attestation for pedigree_graph-0.9.4.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 Sep 23, 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.