Closed hakonanes closed 1 year ago
This check also serves as a confirmation that the following route of PC value conversion works: Oxford Instruments -> kikuchipy/Bruker -> PyEBSDIndex.
May thanks for putting that together. I guess I have assumed that OXFORD PC == EDAX PC, and thus that direct input of the Oxford PC was not a necessary test. I tried pulling that smaller datafile, but the link is dead already (at least for me). But I really like the integration that you did with kikuchipy. I think the differences I am seeing in the EMsoft IPF and Kikuchipy are likely because you did not specify the camera tilt, and thus using a default value. No big deal, but if anyone asks, this is the likely answer.
Also nice to see that it works well with wide band patterns, that can be harder for Hough-based methods. But what is going on with AZtech? 60% indexing on what looks like nice patterns? Wonder if some of the parameters are not set properly. I will reply in the EMsoft thread expressing my gratitude for the data/validation.
I think the differences I am seeing in the EMsoft IPF and Kikuchipy are likely because you did not specify the camera tilt, and thus using a default value.
You're right. In the imminent new minor release of kikuchipy (v0.8), the detector tilt (and binning) is read with the patterns from H5OINA files. The detector parameters are stored in the EBSD.detector
attribute of the returned signal.
Taking the detector tilt into account, the IPF-Z map looks like this after HI + orientation refinement using dynamical simulation from EMsoft (dynamic PCs were extrapolated from a mean assuming a detector pixel size of 25 um [as per Philip] and the geometric relations from the appendix of the refinement paper by Singh et al. (2017)):
Colors are quite similar to the maps in https://github.com/EMsoft-org/EMsoft/issues/164#issuecomment-1289151978.
Moving here a short discussion started in https://github.com/EMsoft-org/EMsoft/issues/164 regarding reading EBSD patterns stored in H5OINA files in EMsoft. @Philip-Go kindly shared a small H5OINA file (136 MB), which I could confirm that the soon to be released kikuchipy reader could read successfully (including the pattern center values):
Quoting @Philip-Go:
The IPF map is produced from the results returned from PyEBSDIndex using default values. Do you have anything to add @drowenhorst-nrl? Feel free to close this issue when it suits you.
Below I've included the script I used. It requires the development version of kikuchipy, so to install everything (remaining packages are dependencies of kikuchipy):
Remove the
[gpu]
if an error message shows (see the installation guide). Indexing will use CPU so will be quite a lot slower, but still fast (I'd say). An unimportant warning is raised, which is fixed and will be released as a PyEBSDIndex v0.1.1 patch soon.Then this should produce the plot above:
Here are some further tutorials of Hough indexing with PyEBSDIndex: