MPES reader changes from mpes refactoring#203
Conversation
|
Hey @rettigl, if you like you can already review the I introduced a new feature that the config file can be written in a nested fashion, because I thought this is much easier to read and maintain (and we could easier show an "instance" of data at the workshop). I also added support for |
…concept name included
Pull Request Test Coverage Report for Build 7585289570
💛 - Coveralls |
rettigl
left a comment
There was a problem hiding this comment.
Generally, this looks quite good to me. However, there are a lot of "NOT IN SCHEMA" entries in the log files, some of them new, some of them also old. I think this should be carefully checked if this is supposed to be like this...
If I run the conversion in the tutorials E1 notebook, with definitions on "fairmat" branch, I get the following errors:
The data entry corresponding to /ENTRY[entry]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/ENERGYDISPERSION[energydispersion]/energy_scan_mode is required and hasn't been supplied by the reader.
[info]: Path /ENTRY[entry]/PROCESS[process]/energy_calibration/coefficients not found. Skipping the entry.
The required group, /ENTRY[entry]/SAMPLE[sample]/bias/potentiostat, hasn't been supplied while its optional parent, /ENTRY[entry]/SAMPLE[sample]/bias, is supplied.
Still, the file is being created.
If I run with "mpes-fixes" branch, I get:
The data entry corresponding to /ENTRY[entry]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser]/ENERGYDISPERSION[energydispersion]/energy_scan_mode is required and hasn't been supplied by the reader.
[info]: Path /ENTRY[entry]/PROCESS[process]/energy_calibration/coefficients not found. Skipping the entry.
|
Conversion in E2 fails with: |
This is expected as for
This is because it is named differently in metadata in the example file than the file we have in pynxtools. Changing this value Sorry, I also should've mentioned that I did not yet test the examples with this. But I think E1 should be good now and I will check the error for the E2 as well. |
We check for that and abort if the target does not exist: pynxtools/pynxtools/dataconverter/writer.py Line 179 in 279ba0e The problem in E2 is that it is trying to write an empty field, I think. |
I can try that. It's probably in the template at that point, but None. So this check should be included (that's what I meant). |
I already checked it. It also has problems when the metadata is set manually and I think it's because there are some additional keys in the associated eln file. I'm working on it rn. Yes, with the latest changes everything is working for E2 :) @rettigl please feel free to give it another check but it should be good to go then. |
rettigl
left a comment
There was a problem hiding this comment.
Everything seems to be working now, also with the examples.


This
XPSReadertest (it should then be re-activated from XPS reader: update to new NXmpes after refactor #207 @lukaspie)Fixes #210, Fixes #212