1 Operations Overview L. Coney UC Riverside MICE CM32 – Glasgow – June 2012

2 Operations  New developments in Operations  Shifter training instituted  Review of May run – from Ops perspective  Operations Needs

3 Developments in Operations  Standard Operations now includes:  PPS  New target controller & user interface  Beam bump in ISIS  change to 2V loss limit again  Simplified Ops procedures  Single key exchange with ISIS  Start-up 30 min; shut-down 20 min  MICE controls access to MICE Hall  C&M – see Pierrick’s talk  DAQ – see Yordan’s talk  Online Reconstruction  completed changeover to MAUS  Infrastructure

4 PPS  Smoothly operated – MICE personnel learning to use system as designed  ISIS requested dedicated Controlled Access sign-in record  now have book in MLCR  Record of both controlled access and completed Hall searches  No accidental Hall search drops during May Run  Must maintain this record for running in 2013!  Future:  How operations procedures affected by addition of SC magnets in Hall?  Need assess impact and decide on best practice procedures – requires assistance from experts

5 Target  All safeguards & interlocks in place  Integrated into ISIS BPS system  Single fortress lock key exchange  Automatic consistency checks done by Target system allows us to let go of “Target Calibration”  Now reading out ISIS beam position*  Future:  Still need agreement between ISIS definition of beam loss and MICE definition of beam loss  ISIS requires new activation run with beam bump implemented

6 Online Reconstruction Plots  Names: imagetof_hit_x, imagetof_hit_y, imagetof_pmt10, imagetof_sp_x  Shifter has no idea what to choose or what it shows  

7 Online Reconstruction Plots  Names: imagetof_hit_x, imagetof_hit_y, imagetof_pmt10, imagetof_sp_x  Shifter has no idea what to choose or what it shows  Need to make the entire system more user-friendly 

8 Online Reconstruction Plots  Names: imagetof_hit_x, imagetof_hit_y, imagetof_pmt10, imagetof_sp_x, ckov plot is imageTOF_B  Shifter has no idea what to choose or what it shows  Need to make the entire system more user-friendly  We are aware of this and are working on it

9 Online Reconstruction  Good news – lots of progress made – ALL MAUS NOW!  Milestones:  Visualization – NOT DONE – primary busy on other work  Reco plots to webserver – DONE  thanks to Chris R and Matt R  Prototype Tracker Online Plots – DONE  worked great for single station run – thanks to Edward S.  Prototype KL Online Plots – NOT DONE  Originally aimed at May EMR run – however, EMR delayed, KL not in beam – reduced priority  Software On-Call position worked well during running – my congratulations to the Software Group!  Future: More to be done – we have a good start  Need tweak current plots – what we have, labels, descriptions, need better documentation (is recognized – takes time)  Want get Tracker plots on web  Want auto-recognize new run  Need example for those wanting to implement new plots

10 Infrastructure  New procedures are documented  Documentation is up-to-date  Good progress made – Matt Robinson (Sheffield) working very hard for us  Milestones:  Computing access – NOT done – need David C.  MLCR backups – DONE – Matt installed NAS drive – backups started  New OS installed – NEARLY COMPLETE  Systematically switching machines  Automatic update mechanism decided upon  More:  New portable opi machine (C&M user interface) – used to commission new DL tracker controls system in Hall  Set up onrec test machine in PPD – for pre-MLCR testing of online reco code  Installed miceraid4/5 on micenet  Adding capability to onrec machines  Setting up new DHCP server for micenet  Assessment of security in progress – sysadmin, head of Software & Computing, head of Online Group  More webcams installed; new/better phone in MLCR

11 MICE Shifter Training  At last CM  clear that improvements to shifter training were needed  Systematic, universal, consistent, and with good coverage for all shifter responsibilities  Record of training  New shifter training regime developed for and implemented during May Run

12 MICE Shifter Training May 2012

13 Official Shifter Training  Overview & introduction – given by MOM  Introduces responsibilities and role of Shifters  Notification of safety training requirements  Description of shifter duties  Practical training  Training not real until actually start working with the equipment  Each shifter-in-training has list of tasks they must learn how to complete  Specific individuals are certified to train shifters on systems  Final practical test  Shifter & Lead Shifter now meaningful titles  Not certified to take shift unless have completed this process  Future:  Determine training lifetime and refresher course procedure  How accommodate new equipment

14 Shifter Practical Training  Task  When trained  Who trained

15 Shifter Training Practicals  PPS  Macwaters, Coney, Blackmore, Nebrensky  Target  Smith, Overton, any BLOC  DS & Beamline  Any BLOC  C&M  Hanlet, Coney  DAQ  Karadzhov, Adey, Lead Shifter, Coney  Online Monitoring & Reconstruction  Karadzhov, Rogers, Coney  Datamover  Nebrensky, previously trained shifter

16 Review of May Run  Overall very successful  Congratulations to Tracker Team led by David Adey  Preparation in advance went well  Pre-run to-do list very useful for Hall preparation  Micemine Run Plan extremely useful  Experimenters provided information in advance (goals, schedule, beam configurations) – greatly helped operations

17 Review of May Run  New Shifter Training implemented  Successfully trained ~12 people  However, proved difficult & frustrating to train and run simultaneously  In future – training in advance of dedicated running  Requires personnel on site in advance of scheduled shift  MLCR too small  David, Edward S, Ed O, Alan, Paul, Tom, MOM (occasionally), BLOC (occasionally), Lead Shifter, Shifter, Shifter-in-Training, Occasional expert to address problem  Overflow area outside of MLCR – still not great  Need access to internet, equipment, other people  Need options – possibly use nearby space?  Remote MLCR?  Difficulties due to failing miceraid machines

18 Operations Analysis Group  Need better connection between these groups  Must be good reason to take data – want it analyzed and fed back into Operations  What learn from study? & how does it affect running the beamline?  CKOV analysis of December data  Pion contamination study – can we improve?  D1 scan – are we running at the ideal spot or not?  Beamline  What are “standard” beamline settings?  When do we use “standard” settings when not?  Need magic spreadsheet to be right – Or we need to not use it  Need training on magic spreadsheet – which use when? Difficult to guarantee appropriate beamline settings when doing on the fly in the MLCR  What proton absorber setting for each beam? Need table.  Study was done – but only for 3 settings

19 Operations Beamline  Need standardize settings  What are the currents for a beam?  Do we have the right ones? Matched beams or not?  How do we know?  All access to magic spreadsheet not necessarily good  It’s wrong – missing material – extra material  Does it handle material in the beam correctly?  How do we use it/them? Need change “magic” into “well- understood”  Glad to have Maria on board!

20 Step IV Operations  Continue:  Continue pre-run preparation  Further simplify running  Improve:  Automate procedures  fewer errors  Move from spreadsheet  only ConfigDB  Increase Online Reconstruction capabilities  Complete suite of detectors, Online analysis, Global reco  New equipment arriving  Need expertise – do we have a plan for support?  Timing – with ISIS RF for tracker, plan for RF stages  Modify procedures to include SC magnets and LH2 system  How staff multitude of shifts?

21 Operations Needs  Standardize & understand beamline settings  How cooling channel B fields affect Operations?  can we still control/monitor/operate the equipment?  Handover/knowledge retention between MOMs still not ideal  concerns regarding running in 2013  need permanent overarching position  Systematic understanding/overview of MICE safety systems  MOM position fleeting – lose track of what done

22 Conclusions  Operations going well – we continue to improve for each run  Feb CM Operations Needs:  New magic spreadsheet  New takeover of G4Beamline  Proper training  Documentation to be (remain) current  Documentation of changes to procedure   Much more to do – Step IV is rapidly approaching