-
Notifications
You must be signed in to change notification settings - Fork 6
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.
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
Exclude MoCo Series from compliance evaluations #43
Comments
|
i think it would be good to have a config file, letting users make different types of rules, inclusions, exclusions, thresholds etc |
Right! Can be addressed together with Issue #17 |
Proposed JSON file template. I think we can move some of the CLI arguments which are never used, but still are useful such as include_phantom, include_nifti_header, skip_parameters {
"begin": "2014-03-12T13:37:27+00:00",
"end": "2017-03-12T13:37:27+00:00",
"include_sequence": {
"localizer": false,
"nifti_header": false,
"moco": false,
"sbref": false
},
"skip_parameters": [
"BodyPartExamined",
"StationName"
],
"exclude_subects": [
"210098",
"210078"
]
} |
Can be addressed together with Issue #29 |
Siemens automatically generates motion corrected series for fMRI sequences. We observe that several fMRI sequences are collected together under a new sequence, called mocoseries. As they are different sequences with different protocols, it shows up in the report as non-compliance. We saw that the reference protocol computed is very similar to fmri-ringrewards.
How can we differentiate between raw formats and derivatives? Is there a DICOM flag?
The text was updated successfully, but these errors were encountered: