Closed ProjX0 closed 2 weeks ago
This auto calibration method is based on the zeroth order consistency conditions, so it is an absolute necessity that the projections not be truncated. If you know of a calibration method that works with truncated data, please send me a reference.
Yes, you are correct, that is a typo and should be convert_to_modularbeam(). I just fixed this on the development branch.
Your updated code looks fine to me. The authors state that the cost function is only locally convex, so if your initial guess isn't close to the true solution, it may just converge to a local minimum.
The new geometric_calibration.py in leap v1.13 is very useful. However, it would be even more helpful if it could also work with offset scans.
Additionally, I have two issues: First issue: Is leapct.convert_to_modular() correct at line 214 of d12_geometric_calibration.py? I suspect it should be convert_to_modularbeam().
Second issue: In the example of d12_geometric_calibration.py, it seems to find up to three variables correctly. However, it doesn't seem to find four geometric variables (centerRow, centerCol, tau, and detector tilt). I tested it by modifying the code as follows. Is the code I changed incorrect, or is it that optimization doesn't work well with four variables?