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

Motion Correction XA30 #376

Open
NeuroimagingOL opened this issue Sep 25, 2024 · 4 comments
Open

Motion Correction XA30 #376

NeuroimagingOL opened this issue Sep 25, 2024 · 4 comments

Comments

@NeuroimagingOL
Copy link

Dear all,

We are using the CMRR MB EPI on XA30. To have a first look on the data we want to see the motion correction parameters of the sequence as it is possible in the Siemens Neuro module. However, if I set the parameter "motion correction" in the CMRR sequence, the sequence fails preparation and will not start.

What is the problem? Is it not implemented in the sequence? Is there a work around?

Any help would be appreciated!

best regards,
Tina

@rwmair
Copy link

rwmair commented Sep 25, 2024

Hi Tina,

If I recall correctly, you need to set "Write out SB Ref image" to Off in order to use the features in the Neuro module with the CMRR sequences.

Also, note that you wont be able to run the Neuro module analysis while the scan runs in XA30, as was possible in VE11. Another "benefit" of XA30. :-( You have to wait until the scan is finished, all the series to eventually appear in the Patient Browser, and then load all the derivative files created by the BOLD task card, in addition to the T1w and raw BOLD series, into Neuro3D.

I haven't tried this in XA30 with the CMRR sequences - you may also have to disable 16-bit DICOM output to get it to all work.

Good luck,

Ross

@eauerbach
Copy link
Member

Honestly I have never tested it on XA30. On all versions we have always recommended against using it since it can affect performance, and on XA versions that is even more true. So it is not supported, but also it is not prohibited.

On VD/VE I thought I had some logic to automatically disable the 16-bit DICOM output when inline postprocessing was enabled, since it is a known incompatibility in that case, but on XA30 maybe you need to do it manually. Also prior to XA30 I don't think storing the single-band reference was a problem. But maybe I am mixing up issues with the inline motion correction (configured on the BOLD card) and something else in Neuro/Neuro3D module.

@NeuroimagingOL
Copy link
Author

Dear both,

thanks a lot for you fast reply to my question.

I tried to turn off the SBref image, the 16-bit was already OFF, but still the sequence just did not start, it only starts if I uncheck the motion correction button in the parameter card.

Just to explain the reason, why I tried this: Normally we also do not use motion corrected data directly from the scanner but did motion correction afterwards. However, in the planned study we just quickly wanted to see if the participant moved to much to eventually repeat the measurement. Therefore I found it a nice tool on XA30 to calculate the motion parameters directly to have a quick look if the data is ok or not. Thus, it would be just nice to have. Otherwise we need to realign the data offline (hopefully quickly enough, to restart the measurement).

Best regards,
TIna

@rwmair
Copy link

rwmair commented Sep 26, 2024

Hi Tina,

Following on from Eddie's comment - my response was a mixture of experience with the CMRR sequence in VE11C and only the product sequence using Neuro3D in XA30. I realized later I have also not tried this feature with the CMRR sequence in XA30.

It may be the you need to use the Siemens product BOLD sequence to get the benefit from Neuro3D. Tho that's not a great solution for other reasons.

Alternatively, my colleagues have developed a software tool that plots the motion in real-time during BOLD scans with the data streamed to a seperate computer using the BOLD plugin at the scanner. Details are here:
https://github.com/harvard-nrg/scanbuddy

Ross

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

3 participants