YOUR SHIFT » History » Version 20

Benton Pahlka, 09/01/2011 01:46 PM

1 1 Benton Pahlka
h1. YOUR SHIFT:  Important notes for the shifters:
2 1 Benton Pahlka
3 19 Benton Pahlka
h3. %{color:red}You should have a pair of shoes with you because you may need to go underground. Sandals, flip-flops, high heels, etc are not appropriate footwear for underground access.%
4 19 Benton Pahlka
5 20 Benton Pahlka
h3. You should have been here at least 15 minutes early to:
6 20 Benton Pahlka
7 20 Benton Pahlka
* Talk to either the previous shift physicist or a crew member and discuss what happened during their shift
8 20 Benton Pahlka
* Note any new problems found or old ones fixed.  
9 20 Benton Pahlka
* Inquire whether there were any hardware changes, special activities etc. 
10 20 Benton Pahlka
* Inquire if anyone is underground. 
11 20 Benton Pahlka
* Ask if there are any requests for special data taking and remind them to release DAQ control before they leave
12 20 Benton Pahlka
* Wish the previous shifter a safe drive home.
13 20 Benton Pahlka
14 12 Benton Pahlka
h2. Where to go for help
15 13 Benton Pahlka
16 16 Benton Pahlka
* "MINOS Shifter Guide Number 1": 
17 14 Benton Pahlka
18 16 Benton Pahlka
* "MINOS Shifter Guide Number 2":
19 13 Benton Pahlka
20 19 Benton Pahlka
* "The Online Monitoring Manual":
21 12 Benton Pahlka
22 19 Benton Pahlka
* "The Online Monitoring Gallery": 
23 19 Benton Pahlka
24 17 Benton Pahlka
h2. Shifter's ToDo List
25 11 Benton Pahlka
26 18 Benton Pahlka
* ensure the highest uptime of both Far and Near detectors
27 18 Benton Pahlka
* diagnose and fix problems quickly and efficiently
28 18 Benton Pahlka
* alert the system experts and work with them in case of problems
29 18 Benton Pahlka
* perform regular inspections of the data taken
30 17 Benton Pahlka
* monitor detector systems and environment conditions 
31 10 Benton Pahlka
* fill out shifter's checklists
32 10 Benton Pahlka
33 10 Benton Pahlka
The approximate shifter's ToDo list:
34 10 Benton Pahlka
1.	Be at the control room early.  Arrive 30 minutes before your official shift start time.
35 10 Benton Pahlka
2.	Carefully read all CRL entries entered in the last 24 hours (if it's your first day on shift, then browse thorugh last several days, paying attention to all special tasks accomplished, problems discovered and fixes performed).
36 10 Benton Pahlka
3.	Begin filling Start_Shift.htm form in the Control Room Logbook.
37 10 Benton Pahlka
4.	Restart both run control GUIs on screen.  A window will appear asking for the current operator's name.  Type your name in the appropriate box.  Restarting the RC GUI ensures that you are identified as the current shifter throughout your shift.
38 1 Benton Pahlka
5.	Find out who are the shift physicists and crew supervisor. The shift schedule is posted at
39 20 Benton Pahlka
40 10 Benton Pahlka
7.	Take control of the DAQ using the run control GUI.
41 10 Benton Pahlka
8.	Proceed with filling out shifter's checklists (described in the next section); try to find and diagnose hardware problems; record your findings in the online logbook.
42 10 Benton Pahlka
9.	Regularly check DAQ, DCS status webpages (keep both of them open on top of one of the multiple control room screens).
43 10 Benton Pahlka
10.	Spend time looking at the real time events using the event display.
44 10 Benton Pahlka
11.	Browse through Online Monitoring plots, not just the ones from the checklist.
45 10 Benton Pahlka
12.	Record anything happening in the online logbook.
46 10 Benton Pahlka
13.	Enter all new problems into the JIRA issue tracking system.
47 10 Benton Pahlka
48 10 Benton Pahlka
49 10 Benton Pahlka
50 10 Benton Pahlka
h2. Shifter's Checklist Forms
51 10 Benton Pahlka
52 19 Benton Pahlka
It's important to let the online statistics accumulate, so make sure that the data run has been running for at least two hours before proceeding with the checklist.
53 19 Benton Pahlka
54 10 Benton Pahlka
* Start_Shift 
55 10 Benton Pahlka
* DCSChecklist_Near
56 10 Benton Pahlka
* DCSChecklist_Far
57 10 Benton Pahlka
* OMCheckListNear
58 4 Benton Pahlka
* OMCheckListFar
59 19 Benton Pahlka
* Beam Summary
60 19 Benton Pahlka
* End_Shift  
61 1 Benton Pahlka
62 19 Benton Pahlka
63 1 Benton Pahlka
64 4 Benton Pahlka
65 5 Benton Pahlka
h2. Please click "Update" or "Latest" (or "Current") on NuMI elog before inserting plots
66 5 Benton Pahlka
67 4 Benton Pahlka
68 2 Benton Pahlka
h2. Job List
69 2 Benton Pahlka
70 19 Benton Pahlka
71 7 Phil Adamson
72 2 Benton Pahlka
* The Far Detector needs to be notified of beam downtime as follows.  
73 2 Benton Pahlka
If the beam will be down for long enough from 07:30-17:30, please notify the mine crew.
74 2 Benton Pahlka
** If there is downtime of at least half an hour notify Soudan.
75 2 Benton Pahlka
** If you learn of an all-day shutdown coming in the near future, inform the Run Coordinator and Soudan.
76 2 Benton Pahlka
77 9 Arthur Kreymer
* Please stop and restart OM Gui at the beginning of your shift, it leaks memory.
78 1 Benton Pahlka
79 9 Arthur Kreymer
* When filling in the Near Detector OM check-list please make sure that the socket is "open", and that the status canvas gives a current time stamp. 
80 9 Arthur Kreymer
** When the MINERvA shifter completes their ND OM checklist and shuts down their monitoring window it closes our connection.
81 1 Benton Pahlka
82 9 Arthur Kreymer
* The 'Big Green Button' shows file write latency. It flashes orange if this goes over 3 seconds, and turns red if the file is badly out of date. In this case, restart the Beam data logger, as described at [[BEAMDATA]]
83 9 Arthur Kreymer
** The 'Big Green button' should no longer be getting stuck, showing stale data. Please restart the Button promptly if it gets stuck, and note the time in the ECL.
84 9 Arthur Kreymer
85 9 Arthur Kreymer
* Check for good beam data logging at This plot is updated daily. Thanks, Sarah ! Check reference plots at "BEAMDATA":
86 9 Arthur Kreymer
87 3 Benton Pahlka
* You need to post the Beam Shift Plots using NUMI Elog and Minos CRL sessions on minos-acnet, from the files in /home/minos/BeamPlots . The NFS server which made these available in /misc/mcr/... has been retired, 
88 1 Benton Pahlka
89 1 Benton Pahlka
* The Minerva Control Room Logbook is at
90 3 Benton Pahlka
91 9 Arthur Kreymer
* If G:RD1224 comes into alarm at 14:30, this is expected. If the alarm won't clear after 14:45, call MCR and ask them to remove multiwire 112 from the NuMI beamline. An alert box will pop up on minos-om console to remind you. 
92 1 Benton Pahlka
93 9 Arthur Kreymer
* Please check your own training at: [training status|].  Has it expired?  Then renew it  immediately.  Is it about to expire?  Then renew it so it won't lapse. Shifters are expected to be able to go underground if necessary.
94 1 Benton Pahlka
95 1 Benton Pahlka
* Please check the Run Control GUI, DCS status pages, and JAS regularly for warnings.  The shifter is the 1st responder to these error conditions and should notice alarms on the time scale of minutes (not hours).
96 1 Benton Pahlka
97 1 Benton Pahlka
* Please watch the LCW output temperature on the ND DCS Magnet Status section.  We have had problems with a water filter clogging up, which will take down both the ND and the NuMI absorber if it stopped up.  If the temperature gets very high (>75) or increases quickly (so that it will reach 80 F in less than a day) call the Run Coordinator, then John Voirin or Bill Moorhouse.   The temperature regulation is set at 67 F.
98 1 Benton Pahlka
** This will also restrict cooling to the NuMI absorber.  Please let the NuMI Beam Coordinator (Sam Childress or Peter Lucas) that there is a problem so they can watch that temperature.
99 1 Benton Pahlka
100 1 Benton Pahlka
* Due to budget cuts, we are able to access the far detector only during regular hours (weekend days are still ok) except in emergencies, where loss of data doesn't count as an emergency.
101 1 Benton Pahlka
102 9 Arthur Kreymer
* The Soudan On Call Phone number will not work at night.  Instead, call Bill Miller or Jerry Meier, plus the run coordinator (Greg or Chris) and we will figure out if it's a real emergency or if budget cuts will be costing us data.
103 9 Arthur Kreymer
** If Bill doesn't answer his cell, try his home number.  If he's at home, his land line works and cell coverage doesn't dip down next to the lake.
104 1 Benton Pahlka
105 1 Benton Pahlka
* The ND magnet can now be controlled remotely (E:NDMAG on ACNET).  This includes changing polarity, turning the power supply on and off, and setting the current (a setting value of 4990 produces a current readback of 4973 amperes).  The setting is an unsigned number; the current readback is a negative number.  There is a status bit that indicates polarity.  For further information see [this link|].
106 1 Benton Pahlka
107 1 Benton Pahlka
** If Firefox starts giving errors, then restart it.
108 1 Benton Pahlka
109 1 Benton Pahlka
* Answering the telephone
110 1 Benton Pahlka
** Please let people know where they've called and who you are! E.g.
111 1 Benton Pahlka
** "MINOS Control Room, this is Fred Jones" would suffice.
112 1 Benton Pahlka
** Please try to always answer the telephone in a timely manner.  If you need to step out for a few minutes check the caller ID on the phones when you get back.  Call back all numbers that went unanswered.
113 1 Benton Pahlka
114 1 Benton Pahlka
* Put a note in the logbook when you call experts or the run coordinator, at least the first time in a thread.
115 1 Benton Pahlka
116 6 Benton Pahlka
117 6 Benton Pahlka
h2. Swing and Owl shifts are no longer covered by Minerva
118 6 Benton Pahlka
119 6 Benton Pahlka
The swing and owl shifts are not currently being run by the Minerva shifters. For reference, here are the instructions that applied in that situation:
120 6 Benton Pahlka
121 6 Benton Pahlka
The MINOS shifters should arrive at the control room at the start of their shifts, and should:
122 6 Benton Pahlka
123 6 Benton Pahlka
* Deal with any problems they find
124 6 Benton Pahlka
* Go through the checklists with the previous MINOS shifters
125 6 Benton Pahlka
* Bring themselves up-to-date on any outstanding issues or problems likely to occur during the shift. Make sure the Minerva shifters are away of these, and explain what they should do if the problem arises.
126 6 Benton Pahlka
127 6 Benton Pahlka
128 6 Benton Pahlka
Since there is now no overlap between MINOS shifters, it is __vital__ that regular use is made of the CRL to pass on information, and ensure the following shifter knows the status of the detectors.
129 6 Benton Pahlka
130 6 Benton Pahlka
The MINOS on-call shifter should make a logbook entry from home any time they are called. They should log:
131 6 Benton Pahlka
* What caused the call to be made
132 6 Benton Pahlka
* What action they took
133 6 Benton Pahlka
* Any action they told the Minerva shifter to take
134 6 Benton Pahlka
* Any phonecalls with MINOS experts they made or received.
135 6 Benton Pahlka
136 6 Benton Pahlka
Minerva currently doesn't have access to the MINOS CRL. They should use the blue electronic post-it note on the minos-om. They should log in this any interventions with the MINOS systems, or relevant information such as phonecalls with MINOS experts. The MINOS day shifter should transfer this information to the MINOS CRL at the start of their shift.
137 6 Benton Pahlka
138 1 Benton Pahlka
* Congratulations you made it this far!  Please note in the CRL logbook that you actually read the memopad and know what to do on shift.