Skip to content
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

EchoTime should not be converted to milliseconds #137

Open
astewartau opened this issue Oct 9, 2024 · 0 comments
Open

EchoTime should not be converted to milliseconds #137

astewartau opened this issue Oct 9, 2024 · 0 comments

Comments

@astewartau
Copy link
Contributor

astewartau commented Oct 9, 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):

Screenshot_20241009_153124

@astewartau 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 astewartau changed the title EchoTime should not be converted to miliseconds EchoTime should not be converted to milliseconds Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant