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
The EchoTimeDICOM field stores a value in milliseconds, but BIDS specifies it in seconds.
When ezBIDS reads NIfTI images + JSON sidecars, it multiplies the EchoTime by 1,000. This scaling should not be necessary since most tools producing the sidecars (e.g. dcm2niix) already convert from milliseconds to seconds. The scaling probably should be removed, as it results in an incorrect conversion for my data (in the below example, the JSON sidecar stores 0.004s, but after the conversion the result is 4s):
The text was updated successfully, but these errors were encountered:
astewartau
changed the title
Echo times should not require scaling if extracted from NIfTI JSON sidecars
EchoTime should not be converted to miliseconds
Oct 10, 2024
astewartau
changed the title
EchoTime should not be converted to miliseconds
EchoTime should not be converted to milliseconds
Oct 10, 2024
The
EchoTime
DICOM field stores a value in milliseconds, but BIDS specifies it in seconds.When ezBIDS reads NIfTI images + JSON sidecars, it multiplies the
EchoTime
by 1,000. This scaling should not be necessary since most tools producing the sidecars (e.g.dcm2niix
) already convert from milliseconds to seconds. The scaling probably should be removed, as it results in an incorrect conversion for my data (in the below example, the JSON sidecar stores 0.004s, but after the conversion the result is 4s):The text was updated successfully, but these errors were encountered: