<data_section/>tags, which is also a child of
<yanera/>as is the
Each data set is specified by a set of
<data/> tags, which are the only children of
<data_section> <data data_id="data0"> <file_name>mydata.dat</file_name> <resolution> <type>RESOLUTION_NONE</type> <value/> <file_name/> </resolution> </data> </data_section>
<data/> tags have only two children,
<file_name/> tags and
<resolution/> tags. The first specifies the name of the file containing the data to be fitted. The second contains information regarding the instrumental resolution.
<data/> tags must have a
data_id property that will correspond to the
data_idref of only one
<model/>. Any alpha-numeric string will work for this property.
Users can choose resolution smearing types from the list/
Other options are for instrumental resolution determined by calculating the reflectivity averaged over several points with Gaussian weights. It's a method that was borrowed and made more general from Parratt32. It works by the following, assuming a point average,
RESOLUTION_RELATIVE, we can specify the instrumental resolution due to continually varying slits, . Otherwise, the resolution
RESOLUTION_CONSTANT can be specified as . Specify the value of the resolution by
If the resolution changes during the course of the scan, you can specify an array of values by a two column file, and include the file's name with
<file_name/> tags, such as;
<resolution> <type>RESOLUTION_ARRAY_CONSTANT</type> <file_name>resolution.dat</file_name> </resolution>
In the file, supply the ranges of for each value of the resolution by the minimum , e.g. from 0 to 0.02, from 0.02 to 0.08, and from 0.08 to 0.12 would look like:
Application of resolution smearing slows the fitting a fair bit. Try fitting without resolution first.