Instrument parameters and Instrument definitions - Revision history

Alex Buts: /* Experiment specific parameters */

2023-01-09T16:07:31Z

Experiment specific parameters

Alex Buts: /* Experiment specific parameters */

2023-01-09T16:02:39Z

Experiment specific parameters

Alex Buts: /* Experiment specific parameters */

2023-01-09T15:59:04Z

Experiment specific parameters

Alex Buts: /* Experiment specific parameters */

2023-01-09T15:57:04Z

Experiment specific parameters

Alex Buts: /* Experiment specific parameters */

2023-01-09T15:56:42Z

Experiment specific parameters

Alex Buts at 11:11, 8 October 2020

2020-10-08T11:11:30Z

Alex Buts: /* Experiment specific parameters */

2020-10-08T09:42:29Z

Experiment specific parameters

Alex Buts: /* Instrument Specific Files (Instrument Definitions) */

2017-08-16T13:26:49Z

Instrument Specific Files (Instrument Definitions)

Alex Buts: /* Experiment specific parameters */

2017-03-22T17:37:45Z

Experiment specific parameters

Alex Buts at 18:33, 5 January 2017

2017-01-05T18:33:45Z

@@ Line 24: / Line 24: @@
-[https://github.com/FITLinuxSupport/analysisscripts/blob/master/UpdateSVN Simple scripts] are running each hour on instrument cabin machines and [https://isiscompute.nd.rl.ac.uk/nxwebplayer 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
+[https://github.com/FITLinuxSupport/analysisscripts/blob/master/UpdateSVN Simple scripts] are running each hour on instrument cabin machines and IDAaaS servers pulling data from [https://github.com/pace-neutrons/InstrumentFiles GitHub], so the file added to the 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 [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] only the last results are logged and placed into:
+command. The logs are regularly reviewed and cleared up manually.
 The GIT command:
@@ Line 39: / Line 34: @@
    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 [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] this command needs administrative access.
+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 [https://isis.analysis.stfc.ac.uk/ IDAaaS virtual machines] this command is restricted to the members of the excitation group staff.
 <span style="color:#0000ff; background:#FF69B4"> In 2015 git was the most convenient way to provide data synchronization between various computers, but other methods are available now.

@@ Line 3: / Line 3: @@
 To reduce experimental data described in the previous chapter, user needs access to [http://shadow.nd.rl.ac.uk/wiki/idr/index.php?title=Location_and_details_of_access_to_instrument_parameters,_necessary_to_reduce_data#Instrument_Definition_Files Instrument Definition Files] (IDF) defining main configuration of the instrument and parameters of the script, [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Location_and_details_of_access_to_sample_scripts_used_in_data_processing 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 [https://github.com/pace-neutrons/InstrumentFiles github archive] This archive is cloned to [https://isis.analysis.stfc.ac.uk/ IDAaaS workspaces] and instrument cabin computers at
+The source of these files is stored in publicly available [https://github.com/pace-neutrons/InstrumentFiles GitHub archive] This archive is cloned to [https://isis.analysis.stfc.ac.uk/ IDAaaS workspaces] and instrument cabin computers at
    /usr/local/mprogs/InstrumentFiles/[INSTRUMENT_NAME]
@@ Line 15: / Line 15: @@
 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).
- [https://github.com/pace-neutrons/InstrumentFiles]
+If user wants to run reduction on their own computer, he needs to checkout instrument files from the [https://github.com/pace-neutrons/InstrumentFiles GitHub archive]. Everybody can clone data from this server and some instrument scientists have write access to it. Contact [mailto:alex.buts@stfc.ac.uk Alex Buts] or [mailto:Duc.Le@stfc.ac.uk Duc Lee] 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:

@@ Line 9: / Line 9: @@
 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.
-[http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Automatic_user_configuration Automatic configuration scripts] running on [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] automatically add appropriate folder, corresponding to the instrument to Mantid data search path (see picture below). This make the data, stored in the folder available to the [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Location_and_details_of_access_to_sample_scripts_used_in_data_processing reduction scripts] and places the link to the instrument files to the Nomachine desktop.
+[http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Automatic_user_configuration 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 [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Location_and_details_of_access_to_sample_scripts_used_in_data_processing reduction scripts] and places the link to the instrument files the folder within IDAaaS machine menue.
 [[File:instrumentFiles.png]]

@@ Line 3: / Line 3: @@
 To reduce experimental data described in the previous chapter, user needs access to [http://shadow.nd.rl.ac.uk/wiki/idr/index.php?title=Location_and_details_of_access_to_instrument_parameters,_necessary_to_reduce_data#Instrument_Definition_Files Instrument Definition Files] (IDF) defining main configuration of the instrument and parameters of the script, [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Location_and_details_of_access_to_sample_scripts_used_in_data_processing 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 [https://github.com/pace-neutrons/InstrumentFiles github archive] This archive is cloned to [https://isis.analysis.stfc.ac.uk/ IDAaaS workspaces] and instrument cabin computers at:
+The source of these files is stored in publicly available [https://github.com/pace-neutrons/InstrumentFiles github archive] This archive is cloned to [https://isis.analysis.stfc.ac.uk/ IDAaaS workspaces] and instrument cabin computers at
    /usr/local/mprogs/InstrumentFiles/[INSTRUMENT_NAME]

@@ Line 3: / Line 3: @@
 To reduce experimental data described in the previous chapter, user needs access to [http://shadow.nd.rl.ac.uk/wiki/idr/index.php?title=Location_and_details_of_access_to_instrument_parameters,_necessary_to_reduce_data#Instrument_Definition_Files Instrument Definition Files] (IDF) defining main configuration of the instrument and parameters of the script, [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Location_and_details_of_access_to_sample_scripts_used_in_data_processing 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.)
-On [http://www.isis.stfc.ac.uk/groups/excitations/data-analysis-computers/connecting-to-isiscomputendrlacuk-using-nomachine15120.html isiscompute servers] and instrument cabin computers these files can be accessed at:
+The source of these files is stored in publicly available [https://github.com/pace-neutrons/InstrumentFiles github archive] This archive is cloned to [https://isis.analysis.stfc.ac.uk/ IDAaaS workspaces] and instrument cabin computers at:
    /usr/local/mprogs/InstrumentFiles/[INSTRUMENT_NAME]

@@ Line 44: / Line 44: @@
 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 [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] this command needs administrative access.
-<span style="color:#0000ff; background:#FF69B4"> In 2001 svn was the most convenient way to provide data synchronization between various computers, but other methods are available now.
+<span style="color:#0000ff; background:#FF69B4"> 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. </span>

@@ Line 15: / Line 15: @@
 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 parameter are placed under [https://en.wikipedia.org/wiki/Apache_Subversion SVN source control] with server at:
+Currently instrument parameters are placed on Github with the repository belonging to PACE project:
-  [https://svn.isis.rl.ac.uk/InstrumentFiles/trunk https://svn.isis.rl.ac.uk/InstrumentFiles/trunk]
+  [https://github.com/pace-neutrons/InstrumentFiles]
-If user wants to run reduction on their own computer, he needs to get these files. Everybody can read data from this server and some instrument scientists have write access to it. Contact [mailto:freddie.akeroyd@stfc.ac.uk Freddie Akeroyd] if you believe you  need write access to the server.
+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 [mailto:alex.buts@stfc.ac.uk 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:
-   svn add "file_name"
+   git add "file_name"
-   svn commit -m" message describing purpose of the file"
+   git commit -m" message describing purpose of the file"
 [https://github.com/FITLinuxSupport/analysisscripts/blob/master/UpdateSVN Simple scripts] are running each hour on instrument cabin machines and [https://isiscompute.nd.rl.ac.uk/nxwebplayer 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
@@ Line 38: / Line 38: @@
-The SVN command:
+The GIT command:
-   svn update
+   git pull
-can be issued from svn 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 [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] this command needs administrative access.
+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 [https://isiscompute.nd.rl.ac.uk/nxwebplayer isiscompue servers] this command needs administrative access.
 <span style="color:#0000ff; background:#FF69B4"> In 2001 svn was the most convenient way to provide data synchronization between various computers, but other methods are available now.

@@ Line 69: / Line 69: @@
 *[https://github.com/mantidproject/mantid/blob/master/instrument/MERLIN_Parameters_after2013_4.xml MERLIN Reduction parameters]
 *[https://github.com/mantidproject/mantid/blob/master/instrument/LET_Parameters_dr1to12.xml LET Reduction parameters]
 [http://shadow.nd.rl.ac.uk/wiki/idr/index.php/Setting_up_Mantid,_Matlab_and_auxiliary_programs_to_process_results_of_inelastic_experiments. Back to setting up Mantid]