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

Add first NXraman Version #201

Closed
wants to merge 5 commits into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions contributed_definitions/NXbeam_device.nxdl.xml
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,9 @@
#
# For further information, see http://www.nexusformat.org
-->
<!--
This beam device properites shall later be integrated into NXsource, NXdetector, etc
i.e. each different beam device.-->
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="base" name="NXbeam_device" extends="NXobject" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
<doc>
Properties of generic beam device in an experimental setup.
Expand Down Expand Up @@ -55,6 +58,14 @@
Is used for simplified setup vizualization (or description?).
</doc>
</field>
<attribute name="device" type="NX_CHAR" recommended="true">
<doc>
Link to the NeXus device like a NXdetector, a NXmonochromator or NXsource.

For example:
@device: 'entry/instrument/laser_source'
</doc>
</attribute>
<group type="NXtransformations">
<doc>
Location and orientation of the device. Note that even a
Expand Down
32 changes: 14 additions & 18 deletions contributed_definitions/NXopt.nxdl.xml
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
<?xml version="1.0" encoding="UTF-8"?>
<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet type="text/xsl" href="nxdlformat.xsl"?>
<!--
# NeXus - Neutron and X-ray Common Data Format
#
# Copyright (C) 2014-2022 NeXus International Advisory Committee (NIAC)
#
#
# Copyright (C) 2014-2024 NeXus International Advisory Committee (NIAC)
#
# This library is free software; you can redistribute it and/or
# modify it under the terms of the GNU Lesser General Public
# License as published by the Free Software Foundation; either
Expand All @@ -21,14 +21,16 @@
#
# For further information, see http://www.nexusformat.org
-->
<!--05/2023
<!--
05/2023
Draft of a NeXus application definition which serves as a template for various
optical spectroscopy experiments-->
<!--To do:
<!--
To do:
[ ] Check base classes (NXbeam_path + base classes used by it)
[ ] Harmonize NXopt and NXellipsometry
[ ] Fix dimensions and ranks-->
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="application" name="NXopt" extends="NXobject" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="application" type="group" name="NXopt" extends="NXobject" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
<symbols>
<doc>
Variables used throughout the document, e.g. dimensions or parameters.
Expand Down Expand Up @@ -277,18 +279,12 @@ optical spectroscopy experiments-->
</doc>
</field>
</group>
<group type="NXbeam_path">
<group type="NXbeam_device" recommended="true">
<field name="previous_devices"/>
</group>
<group type="NXbeam" optional="true">
<doc>
Describes an arrangement of optical or other elements, e.g. the beam
path between the light source and the sample, or between the sample
and the detector unit (including the sources and detectors
themselves).

If a beam splitter (i.e. a device that splits the incoming beam into
two or more beams) is part of the beam path, two or more NXbeam_path
fields may be needed to fully describe the beam paths and the correct
sequence of the beam path elements.
Use as many beam paths as needed to describe the setup.
Beam characteristics between two beam_devices.
</doc>
</group>
<field name="angle_of_incidence" type="NX_NUMBER" units="NX_ANGLE">
Expand Down
Loading