Closed rpeltekov closed 2 months ago
I have it working to this capacity. performance seems iffy
as talking before, performance might be very limited slice by slice, with just gradients. either might need to solve for a wider number of slices, than just the ones sandwiching the selected slice, or maybe just need to switch over to using just the ROI and volume shimming. i don't know much how to expect performance of the shim system here...
to write it down here too:
the purpose of an overwrite background button will be as miki sort of designed in what he expected as a feature. you should be able to click a button, save the current shims, and then solve for a more close solution again? since the measurements themselves are noisy maybe this is where there is some leverage from resolving the least squares again when you are closer to the solution.
nevermind. performance is very directly tied to the auto-prescan settings that are used. I was using previous / old prescan settings via the load state button...
latest plan on the "principle sols"
some slices dont work but here is an example of when it did pretty well tbf....
After talking / showing Miki the UI, there were a series of usability fixes that should be implemented to make the tool actually useful
dependent on #2
Where I am leaving off June 5 evening: it looks like it can properly obtain the first fieldmap and then do the basis map scan after that and generate expected fields, etc...