Altar Enformer binding
altar-enformer is the lightweight control-plane binding for high-throughput Enformer variant scoring. It
registers ENFORMER in Altar's canonical model-plugin group and has no TensorFlow dependency.
One Altar model instance contains immutable SavedModel and target-metadata resources plus a fixed selection of Enformer's 5,313 human output tracks. A job is partitioned upstream into deterministic scoring batches; the binding emits one independently retryable container task per batch. The runtime loads the model once per task, microbatches reference/alternate sequence pairs, and writes:
- one primary row per variant, containing the track with the largest absolute SAD; and
- a
track_effectsdetail row for every selected(variant, track)pair, preserving reference and alternate activity, SAD, and SADR.
SAD and SADR follow the definitions in the Basenji variant scorer linked by DeepMind's Enformer
release:
SAD = sum(alt) - sum(ref) and SADR = log2(sum(alt) + 1) - log2(sum(ref) + 1) across the model's 896 output
bins. DeepMind's simpler EnformerScoreVariantsRaw
notebook divides SAD
by the constant 896 by taking means; that does not change per-variant track ranking. SAR is a different Basenji
statistic—the sum of per-bin log ratios—and is intentionally not emitted under the wrong name. Track selection,
weight bytes, metadata bytes, runtime image, and hg38 reference identity are all durable inputs.
Scoring semantics 2.0 selects the primary track by absolute SAD, the main published Enformer variant-effect
score, and renames the former sar/top_track_sar fields to sadr/top_track_sadr. Existing primary scores
must be regenerated. Existing complete track_effects rows are sufficient for a later storage-layer migration
because their numeric sar values already contained SADR; Altar itself does not mutate deployed result stores.
The corresponding TensorFlow 2.13 / Python 3.10 executor lives under runtimes/enformer with its own lockfile
and immutable image lifecycle.
Metadata
Release files for altar-enformer 0.3.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 |
|---|---|---|---|---|
| altar_enformer-0.3.0.tar.gz | 19.4 kB | Without provenance | Details for altar_enformer-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| altar_enformer-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for altar_enformer-0.3.0-py3-none-any.whl |
Total release size: 31.6 kB
Release files / altar_enformer-0.3.0.tar.gz
| Download URL | altar_enformer-0.3.0.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4aecf196ecc2cb36c8344f074daf1cdad53a4a6633bb9af7d88176ef5842bab9
|
|
BLAKE2b-256 checksum How to use checksums |
267b12ac3132a445539d21a3cae5b3fbdfe93b50c263a8348eeea5fb2b899bc9
|
| 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_enformer-0.3.0-py3-none-any.whl
| Download URL | altar_enformer-0.3.0-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
10e2f235f28acc4efb3bf8b0b71c47a0f18537a5da7dd2ef423a853aeccf7cc5
|
|
BLAKE2b-256 checksum How to use checksums |
db120afd095c68f6da7303f056c3725e1bdf60493ae46d499aec5a75644fcc2a
|
| 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-enformer 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.