You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've stumbled upon an issue with a protocol at our imaging facility where the SE EPI PhaseEncodingDirection values are all "j", rather than the PA being "j" and the AP being "j-". When validating the data, no warning messages arose to indicate this issue. From my understanding, SE EPI are prone to error because they can require the user to manually flip the phase encoding direction 180 degrees. Given this, I was wondering if it's possible for the validator to check the SE EPI json files and produce a warning message when the directions are not flipped?
Thanks,
Dan
The text was updated successfully, but these errors were encountered:
This would be a difficult one to write schema rules for. We would need to have some notion of collections of files and collating metadata in a useful way.
More simply, we could do something like check that dir-AP/PA/LR/RL correspond to PhaseEncodingDirections that work with the image affine to produce a consistent orientation.
Hello,
We've stumbled upon an issue with a protocol at our imaging facility where the SE EPI PhaseEncodingDirection values are all "j", rather than the PA being "j" and the AP being "j-". When validating the data, no warning messages arose to indicate this issue. From my understanding, SE EPI are prone to error because they can require the user to manually flip the phase encoding direction 180 degrees. Given this, I was wondering if it's possible for the validator to check the SE EPI json files and produce a warning message when the directions are not flipped?
Thanks,
Dan
The text was updated successfully, but these errors were encountered: