Fix geometry for translation motors
According to the Nexus standard there are only 3 keys that are related to the position of the sample in space.
x_translation
y_translation
z_translation
No key is designed to handle the position of the base translation
In Bliss-tomo there is a different definition
translation_x #below rotation axis
translation_y #below rotation axis
translation_z #below rotation axis
sample_u #real x motor
sample_v #real y motor
sample_x #pseudo x motor related to rotation angle
sample_y #pseudo y motor related to rotation angle
In nxtomomill there is:
X_TRANS_KEYS = ("sx", "d3tx", "tfx", "px", "fake_sx")
"""Keys used to find the x translation"""
Y_TRANS_KEYS = ("sy", "d3ty", "hry", "py", "fake_sy")
"""Keys used by bliss to store y translation"""
Z_TRANS_KEYS = ("sz", "d3tz", "hrz", "pz", "mrsz", "fake_sz")
"""Keys used by bliss to store translation"""
Y_ROT_KEY = "instrument/positioners/yrot"
"""Key used by bliss to store the estimated center of rotation for half
acquisition"""
We need to improve the motor definitions in reading the Bliss h5 file and pass the arguments correctly to NxTomo