Paraphrase
Parse paraphase JSONs.
Usage
Usage: paraphrase [OPTIONS]
Parse paraphase JSONs.
╭─ Options ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ * --input -f FILE Input JSON files (can be multiple) [required] │
│ * --sample -s TEXT Sample names corresponding to input JSON files [required] │
│ --rules -r FILE Optional YAML file with per-gene classification rules (adds 'status' fields) │
│ --skip-keys TEXT Comma-separated keys to skip (e.g. region_depth,final_haplotypes) │
│ --genes TEXT Optional comma-separated list of gene names to process │
│ --output-format -o TEXT Output format: 'json' (default) or 'tsv' [default: json] │
│ --help Show this message and exit. │
╰───────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Example command:
uv run paraphrase \
--input test-data/HG002.paraphase.json \
--input test-data/HG003.paraphase.json \
--input test-data/HG004.paraphase.json \
--sample HG002 \
--sample HG003 \
--sample HG004 \
--rules test-data/rules.yaml \
--genes CFH,CFHR3,f8,GBA,hba,ikbkg,ncf1,neb,opn1lw,pms2,rccx,smn1,strc
Rules YAML (per-gene status classification)
Rules are evaluated per gene. Conditions within a single when mapping are
combined with logical AND (all must be true). If multiple rules match, you can
provide a status_order to pick the most severe (last wins by order).
Example:
smn1:
# Optional; defaults to "normal" if omitted
default_status: normal
# Optional; defaults to [normal, intermediate, pathological] if omitted
status_order: [normal, intermediate, pathological]
rules:
- status: intermediate
when:
smn1_cn: 0
smn2_cn: { ">=": 4 }
reason: "SMN1 deleted but SMN2 high"
- status: pathological
when:
smn1_cn: { "<": 2 }
reason: "SMN1 copy number low"
Metadata
Release files for paraphrase 0.2.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 |
|---|---|---|---|---|
| paraphrase-0.2.0.tar.gz | 2.1 MB | Without provenance | Details for paraphrase-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| paraphrase-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for paraphrase-0.2.0-py3-none-any.whl |
Total release size: 2.1 MB
Release files / paraphrase-0.2.0.tar.gz
| Download URL | paraphrase-0.2.0.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7136efb602b0b29f62c1cdcf20f4140005a607eaac15d9b2b44a4de21fefb0ed
|
|
BLAKE2b-256 checksum How to use checksums |
de1df0b3f71454cb13a0074a7048552231e1e5859fe9801f0c82255ee083ed3b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / paraphrase-0.2.0-py3-none-any.whl
| Download URL | paraphrase-0.2.0-py3-none-any.whl |
|---|---|
| Size | 12.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
081da766217874f26833a074ef311e278361b3e5976824cb27647e09d3350405
|
|
BLAKE2b-256 checksum How to use checksums |
ae3ba8224b65dff7b80d8576e673478292c8d11a2686083e5e19d425466126ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.10.6 {"installer":{"name":"uv","version":"0.10.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for paraphrase 0.2.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.