Austin Gerlt

question about this because it came up, what should happen in the following situation? ```python from orix.quaternion import Orientation, symmetry pg432 = symmetry.O pg622 = symmetry.get_point_group(180) o1 = Orientation((1, 0,...

Okay, my two cents: I really like the orix convention that for all combinations of Rot/Ori/Mis, A*B gives the same class as B. in that sense, I don't care too...

Alright, I like that logic. Followup to all this then, for symmetry inheritance, I was going to write everything to stick to the following rules: 1) when doing A*B, the...

There has to be a more elegant way to do this, but I imagined it like this: ```python o1._symmetry = S1 o2._symmetry = S2 m12._symmetry[0] = Symmetry(np.vstack([S1[0].data, S2[0].data])) m12._symmetry[1] =...

> We can either go via the quaternion, as in Quaternion.from_axes_angles(ax).to_homochoric() I planned on doing it this way, but only because that's how `scipy.spatial.transform.Rotations` does it, so it's the way...

Thanks, I'll give it a try. And yeah, as a general FYI, we are trying to recreate a very specific piece of software that exists in MTEX but not in...

Sorry for the radio silence. First off, @hakonanes: Thanks for that code snippet. I eventually found I could do "mis = R.__mul__(o1, o2.inv())" and we all started using variations of...

Hey, sorry for the long radio silence, but quick update/question for the experts: After spending a few weeks poking around on this, it seemed to me the best solution was...

@harripj ,you are right, scipy currently sticks you to 1D arrays of rotations. At one point, I thought about making a child class of scipy Rotations to change that, or...

Okay, I gave this a go with the new numpy quaternion objects and the result honestly surprised me. Here is the quick and dirty speed test I did just now:...