Useability Fixes that are necessary

rpeltekov commented 3 months ago

After talking / showing Miki the UI, there were a series of usability fixes that should be implemented to make the tool actually useful

[x] AutoPrescan checkbox: just a checkbox that should default on for first scan, to show it will autoprescan, then it checks off for subsequent scans. should allow the user to check it on in the future too. doing so should scrap the old default CF / linear shim values
[x] Single Fieldmap Button only: there should be only one button to do a fieldmap. currents / correct values should be computed off just the latest scanned fieldmap

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...

[x] overwrite background button seems to not function correctly. need to evaluate how this functions as expected more adeptly...
[x] need to then make sure that clicking the fieldmap button a second time performs as expected and saves a shimmed fieldmap again at the position that I expect it
[x] then need to test things again with the ROI selected, and start developing things on the third checkmark here.

rpeltekov commented 3 months ago

I have it working to this capacity. performance seems iffy

rpeltekov commented 3 months ago

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...

rpeltekov commented 3 months ago

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.

rpeltekov commented 3 months ago

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...

rpeltekov commented 3 months ago

latest plan on the "principle sols"

rpeltekov commented 3 months ago

some slices dont work but here is an example of when it did pretty well tbf....

rpeltekov / ge3t_shim_tool

Useability Fixes that are necessary #20