-
Notifications
You must be signed in to change notification settings - Fork 1
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
Register the other shim methods to the GRE CoV scan #35
Comments
Since sub-04 is the one with the worst image quality (chunky lad), I propose using it as a benchmark. Likewise, patient or volume tend to have the lowest signal intensity/contrast, so they are a good worst case scenario. For sub-04, I am looking at CoV-2-CoV (good sanity check), CP-2-CoV, Volume-2-CoV, and Target-2-CoV. I looked at a one-step coreg using affine, slicereg and bsplinesyn. And dl for good measure. Code in question: Using affine: Quite bad on patient, see jumping SC at cursor: Screen.Recording.2024-01-11.at.22.15.17.movUsing slicereg: Screen.Recording.2024-01-11.at.22.27.07.movUsing bsplinesyn: Screen.Recording.2024-01-11.at.22.41.41.movUsing DL: Screen.Recording.2024-01-11.at.22.49.55.movWhat is your opinion @jcohenadad ? |
Thank you for these investigations. The DL algo definitely looks promising. I've had hard time doing a proper registration on sub-04, see preliminary investigations in #57 (comment). The issue is partly because of #58. However, given that we don't absolutely need to report GRE signal across all shim modes (I think there is enough material in the paper so far), I would skip that step for now. |
No description provided.
The text was updated successfully, but these errors were encountered: