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

MPES appdef hierarchy (also NAP-XPS) #196

Open
lukaspie opened this issue Mar 11, 2024 · 0 comments
Open

MPES appdef hierarchy (also NAP-XPS) #196

lukaspie opened this issue Mar 11, 2024 · 0 comments
Assignees

Comments

@lukaspie
Copy link
Collaborator

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants