MPES appdef hierarchy (also NAP-XPS) - Githubissues

FAIRmat-NFDI / nexus_definitions

Definitions of the NeXus Standard File Structure and Contents

https://manual.nexusformat.org/

Other

6 stars 8 forks source link

MPES appdef hierarchy (also NAP-XPS) #196

Open lukaspie opened 6 months ago

lukaspie commented 6 months ago

From workshop:

Do we want/need the separation of NXmpes/NXpeem?
Where to place fixed energy kPEEM without energy resolution (Momentum microscope with hemisphere)?
APXPS should have its own app def where we specify all relevant sensors/environments/data axes.
- You would also like to store mass spec / GC data for operando experiments.

From Sandor:

Are the required fields enough so that a data consumer could work with this set of data?
AppDef separation shall be based on the different requirements of the expected data analysis tools
do we need separate AppDefs for PEM? IPES?
possible priority (also based on market share): XPS, ARPES, PEEM, liquidjet

PaNET ontology: https://bioportal.bioontology.org/ontologies/PANET

Discussion:

remove NXmpes
have all sub app-defs one level below NXphotoemission