DICOM Splitter
This gear is meant to split DICOM archives into two or more archives. The main use cases for this gear are if,
- There are one or more localizers (scouts, etc.) mixed in with primary images
- There are multiple Series in one archive.
- The archive is multiphasic with respect to slice location (geometry split)
- The archive has non uniform image orientations (geometry split)
- Some field varies across the archive and you have reason to the archive based on that field (Note: This "group by" option is exclusive if a previous geometry split is performed)
The gear is set to do the first two above by default, i.e. it will extract a localizer(s) from the archive, and it will extract each unique SeriesInstanceUID into its own archive.
Usage
Inputs
- dicom : DICOM archive input
Configuration
- extract_localizer (boolean, default True): Whether or not to extract localizer from archive.
- group_by (string, default "SeriesInstanceUID"): Comma separated list of dicom tags to split the archive on.
- tag (string, default "splitter"): The tag to be added on input file upon run completion.
- debug (boolean, default False): Include debug output.
- delete_input (boolean, default True): Delete input if DICOM is successfully split.
Outputs
The gear will output nothing if no splitting action was taken. Otherwise it will output a variable number of archives depending on the input and configuration named with the following pattern:
series-<SeriesNumber>_<Modality>_<SeriesDescription>_<GroupByTags>[_localizer], where
SeriesNumberis the value of theSeriesNumbertag across the archive. By default the largest sized archive (by number of slices) will retain the originalSeriesNumberand additional archives will be incremented by1000 + i, whereiis the index of the archive in a list of total archives.SeriesDescriptionis the value of theSeriesDescriptiontag across the archiveGroupByTagsis an underscore separated list of all tags appearing in thegroup_bylist, and their corresponding value in that archive. Tags "SeriesInstanceUID" and "SeriesNumber" are not included even if they appear in thegroup_bylist.Modalityis the value of theModalitytag across the archive- If the series is a localizer,
_localizerwill be appended.
Metadata
Release files for fw-gear-splitter 1.7.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| fw_gear_splitter-1.7.2-py3-none-any.whl | Python 3 | none | any | Details for fw_gear_splitter-1.7.2-py3-none-any.whl |
Release files / fw_gear_splitter-1.7.2-py3-none-any.whl
| Download URL | fw_gear_splitter-1.7.2-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a82105c68c1b106123dd2986b00ea738b36f2917120e2b878e494f3f2f71b4b2
|
|
BLAKE2b-256 checksum How to use checksums |
a13c49e9c6fe7d175f48c093bfa8fa68b4254dd26e05f0362bafb7097de4dca6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.8.2 CPython/3.9.19 Linux/5.15.146+
|
Security for fw-gear-splitter 1.7.2
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.