-
Notifications
You must be signed in to change notification settings - Fork 10
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
signal_type "EDS" not understood #19
Comments
Adding a workaround setting There are situation where setting the |
While I am absolutely against on subdivision of EDS into EDS_SEM and EDS_TEM which brings pain dealing with XRF datasets... (I guess this SEM/TEM subdivision had creeped-in by copying Oxford EDS system options where authors of first Hyperspy iterations were most familiar with...)... however, following their article: https://www.oxinst.com/blogs/what-makes-tem-eds-different-from-sem-eds |
Loading an MSA file (from EDAX), the signal type is set to
EDS
, which is not a known signal type as onlyEDS_SEM
andEDS_TEM
are available. The MSA files do not contain any information on the type of instrument, but as far as I remember some other readers decide on the basis of the acceleration voltage (>30 kV = TEM, otherwise SEM), which signal_type to use.Easiest might be to implement the correct signal_type setting in the
rsciio
reader? Alternatively, we could could try to implement the decision on the exspy side, because it should affect various types of file formats and does not make too much sense to repetitively have that code in differentrsciio
readers.Here is the error message:
The text was updated successfully, but these errors were encountered: