Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Generic writing of an .h5ebsd file #721

Closed
CSSFrancis opened this issue Jan 23, 2025 · 1 comment
Closed

Generic writing of an .h5ebsd file #721

CSSFrancis opened this issue Jan 23, 2025 · 1 comment

Comments

@CSSFrancis
Copy link
Member

I am in the process of allowing Direct Electron Cameras to write directly to an h5ebsd. Looking further into this it seems like there are many different headers/ ways to write the header for an h5ebsd file.

I was wondering if there is a more/less correct way to write this file and what standard you would recommend. Ideally, it would be nice to write one file type that would be readable by the largest number of EBSD software without having to individually implement each file type.

@hakonanes
Copy link
Member

There isn't, unfortunately. h5ebsd is a format proposed by Mike Jackson (DREAM.3D), Dave Rowenhorst (PyEBSDIndex), Marc De Graef (EMsoft), and others in https://doi.org/10.1186/2193-9772-3-4.

Variations on storing EBSD datasets in HDF5 files I know of:

  • EDAX TSL, example file
  • Oxford Instruments H5OINA, specification
  • Bruker Nano, example file
  • kikuchipy's format (no standard! Only meant to be used internally in kikuchipy and to index patterns processed in kikuchipy with EMsoft)

I'm curious, why are you creating this writer?

@pyxem pyxem locked and limited conversation to collaborators Mar 9, 2025
@hakonanes hakonanes converted this issue into discussion #724 Mar 9, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants