You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MX offers two main forms of "line" scan - Helical and Wedged.
Helical is straight forward, omega is continuously rotated while the sample stages move between positions.
Wedged is more tricky.
Omega performs part of its rotation and different x, y positions. That is, the full rotation is broken up into stages, performed at different points.
The first wedge happens at "(0, 0)", the next part at "(1, 1)".
We don't have a good way of describing such scans. We could specify the full x, y arrays as an ArrayGenerator and zip them with omega, but that is inelegant, and far from concise.
MX also has the concept of Inverse Beam data collections:
MX offers two main forms of "line" scan - Helical and Wedged.
Helical is straight forward, omega is continuously rotated while the sample stages move between positions.
E.g. scan axis values are:
Wedged is more tricky.
Omega performs part of its rotation and different x, y positions. That is, the full rotation is broken up into stages, performed at different points.
The first wedge happens at "(0, 0)", the next part at "(1, 1)".
We don't have a good way of describing such scans. We could specify the full x, y arrays as an ArrayGenerator and zip them with omega, but that is inelegant, and far from concise.
MX also has the concept of Inverse Beam data collections:
Here omega performs a full rotation, but again broken up into wedges that are "flipped" between a rotation started at 0 and a rotation started at 180.
The text was updated successfully, but these errors were encountered: