-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading of master patterns generated with EDAX #662
Comments
@hakonanes Yes, we do have EDAX OIM Matrix. But I have not used the .oem format yet. I'll take a look to see if I can find any clue. |
Hm, I remember you saying that they are stored as HDF5 files identical to EMsoft's HDF5 files, right? |
Aha, thank you for checking! I should of course have checked this myself. Unless EDAX makes any significant changes to the way they write master pattern HDF5 files compared to the EMsoft way, we should be able to include the "oem" extension in
|
I've received a master pattern file generated with EDAX OIM Matrix from a colleague. It's a binary file with file extension .oem of 157.3 MB (157 286 400 bytes). I know nothing of the contents of the file, but I assume it contains master patterns of nickel, possibly for more than one beam energy. Thus, I cannot create a reader for it for kikuchipy at the moment.
@IMBalENce, you have access to EDAX OIM Matrix, right? Are you familiar with .oem files and their contents?
I'll leave this issue open if anyone with more information on this file format stumbles upon kikuchipy.
The text was updated successfully, but these errors were encountered: