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

Terminate statistical analyses for unsupported mixed data types #338

Open
neurolabusc opened this issue Jan 20, 2022 · 0 comments
Open

Terminate statistical analyses for unsupported mixed data types #338

neurolabusc opened this issue Jan 20, 2022 · 0 comments

Comments

@neurolabusc
Copy link

The most recent release of dcm2niix changed its default behavior to preserve original data type (e.g. the default is now -l o, where old default behavior was -l n). This ensures that multiple runs acquired with UINT16 datatype are always saved as UINT16 (which AFNI does not internally support, so they get promoted to FLOAT32 at the cost of disk space). This avoids the rare situation where a first level analysis might have two series of data where one run was saved as the supported INT16 and the other as FLOAT32, with AFNI generating bogus statistical images.

A user first described this issue in 2019. While recent versions of dcm2niix prevent this unlikely situation, we should also make sure that AFNI correctly detects the error and terminates, rather than generating bogus images. This will protect users analyzing data converter with older versions of dcm2niix, using modern dcm2niix with different settings (to preserve disk space), or using different tools.

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