Difference between revisions of "Overriding and setting default values for homer processes"
| Line 1: | Line 1: | ||
| − | == | + | |
| + | == Where are the defaults specified == | ||
the homer distribution files are contained in | the homer distribution files are contained in | ||
on a [[Download_and_setup_LIBISIS|windows distribution]] | on a [[Download_and_setup_LIBISIS|windows distribution]] | ||
| + | <tt>/your_libisis_directory/matlab<tt> | ||
| − | + | on a linux rpm installation: | |
| − | on a linux | + | <tt>/usr/local/libisis/applications/matlab/</tt> |
| − | <tt>/ | ||
in the svn repository: | in the svn repository: | ||
<tt>/libisis/applications/matlab/</tt> | <tt>/libisis/applications/matlab/</tt> | ||
| − | there are instrument specific files used to set up | + | each instrument has a 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. |
| − | + | == overriding instrument specific population == | |
| + | 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. [[Overriding_and_setting_default_values_for_homer_processes#Creating populated nexus files]] | ||
| Line 27: | Line 29: | ||
these files are not distributed with libisis package as they can change. the 'inst_nxs:::' path is a standard definition which is specified in the inst_defs.m file | these files are not distributed with libisis package as they can change. the 'inst_nxs:::' path is a standard definition which is specified in the inst_defs.m file | ||
| + | |||
| + | |||
| + | == Creating populated nexus files == | ||
Revision as of 10:03, 4 July 2008
Where are the defaults specified
the homer distribution files are contained in
on a windows distribution /your_libisis_directory/matlab
on a linux rpm installation: /usr/local/libisis/applications/matlab/ in the svn repository: /libisis/applications/matlab/
each instrument has a 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.
overriding instrument specific population
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. Overriding_and_setting_default_values_for_homer_processes#Creating populated nexus files
the specific MERLIN population information is contained in the file
setup_merlin_data_source.m
this defines the nexus files which are required for population of the IXTrunfile object which in turn the .spe file is produced from. i added the following two lines to this file, with these lines present the libisis system will try and load the IXTdetector and IXTspectra object from these files.
DSO=add_item(DSO,'inst_nxs:::merlin_detector.nxs','detector'); DSO=add_item(DSO,'inst_nxs:::merlin_spectra.nxs','spectra');
these files are not distributed with libisis package as they can change. the 'inst_nxs:::' path is a standard definition which is specified in the inst_defs.m file