Slide 1Slide 1

Peter LochUniversity of Arizona

Tucson, Arizona 85721

Run CoordinationSummary of the May 14, 2004 Run Coordinator

Meeting

CT-EC2 Run CT-EC2 Run Preparation Preparation MeetingMeetingMay 17, 2004May 17, 2004

Run coordinators for Run I (May-July):Run coordinators for Run I (May-July):

May 17 May 20 Peter Schacht

May 20 May 27Leonid Kurchaninov

May 27 June 2 Peter Krieger

June 2 June 9 Peter Schacht

June 9 June 15 No beam

June 15 June 28 Peter Loch

June 28 July 3 Mikhael Kazarinov

July 3 July 7 Peter Schacht

Slide 2Slide 2

Peter LochUniversity of Arizona

Tucson, Arizona 85721

Run CoordinationSummary of the May 14, 2004 Run Coordinator

Meeting

CT-EC2 Run CT-EC2 Run Preparation Preparation MeetingMeetingMay 17, 2004May 17, 2004

Run coordination issues (1):Run coordination issues (1):

Run program:Run program:

overall program outline -> this meeting!overall program outline -> this meeting!

program of the day (or shift, at least) on white board in counting house;program of the day (or shift, at least) on white board in counting house;

changes/adaption to beam conditions only by run coordinatorchanges/adaption to beam conditions only by run coordinator -> to be contacted by -> to be contacted by shift crew for approval at any time!shift crew for approval at any time!

progress and status traceable on web page linked from official LAr Testbeam web progress and status traceable on web page linked from official LAr Testbeam web page (maintained by run coordinator);page (maintained by run coordinator);

daily meetings (8:00 in NA meeting room) starting at the beginning of physics daily meetings (8:00 in NA meeting room) starting at the beginning of physics running;running;

at least one more status meeting before physics running;at least one more status meeting before physics running; Shifts:Shifts:

run coordinator present at every shift change, at least in the beginning;run coordinator present at every shift change, at least in the beginning;

instructions to shift crews by run coordinator only (may be delegated);instructions to shift crews by run coordinator only (may be delegated);

any change in shift schedule needs to be confirmed by run coordinator;any change in shift schedule needs to be confirmed by run coordinator;

checklist once/shift at fixed time to maintain checklist once/shift at fixed time to maintain ΔΔt = 8 hours – also at times of no beams!t = 8 hours – also at times of no beams!

experts and shifters only in the counting house, please!experts and shifters only in the counting house, please!

notify run coordinator of expert activties (e-mail/phone);notify run coordinator of expert activties (e-mail/phone);

Slide 3Slide 3

Peter LochUniversity of Arizona

Tucson, Arizona 85721

Run CoordinationSummary of the May 14, 2004 Run Coordinator

Meeting

CT-EC2 Run CT-EC2 Run Preparation Preparation MeetingMeetingMay 17, 2004May 17, 2004

Run coordination issues (2):Run coordination issues (2):

Experts:Experts:

coordinate interventions during physics running with run coordinator;coordinate interventions during physics running with run coordinator;

pre-plan as much as possible, schedule non-emergency work on beam-off days, etc.; pre-plan as much as possible, schedule non-emergency work on beam-off days, etc.;

please limit presence in the counting house and on the platform to when it’s really please limit presence in the counting house and on the platform to when it’s really needed!needed!

shift crews should know about experts working;shift crews should know about experts working;

Documentation:Documentation:

general logbook (shift log), additional beam settings log, electronics/DAQ log… ;general logbook (shift log), additional beam settings log, electronics/DAQ log… ;

run sheets (electronic and paper) and run summaries (histogram files publicly run sheets (electronic and paper) and run summaries (histogram files publicly readable, probably on prints);readable, probably on prints);

web application a la EMB for run sheets -> public read access through web;web application a la EMB for run sheets -> public read access through web;

program progress monitored by run coordinators (stats/program point), status program progress monitored by run coordinators (stats/program point), status available on the web (~daily updates);available on the web (~daily updates);

data quality monitored by run coordinator, estimated by shift crew -> good/bad run data quality monitored by run coordinator, estimated by shift crew -> good/bad run list on the web;list on the web;

beam profiles, magnet, coll, CEDAR, etc., settings logged for each beam change; beam profiles, magnet, coll, CEDAR, etc., settings logged for each beam change;

clearly indicate shift changes and other entries in general logbook with clearly indicate shift changes and other entries in general logbook with date/time/name stamp, please! date/time/name stamp, please!

Slide 4Slide 4

Peter LochUniversity of Arizona

Tucson, Arizona 85721

Run CoordinationSummary of the May 14, 2004 Run Coordinator

Meeting

CT-EC2 Run CT-EC2 Run Preparation Preparation MeetingMeetingMay 17, 2004May 17, 2004

Computing and data access:Computing and data access:

Monitoring:Monitoring:

monitoring/event display done on Arizona PC (pcfcal01) in counting house;monitoring/event display done on Arizona PC (pcfcal01) in counting house;

PC has only public shift account (h6run, no write access to source code) and restricted PC has only public shift account (h6run, no write access to source code) and restricted development and testing account (h6dev,Rob, Monika, myself); development and testing account (h6dev,Rob, Monika, myself);

monitoring starts automatically after n secs after DAQ start;monitoring starts automatically after n secs after DAQ start;

event display is user driven, i.e. shift crew can browse events independent of event display is user driven, i.e. shift crew can browse events independent of monitoring running;monitoring running;

Computing:Computing:

absolutely no public computing (web, e-mail, … ) in the counting houseabsolutely no public computing (web, e-mail, … ) in the counting house – all nodes in – all nodes in there have dedicated and important tasks!there have dedicated and important tasks!

offline data access through lxplus and CASTOR – most runs available to everybody offline data access through lxplus and CASTOR – most runs available to everybody within minutes, hopefully!within minutes, hopefully!

we will communicate advances in software (change of releases etc.) so people can we will communicate advances in software (change of releases etc.) so people can follow;follow;

contributions to monitoring (new histograms, algos…) are highly welcome, but need contributions to monitoring (new histograms, algos…) are highly welcome, but need to be evaluated (performance etc.) and integrated (code checking) by Rob, Monika, to be evaluated (performance etc.) and integrated (code checking) by Rob, Monika, myself…;myself…;

don’t forget to communicate your analyzises and publish your code!don’t forget to communicate your analyzises and publish your code!