Project

General

Profile

REMOTE » History » Version 2

Stefano Tognini, 05/27/2013 03:22 PM

1 1 Arthur Kreymer
h1. REMOTE MINOS+ STATIONS REQUIREMENTS AND POLICIES
2 1 Arthur Kreymer
3 1 Arthur Kreymer
Notes underlined show topics that need discussion, improvement or maybe a complete change.
4 1 Arthur Kreymer
5 1 Arthur Kreymer
Notes with *bold font*  shows the significant differences between
6 2 Stefano Tognini
 docDB 7789-v4 (Remote MINOS Shifts - Brett Viren, Rob Plunkett and Benton Pahlka) and this documentation.
7 1 Arthur Kreymer
8 1 Arthur Kreymer
h2. INTRODUCTION
9 1 Arthur Kreymer
10 2 Stefano Tognini
A remote MINOS station can save effort and funds of different institutions by providing a possibility to the collaboration to take shifts remotely. Since shifters rarely are in physical contact with the detectors and all duties are done by networked applications, a remote shift has almost no lacks comparing to a local shift. This document provides the hardware and software requirements to set a remote shift station from the ground up and defines the requirements, certification and policies for MINOS+ Remote Stations.
11 1 Arthur Kreymer
12 1 Arthur Kreymer
h2. HARDWARE AND DOCUMENTATION REQUIREMENTS
13 1 Arthur Kreymer
14 1 Arthur Kreymer
In order to be certified for remote MINOS+ shifts one will need to fulfill the requirements shown below :
15 1 Arthur Kreymer
* Two computers, each one powerfull enough to run all the software simultaneously. 
16 1 Arthur Kreymer
One sufficiently powerfull computer ought to be enough for a shift, 
17 2 Stefano Tognini
but it is strongly recommended to split the load on two machines. A second computer is also important for redundancies: in case one computer crashes, there is still one working and capable of doing all the shift tasks.
18 1 Arthur Kreymer
* At least 3 displays (NuMIMon, RC GUI and DCS must be visible by default).
19 1 Arthur Kreymer
* A telephone line able to make and receive domestic / international calls.
20 1 Arthur Kreymer
* A copy of the Shifter's Guide (available at http://www-numi.fnal.gov/Minos/ControlRoom/ShiftersGuide.pdf).
21 2 Stefano Tognini
* A list of all phone numbers listed in the blackboard at the MINOS+ Control Room (available at https://cdcvs.fnal.gov/redmine/projects/minos-memopad/wiki/CONTACTS).
22 1 Arthur Kreymer
23 1 Arthur Kreymer
h2. INSTALLATION AND CONFIGURATION
24 1 Arthur Kreymer
25 2 Stefano Tognini
MINOS+ Control Room operates under the Scientific Linux Fermi 5.5 in the 32 bit version. This must be the RMS operational system as well and it can be downloaded at http://fermilinux.fnal.gov
26 1 Arthur Kreymer
27 2 Stefano Tognini
The Control Room software and the necessary steps to configure a Remote MINOS+ Station are available in a centralized and online page (link below). This guarantee that the software is always available and the documentation used to set it up is up to date.
28 1 Arthur Kreymer
29 2 Stefano Tognini
> https://cdcvs.fnal.gov/redmine/projects/remotestation/wiki
30 1 Arthur Kreymer
31 1 Arthur Kreymer
32 1 Arthur Kreymer
h2. REMOTE SHIFT LIMITATIONS
33 1 Arthur Kreymer
34 2 Stefano Tognini
On remote shifts some tasks will be different or missing comparing to a local shift. The first is that there is no possibility to manage the keys for going underground on the Near Detector Hall. Since this duty is shared with MINERvA, it will be delegated to them during remote shifts or, otherwise, this will not be performed. Also, ACNET beam plots will not be made. The choice was made by weighting the technical challenge against their importance and the ease of which experts can perform them.
35 1 Arthur Kreymer
36 1 Arthur Kreymer
h2. CERTIFYING A NEW RMS
37 1 Arthur Kreymer
38 2 Stefano Tognini
In order to be an official RMS, the institution's remote station must fulfill some requirements:
39 2 Stefano Tognini
40 1 Arthur Kreymer
* Have technical resources to configure and maintain the remote station.
41 1 Arthur Kreymer
* Be committed to making the station available for collaborators from outside the hosting institution for their own remote shifts.
42 1 Arthur Kreymer
* Successfully complete two (uncounted) test shifts by two different people, concurrent with a local shift (at FNAL). 
43 1 Arthur Kreymer
At least one uncounted shift must be performed by one who is not directly involved in configuring and maintaining the RMS.
44 2 Stefano Tognini
** +The condition above may be changed to:
45 2 Stefano Tognini
- Successfully complete two (uncounted) test shifts concurrent with a local shift (at FNAL). Removing the condition of doing shifts with 2 different people will allow that Universities with only ONE researcher can be defined as an official RMS. The same person will configure the RMS, maintain it and do the necessary shifts.+
46 1 Arthur Kreymer
* An informal report describing issues (if any) found during the shift should be given to
47 1 Arthur Kreymer
the run coordinators and other interested parties.
48 1 Arthur Kreymer
49 2 Stefano Tognini
he fulfillment of the fore mentioned requirements certifies the RMS for official remote shifts. A list with the officially maintained MINOS+ remote stations can be found in the Remote MINOS+ Station's Wiki and in the Remote section in the MemoPad:
50 1 Arthur Kreymer
https://cdcvs.fnal.gov/redmine/projects/remotestation/wiki
51 1 Arthur Kreymer
52 2 Stefano Tognini
+Stefano's note: If the wiki gets moved to the Memopad, than the last paragraph will just mention that the officially maintained MINOS+ remote stations can be found in the section "List of officially maintained MINOS+ remote stations"+
53 2 Stefano Tognini
54 1 Arthur Kreymer
h2. SHIFTER TRANSITION
55 1 Arthur Kreymer
56 2 Stefano Tognini
Local shifts have an informal procedure for shift hand-off. The new shifter should be updated with some current issues (if any), the current status of the experiment and if someone is performing some tasks underground. This should be done during shift hand-off for remote shifts as well.
57 1 Arthur Kreymer
58 1 Arthur Kreymer
* The oncoming remote shifter calls the current local (or remote) shifter before the end of
59 1 Arthur Kreymer
the current shift to discuss the status of the experiment. It is strongly recommended that
60 1 Arthur Kreymer
the oncoming shifter also checks the Logbook and the Memopad. (Ignore this step if there was
61 1 Arthur Kreymer
no previous shift, but checking the Logbook and MemoPad before the start of the shift is
62 1 Arthur Kreymer
strongly recommended and could avoid some problems.)
63 1 Arthur Kreymer
* The oncoming remote shifter must ensure that the remote shift contact information is
64 1 Arthur Kreymer
prominently displayed in the MINOS+ Control Room.
65 1 Arthur Kreymer
*A note in the Logbook informing the start of a remote shift with the remote station's
66 1 Arthur Kreymer
name, the remote shifter's name and its contact should be done.*
67 1 Arthur Kreymer
* The MINERvA shifter must be informed that a remote MINOS+ shift is starting.
68 1 Arthur Kreymer
* The MINERvA shifter must inform the Main Control Room (MCR) that they are now the NuMI contact.
69 1 Arthur Kreymer
* +The 2 steps in italic above should be removed, since NOvA is now responsible for
70 1 Arthur Kreymer
the NuMI.+
71 1 Arthur Kreymer
72 1 Arthur Kreymer
On end shift hand-off, the steps are reversed:
73 1 Arthur Kreymer
74 1 Arthur Kreymer
Oncoming local (or remote) shifter must call the Remote MINOS+ Station before the end of
75 1 Arthur Kreymer
the shift in order to be updated with the status of the experiment.\
76 1 Arthur Kreymer
* The remote shift announce must be removed from the MINOS+ Control Room display.\
77 1 Arthur Kreymer
* *The remote shifter should state, in the Logbook, that the remote shift has ended.*
78 1 Arthur Kreymer
* If the new shifter is a local shifter, then the Main Control Room must be informed that MINOS+ is the current NuMI contact.
79 1 Arthur Kreymer
+The step in italic should be removed,  since NOvA is now responsible for the
80 1 Arthur Kreymer
NuMI+