|
24 | 24 | <definition xmlns="http://definition.nexusformat.org/nxdl/3.1" category="base" |
25 | 25 | xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" |
26 | 26 | xsi:schemaLocation="http://definition.nexusformat.org/nxdl/3.1 ../nxdl.xsd" |
27 | | - name="NXparameters" |
28 | | - type="group" extends="NXobject"> |
29 | | - <doc>Container for parameters, usually used in processing or analysis.</doc> |
30 | | - <field name="PARAMETER" nameType="any" type="NX_CHAR_OR_NUMBER" units="NX_ANY" minOccurs="0" maxOccurs="unbounded"> |
31 | | - <!-- maxOccurs="unbounded" is intended but is not allowed by current syntax --> |
32 | | - <doc>A parameter (also known as a term) that is used in or results from processing.</doc> |
33 | | - <attribute name="units"/> |
| 27 | + name="NXparameters" type="group" extends="NXobject"> |
| 28 | + |
| 29 | + <doc> |
| 30 | + Container for parameters used in processing or analysing data. |
| 31 | + |
| 32 | + Typically, this group is stored in a :ref:`NXprocess` group in |
| 33 | + order to contain parameters that are either inputs to or |
| 34 | + resulting from the process defined by the parent group. However, |
| 35 | + this base class can also be added to other groups for use in |
| 36 | + other contexts. |
| 37 | + |
| 38 | + Although this base class can be used to store any kind of |
| 39 | + parameter, one possible use case is to store parameters that are |
| 40 | + refined by a fitting function or model. A number of attributes |
| 41 | + have been defined to store metadata associated with such a |
| 42 | + refinement. |
| 43 | + </doc> |
| 44 | + <attribute name="model"> |
| 45 | + <doc> |
| 46 | + The name of the model used in optimizing the parameter |
| 47 | + values. Fitting packages such as LMFIT |
| 48 | + (https://lmfit.github.io/lmfit-py/) provide models, which |
| 49 | + instantiate functions to be fitted to the data. If this |
| 50 | + attribute is provided, it is assumed that all the parameters |
| 51 | + in this group are associated with this model. |
| 52 | + </doc> |
| 53 | + </attribute> |
| 54 | + <field name="PARAMETER" type="NX_CHAR_OR_NUMBER" nameType="any"> |
| 55 | + <doc> |
| 56 | + A parameter that is used in or results from processing. |
| 57 | + </doc> |
| 58 | + <attribute name="units" /> |
| 59 | + <attribute name="error" type="NX_NUMBER"> |
| 60 | + <doc> |
| 61 | + The standard deviation of the parameter after optimizing |
| 62 | + its value. |
| 63 | + </doc> |
| 64 | + </attribute> |
| 65 | + <attribute name="description"> |
| 66 | + <doc> |
| 67 | + A description of what this parameter represents. |
| 68 | + </doc> |
| 69 | + </attribute> |
| 70 | + <attribute name="expression"> |
| 71 | + <doc> |
| 72 | + A string representing an expression that can be used to |
| 73 | + relate the parameter to another parameter's value. The |
| 74 | + format of this string is dependent on the program used |
| 75 | + to optimize the parameters and is not specified by |
| 76 | + NeXus. |
| 77 | + </doc> |
| 78 | + </attribute> |
| 79 | + <attribute name="initial" type="NX_NUMBER"> |
| 80 | + <doc> |
| 81 | + The initial value of the parameter used in optimization. |
| 82 | + </doc> |
| 83 | + </attribute> |
| 84 | + <attribute name="max" type="NX_NUMBER"> |
| 85 | + <doc> |
| 86 | + The upper bound of the parameter used in optimization. |
| 87 | + </doc> |
| 88 | + </attribute> |
| 89 | + <attribute name="min" type="NX_NUMBER"> |
| 90 | + <doc> |
| 91 | + The lower bound of the parameter used in optimization. |
| 92 | + </doc> |
| 93 | + </attribute> |
| 94 | + <attribute name="vary" type="NX_BOOLEAN"> |
| 95 | + <doc> |
| 96 | + True if the parameter was varied during optimization. |
| 97 | + </doc> |
| 98 | + </attribute> |
34 | 99 | </field> |
35 | 100 | </definition> |
36 | | - |
|
0 commit comments