I think we currently have too many way of representing matrices in the IMP API.<br>- Rotation3D<br>- EulerAnglesZYZ<br>- and EulerMatrix<br><br>The last doesn&#39;t make any sense as there is no reason to tie together two disparate representations. Given that one can create a Rotation3D from Euler angles I don&#39;t see any reason to expose the second. If we find rotational matrices are faster than quaternions for actually performing the rotations, then we should cache the matrix in Rotation3D rather than add another class.<br>
<br>Comments? Justifications for having many different versions?<br>