-
Notifications
You must be signed in to change notification settings - Fork 9
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
Cannot determine binning factor from some EBSD "Camera Binning Mode" dataset strings #5
Comments
Hi @hakonanes, I forwarded your question to our EBSD expert. I'll let know when I get a reply. |
Fantastic, thank you @ppinard. I'm asking because I think better reading of file metadata in third-party software and libraries will benefit H5OINA users who value interoperability. |
Hi Hakon, here is a response below from our EBSD team. I will look into removing the word 'binning' from the other parameter and leaving it as 'Camera mode' to make it less confusing. Symmetry’s resolution mode is 1244x1024 resolution, this is effectively the unbinned pattern resolution. |
Hi @k8macarthur, thank you, @ppinard and the EBSD team for the detailed answer. This is all the information I need, as far as I can tell. Feel free to close this issue.
That would be nice, as having "binning" in the name sets an expectation of a self-contained conversion factor. |
Dear H5OINA developers,
I'm unable to determine the binning factor from some EBSD "Camera Binning Mode" dataset strings, like "Speed 2 (156x128 px)". Can I determine it in some other way from such files?
I believe patterns in files with these types of binning modes are obtained on Symmetry Sx detectors (x = 1-3) where a part of the detector is unused (say the upper 96 rows -> (1344 - 96) / 8 = 156 px). Can I assume that these detectors always have the same number of unbinned pixels (say 1344x1024), so that I can reliably calculate the binning factor from "Speed 2 (156x128 px)"?
The text was updated successfully, but these errors were encountered: