sinhaharsh/protocol

generic framework to develop protocols

protocol

Library and utilities to develop protocols and check for protocol compliance in medical imaging.

We use the term "protocol" here loosely, to refer to MRI acquisition protocols, or neuroimaging data QC protocols.

Current release focuses on MRI image acquisition protocols for QA purposes only.

Features

• simple tool to check for protocol compliance :

  ensure all subjects in a given dataset were acquired with same/compatible values for few key parameters.

• programmatic parsing of Siemens protocols in XML format

Documentation

• Docs with examples : https://raamana.github.io/protocol
• Free software: Apache 2.0 license

protocol's Issues

Catch errors in a better way, possible?

See if there is a better way. Can we just catch errors inside setitem?

    try:
        self[pname] = param_class(value)
    except (TypeError, ValueError):
        self[pname] = param_class(Invalid)

Fix Non-linear gradient correction parameter class

NonLinearGradientCorrection ['ORIGINAL', 'PRIMARY', 'M', 'ND']

I am using ImageType tag (0x08, 0x08) to get the information about Non Linear Gradient Correction. However, only the last field (ND) corresponds to non-linear gradient correction. I would have to correct that based on the following information.

Source :
The inclusion of DIS2D or DIS3D in these one of these fields (the former prior to XA30, the latter with XA30 and later) is consistent with NonlinearGradientCorrection being true while ND suggests false.

The proposed criteria would be
If the ImageType list contains DIS2D or DIS3D , then non-linear gradient correction is True.
If the ImageType list contains ND , then non-linear gradient correction is False.
Otherwise it is Unspecified.

Session info not matching for PET and 7T datasets

slice.get_session_info doesn't match for PET and 7T dicom datasets. Inspect why?

Cannot read private header for PET datasets

Cannot read private header even for Siemens datasets. Why?

Check Software versions in ABCD DTI report. Setup compliance check properly

Reference Value : ['5.3.0','5.3.0.0']
Non-compliant Value : ['5.3.0','5.3.0.3']

Should it be an issue?

How to interpret the following parameters?

WindowCenter
WindowWidth
SmallestImagePixelValue
LargestImagePixelValue
GradientMode
ImagePositionPatient