<div dir="ltr"><div dir="ltr"><div dir="ltr">Laurent,<div><br></div><div>This came directly from the implementation group discussions back in Dec 2018.</div><div><div>gWCS has use cases where more than 3 rotations are useful, for example EulerRotation(angles=[12, 1, 2, 3], axes=‘xyzx’).</div><div>So we've taken this approach of having a sequence of EulerAngles which specify the 'axis of rotation' (of the 3D space as either 'x', 'y', or 'z') and angle.</div><div><br>Mark</div></div><div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 2, 2020 at 8:31 AM Laurent MICHEL <<a href="mailto:laurent.michel@astro.unistra.fr">laurent.michel@astro.unistra.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">Dear,<br>
<br>
My comment #1: Why is the Euler Transformation class so complex?<br>
<br>
- It is always a 3D transformation, this there is no reason to setup a <br>
1-* aggregation with angles.<br>
<br>
- Euler angles (nutation, rotation, intrinsic rotation) are well <br>
defined, there is no need for a specific datatype (EulerAngle). So we <br>
could just have 3 class attributes.<br>
<br>
- Using a specific datatype where angles are identified by a the name of <br>
the rotation axis supposes we have a vocabulary for this, which is a bit <br>
complicated for this purpose with the risk a implementation errors.<br>
<br>
Take care of yourself.<br>
<br>
LM<br>
<br>
-- <br>
---- Laurent MICHEL Tel (33 0) 3 68 85 24 37<br>
Observatoire de Strasbourg Fax (33 0) 3 68 85 24 32<br>
11 Rue de l'Universite Mail <a href="mailto:laurent.michel@astro.unistra.fr" target="_blank">laurent.michel@astro.unistra.fr</a><br>
67000 Strasbourg (France) Web <a href="http://astro.u-strasbg.fr/~michel" rel="noreferrer" target="_blank">http://astro.u-strasbg.fr/~michel</a><br>
---<br>
</blockquote></div>