</center></p><p>Here we have the axes \(x\) and \(y\) which describe how the map coordinates needs to be interpreted and the axes \(A_1\), \(A_2\), \(A_3\) which describe how the Euler angles, and in consequence, the pole figures needs to be interpreted. We see that in non of these settings the map reference system coincides with the Euler angle reference frame.</p><p>This situation is not specific to EDAX but occurs as well with EBSD data from Oxford or Bruker, all of them using different reference system alignments. For that reason MTEX stronly recommends to transform the data such that both map coordinates and Euler angles refer to the same coordinate system.</p><p>Doing this we have two choices:</p><div><ol><li>transfrom everything to the reference system \(x\), \(y\) using the option <code class="language-plaintext highlighter-rouge">'convertEuler2SpatialReferenceFrame'</code>. This will keep the map coordinates while changing the Euler angles</li><li>transfrom everything to the reference system \(A_1\), \(A_2\), \(A_3\) using the option <code class="language-plaintext highlighter-rouge">'convertSpatial2EulerReferenceFrame'</code>. This will keep the Euler angles while changing the map coordinates.</li></ol></div><p>In the case of EDAX data imported from an <code class="language-plaintext highlighter-rouge">*.ang</code> file we still need to specify the export option used by the EDAX software. This is done by the options <code class="language-plaintext highlighter-rouge">'setting 1'</code>, <code class="language-plaintext highlighter-rouge">'setting 2'</code>, <code class="language-plaintext highlighter-rouge">'setting 3'</code> or <code class="language-plaintext highlighter-rouge">'setting 4'</code>.</p><p>Since setting 2 is default for most EDAX exports a typical command for importing data from an ang file would look like this</p>
0 commit comments