-
Hi, we have tried running v.23.2.1 (and .0) with a couple of different data sets. None of the outputs include any *desc-bbregister_bold.svg files; instead we have *desc-coreg_bold.svg. It's my understanding that this indicates that bbregistration failed and the fallback to coreg was used (https://neurostars.org/t/fmriprep-coreg-figures/4334/3). However, the summary and boilerplate still indicate that bbregister was used. Has there been a change to fmriprep, so that it no longer creates a *desc-bbregister_bold.svg file? Or is it silently switching to another registration method without changing the boilerplate text? If it's the latter, I see this as a huge problem: people are going to believe and report that they used a registration method that they did not in fact use. If we should in fact be getting *desc-bbregister_bold.svg files: has anyone gotten them with the latest version of fmriprep? Does anyone have any ideas why it might not be working for us? We are running on an HPC using apptainer. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The naming of SVGs no longer reflects the specific coregistration tool that generated the transformation. That's an implementation detail that was used to debug a particular case. The report should be correct. |
Beta Was this translation helpful? Give feedback.
-
Thank you! This is a relief.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Chris Markiewicz ***@***.***>
Sent: Thursday, April 25, 2024 11:52:17 AM
To: nipreps/fmriprep ***@***.***>
Cc: Jolinda Smith ***@***.***>; Author ***@***.***>
Subject: Re: [nipreps/fmriprep] No bbregister_bold file but boilerplate says bbregister was run (Discussion #3275)
The naming of SVGs no longer reflects the specific coregistration tool that generated the transformation. That's an implementation detail that was used to debug a particular case.
The report should be correct.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/nipreps/fmriprep/discussions/3275*discussioncomment-9228616__;Iw!!C5qS4YX3!FxNdqmhQvmaFds6BEt1HX4ifzV_068QEpgxc2LvIuxzyStwDSDHp5qPR6otUCFnXXlCHk_ePjBSc6R9aV7h03muH6Xs$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AD5BI6QRFXZFIBJCA2JODRTY7FGGDAVCNFSM6AAAAABGZMSHFKVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TEMRYGYYTM__;!!C5qS4YX3!FxNdqmhQvmaFds6BEt1HX4ifzV_068QEpgxc2LvIuxzyStwDSDHp5qPR6otUCFnXXlCHk_ePjBSc6R9aV7h0UNxXgew$>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
The naming of SVGs no longer reflects the specific coregistration tool that generated the transformation. That's an implementation detail that was used to debug a particular case.
The report should be correct.