altar-conservation
altar-conservation adds UCSC's hg38 phyloP 100-way
conservation score at each variant's base to Altar runs, as the phylop100way annotation source.
Maturity: Stable. Validation: Matches upstream on spot checks.
Install
pip install altar-conservation
The source reads the track from a public bucket the Kundaje lab publishes, with no download and no credentials. To build your own copy from UCSC's bigWig:
pip install "altar-conservation[build]"
altar-conservation-build --track phylop100way --input hg38.phyloP100way.bw --output ./phylop100way-hg38
Use it in a run spec
[sources.phylop]
type = "phylop100way"
options = { indels = "max" } # optional: score indels too, by the greatest score over their bases
altar sources phylop100way lists the column and options.
Documentation: https://kundajelab.github.io/altar/integrations/phylop100way/
Cite and terms
- phyloP: Pollard KS, et al. Detection of nonneutral substitution rates on mammalian phylogenies. Genome Research 2010;20(1):110–121. doi:10.1101/gr.097857.109.
- Conserved elements: Siepel A, et al. Genome Research 2005;15(8):1034–1050. doi:10.1101/gr.3715005.
- UCSC Genome Browser: Casper J, et al. Nucleic Acids Research 2026;54(D1):D1331–D1335. doi:10.1093/nar/gkaf1250.
- Terms: UCSC's phyloP files are freely available for public use; credit UCSC (citing UCSC). The package ships no data.
Licence
MIT.
Metadata
Release files for altar-conservation 0.4.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_conservation-0.4.0.tar.gz | 19.9 kB | Without provenance | Details for altar_conservation-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| altar_conservation-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for altar_conservation-0.4.0-py3-none-any.whl |
Total release size: 34.3 kB
Release files / altar_conservation-0.4.0.tar.gz
| Download URL | altar_conservation-0.4.0.tar.gz |
|---|---|
| Size | 19.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9c402412b7cf0277e040ce66f1da5dceae1ec6b852fa43a9990fbe1a4b3e94e4
|
|
BLAKE2b-256 checksum How to use checksums |
7c47de05f67049fbe16811dcae5380c970e75acb713c573ec0ccfd7c6f81d402
|
| 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_conservation-0.4.0-py3-none-any.whl
| Download URL | altar_conservation-0.4.0-py3-none-any.whl |
|---|---|
| Size | 14.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96b45a40f0977e54edff9aa5b725fafd1c6b40c71ccd943980bfb15976cb1a20
|
|
BLAKE2b-256 checksum How to use checksums |
9f9f555a633b8dfb8b46255080e2d30a99fb0185cf7cf501b093439e989e8f0e
|
| 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-conservation 0.4.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.