search

FAIRmat-NFDI / nexus_definitions

Definitions of the NeXus Standard File Structure and Contents
https://manual.nexusformat.org/
Other
5 stars 8 forks source link

Add nexus definitions/files for beam path description #183

Closed RonHildebrandt closed 4 months ago

RonHildebrandt commented 4 months ago

Adding functionality for a description of a beam path In total four NeXus definitions are added:

Optical elements (NXopt_element) describe elements of a setup. A beam can be defined as object(NXopt_beam), which is associated with two optical elements and can be used to describe physical properties of a photon beam. A unique path can describe the beam properties along a starting element (source) and an ending element (detector). The beam properties are modified by each optical element (e.g. attenuation, divergence). Matrices shall be used to describe this change of beam properties. These elements are part of the optical assemly (NXopt_assembly), in which the respective formalism is given. For each formalism, there can be different matrices. These matricies are part of a large table, which contains all the necessary information to model the beam properties along a path. Each matrix table is associated for one optical element for one combination of input and output beams.

Unclear The NXtransfer_matrix_table data structure is based on the NXellipsometry definition. Im quite unsure if this structure can be functional this way.

First PR As this is the first PR by myself - Any advices for further PR and explanations for general rules are welcomed Just did by to the best of my knowledge and belief.

RonHildebrandt commented 4 months ago

I have added adjustments of all files. Still have to solve the failing checks. Is there a problem with the nyaml versions right now or should it be fine, if "make local" and "make nxdl" works?