For pepolar fieldmaps, the reference is actually the mean image estimated by TOPUP. In the future, I would like to select as the reference the EPI image that matches the polarity of the BOLD/SBREF file to be corrected, but this works well enough most of the time.
Yes.
Yes. A bad registration of a fieldmap to a BOLD volume would mean performing a warp where the expected signal sources and targets do not correspond to the right locations in the input image. You should be able to see evidence of this in the first two plots for a functional image, in fMRIPrep 23.2, at least.
So the primary output to check in the reports would be the one on “Alignment of functional and anatomical MRI data (coregistration)”, rather than the ones on SDC and alignment of SDC & “Alignment between the anatomical reference of the fieldmap and the target EPI”?
You really should look at all of it. First, you want to look at the fieldmap report to see that the blue/red distortion blobs show up in reasonable places relative to the brain. (If this isn’t something you have experience with yet, they should at least be ~left/right symmetric in AP images, and focused near the frontal and temporal poles.) Then you want to look at the fieldmap reference-to-BOLD reference registration. It would also be good to look at the fieldmap correction before/after; if you’re not using precisely applicable BOLD inputs, you would expect a little bit of suboptimal correction but you shouldn’t see induced distortion. The coregistration report should clearly line up, though there will be sections where dropout and distortion do not fully recover anatomical fidelity in the BOLD image.
I also want to perform RSA comparing activity between two sessions (within-subject). I originally planned to do parts of the analysis in native EPI space and intended to use the sbref hack mostly for that, given that I thought – perhaps incorrectly – that this would not actually matter after coregistration to T1w space. I assumed that coregistering (to any space) would essentially align images within that space, making it possible to compare between sessions.
[…]Would you consider it necessary to use the sbref hack at all? And if so, would you think it’s sufficient to use it as @cpauley intended (which I had previously misinterpreted) only within session, before coregistering to T1?
If you want to do things in native EPI space and for that to be a single space within each session, then the sbref hack makes sense (and use --output-space bold). If you’re going to be comparing across sessions, you can use the hack, but I would use fake sbrefs from both sessions to find a space that’s equidistant from both sessions; that way you aren’t inducing more resampling artifacts in one than the other. It’s probably simplest just to target the T1w space, though.
How does the alignment pre-coregistration affect alignment post-coregistration (in T1w (or potentially MNI) space)?
The effect should be pretty small.