I ran into a weird symmetrize issue where I wasn't getting the expected number twin components. The following code demonstrates the issue and to first order the crystal symmetries look the same:
%% Load from cif and define twins
cs1 = crystalSymmetry.load('Mg-Magnesium.cif')
sS1 = slipSystem.twinT1(cs1);
% consider all symmetrically equivlent slip systems
sS1 = sS1.symmetrise('antipodal')
%% Similarly define
mtexdata twins silent
sS2 = slipSystem.twinT1(ebsd{2}.CS);
% consider all symmetrically equivlent slip systems
sS2 = sS2.symmetrise('antipodal')
It seems this was already fixed in 2d89fb3e957d855ea6b9afbcc150dea7cb12da1b. Could you checkout the current development version? I will also release a new beta shortly.
Hi guys,
MTEX 5.4 Matlab 2020b
I ran into a weird symmetrize issue where I wasn't getting the expected number twin components. The following code demonstrates the issue and to first order the crystal symmetries look the same:
Outputs:
Regards, Dan