-
Notifications
You must be signed in to change notification settings - Fork 296
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
fieldmap-less distortion correction not working #3089
Comments
I believe this should have been fixed by #3060. Can you try 23.1.4? |
Thanks! That works! And wow, it seems to work better than using the actual fieldmaps... |
That's good to hear... I'm finding some cases where SyN is failing pretty badly, and I hope it's just that I'm finding new cases and we haven't somehow broken it for everybody. |
I don't have a ton of data points on SyN yet, but maybe something is off with our fieldmaps in some cases. We'll investigate further and post to NeuroStars or file a separate issue if it looks like a potential bug with how fieldmaps are being handled with our data. |
I'm also looking into fieldmaps. There's an issue with resampling the fieldmap onto the target space that seems to be affecting phasediff fieldmaps in particular, and I don't yet understand why. |
What happened?
We have a few subjects where the fieldmaps weren't collected correctly for all of the runs because the subject got out of the scanner and we didn't collect a second fieldmap when they got back in the scanner. So, we're trying to use
--use-syn-sdc
and--ignore fieldmaps
on these subjects, but FMRIprep is crashing (see error/log information below).I'm only using the
--ignore fieldmaps
flag because we haven't yet updated our IntendedFor fields in the json files for these subjects. Ultimately, I'd like to use the fieldmap we collected for the runs that we collected before the subject got out of the scanner, and then use fieldmap-less distortion correction for the runs that were collected after the subject got back into the scanner.Thanks!
David
What command did you use?
What version of fMRIPrep are you running?
23.1.3
How are you running fMRIPrep?
Singularity
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered: