In creating the first version of NXraman, I thaught that in principle some NeXus definitions can be updated by deriving the respective elements from NXbeam_device?
This could be the case for:
NXbeam_splitter
NXdeflector (?)
NXfiber
NXlens_em (?)
NXlens_opt
NXmagnetic_kicker (?)
NXpolarizer_opt
NXseperator (?)
NXsolenoid_magnet (?)
NXwaveplate
Is this desired? It this easily doable by replacing NXobject in e.g. NXwaveplate(NXobject) by NXbeam_device?
Without this, the current implementation of a beam path via NXbeam_device is not possible in NXraman nor NXellipsometry.
In creating the first version of NXraman, I thaught that in principle some NeXus definitions can be updated by deriving the respective elements from NXbeam_device?
This could be the case for: NXbeam_splitter NXdeflector (?) NXfiber NXlens_em (?) NXlens_opt NXmagnetic_kicker (?) NXpolarizer_opt NXseperator (?) NXsolenoid_magnet (?) NXwaveplate
Is this desired? It this easily doable by replacing NXobject in e.g. NXwaveplate(NXobject) by NXbeam_device?
Without this, the current implementation of a beam path via NXbeam_device is not possible in NXraman nor NXellipsometry.