MICE Shifter Guides » History » Version 46
Boyd, Steven, 25 July 2016 12:38
1 | 1 | Boyd, Steven | h1. MICE Shifter Guides |
---|---|---|---|
2 | |||
3 | * [[First shift]] guide |
||
4 | * [[UnofficialShifterGuide|The Unofficial Guide to being a Shifter]] |
||
5 | * [[ShifterRostering|Shifter scheduling]] |
||
6 | * [[Shifter Training]] |
||
7 | 40 | Boyd, Steven | * [[Shifter Rules and Checklists]] |
8 | 6 | Boyd, Steven | * "Where to find the CDB Viewer":http://cdb.mice.rl.ac.uk/cdbviewer/ |
9 | 21 | Boyd, Steven | * [[Suggestions to streamline/enhance shiftes|Shift Streamlining Suggestions]] |
10 | 45 | Boyd, Steven | * "Current Expert List (14/6/2016)":http://micewww.pp.rl.ac.uk/documents/178 |
11 | 11 | Boyd, Steven | |
12 | h1. What to do when something happens on shift |
||
13 | |||
14 | 1 | Boyd, Steven | Shifter information for various problems that may be encountered on shift |
15 | 12 | Boyd, Steven | |
16 | h2. Shifter Instructions or What to Do on Shift |
||
17 | |||
18 | "What to do on-shift : MICE Shifter Training":http://micewww.pp.rl.ac.uk/documents/144 |
||
19 | |||
20 | 22 | Boyd, Steven | As part of your shift you should keep a record of people present, the main parameters of the |
21 | run and incidents that occurred during the run. A good example is shown in the |
||
22 | |||
23 | 23 | Boyd, Steven | Guide to using the eLog for shift : attachment:Shifter_Elog_Guide.pdf |
24 | |||
25 | Note that in the example given in this guide, the shifters were explicitly asked to check the temperature differentials |
||
26 | in the conventional magnets every half hour. |
||
27 | 22 | Boyd, Steven | |
28 | 12 | Boyd, Steven | h2. How to launch and work with the Run Control |
29 | |||
30 | "Using the Run Control GUI [2015]":http://micewww.pp.rl.ac.uk/documents/135 |
||
31 | |||
32 | h2. Shifter checklist : How to start a run |
||
33 | |||
34 | 41 | Heidt, Christopher | [[Shifter checklist to start a MICE run]] |
35 | 12 | Boyd, Steven | |
36 | h2. Where to find the CDB Viewer |
||
37 | |||
38 | 42 | Boyd, Steven | The CDB Viewer can be found at http://heplnv152.pp.rl.ac.uk:4443/cdbviewer/ |
39 | 12 | Boyd, Steven | |
40 | 44 | Orestano, Domizia | h2. Target and Beamline: What to do when.... |
41 | 12 | Boyd, Steven | |
42 | "The RATS daemon crashes":http://micewww.pp.rl.ac.uk/projects/operations/wiki/ShifterTrainingTarget |
||
43 | "A BPS error is encountered":http://micewww.pp.rl.ac.uk/projects/operations/wiki/ShifterTrainingTarget |
||
44 | 32 | Nebrensky, Henry | [[BeamlineProcsEarthLeakTrip|... a conventional magnet trips off]] |
45 | 34 | Nebrensky, Henry | [[BeamlineProcsTargetFail|... the target throws an error]] |
46 | 36 | Nebrensky, Henry | ... beamline polarity sensors misbehave: [[BeamlineProcsTestPOMPOMs|check voltages]] (until the proper user guide is finished) |
47 | 37 | Nebrensky, Henry | [[BeamlineProcsDSThermalTrip|... Decay Solenoid PSU trips off]] |
48 | 13 | Boyd, Steven | |
49 | 46 | Boyd, Steven | h2. What to do when you are requested by the BLOC to reset one of the conventional magnets |
50 | |||
51 | * Press the Controls Menu desktop GUI |
||
52 | * under BeamLine Elements, select BeamLine Summary |
||
53 | * press the third option, control option on the right hand side of the Beamline summary GUI |
||
54 | * the Danfysik MPS 8000 - MICE Beamline Magnets window opens |
||
55 | * press the Reset option in the second box, control box of this window. |
||
56 | |||
57 | 13 | Boyd, Steven | h2. What if one of the MICE thin clients crashes? |
58 | |||
59 | 26 | Boyd, Steven | Very rarely one the thin clients can crash like this https://micewww.pp.rl.ac.uk/elog/Shift+summary/150623_043853/MICETHIN02_error_230615.JPG |
60 | 1 | Boyd, Steven | |
61 | 18 | Boyd, Steven | The current response to this is : |
62 | |||
63 | If the applications that had been running on the machine can just be opened elsewhere, then they should be, and an email |
||
64 | should be sent to the online expert (Paolo). If the process hasn't been released by the machine, and can't be run |
||
65 | in multiple instances (i.e. RunControl) then the SOC should be called, who will in turn probably call the online |
||
66 | expert. |
||
67 | 25 | Boyd, Steven | |
68 | h2. What if an error from the DataMover is reported from Run Control |
||
69 | |||
70 | If an error is reported via Run Control then the shifters don't NEED to do anything - they can |
||
71 | carry on with the next run; all that will happen is that the data distribution will be delayed. |
||
72 | |||
73 | Make an eLog entry, then wait until a suitable time when DAQ is stopped (e.g a shift change) and run the manual |
||
74 | script. If it still doesn't work, eLog the error and escalate to (for now) Henry. |
||
75 | 27 | Boyd, Steven | |
76 | 31 | Boyd, Steven | Instructions to run the datamover manually can be found in the Red Binder and in the latest version of "the datamover instructions":http://micewww.pp.rl.ac.uk/documents/10 |