Phenotype2Phenopacket
Phenotype2Phenopacket is a command-line interface (CLI) application for the construction of phenopackets from a phenotype annotation file.
Installation
Phenotype2Phenopacket can be installed from PyPi.
pip install phenotype2phenopacket
Usages
To convert all OMIM diseases in a phenotype annotation file to disease phenopackets, where all phenotypes are retained:
p2p convert --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir
To convert all OMIM diseases in a phenotype annotation file to lightweight disease phenopackets (without phenotypic features):
p2p convert --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir --skip-phenotypic-features
To create synthetic patient disease phenopackets, where the dataset is more variable and frequencies are taken into account and constrained noise is applied :
p2p create --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir
You can also limit the number of disease phenopackets converted/created:
p2p convert --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir --num-diseases 100
Or limit for a specific OMIM disease:
p2p create --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir --omim-id OMIM:619340
Or limit for a list of OMIM IDs specified in a text file, with each ID separated by a new line:
p2p create --phenotype-annotation /path/to/phenotype.hpoa --output-dir /path/to/output-dir --omim-id-list /path/to/list.txt
To add known gene-to-phenotype relationships to phenopackets:
p2p add-genes --phenopacket-dir /path/to/synthetic-phenopackets --genes-to-disease /path/to/genes_to_disease.txt --hgnc-data /path/to/hgnc_complete_set.txt --output-dir /path/to/output-dir
NOTE: To add known gene-to-phenotype the genes_to_disease.txt is expected. It can be downloaded here.
Metadata
Release files for phenotype2phenopacket 0.6.18
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 |
|---|---|---|---|---|
| phenotype2phenopacket-0.6.18.tar.gz | 4.0 MB | Without provenance | Details for phenotype2phenopacket-0.6.18.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| phenotype2phenopacket-0.6.18-py3-none-any.whl | Python 3 | none | any | Details for phenotype2phenopacket-0.6.18-py3-none-any.whl |
Total release size: 8.0 MB
Release files / phenotype2phenopacket-0.6.18.tar.gz
| Download URL | phenotype2phenopacket-0.6.18.tar.gz |
|---|---|
| Size | 4.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
493c2109ca9af075dce6ce06ef2cc0c929837d04f59b469c675f785a504bb8df
|
|
BLAKE2b-256 checksum How to use checksums |
8756852ff1e56f897f75779f6a19161b30a1fe41781311a6da5452ccf1d7e419
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Release files / phenotype2phenopacket-0.6.18-py3-none-any.whl
| Download URL | phenotype2phenopacket-0.6.18-py3-none-any.whl |
|---|---|
| Size | 4.0 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0ed6a60823d27e21f4144ce11773cb54eda23fe6d6757a5e73e093b16e824f1d
|
|
BLAKE2b-256 checksum How to use checksums |
6108e8cc8acd83ab44e9b839f14ddb7107d71d3b8966e1bcfb2235fd80fa1632
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Security for phenotype2phenopacket 0.6.18
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.