altar-chrombpnet
Adds ChromBPNet to Altar: predicted effects of variants on chromatin accessibility in one cell type, from a five-fold model ensemble, run in a container on an NVIDIA GPU.
Validation: Reference comparison (compared with kundajelab/varscore). Interpretation: Provisional.
pip install altar-chrombpnet
Fetch ENCODE's K562 DNase ensemble and write its resource manifest, then derive the files scoring reads:
altar-chrombpnet-resources fetch-official --output-dir chrombpnet-resources
altar prepare spec.toml --model k562-dnase
A run spec section:
[models.k562-dnase]
type = "CHROMBPNET"
resource_manifest = "chrombpnet-resources/chrombpnet.resources.json"
ChromBPNet scores, prepares and interprets bias-corrected models only. The five fold files must be
model.chrombpnet_nobias.fold_<k>.<experiment>.h5, not the full model.chrombpnet.fold_<k>.<experiment>.h5, whose
predictions keep the Tn5 or DNase bias, and not a standalone bias model. Check them before you register a model:
pip install 'altar-chrombpnet[inspect]'
altar-chrombpnet-resources inspect fold_*/model.chrombpnet_nobias.fold_*.h5
It prints one JSON line per file, with its kind (absent, included or bias_only) and input and output
lengths, and exits 1 if any file is not bias-corrected (absent). Both scoring images a run can select refuse
such a fold file before loading it, too.
altar models chrombpnet lists the columns and configuration fields.
Documentation: https://kundajelab.github.io/altar/integrations/chrombpnet/
Cite and terms
- ChromBPNet: Pampari A, et al. bioRxiv (2024), doi:10.1101/2024.12.25.630221. The ChromBPNet code is MIT-licensed.
- The official K562 models are ENCODE data, free to use; cite ENCODE and the accessions you used.
Licence
MIT. See LICENSE.
Metadata
Release files for altar-chrombpnet 0.9.1
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.9.1.tar.gz | 90.2 kB | Without provenance | Details for altar_chrombpnet-0.9.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| altar_chrombpnet-0.9.1-py3-none-any.whl | Python 3 | none | any | Details for altar_chrombpnet-0.9.1-py3-none-any.whl |
Total release size: 127.8 kB
Release files / altar_chrombpnet-0.9.1.tar.gz
| Download URL | altar_chrombpnet-0.9.1.tar.gz |
|---|---|
| Size | 90.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5e7434499dc26617d7211f569773663af6475e4ee9a352c475ac6265b20865be
|
|
BLAKE2b-256 checksum How to use checksums |
8d18fd7a602502bf8483351c1a3cbbfd9879dd2d3f40d6c8b51bb17552767722
|
| 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.9.1-py3-none-any.whl
| Download URL | altar_chrombpnet-0.9.1-py3-none-any.whl |
|---|---|
| Size | 37.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d675e0e71b2906afa121877e4010281aedb4357580e2c6884b7edce9bf561a82
|
|
BLAKE2b-256 checksum How to use checksums |
9334b24b03a31f0bf5541702570eb51bfbc0c3aa2cdb9ccd9f4e1bdeaaa48319
|
| 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.9.1
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.