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