Altar ChromBPNet binding
altar-chrombpnet is the lightweight control-plane binding between Altar and the independently locked
ChromBPNet runtime under runtimes/chrombpnet. Installing it registers CHROMBPNET through Altar's standard
model-plugin entry point; the base altar distribution does not contain ChromBPNet-specific science.
pip install altar-chrombpnet
from altar.models import get_model_plugin
from altar_chrombpnet import ChromBPNetConfiguration
plugin = get_model_plugin("CHROMBPNET")
The binding owns ChromBPNet configuration, score schemas, prioritization, preprocessing, scoring, and interpretation plans. It depends only on Altar's public façades and Pydantic. TensorFlow, model code, weights, reference genomes, peaks, and provider SDKs remain outside the binding.
The binding also owns ChromBPNet's logical paths (altar_chrombpnet.layouts): the derived per-fold peak
distributions and interval index, the staged peaks and motif set, and the interpretation run tree. Altar core
provides only the model-neutral ModelArtifactLayout and ScoringLayout; every model-owned ChromBPNet file is
composed from model_resource_file, so preparation and scoring name the same files under one layout. Staged
file names come from the declared weights_format and peaks_compression, never from a resource URI.
Preprocessing emits a manifest that records the ordered weights, peaks, genome, strand policy, producer
image, and output digests. The scoring plan reads the conventional peak-distribution and safe interval-index
paths directly and does not require a manifest, an Altar-owned directory, or an adoption step. With
ChromBPNetRunInputs.verify_preprocessing, it also passes the manifest and the expected preprocessing identity,
and the runtime refuses artifacts prepared for another configuration or reference. Historical scores and
externally managed artifacts are not rewritten or recomputed.
Existing callers migrating from Altar core must install this package and replace imports such as
from altar.models import ChromBPNetPlugin with from altar_chrombpnet import ChromBPNetPlugin. Registry-based
callers need only install the package; the CHROMBPNET key is unchanged.
Metadata
Release files for altar-chrombpnet 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_chrombpnet-0.3.0.tar.gz | 63.1 kB | Without provenance | Details for altar_chrombpnet-0.3.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| altar_chrombpnet-0.3.0-py3-none-any.whl | Python 3 | none | any | Details for altar_chrombpnet-0.3.0-py3-none-any.whl |
Total release size: 91.2 kB
Release files / altar_chrombpnet-0.3.0.tar.gz
| Download URL | altar_chrombpnet-0.3.0.tar.gz |
|---|---|
| Size | 63.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e841cef1e03f8cc2e0346bdf59d6c06d1a18fcb39a481bc770e2772799317cb6
|
|
BLAKE2b-256 checksum How to use checksums |
d7f9b79ffab1109bd23029c27d79394bf64cc5bd966880f082300764d015a857
|
| 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_chrombpnet-0.3.0-py3-none-any.whl
| Download URL | altar_chrombpnet-0.3.0-py3-none-any.whl |
|---|---|
| Size | 28.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
014268bf864b649a39b9991d145117bb7dcab57c8ca934a5979a12076098ba70
|
|
BLAKE2b-256 checksum How to use checksums |
7efb31ec83e2debf335b760a1f811b5d1b40f61278997d2cb41e5ec93f37d221
|
| 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-chrombpnet 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.