Skip to content
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

Check if all fields from NXarpes are reflected in NXmpes #162

Open
lukaspie opened this issue Feb 9, 2024 · 2 comments
Open

Check if all fields from NXarpes are reflected in NXmpes #162

lukaspie opened this issue Feb 9, 2024 · 2 comments
Assignees
Labels

Comments

@lukaspie
Copy link
Collaborator

lukaspie commented Feb 9, 2024

Required fields in NXmpes that are not part of NXarpes:
/ENTRY[entry]/definition/@Version
/ENTRY[entry]/data/data
/@Units
/@signal
/energy -> not in NXphotoemission
/energy/@Units
/energy/@type
/ENTRY[entry]/INSTRUMENT[instrument]/beam_TYPE -> no NXbeam in NXarpes
/incident_energy
/incident_energy/@Units
/ENTRY[entry]/INSTRUMENT[instrument]/ELECTRONANALYSER[electronanalyser] -> analyser = NXdetector in NXarpes
/description
/COLLECTIONCOLUMN[collectioncolumn]
/scheme
/ENERGYDISPERSION[energydispersion]
/scheme
/pass_energy
/pass_energy/@Units

Required fields in NXarpes that are not part of NXmpes:
/ENTRY[entry]/@entry -> have never seen this being used before
/ENTRY[entry]/INSTRUMENT[instrument]/SOURCE[source] -> source_TYPE in NXmpes
/name -> recommended in NXmpes
/probe = x-ray > recommended in NXmpes, can be any of the values defined in the base class
/ENTRY[entry]/INSTRUMENT[instrument]/DETECTOR[analyser] -> -> electronanalyser in NXarpes
/data(NX_NUMBER) -> we have this in NXdetector/raw_data(NXdata), but only recommended
/lens_mode -> we have this in NXcollectioncolumn, but only recommended
/acquisition_mode -> we have this in NXenergydispersion/energy_scan_mode, but only recommended and with a different enumeration
/entrance_slit_shape(NX_CHAR) -> we have NXenergydispersion/entrance_slit, only recommended. It is also an NXaperture and shape is only optional
/entrance_slit_setting(NX_NUMBER): we don't have the notion of a setting on an aperture, could be added
/entrance_slit_setting/@Units
/entrance_slit_size(NX_NUMBER) -> NXenergydispersion/entrance_slit/size, but only optional
/entrance_slit_size/@Units
/pass_energy: we have this in NXenergydispersion/pass_energy, but only recommended
/time_per_channel: not in NXmpes
/time_per_channel/@Units: not in NXmpes
/angles(NX_NUMBER) -> this would be angular0, angular1 as we have it now in NXdata_mpes
/angles/@Units
/energies -> we have this in the main NXdata as energy
/energies/@Units
/sensor_size(NX_INT): not in NXmpes
/region_origin(NX_INT): not in NXmpes
/region_size(NX_INT): not in NXmpes
/ENTRY[entry]/SAMPLE[sample]
/temperature(NXnumber) -> we have this as temperature(NXenvironment), but only recommended
/temperature/@Units

@lukaspie lukaspie self-assigned this Feb 9, 2024
@lukaspie
Copy link
Collaborator Author

lukaspie commented Feb 9, 2024

I have also created an issue on pynxtools: FAIRmat-NFDI/pynxtools#235

@lukaspie lukaspie added the mpes label Feb 9, 2024
@rettigl
Copy link
Collaborator

rettigl commented Feb 12, 2024

/incident_energy

This is given as Monochromator energy in NXarpes

/pass_energy

This is also there in NXarpes

/entrance_slit_setting(NX_NUMBER): we don't have the notion of a setting on an aperture, could be added

Maybe a good idea to add

/time_per_channel: not in NXmpes

We anyways discussed adding something to keep track of acquisition procedures, no?

/sensor_size(NX_INT): not in NXmpes

Yes, there is NXdetector->dimension or so

/region_origin(NX_INT): not in NXmpes
/region_size(NX_INT): not in NXmpes

Not sure, if not there can also go to NXdetector

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants