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
I'm working on developing a tool to convert Bruker ParaVision 6.0.1 specoscopy data into NIfTI-MRS format (because spec2nii crashes with our data). When I tested the generated .nii.gz file, I found that mrs_tools info doesn't interpret dwell time and spectral width correctly when time unit is not second.
FSL-MRS version: 2.3.1
python version: 3.12
Below is a minimal example to reproduce the error.
$ mrs_tools info ./demo.nii.gz
File demo.nii.gz (/home/nmr/Projects/NIfTI_MRS_converter)
NIfTI-MRS version 0.9
Data shape (1, 1, 1, 128)
Dimension tags: [None, None, None]
Spectrometer Frequency: 100.679124582065 MHz
Dwelltime (Spectral bandwidth): 1.250E+02 s (0 Hz)
Nucleus: 13C
Field Strength: 9.40 T
As you can see, dwell time is interpreted as 125s instead of 125 us.
I found the problem is due to from fsl.data.image import Image, where Image doesn't interpret dwell time correctly. However, I attempted to fix this problem but failed.
For now, the workaround is always using second as the time unit. Don't use "usec" or "msec".
The text was updated successfully, but these errors were encountered:
Hi,
I'm working on developing a tool to convert Bruker ParaVision 6.0.1 specoscopy data into NIfTI-MRS format (because spec2nii crashes with our data). When I tested the generated .nii.gz file, I found that
mrs_tools info
doesn't interpret dwell time and spectral width correctly when time unit is not second.FSL-MRS version: 2.3.1
python version: 3.12
Below is a minimal example to reproduce the error.
As you can see, dwell time is interpreted as 125s instead of 125 us.
I found the problem is due to
from fsl.data.image import Image
, whereImage
doesn't interpret dwell time correctly. However, I attempted to fix this problem but failed.For now, the workaround is always using second as the time unit. Don't use "usec" or "msec".
The text was updated successfully, but these errors were encountered: