-
Notifications
You must be signed in to change notification settings - Fork 4
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
FSL MRS issue traced back to ValueError in nifti_mrs #21
Comments
Hi John, This will be an effect of me making sure that the NIfTI-MRS class validation tools abide strictly by the NIfTI-MRS standard, and then making the more recent versions of FSL-MRS require a more recent version of the NIfTI-MRS tools package (with the stricter validation). The requirement for a description was always in the standard for any user-defined header values, because we allow anything to be put in that doesn't collide with those defined in the standard, and therefore it's useful to know what the header values mean. On the flip side, if you form the files using these tools it should always be compliant. In this particular case it looks like there are two values of conversion time:
The first, In this instance you can probably just blow away that second conversion time and then it will be compliant. |
You can do this by loading the file using the Something like
|
Hi Will, thank you very much! It seems I will need to update my notebook for converting my simulations to NIfTI-MRS. I'll give your suggestion a try. Thanks again! |
I am trying to use FSL MRS interactively and I've run into the following error:
This happens with every input file, but we used FSL MRS to fit all of this data this summer, so I know it worked a few months ago.
I went through the data file using the following code:
And got the following output showing that 'conversion_time' does in fact have a filled in value pair.
Do you have any suggestions for what could be causing this and how to fix it or work around it?
Best,
John
The text was updated successfully, but these errors were encountered: