YOUR SHIFT » History » Version 26

Benton Pahlka, 09/01/2011 03:55 PM

1 26 Benton Pahlka
h1. YOUR SHIFT:  Important notes for shifters:
2 1 Benton Pahlka
3 21 Benton Pahlka
h2. %{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 23 Benton Pahlka
** %{color:red}Please check your own training at: "training status": .%  
6 22 Benton Pahlka
* Has it expired?  Then renew it immediately.  
7 22 Benton Pahlka
* Is it about to expire?  Then renew it so it won't lapse. 
8 22 Benton Pahlka
9 21 Benton Pahlka
h2. You should have been here at least 15 minutes early to:
10 20 Benton Pahlka
11 20 Benton Pahlka
* Talk to either the previous shift physicist or a crew member and discuss what happened during their shift
12 20 Benton Pahlka
* Note any new problems found or old ones fixed.  
13 20 Benton Pahlka
* Inquire whether there were any hardware changes, special activities etc. 
14 20 Benton Pahlka
* Inquire if anyone is underground. 
15 20 Benton Pahlka
* Ask if there are any requests for special data taking and remind them to release DAQ control before they leave
16 22 Benton Pahlka
* Make sure the Minerva shifters are away of these, and explain what they should do if the problem arises.
17 20 Benton Pahlka
* Wish the previous shifter a safe drive home.
18 20 Benton Pahlka
19 12 Benton Pahlka
h2. Where to go for help
20 13 Benton Pahlka
21 16 Benton Pahlka
* "MINOS Shifter Guide Number 1": 
22 14 Benton Pahlka
23 16 Benton Pahlka
* "MINOS Shifter Guide Number 2":
24 13 Benton Pahlka
25 19 Benton Pahlka
* "The Online Monitoring Manual":
26 12 Benton Pahlka
27 19 Benton Pahlka
* "The Online Monitoring Gallery": 
28 19 Benton Pahlka
29 25 Benton Pahlka
* "Who else is taking shifts?":
30 25 Benton Pahlka
31 17 Benton Pahlka
h2. Shifter's ToDo List
32 11 Benton Pahlka
33 18 Benton Pahlka
* ensure the highest uptime of both Far and Near detectors
34 18 Benton Pahlka
* diagnose and fix problems quickly and efficiently
35 18 Benton Pahlka
* alert the system experts and work with them in case of problems
36 18 Benton Pahlka
* perform regular inspections of the data taken
37 24 Benton Pahlka
* monitor detector systems and environment conditions 
38 1 Benton Pahlka
* Regularly check DAQ, DCS status webpages
39 25 Benton Pahlka
* Spend time looking at the real time events using the event display
40 1 Benton Pahlka
* READ the previous CRL entries entered in the last 24 hours
41 1 Benton Pahlka
* RECORD anything anomalous in the CRL
42 25 Benton Pahlka
* Enter new problems into the JIRA issue tracking system
43 25 Benton Pahlka
* fill out %{color:red}shifter's checklists%
44 10 Benton Pahlka
45 10 Benton Pahlka
46 25 Benton Pahlka
h2. %{color:red}Shifter's Checklist Forms%
47 19 Benton Pahlka
48 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.
49 10 Benton Pahlka
50 10 Benton Pahlka
* Start_Shift 
51 19 Benton Pahlka
* DCSChecklist_Near
52 19 Benton Pahlka
* DCSChecklist_Far
53 1 Benton Pahlka
* OMCheckListNear
54 19 Benton Pahlka
* OMCheckListFar
55 1 Benton Pahlka
* Beam Summary
56 4 Benton Pahlka
* End_Shift  
57 5 Benton Pahlka
58 5 Benton Pahlka
h2. Please click "Update" or "Latest" (or "Current") on NuMI elog before inserting plots
59 4 Benton Pahlka
60 2 Benton Pahlka
61 2 Benton Pahlka
h2. Job List
62 19 Benton Pahlka
63 7 Phil Adamson
64 2 Benton Pahlka
65 2 Benton Pahlka
* The Far Detector needs to be notified of beam downtime as follows.  
66 2 Benton Pahlka
If the beam will be down for long enough from 07:30-17:30, please notify the mine crew.
67 2 Benton Pahlka
** If there is downtime of at least half an hour notify Soudan.
68 2 Benton Pahlka
** If you learn of an all-day shutdown coming in the near future, inform the Run Coordinator and Soudan.
69 9 Arthur Kreymer
70 9 Arthur Kreymer
* Please stop and restart OM Gui at the beginning of your shift, it leaks memory.
71 1 Benton Pahlka
72 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. 
73 9 Arthur Kreymer
** When the MINERvA shifter completes their ND OM checklist and shuts down their monitoring window it closes our connection.
74 9 Arthur Kreymer
75 1 Benton Pahlka
* 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]]
76 1 Benton Pahlka
77 22 Benton Pahlka
78 22 Benton Pahlka
* Check for good beam data logging at This plot is updated daily.  Check reference plots at "BEAMDATA":
79 1 Benton Pahlka
80 1 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, 
81 3 Benton Pahlka
82 1 Benton Pahlka
* The Minerva Control Room Logbook is at
83 1 Benton Pahlka
84 22 Benton Pahlka
* 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. 
85 22 Benton Pahlka
** If Firefox starts giving errors, then restart it.
86 1 Benton Pahlka
** 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.
87 9 Arthur Kreymer
88 22 Benton Pahlka
89 1 Benton Pahlka
90 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).
91 1 Benton Pahlka
92 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.
93 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.
94 1 Benton Pahlka
95 9 Arthur Kreymer
* 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.
96 9 Arthur Kreymer
97 1 Benton Pahlka
* 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.
98 1 Benton Pahlka
** 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.
99 1 Benton Pahlka
100 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|].
101 1 Benton Pahlka
102 22 Benton Pahlka
103 1 Benton Pahlka
104 1 Benton Pahlka
* Answering the telephone
105 1 Benton Pahlka
** Please let people know where they've called and who you are! E.g.
106 1 Benton Pahlka
** "MINOS Control Room, this is Fred Jones" would suffice.
107 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.
108 1 Benton Pahlka
109 6 Benton Pahlka
* Put a note in the logbook when you call experts or the run coordinator, at least the first time in a thread.
110 6 Benton Pahlka
111 6 Benton Pahlka
112 6 Benton Pahlka
h2. Swing and Owl shifts are no longer covered by Minerva
113 6 Benton Pahlka
114 1 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:
115 6 Benton Pahlka
116 6 Benton Pahlka
The MINOS shifters should arrive at the control room at the start of their shifts, and should:
117 6 Benton Pahlka
118 6 Benton Pahlka
* Deal with any problems they find
119 22 Benton Pahlka
* Go through the checklists with the previous MINOS shifters
120 6 Benton Pahlka
* Bring themselves up-to-date on any outstanding issues or problems likely to occur during the shift. 
121 6 Benton Pahlka
122 6 Benton Pahlka
123 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.
124 6 Benton Pahlka
125 6 Benton Pahlka
The MINOS on-call shifter should make a logbook entry from home any time they are called. They should log:
126 6 Benton Pahlka
* What caused the call to be made
127 6 Benton Pahlka
* What action they took
128 6 Benton Pahlka
* Any action they told the Minerva shifter to take
129 6 Benton Pahlka
* Any phonecalls with MINOS experts they made or received.
130 6 Benton Pahlka
131 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.
132 1 Benton Pahlka
133 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.