domains / families / data / dicom-series-to-volume

dicom-series-to-volume

separate

Used for converting one CT DICOM series folder to a HU NIfTI volume with affine evidence. Not for multi-frame DICOM or clinical use.

When to use

• Used for converting one CT DICOM series folder to a HU NIfTI volume with affine evidence. Not for multi-frame DICOM or clinical use.
• Use the wrapper exactly as documented; do not replace the upstream entrypoint with a handwritten implementation.
• Manifest I/O: inputs are `dicom_dir`; outputs are `nifti_volume` and `result_json`.

When not to use

• Single-series only; multi-series input is rejected at preflight.
• Multi-frame DICOM (NumberOfFrames > 1 per file) not supported.
• Compressed transfer syntaxes (JPEG / JPEG2000 / RLE) not supported.
• No voxel reorientation. The affine is derived from DICOM headers and represented in NIfTI/RAS coordinates; a downstream gate (e.g. expected_axcodes) is expected to assert orientation before this volume is fed to a segmentation model.
• Not for clinical deployment, autonomous diagnosis, regulatory submission, production inference (use a vetted converter such as dcm2niix for that).

Skill page

Source