MICE Shifter Guides » History » Version 31
Boyd, Steven, 25 June 2015 12:36
h1. MICE Shifter Guides
* [[First shift]] guide
* [[UnofficialShifterGuide|The Unofficial Guide to being a Shifter]]
* [[ShifterRostering|Shifter scheduling]]
* [[Shifter Training]]
* [[Shifter Rules]]
* "Where to find the CDB Viewer":http://cdb.mice.rl.ac.uk/cdbviewer/
* [[Suggestions to streamline/enhance shiftes|Shift Streamlining Suggestions]]
h1. What to do when something happens on shift
Shifter information for various problems that may be encountered on shift
h2. Shifter Instructions or What to Do on Shift
"What to do on-shift : MICE Shifter Training":http://micewww.pp.rl.ac.uk/documents/144
As part of your shift you should keep a record of people present, the main parameters of the
run and incidents that occurred during the run. A good example is shown in the
Guide to using the eLog for shift : attachment:Shifter_Elog_Guide.pdf
Note that in the example given in this guide, the shifters were explicitly asked to check the temperature differentials
in the conventional magnets every half hour.
h2. How to launch and work with the Run Control
"Using the Run Control GUI ":http://micewww.pp.rl.ac.uk/documents/135
h2. Shifter checklist : How to start a run
"Shifter checklist to start a MICE run":http://micewww.pp.rl.ac.uk/documents/136
h2. Where to find the CDB Viewer
The CDB Viewer can be found at http://cdb.mice.rl.ac.uk/cdbviewer/
h2. Shifter Target Training and what to do when....
"The RATS daemon crashes":http://micewww.pp.rl.ac.uk/projects/operations/wiki/ShifterTrainingTarget
"A BPS error is encountered":http://micewww.pp.rl.ac.uk/projects/operations/wiki/ShifterTrainingTarget
h2. What if one of the MICE thin clients crashes?
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
The current response to this is :
If the applications that had been running on the machine can just be opened elsewhere, then they should be, and an email
should be sent to the online expert (Paolo). If the process hasn't been released by the machine, and can't be run
in multiple instances (i.e. RunControl) then the SOC should be called, who will in turn probably call the online
h2. What if an error from the DataMover is reported from Run Control
If an error is reported via Run Control then the shifters don't NEED to do anything - they can
carry on with the next run; all that will happen is that the data distribution will be delayed.
Make an eLog entry, then wait until a suitable time when DAQ is stopped (e.g a shift change) and run the manual
script. If it still doesn't work, eLog the error and escalate to (for now) Henry.
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