LET_Parameters.xml

<?xml version="1.0" encoding="UTF-8" ?>
<parameter-file instrument = "LET" valid-from = "2013-06-12T00:00:00">

<component-link name = "LET">

<!-- files properties : -->

<!-- Specify that the detector positions should be taken from the data file (Not used TODO!) -->
<parameter name="det-pos-source" type="string">
  <value val="datafile"/>
</parameter>

<!-- The file which defines proper (calibrated) detector positions 
     if None - it is undefined -->
<parameter name="det_cal_file" type="string">
   <value val="det_LET_cycle12-3.dat"/>
</parameter>

<!-- The file which defines detectors to spectra mapping; File extension has to be specified here but filepath not
     if None - one2one map is used  -->
<parameter name="map_file" type="string">
   <value val="LET_one2one_123.map"/>
</parameter>

<!-- Prefered extension of the data files obtained from DAE, e.g. what to prefer if two 
     files with the same name and different extension are found
 -->
<parameter name="data_file_ext" type="string">
   <value val=".raw"/>
</parameter>
<!-- The name of the hard mask file to use together with diag masking -->
<parameter name="hard_mask_file" type="string">
    <value val="hard.msk"/>
</parameter>
<!-- The map file used when calculating absolute units conversion integrals 
     This map usually groups together large areas of detectors to obtain proper vanadium statistics  -->
<parameter name="monovan_mapfile" type="string">
   <value val="LET_rings_123.map"/>
</parameter>




<!-- RunNumber to use for diag instead of the input run number if none - use input run 
     if yes, will probably change from command line-->
<parameter name="mask_run" type="string">
   <value val="None"/>
</parameter>

<!-- Energy conversion mode direct/indirect/elastic (the one the reducer understands) -->
<parameter name="deltaE-mode" type="string">
  <value val="direct"/>
</parameter>

<!-- normalise_method normalization. To compare different runs with different length one uses normalization by some flux-dependent parameter
     Available values are: none (-largely meaningless), monitor-1,monitor-2, current 
     the acceptable values are defined in DirectEnergyConversion initialization routine as recognized by direct energy conversion normalize method
     these three are currently disabled/unknown:  uamph peak-->
<parameter name="normalise_method" type="string">
    <value val="monitor-1"/>
</parameter>

<!-- Monitor used to estimate total current on the sample  while normalizing by monitor 1.  -->
<parameter name="norm-mon1-spec">
  <value val="40961"/>
</parameter>
<!-- Time interval used for integration to estimate current on the sample 
    This interval is usually taken around the monitor peak-->
<parameter name="norm-mon1-min">
  <value val="10000"/>
</parameter>
<parameter name="norm-mon1-max">
  <value val="12000"/>
</parameter>
<parameter name="norm_mon_integration_range"  type="string">
  <value val="norm-mon1-min:norm-mon1-max"/>
</parameter>

<!-- Monitor after chopper used to estimate total current on the sample, if normalization is done on monitor 2  -->
<parameter name="norm-mon2-spec"  type = "int" >
    <value val="40966"/>
</parameter>

<!-- Relative energy range (wrt. to the incident energy) in which monitor 2 signal is present and the integration to 
     calculate monitor-2 current occurs   -->
<parameter name="mon2_norm_energy_range" type = "string">
    <value val="0.8,1.2"/>
</parameter>

<!-- Usually one wants to avoid loading monitors together with data except in special cases. One of this cases is 
     MARI which monitors numbers are in the beginning of the spectra. If one loads them separately, 
     spectra numbers change and ISIS hard masks (msk) prepared for workspace with monitors become invalid. 
     This parameter is actual until Mantid Masking change
  -->
<parameter name="load_monitors_with_workspace"  type="bool">
<value val="False"/>
</parameter>

<!-- -->
<parameter name="ei-mon1-spec"  type="int">
  <value val="40966"/>
  <description is="First spectra number (monitor's spectra number) to use when measuring incident energy,
     or comma separated list of such numbers.
     Should be spectra with well defined energy peak or monitor's spectra.
     If list of numbers is provided, the final spectrum is the sum of the spectra with the numbers provided.
     It is important to have the detectors for these spectra to be located at the same distance from the source,
     as the position of the combined detector will be defined by the position of the first spectra's detector."/>
</parameter>
<!-- -->
<parameter name="ei-mon2-spec"  type="int">
  <value val="5506"/>
  <description is="Second spectra number (monitor's spectra number) to use when measuring incident energy,
     or comma separated list of such numbers.
     Should be spectra with well defined energy peak or monitor's spectra.
     If list of numbers is provided, the final spectrum is the sum of the spectra with the numbers provided.
     It is important to have the detectors for these spectra to be located at the same distance from the source,
     as the position of the combined detector will be defined by the position of the first spectra's detector."/>
</parameter>
<!-- -->
<parameter name="ei_mon_spectra"  type="string">
  <value val="ei-mon1-spec:ei-mon2-spec"/>
  <description is="List of spectra, used to calculate incident energy of beam in inelastic experiments by GetEi algorithm.
  It is complex property, dependent on two other properties, namely ei-mon1-spec and ei-mon2-spec, which define spectrum or
  spectra lists for each of two monitors, used in GetEi calculations"/>
</parameter>

<!-- -->
<parameter name="spectra_to_monitors_list"  type="string">
  <value val="5506"/>
  <description is="If you use some detectors as monitors and work in event mode,
    one needs to specify the comma separated list of these detectors as the value of this property
    to copy detectors spectra to monitors spectra collected in histogram mode.
    If no such monitors are used, None (or text string 'None' in IDF) has to be specified as the value.
    This is also necessary in Histogram mode if you want to use some detectors as monitors and 
    load_monitors_with_workspace is set to False necessary if monitors are measured with different time channels"/>
</parameter>

<!-- -->
<parameter name="multirep_tof_specta_list"  type="string">
    <value val="12416,21761"/>
    <description is="List of two spectra corresponding to the detectors which are closest and furthest from the sample.
    These detectors locations are used to identify TOF range, contributing into each energy range
    in multirep mode"/>
</parameter>


<!-- by default getEi looks for peaks within (1+-0.1)*TOF_GUES range where TOF_GUES is evaluated on the basis of ei guess.
    If the peaks are very narrow, or there are a lot of them very close to each other, 
    this value can be reduced. For example, such situation happens on MARI for very high incident energies Ei=1800.
 -->
<parameter name="ei_mon_peak_search_range">
   <value val="0.1"/>
</parameter>


<parameter name="scale-factor">
  <value val="1.7016e8"/>
</parameter>

<parameter name="wb-scale-factor">
  <value val="1000"/>
</parameter>

<!--  -->
<parameter name="check_background"  type="bool">
   <value val="False"/>
   <description is="If True, remove the count rate seen in the regions of the
     histograms defined as the background regions. 
     The background region is defined by background_range property."/>
 </parameter>

<parameter name="nullify_negative_signal"  type="bool">
  <value val="False"/>
  <description is="If True and background removed, nullify the negative signal, which
     may occur at some detectors at some moments of time due to flat background removal and modify errors accordingly.
     If False, leave signals and errors unchanged. "/>
</parameter>

<!--  detector_van_range- integratin in E(mev) for detector(white beam) vanadium data [20,100] -->
<parameter name="wb-integr-min">
  <value val="0.5"/>
</parameter>
<parameter name="wb-integr-max">
  <value val="200"/>
</parameter>
<parameter name="wb_integr_range"   type="string">
    <value val="wb-integr-min:wb-integr-max"/>
</parameter>


<!-- integration range for background tests  (in TOF) - composite property 
  Used in test to reject high backgound (FlatBackground) and in High Background tests integration in Diagnostics
  if diag_background_test_range is not set -->
<parameter name="bkgd-range-min"> 
  <value val="90000"/>
</parameter>
<parameter name="bkgd-range-max">
  <value val="95000"/>
</parameter>
<parameter name="background_range"  type="string">
      <value val="bkgd-range-min:bkgd-range-max"/>
</parameter>

<!-- ******************************** DIAGNOSTICS DEFAILTS **************************************** -->

<!-- Perform diag by bank. These are the spectrum numbers -->
<parameter name="diag_spectra" type="string">
  <value val="None"/>
</parameter>

<!-- Absolute lo threshold for vanadium diag (tiny) -->
<parameter name="diag_tiny">
  <value val="1e-10"/>
</parameter>

<!-- Absolute hi threshold for vanadium diag (large) -->
<parameter name="diag_huge">
  <value val="1e10"/>
</parameter>

<!-- Setting diag to reject zero backgrounds; If true then zeroes in (vanadium) data are masked as fail  -->
<parameter name="diag_samp_zero"  type="bool">
  <value val="False"/>
</parameter>

<!-- Fraction of median to consider counting low for the white beam diag (diag_van_median_rate_limit_hi sv_lo)-->
<parameter name="diag_samp_lo">
  <value val="0.0"/>
</parameter>
<!-- Fraction of median to consider counting high for the white beam diag (sv_hi)-->
<parameter name="diag_samp_hi">
  <value val="1.5"/>
</parameter>

<!-- Error criterion as a multiple of error bar for background (sv_sig) 
  i.e. to fail the test, the magnitude of the
  difference with respect to the median value must also exceed this number of error bars (default=3.3)
-->  
<parameter name="diag_samp_sig">
  <value val="3.3"/>
</parameter>

<!-- Lower bound defining outliers as fraction of median value (v_out_lo)-->
<parameter name="diag_van_out_lo">
  <value val="0.01"/>
</parameter>

<!-- Upper bound defining outliers as fraction of median value (v_out_hi) -->
<parameter name="diag_van_out_hi">
  <value val="100."/>
</parameter>

<!-- Fraction of median to consider counting low for the white beam diag (vv_lo)  vanlo=0.1  -->
<parameter name="diag_van_lo">
  <value val="0.1"/>
</parameter>

<!-- Fraction of median to consider counting high for the white beam diag (vv_hi) vanhi=1.5 -->
<parameter name="diag_van_hi">
  <value val="2.0"/>
</parameter>

<!-- Error criterion as a multiple of error bar     van_sig  "
    i.e. to fail the test, the magnitude of the difference with respect to the median value must also exceed this number of error bars (default=0.0)
-->
<parameter name="diag_van_sig">
  <value val="0.0"/>
</parameter>

<!-- Variation for ratio test with second white beam -->
<parameter name="diag_variation">
  <value val="1.1"/>
</parameter>
<!-- The range used in diagnostics and rejecting high background.
  If none, the diag background range uses background ranges from background_range. Has to be directly set otherwise -->
<parameter name="diag_background_test_range"  type="string" >
    <value val="None"/>
</parameter>

<!--  -->
<!--  Bleeding corrections   -->

<!--  the number of pixels ignored within the bleed test diagnostic -->
<parameter name="diag_bleed_pixels">
    <value val="80"/>
</parameter>
<!--  the maximum framerate allowed in a tube -->
<parameter name="diag_bleed_maxrate">
    <value val="0.01"/>
</parameter>
<!-- True if the bleed tests should be run use_bleeding-->
<parameter name="diag_bleed_test"  type="bool">
    <value val="False"/>
</parameter>

<!-- **************************************** DIAGNOSTICS DEFAILTS END ****************************************    -->


<!-- **************************************** ABSOLUTE UNITS CORRECTION DEFAULTS ********************************  -->
<!-- Absolute units conversion average -->
<parameter name="monovan_lo_bound">
  <value val="0.01"/>
</parameter>

<parameter name="monovan_hi_bound">
  <value val="100"/>
</parameter>

<!-- This property is the part of the composite definition for abs_units_van_range: 
 It specifies the relative to incident energy lower integration limit for monochromatic vanadium in the mono-vanadium integration -->
<parameter name="monovan_lo_frac">
  <value val="-0.8"/>
</parameter>

<!-- This property is the part of the composite definition for abs_units_van_range:
 It specifies the the lower limit of energy range in the monochromatic-vanadium integration 
 Used only if abs_units_van_range is set to val="monovan_lo_value,monovan_hi_value"-->
<parameter name="monovan_lo_value">
  <value val="-40."/>
</parameter>

<!-- This property is the part of the composite definition for abs_units_van_range
 It specifies the relative to incident energy higher integration limit for monochromatic vanadium in the mono-vanadium integration -->
<parameter name="monovan_hi_frac">
  <value val="0.8"/>
</parameter>
<!-- This property is the part of the composite definition for abs_units_van_range
 It specifies the the higher limit of energy range in the monochromatic-vanadium integration 
 Used only if abs_units_van_range is set to val="monovan_lo_value,monovan_hi_value"-->
<parameter name="monovan_hi_value">
  <value val="40."/>
</parameter>

<!-- energy range for integration calculating absolute units correction vanadium data. 
     if None, range is calculated from monovan_hi_frac/monovan_lo_frac 
     - providing the fractions of the incident energy      
     if one wants to specify the energy values here it has to be defined in the form:
    <value val="monovan_lo_value,monovan_hi_value"/>      -->    
<parameter name="abs_units_van_range"  type="string">
  <value val="None"/>
</parameter>
<!-- Sample mass used in absolute units normalization and should usually be changed by user-->
<parameter name="sample_mass">
  <value val="1"/>
</parameter>
<!-- Sample rmm used in absolute units normalization should usually be changed by user -->
<parameter name="sample_rmm">
  <value val="1"/>
</parameter>
<!-- Vanaduim mass used in absolute units normalization and is usually instrument specific (changes rarely) -->
<parameter name="vanadium-mass">
  <value val="20.79"/>
</parameter>
<!-- if this value set to true, modo-vanadium run is not analyzed and masks obtained for arbitrary units are used for mono-vanadium -->
<parameter name="use_sam_msk_on_monovan" type = "bool">
  <value val="False"/>
</parameter>

<!-- if this value is provided (not None) it is string reperesentation of the number used instead of calculating mono-vanadium based normalization factor 
   one does not need to provide mono-vanadium run if this value is provided as it will be used instead
  -->
<parameter name="mono_correction_factor" type="string">
  <value val="None"/>
</parameter>
  
<!-- **************************************** ABSOLUTE UNITS CORRECTION DEFAULTS END ****************************  -->

<!-- if defined to true, fix incident energy to this value and do not calculate the energy from the run -->
<parameter name="fixei"  type="bool">
    <value val="False"/>
</parameter>

<!--  ****************************************  Workflow control **************************** -->

<!-- This parameter controls the format of output data written by reducer. 
    Three values are currently supported, namely .spe, .nxspe, and nexus (mantid workspace) (.nxs)
     Three possible values for this are defined inin DirectEnergyConversion init routine as recognized by save method 
     If None is there, no internal script saving occurs and one needs to use external save operations -->  
<parameter name="save_format" type="string">
   <value val="None"/>
</parameter>

<!-- If one wants to sum runs. By default no, as in addition to the key word one has to provide list of input run-numbers
     but presence of this key here allows to propagate this key-word to the reducer   -->
<parameter name="sum_runs"  type="bool">
   <value val="False"/>
</parameter>

<!-- # Run Detector Efficiency Correction -->
<parameter name="apply_detector_eff"  type="bool">
   <value val="True"/>
</parameter>
<!-- # Multiply result by ki/kf value -->
<parameter name="apply_kikf_correction"  type="bool">
   <value val="True"/>
</parameter>

<!-- The if true, use only hard mask file specified above and do not run diagnostics procedures -->
<parameter name="use_hard_mask_only" type="bool">
    <value val="False"/>
</parameter>

<!-- Parameter specifies if one wants to run diagnostics (which include applying hard mask file) or not-->
<parameter name="run_diagnostics" type="bool">
    <value val="True"/>
</parameter>


<!-- If this parameter is set to true, dgreduce will try to load mask from the mask file
     correspondent to the run if finds it and uses this mask as hard mask only (does not run diagnostics). 
     If such file has not been found, it will run diagnostics and save the masks into mask file for reuse 
     Hard Mask file, provided separately or as additional hard mask file is ignored in this case -->
<parameter name="save_and_reuse_masks"  type="bool">
   <value val="False"/>
</parameter>

<!-- The semicolon separated list of possible log names, containing information on crystal rotation.
     First found log will be used together with motor_offset to identify crystal rotation 
     (psi in Horace) -->
<parameter name="motor_log_names"  type="string">
   <value val="CCR_ROT;Rot"/>
</parameter>
<!-- Initial value used to identify crystal rotation angle psi=motor_offset+wccr.timeAverageValue()  -->
<parameter name="motor_offset">
   <value val="None"/>
</parameter>

<parameter name="correct_absorption_on"  type="string">
  <value val="None"/>
  <description is="If defined, the property would initiate the run of the absorption corrections procedure, specific for the measured sample. 
  The corrections themselves are controlled by one of the absorption shapes classes, defined for Direct inelastic reduction. 
  These shapes are Cylinder, Plate, HollowCylinder and other defined in the AbsorptionShapes module within the direct inelastic 
  reduction scripts folder"/>
</parameter>
<parameter name="abs_corr_info"  type="string">
  <value val="None"/>
  <description is="The property describes the type of the absorption corrections to run and, if necessary, 
  additional properties of the absorption algorithm to use. The acceptable types are:
  is_mc:True (for Monte-Carlo corrections)  This option is default option if neither is_mc nor is_fast key is present.
  is_fast:True (for numerical and, when possible, analytical corrections)
  The property string may have a form:
  is_mc:True,NumberOfWavelengthPoints:50,EventsPerPoint:100 or any other non-sample related properties, accepted by Monte-Carlo corrections algorithm
  or
  is_fast:True,ExpMethod:FastApprox,ElementSize:10 or any other non-sample related accepted by AbsorptionCorrection algorithm
  If set up in a Python script, the info can be provided both as a string above and as a Python dictionary. 
  "/>
</parameter>


<!-- List of the words which can be used as a command line arguments to define reducer keywords
     the form is reducer_keword1=synonim1=synonim2=synonim3;reducer_keword1=synonim1a, so, 
     the reducer keywords are the leftmost values of the keyword assignments below
     Each keyword met in command line or file above are converted into reducer keyword as below
-->  
<parameter name="synonims" type="string">
   <value val="normalise_method=norm_method;
       fix_ei=fixei;
       sum_runs=sum;
       wb_integr_range=detector_van_range;
       motor_log_names = motor_name;
       van_mass=vanadium-mass;
       check_background = background;

       mon1_norm_spec=norm-mon1-spec;
       mon2_norm_spec=norm-mon2-spec;
       scale_factor=scale-factor;
       wb_scale_factor=wb-scale-factor;
       monovan_integr_range=abs_units_van_range;
       monovan_lo_value = monovan-integr-min;
       monovan_hi_value = monovan-integr-max;
       bkgd_range = background_range;
       background_test_range = diag_background_test_range;
       hard_mask_file=hard_mask;
       van_out_lo = diag_van_median_rate_limit_lo=diag_van_out_lo;
       van_out_hi = diag_van_median_rate_limit_hi=diag_van_out_hi;
       van_lo     = diag_van_median_sigma_lo=diag_van_lo;
       van_hi     = diag_van_median_sigma_hi=diag_van_hi;
       van_sig    = diag_van_median_sigma=diag_van_sig;
       tiny       = diag_tiny;
       huge       = diag_huge=large;
       samp_zero  = diag_remove_zero=diag_samp_zero;
       samp_lo    = diag_samp_median_sigma_lo=diag_samp_lo;
       samp_hi    = diag_samp_median_sigma_hi=diag_samp_hi;
       samp_sig   = diag_samp_median_sigma=diag_samp_sig;
       variation  = diag_variation;
       bleed_test = bleed = diag_bleed_test;
       bleed_maxrate= diag_bleed_maxrate;
       bleed_pixels  = diag_bleed_pixels;
       deltaE_mode =  deltaE-mode;
       ei-mon1-spec=ei_mon1_spec;
       ei-mon2-spec = test_ei2_mon_spectra=ei_mon2_spec;
       ei_mon_spectra=test_mon_spectra_composite"
    />
</parameter>

<!-- The same parameters are present in IDF file and here is their duplicate. 
    These parameters are used as corrections for instrument parameters loaded from nexus IDF file.
    Duplicate loading of the same parameters is acceptable and performance lose is negligible.
-->
<parameter name="TubePressure">
      <value units="atm" val="10.0"/>
</parameter>
<parameter name="TubeThickness">
      <value units="metre" val="0.0008"/>
</parameter>
<parameter name="DelayTime">
      <value units="microseconds" val="-5.3"/>
</parameter>


  <!-- -->
</component-link>

</parameter-file>