Dicom-To-CNN
Install : pip install dicom-to-cnn
Features :
- Description of Series content in a huge dataset of DICOM (output JSON descriptor for each series containings main DICOM tags).
- Conversion :
- Dicom to Nifti
- Mask to RTSS and DICOMSeg
- RTSS to mask
- DicomSeg to mask
- PET/CT
- Conversion Bqml/Counts to SUV and SUL
- Fusion
#Maintainer : Salim Kanoun #Contributors : Thomas Trouillard, Wendy Revailler
Metadata
Release files for dicom-to-cnn 0.76
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 |
|---|---|---|---|---|
| dicom_to_cnn-0.76.tar.gz | 42.3 kB | Without provenance | Details for dicom_to_cnn-0.76.tar.gz |
Release files / dicom_to_cnn-0.76.tar.gz
| Download URL | dicom_to_cnn-0.76.tar.gz |
|---|---|
| Size | 42.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4cafc2d64a11c283a4a63daf0b8be248223e1b7bfb60905b354d1a342807b47
|
|
BLAKE2b-256 checksum How to use checksums |
20885548582f489643776074209422674affe82535b55f38ca142016acfa7e63
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.3.0 pkginfo/1.7.0 requests/2.24.0 setuptools/57.1.0 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.5
|
Security for dicom-to-cnn 0.76
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.