Closed htp2 closed 1 year ago
Previously, the "AMBFPose" transform acted within Slicer's coordinate frame choice (RAS). The user had to realize this and align visually based on the AMBF_X, AMBF_Y, AMBF_Z axes provided. This was not very intuitive to the user. So instead, under the hood, that transform will get applied as if it was a transform in LPS (the coordinate frame choice from AMBF).
Before the visuals matched, but the transformation matrix in Slicer was in RAS not LPS.
Now both should match (visuals AND numbers)
…riendly