Skip to content

Commit 3877b11

Browse files
committed
Merge remote-tracking branch 'upstream/main' into fairmat-2024-mpes
2 parents 33fc441 + fb7142d commit 3877b11

File tree

6 files changed

+14
-84
lines changed

6 files changed

+14
-84
lines changed

base_classes/NXactuator.nxdl.xml

Lines changed: 6 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -27,11 +27,6 @@
2727

2828
The condition itself is described in :ref:`NXenvironment`.
2929
</doc>
30-
<field name="model">
31-
<doc>
32-
Actuator identification code/model number
33-
</doc>
34-
</field>
3530
<field name="name">
3631
<doc>
3732
Name of the actuator
@@ -42,10 +37,11 @@
4237
Short name of actuator used e.g. on monitor display program
4338
</doc>
4439
</field>
45-
<field name="attached_to">
40+
<field name="actuation_target">
4641
<doc>
47-
Describe where the actuator is attached to.
48-
This could be an instance of NXsample or a device on NXinstrument.
42+
The physical component on which this actuator acts.
43+
This should be a path in the NeXus tree structure.
44+
For example, this could be an instance of NXsample or a device on NXinstrument.
4945
</doc>
5046
</field>
5147
<field name="physical_quantity">
@@ -68,34 +64,12 @@
6864
:Voltage: potentiostat
6965
</doc>
7066
</field>
71-
<field name="OUTPUT" type="NX_FLOAT" units="NX_ANY">
67+
<field name="outputVALUE" type="NX_NUMBER" units="NX_ANY" nameType="partial">
7268
<doc>
7369
Any output that the actuator produces.
74-
For example, a heater can have the field heater_power(NX_FLOAT).
70+
For example, a heater can have the field output_power(NX_NUMBER).
7571
</doc>
7672
</field>
77-
<group name="OUTPUT_log" type="NXlog">
78-
<doc>
79-
Time history of actuator outputs.
80-
</doc>
81-
</group>
82-
<group type="NXpid">
83-
<doc>
84-
If the actuator is PID-controlled, the settings of the PID controller can be
85-
stored here.
86-
</doc>
87-
<field name="setpoint" type="NX_FLOAT" units="NX_ANY">
88-
<doc>
89-
Nominal actuator setpoint.
90-
Can be a scalar or a vector (of [n] actuations).
91-
</doc>
92-
</field>
93-
<group name="setpoint_log" type="NXlog">
94-
<doc>
95-
Time history of actuator setpoints.
96-
</doc>
97-
</group>
98-
</group>
9973
<field name="depends_on" type="NX_CHAR">
10074
<doc>
10175
Refers to the last transformation specifying the position of the actuator
@@ -110,18 +84,5 @@
11084
other component groups.
11185
</doc>
11286
</group>
113-
<attribute name="default">
114-
<doc>
115-
.. index:: plotting
116-
117-
Declares which child group contains a path leading
118-
to a :ref:`NXdata` group.
119-
120-
It is recommended (as of NIAC2014) to use this attribute
121-
to help define the path to the default dataset to be plotted.
122-
See https://www.nexusformat.org/2014_How_to_find_default_data.html
123-
for a summary of the discussion.
124-
</doc>
125-
</attribute>
12687
<group type="NXfabrication"/>
12788
</definition>

base_classes/NXdistortion.nxdl.xml

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
#
2222
# For further information, see http://www.nexusformat.org
2323
-->
24-
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="base" name="NXdistortion" extends="NXobject" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
24+
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="base" name="NXdistortion" extends="NXprocess" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
2525
<symbols>
2626
<doc>
2727
The symbols used in the schema to specify e.g. dimensions of arrays
@@ -45,11 +45,6 @@
4545
<doc>
4646
Subclass of NXprocess to describe post-processing distortion correction.
4747
</doc>
48-
<field name="last_process" type="NX_CHAR">
49-
<doc>
50-
Indicates the name of the last operation applied in the NXprocess sequence.
51-
</doc>
52-
</field>
5348
<field name="applied" type="NX_BOOLEAN">
5449
<doc>
5550
Has the distortion correction been applied?

base_classes/NXenvironment.nxdl.xml

Lines changed: 0 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -92,17 +92,4 @@
9292
defined in an NXinstrument instance.
9393
</doc>
9494
</group>
95-
<attribute name="default">
96-
<doc>
97-
.. index:: plotting
98-
99-
Declares which child group contains a path leading
100-
to a :ref:`NXdata` group.
101-
102-
It is recommended (as of NIAC2014) to use this attribute
103-
to help define the path to the default dataset to be plotted.
104-
See https://www.nexusformat.org/2014_How_to_find_default_data.html
105-
for a summary of the discussion.
106-
</doc>
107-
</attribute>
10895
</definition>

base_classes/NXfabrication.nxdl.xml

Lines changed: 5 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -36,35 +36,27 @@
3636
</doc>
3737
<attribute name="version" type="NX_CHAR">
3838
<doc>
39-
If different versions exist are possible, the value in this field should be made
39+
If it is possible that different versions exist, the value in this field should be made
4040
specific enough to resolve the version.
4141
</doc>
4242
</attribute>
4343
</field>
44-
<group name="identifier" type="NXidentifier">
45-
<doc>
46-
Ideally, (globally) unique persistent identifier. This may contain e.g. a hash
47-
identifier of the component.
48-
</doc>
49-
</group>
5044
<field name="serial_number" type="NX_CHAR">
5145
<doc>
5246
Serial number of the component.
5347
</doc>
5448
</field>
55-
<field name="construction_year" type="NX_DATE_TIME">
49+
<field name="construction_date" type="NX_DATE_TIME">
5650
<doc>
57-
Datetime of components initial construction. This refers to the date of
51+
Datetime of component's initial construction. This refers to the date of
5852
first measurement after new construction or to the relocation date,
5953
if it describes a multicomponent/custom-build setup.
60-
Should be a ISO8601 date/time stamp. It is recommended to add an explicit time zone,
61-
otherwise the local time zone is assumed per ISO8601.
54+
Just the year is often sufficient, but if a full date/time is used, it is recommended to add an explicit time zone.
6255
</doc>
6356
</field>
6457
<field name="capability" type="NX_CHAR">
6558
<doc>
66-
Free-text list with eventually multiple terms of
67-
functionalities which the component offers.
59+
Free-text list of functionalities which the component offers.
6860
</doc>
6961
</field>
7062
</definition>

base_classes/NXregistration.nxdl.xml

Lines changed: 1 addition & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
#
2222
# For further information, see http://www.nexusformat.org
2323
-->
24-
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="base" name="NXregistration" extends="NXobject" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
24+
<definition xmlns="http://definition.nexusformat.org/nxdl/3.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" category="base" name="NXregistration" extends="NXprocess" type="group" xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd">
2525
<doc>
2626
Describes image registration procedures.
2727
</doc>
@@ -30,11 +30,6 @@
3030
Has the registration been applied?
3131
</doc>
3232
</field>
33-
<field name="last_process" type="NX_CHAR">
34-
<doc>
35-
Indicates the name of the last operation applied in the NXprocess sequence.
36-
</doc>
37-
</field>
3833
<field name="depends_on" type="NX_CHAR">
3934
<doc>
4035
Specifies the position by pointing to the last transformation in the

manual/source/datarules.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ described by the following :index:`rules <rules; naming>`:
9393
^[a-zA-Z0-9_]([a-zA-Z0-9_.]*[a-zA-Z0-9_])?$
9494
9595
The length should be limited to no more than
96-
63 characters (imposed by the HDF5 :index:`rules <rules; HDF5>` for names).
96+
63 characters (historically imposed by the HDF4 :index:`rules <rules; HDF>` for names).
9797

9898
It is recognized that some facilities will construct data files with
9999
group and field names with upper case letters or start names with a

0 commit comments

Comments
 (0)