search

nexusformat / NIAC

Issue for the NIAC to discuss (no code)
2 stars 0 forks source link

AppDef for Multidimensional photoemission spectroscopy (MPES) #105

Open sanbrock opened 2 years ago

sanbrock commented 2 years ago

https://github.com/FAIRmat-Experimental/nexus_definitions/tree/fairmat

prjemian commented 2 years ago

The new definition should be added to the contributed_definitions folder of the definitions repository (in a branch or fork). Once ratified by the NIAC (item 3 of NeXus Constitution), it will be moved to the applications folder.

The pull request should be made to the definitions repository.

sanbrock commented 2 years ago

https://github.com/nexusformat/definitions/pull/998

benajamin commented 2 years ago

I notice that some fields in NXmanipulator would be appropriate to have in NXsample. Is there a reason to choose one location over another? Perhaps having a policy of using links so that they are found in both locations would be useful?

Tommaso-Pincelli commented 2 years ago

I notice that some fields in NXmanipulator would be appropriate to have in NXsample. Is there a reason to choose one location over another? Perhaps having a policy of using links so that they are found in both locations would be useful?

NXmanipulator is a rough draft. It does not contain the depends_on/NXtransformations structure yet (which we have implemented in our local versions). We created the class because in most photoemission experiments the manipulator is a complex independent experimental subsystem with a lot of functionalities. Clearly it can be linked into NXsample. We are debating if it should:

  1. Disappear by merging with NXstage
  2. Be a sub-class of NXsample
  3. Be indipendent