Instrument parameters and Instrument definitions

Experiment specific parameters

To reduce experimental data described in the previous chapter, user needs access to Instrument Definition Files (IDF) defining main configuration of the instrument and parameters of the script, which processes the data, and the range of auxiliary files such as detector calibration file, defining actual neutronic positions of detectors in an experiment, map files (extension .map), defining the detector grouping, mask files (extension .msk) defining the lists of detectors which should not be processed and in less extend other files (.par, .phx, .nxs etc.)

The source of these files is stored in publicly available github archive This archive is cloned to IDAaaS workspaces and instrument cabin computers at

 /usr/local/mprogs/InstrumentFiles/[INSTRUMENT_NAME]

folder where the INSTRUMENT_NAME should be replaced by one out of [mari,maps,merlin,let] values list. Some instrument scientists create symbolic links (usually on Desktop) providing quick access to the files relevant for a particular instrument.

Automatic configuration scripts running on IDAaaS automatically adds appropriate folder, corresponding to the instrument to the Mantid data search path (see picture below). This make the data, stored in the folder available to the reduction scripts and places the link to the instrument files the folder within IDAaaS machine menue.

The path to the requested instrument parameters on the picture above is set to merlin instrument parameter's folder in the first row of the data search path folders list (blue arrow).

Currently instrument parameters are placed on Github with the repository belonging to PACE project:

[1]

If user wants to run reduction on their own computer, he needs to checkout these files. Everybody can clone data from this server and some instrument scientists have write access to it. Contact Alex Buts if you believe you need write access to the server. On a Unix machine, an authorized person can add an instrument file to the source control and send it to the server by placing the file into appropriate instrument folder and issuing the following commands:

 git add "file_name"
 git commit -m" message describing purpose of the file"
 git push

Simple scripts are running each hour on instrument cabin machines and isiscompue servers pulling data from SVN server, so the file added to the svn server on any machine is ready to be used everywhere within an hour. The result of script operations is currently mailed to main instrument machine user (mari, let,maps or merlin) so you can see results of these scripts work logging in as this user and typing

>>mail 

command. The logs are regularly reviewed and cleared up manually. On isiscompue servers only the last results are logged and placed into:

  /var/log/UpdateSVN.log.

available on ndmlnx01 node only.

The GIT command:

 git pull

can be issued from the instruments folder of a particular machine (always /usr/local/mprogs/InstrumentFiles/ but may have additional references on particular machines) to get immediate access to a new data, but on isiscompue servers this command needs administrative access.

In 2015 git was the most convenient way to provide data synchronization between various computers, but other methods are available now. Group needs to discuss if this is still appropriate way of sharing data these days.

Back to setting up Mantid

Instrument Specific Files (Instrument Definitions)

Instrument definition files, which describe the the instrument configuration and main parameters of the reduction are part of Mantid and are usually located in /opt/Mantid/instrument folder on Unix or MantidInstallationFolder\instrument folder (c:\MantidInstall\instrument by default) on Windows.

Newer version of these files produced after Mantid release are automatically retrieved by Matnid at startup into ~/.mantid/instrument on Unix or c:\Users\USERACCOUNT_FOLDER\AppData\Roaming\mantidproject\mantid\instrument folder on Windows. Such files, if present for a particular instrument override files in Mantid installation directory.

 INSTRUMENT_NAME_Parameters.xml

file provide comprehensive list and description of almost all parameters used by the data reduction script and the file:

 INSTRUMENT_NAME_Definition.xml

describes all details of the instrument geometry. For further details of the file format and their contents user should look at Mantid IDF description pages.

Actual default parameters for inelastic data reduction scripts, which are used by Mantid reduction script can also be accessed on the web from Mantid Git repository:

• MARI Reduction parameters
• MAPS Reduction parameters
• MERLIN Reduction parameters
• LET Reduction parameters
• HET Reduction parameters

Back to setting up Mantid