ID-uptake-values
Estimate SUV (body-mass normalised) and SUL (lean-body-mass normalised) PET images without DICOM metadata such as injected dose or patient weight. Total activity and body mass / lean body mass are inferred from the images themselves, using TotalSegmentator masks and a k-nearest-neighbour model over axial distribution functions.
Installation
pip install . # or: uv sync
The model weights are bundled with the package.
Usage
Inputs are NIfTI files: PET, CT, and TotalSegmentator segmentations (total, body, and for SUL also tissue).
# SUV
python -m id_uptake_values.suv --pet pet.nii.gz --ct ct.nii.gz \
--totalseg total.nii.gz --bodyseg body.nii.gz \
--output-image suv.nii.gz --output-json suv.json
# SUL (optionally with a debug plot of the alignment and nearest-neighbour fit)
python -m id_uptake_values.sul --pet pet.nii.gz --ct ct.nii.gz \
--totalseg total.nii.gz --tissueseg tissue.nii.gz --bodyseg body.nii.gz \
--output-image sul.nii.gz --output-json sul.json --debug-image debug.png
The JSON contains the estimated activity (MBq), the estimated body mass or lean body mass (kg), and the denominator the PET image was divided by.
The scan must cover the region from C1 to the sacrum; otherwise a ValueError is raised.
Development
uv sync
uv run pytest
The tests download subject sub-000 from the DEPICT-RH/Multimodal-HC dataset into the Hugging Face cache.
Metadata
Release files for id-uptake-values 0.1.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 |
|---|---|---|---|---|
| id_uptake_values-0.1.0.tar.gz | 12.6 MB | Without provenance | Details for id_uptake_values-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| id_uptake_values-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for id_uptake_values-0.1.0-py3-none-any.whl |
Total release size: 25.3 MB
Release files / id_uptake_values-0.1.0.tar.gz
| Download URL | id_uptake_values-0.1.0.tar.gz |
|---|---|
| Size | 12.6 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db9982bbf089300bffdec0f15407105ea1b857e6e1d0dec1d0868c051a8b8957
|
|
BLAKE2b-256 checksum How to use checksums |
7b4645d7e6136c4d81210fcef0f5f8b37881a1478360c83085fe068b24a26e27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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 / id_uptake_values-0.1.0-py3-none-any.whl
| Download URL | id_uptake_values-0.1.0-py3-none-any.whl |
|---|---|
| Size | 12.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5d2e9b775af5e786be2f08938a57cf80d366b591685dc192a0727111da682491
|
|
BLAKE2b-256 checksum How to use checksums |
50b96cddd737fb54088fcb867d49467fb80f668f6c67ea80cfc18a1151570df8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.12.23 {"installer":{"name":"uv","version":"0.12.23","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 id-uptake-values 0.1.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.