MICE Shifter Guides » History » Revision 22

Revision 21 (Boyd, Steven, 24 June 2015 08:17) → Revision 22/70 (Boyd, Steven, 24 June 2015 10:47)

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": 
 * [[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": 

 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":Shifter Elog Guide.pdf 

 h2. How to launch and work with the Run Control 

 "Using the Run Control GUI [2015]": 

 h2. Shifter checklist : How to start a run 

 Shifter checklist to start a MICE run - attachment:Shifter_Checklist.pdf 

 h2. Where to find the CDB Viewer 

 The CDB Viewer can be found at 

 h2. Shifter Target Training and what to do when.... 

 "The RATS daemon crashes": 
 "A BPS error is encountered": 

 h2. What if one of the MICE thin clients crashes? 

 Sometimes one the thin clients can crash like this 

 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