Skip to main content

Altar AlphaGenome binding

altar-alphagenome connects Google DeepMind's hosted AlphaGenome API to Altar. It registers ALPHAGENOME in Altar's canonical altar.model_plugins group and scores inline: build_scoring_plan returns a JSON-durable InlineScoringPlan, and execute_inline calls the API in process without an execution backend or container.

The binding is not on PyPI. Install it from a clone of the repository, which also installs Altar from the same checkout:

uv pip install -e bindings/alphagenome

The binding depends on the exact alphagenome SDK release recorded in its runtime identity and refuses to execute with a different version. The SDK is imported only when the default scorer runs, so plans can be built, validated, and materialized without loading the client.

An Altar model instance is AlphaGenome plus its configured organism, ontology terms, variant scorers, and sequence length. The binding always calls the production ALL_FOLDS model rather than exposing training folds in user configuration. Human coordinates must be hg38 and mouse coordinates mm10. The API key is a SecretReference in durable configuration; the raw key, an injected scorer, or an SDK client reaches the plugin only through the non-durable AlphaGenomeRuntime.

Each variant yields one scalar headline row (top_output_type, top_track, max_abs_raw_score, top_track_abs_quantile_score, max_abs_quantile_score, n_tracks_scored) and a lossless track_scores detail table with one row per scorer, genomic track, gene, and splice junction. Persist the detail table with any Altar DetailStore.

See the AlphaGenome integration page for the reduction, prioritization rule, and compatibility notes. API quota, availability, privacy policy, and provider terms of use apply independently of this MIT-licensed binding.

Metadata

Release files for altar-alphagenome 0.3.0

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

Source distribution (sdist)

Source distribution for altar-alphagenome 0.3.0
File Size Uploaded Provenance Actions
altar_alphagenome-0.3.0.tar.gz 28.8 kB Without provenance Details for altar_alphagenome-0.3.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for altar-alphagenome 0.3.0
File Interpreter ABI Platform Actions
altar_alphagenome-0.3.0-py3-none-any.whl Python 3 none any Details for altar_alphagenome-0.3.0-py3-none-any.whl

Total release size: 44.3 kB

Release files / altar_alphagenome-0.3.0.tar.gz

Download URL altar_alphagenome-0.3.0.tar.gz
Size 28.8 kB
Tags Source
SHA-256 checksum
How to use checksums
f31d69ec6531b8c0685d3f5b044bd9d628c82d413cf0c6081584398e5b1762e5
BLAKE2b-256 checksum
How to use checksums
aba640c292232198707d3aaf65241c29dd4917e43e3bf789c28f691ef6818186
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / altar_alphagenome-0.3.0-py3-none-any.whl

Download URL altar_alphagenome-0.3.0-py3-none-any.whl
Size 15.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
13f44e880587283fbf39881bbc88d336f327dc15f8b24fca2f61f52530c2bd23
BLAKE2b-256 checksum
How to use checksums
53e3f548972a9b504323d3c01a600440dc7a5ae7f5b7c3245498f390a2c502d5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.12.17 {"installer":{"name":"uv","version":"0.12.17","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"22.04","id":"jammy","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for altar-alphagenome 0.3.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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.

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