Unfortunately, unless it’s in the scanner protocol, I do not know the scanner software version, but will see what I can find out! Unless, “XA30” is the software version…?
Ah, great - that is a use case we have not yet encountered, an XA30 sequence with an internal water reference scan (Sequence → Common → Ref. Scan Mode = Inline Correction)! This was not possible on older Siemens software versions. It means that the sequence itself acquires a water reference scan and stores it alongside the metabolite data (and you do not need to acquire a separate water reference scan).
I am not sure whether you are able to share these data institutionally (we have deidentification scripts in the Osprey folder), but they would be very helpful for us (and we need to modify the loader to fix the problem). If you can’t, phantom data acquired with the same protocol will do.
I just tried to reproduce the error you reported but the data (from the right ventral striatum) load and process totally fine. I’m noticing that in your job file you’re pointing to the exact same file (meas_MID00084_FID46817_RightVS_svs_se_30_TXRX_TR200.dat) for both files and files_ref, so I assume you made a simple copy/paste error. I used the water-unsuppressed file meas_MID00085_FID46818_RightVS_svs_se_30_TXRX_NWS_TR2000.dat in files_ref and everything is peachy.
I have not investigated the inline water correction mode right now but the dataset will be useful to explore that once I have more time.
I have not looked at the ACC data that you have acquired with a different protocol (please share that protocol).
I also have some feedback on your protocol in general:
(IMPORTANT) Whenever you acquire a separate water reference, you need to set Sequence → Common → Delta Frequency to 0.0 ppm so that the water reference signal is co-localized to the water-suppressed acquisition (this counters the chemical shift displacement artefact).
(SOMEWHAT LESS IMPORTANT) 12 transients for the water-unsuppressed scan is plenty. You can easily get away with 4 because you get so much signal.
Since these are protocol issues that I give feedback on very frequently, I should probably write a sticky post about them… maybe this weekend if I find time.
Thank you greatly for this feedback and guidance! Thank you for the feedback on our MRS protocol!
Could you share your job file? I have changed the file name for the “files_ref” input but continue to get an error when I try to load the data in the GUI.