Skip to content

add ScannerInformation.collimatorType (as in DICOM) #198

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
KrisThielemans merged 2 commits into from
Aug 21, 2026
Merged

add ScannerInformation.collimatorType (as in DICOM) #198

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
de3c620
add ScannerInformation.collimatorType (as in DICOM)
KrisThielemans Aug 17, 2026
5875fe8
refer to dicom spec
KrisThielemans Aug 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions model/ScannerInformation.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,6 +93,14 @@ ScannerInformation: !record
# An empty field implies the identity transformation.
gantryAlignment: RigidTransformation?

# Collimator Type.
# Defined Terms in 2026 (required):
# NONE (no collimator), RING (transverse septa)
# Please refer to the DICOM specification.
# (0018,1181) (Enhanced PET Acquisition Module)
# https://dicom.nema.org/medical/dicom/current/output/html/part03.html#table_C.8.22-2
collimatorType: string

# Edge information for TOF bins in mm
#
# This is a nested vector with elements of type BinEdges, i.e. it specifies the edges for every module-pair
Expand Down