Overriding and setting default values for homer processes - Revision history

Dickon Champion: /* Overriding instrument specific population */

2008-07-04T11:07:10Z

Overriding instrument specific population

2008-07-04T11:00:40Z

using a reference file built from a detector.dat information

2008-07-04T10:55:32Z

Overriding instrument specific population

2008-07-04T10:45:47Z

2008-07-04T10:41:48Z

Setting homer defaults

2008-07-04T10:41:25Z

Setting homer defaults

2008-07-04T10:29:29Z

Setting homer defaults

2008-07-04T10:27:27Z

Setting homer defaults

2008-07-04T10:26:06Z

2008-07-04T10:21:49Z

Overriding instrument specific population

@@ Line 85: / Line 85: @@
 <tt>MAPS/setup_maps_data_source.m</tt>
-we add  the line
+we add the line:
-,'inst_nxs:::detref.nxs','detector','full_reference_detector'
+<pre>
 == Creating populated nexus files ==

@@ Line 79: / Line 79: @@
 it is possible to generate detector information from the files specified to create detector.dat files, these contain extra information about the [[IXTgeometry]], [[IXTshape]], [[IXTtranslation] and [[IXTorientation]] of the detectors.
-It is first necessary to [[Building a reference detector file|build a reference detector file]]
+It is first necessary to [[Building a reference detector file|build a reference detector file]]. Once you have done this it is again necessary to edit a script.
 == Creating populated nexus files ==

@@ Line 58: / Line 58: @@
 == Overriding instrument specific population ==
+=== using defined nexus files ===
 In the case where there is incorrect information in the rawfile which has been generated we can populate detector and spectra information from a nexus file. The [[Overriding_and_setting_default_values_for_homer_processes#Creating populated nexus files|creation of these files]] is defined below
@@ Line 74: / Line 74: @@
 These files are not distributed with the libisis package as they can change. The '<tt>inst_nxs:::</tt>' path is a standard definition which is specified in the <tt>[[Homer_Gui_setup|inst_defs.m]]</tt> file or in the [[Instrument setup]]
 == Creating populated nexus files ==

@@ Line 48: / Line 48: @@
 <pre>
 ixf_global_var('homer_white_beam','set','normalisation','uamp');
 </pre>

@@ Line 42: / Line 42: @@
 <pre>
 ixf_global_var('homer_white_beam','set','d_int',[20,100]);
-ixf_global_var('homer_white_beam','set','range',[1000,2000]);
+ixf_global_var('homer_white_beam','set','range',[1000,5000]);
 </pre>

@@ Line 16: / Line 16: @@
 == Setting homer defaults ==
-For each instrument there can be particular default values specified for each step in the homering process. When homering using a script there are set default values for the [[Scripting_Homer_Functions#white_beam|white beam]] process. For example the MARI white beam defaults are specified in:
+For each instrument there can be particular default values specified for each step in the homering process. When homering using a script there are set default values for the [[Scripting_Homer_Functions#white_beam|white beam]] process (None of the following is relevant to the GUI system). For example the MARI white beam defaults are specified in the script:
 == Overriding instrument specific population ==

← Older revision		Revision as of 10:26, 4 July 2008
Line 13:		Line 13:

	each instrument has a named directory where there are instrument specific scripts used to define default values and files which are used to set up and populate the [[IXTrunfile]] object.		each instrument has a named directory where there are instrument specific scripts used to define default values and files which are used to set up and populate the [[IXTrunfile]] object.
		+
		+	== Setting homer defaults ==
		+
		+	For each instrument there can be particular default values specified for each step in the homering process. For example the MARI [[white beam]]

	== Overriding instrument specific population ==		== Overriding instrument specific population ==