380 likes | 505 Views
cosmic ray muons. reaction plane. Mike Leitch, LANL Run Coordinator Run7 Report PHENIX 2007 Collaboration Meeting Boulder, 11-13 July 2007. cosmics. Run7 Chronology. Originally hoped to start with Nov 1 st cool-down and PHENIX planned for:
E N D
cosmic ray muons reaction plane Mike Leitch, LANL Run Coordinator Run7 Report PHENIX 2007 Collaboration Meeting Boulder, 11-13 July 2007 PHENIX - MJL
cosmics Run7 Chronology • Originally hoped to start with Nov 1st cool-down and PHENIX planned for: • AuAu – 15 wks (1.1 nb-1), pp – 10 wks (32 pb-1) • Delayed by continuing resolution & meager FY06 level to match • But PHENIX started anyhow: • Cosmic rays starting Jan 9th • “Run7 is on” Feb 1st • Start of cool-down Feb 8th • Cryo problems Feb 24th • Rings cold & with beam Mar 13th • Start of Physics Mar 27th • End of Run7 Jun 26th • 13 wks of physics (Mar 27th – Jun 26th) PHENIX - MJL
Important Run7 Dates and Run Numbers • 3/27 "Start of physics" 1st run 227016 • 4/2 23:59 Change to BBCLL1(>1 tubes) 1st run after change 228040 for main MB trigger • 4/4 14:15 scaler update change 1st run after change 228040 from 5 to 30 seconds • 4/25 HBD West out 1st run after this 231210 (during maintenance day) • 5/11 20:18 last level-2 config change 1st run after 234416 (E/p > 0.35 instead of > 0.5) • 5/21 9:30 am "++" magnetic field 1st run after this started 235889 - 5/23 10:00 am • 5/23 10:00 go to "-+" magnet config 1st run after change 236133 (during maintenance day) • 6/4 14:22 fixed PC-E channels finally about 237717 • 6/6 5pm low-energy run last run before this 237831 - 6/7 4pm (after maintenance day) 1st run after it 238022 • 6/12 major DC LV repair after 238681 West-south sectors 6,7,8 • 6/12 12:05 am (west) converter run includes runs between 238682 - 6/14 8:00 am and 238854 (inclusive) run 238943 is after it is out • 6/26 11:00 end of run last run 240121 • 6/29 2:00 end of run party.... PHENIX - MJL
PHENIX Physics Goals for Run7 • Increase statistical & systematic precision of rare signals in AuAu, e.g. J/, jet correlations, etc • Increase reach in pT, especially with PID from new TOF-West detector (pT > 8 GeV/c) • Identified particle spectra • Identified leading particles in jets • Factor of two or more improvement in Reaction Plane resolution - valuable to many signals • v2 for J/, - new • electrons, hadrons – extended • Low-mass lepton pairs with the HBD simulation Submitted to PRL PHENIX - MJL
Four New Detector Subsystems for Run7 MPC-N RXNP TOF-W HBD PHENIX - MJL
MPC RXNP < cos 2(Fsouth - Fnorth ) > MPC BBC < cos 2(FA+B - Ftrue ) > RXN MPC BBC < cos 2(FA – FB ) > PHENIX Reaction Plane Measurements Now from MPC, RXNP & BBC Reaction Plane Detector Centrality PHENIX - MJL
TOF-West Particle Identification PHENIX - MJL
5.12 Billion Min-bias events 813 b-1 (~3.4 x Run4) PHENIX - MJL
The PHENIX Luminosity Story *Vertex eff slightly worse after “+-” “-+” magnetic field change (cause of lower vtx eff for last week than whole run) PHENIX - MJL
Effects of Stochastic Cooling at PHENIX beginning of store Improvement in integrated luminosity for PHENIX with Stochastic Cooling (SC) 16% end of store from blue beam from yellow beam PHENIX - MJL
Fraction of Time at Collision PHENIX - MJL
Luminosity/Day vs Day PHENIX - MJL
PHENIX Triggering & fast analysis for Run7 • Level-1 Triggering just Minimum-Bias (+UPC) • 5 kHz event rate through DAQ • only small fraction of integrated luminosity missed due to rates above the DAQ limit in the 1st ½ hour or so of stores • Level-2 filtering in ATP’s producing selected, parallel sample of enriched events for fast processing • J/ ; J/ ee; high-pT level-2 triggers • 10% of raw data size • sent to CCF in France via GRIDFTP • analyzed in France for fast results • 10% of min-bias events sent to Vanderbilt for fast analysis • check analysis/calibrations, prepare for full analysis pass • provide events needed for mixing in level-2 analysis • Counting house machines for fast HBD analysis PHENIX - MJL
PHENIX Data Acquisition (DAQ) • Present DAQ performance: • up to 5 khz event rate & 700 Mb/sec throughput • DAQ Advances: • level-2 code speedup • additional buffer box • fix SEB memory leaks • more compact HBD data format • etc PHENIX - MJL
(plot from Tom Throwe) PHENIX - MJL
cosmics PHENIX Shakedown/Cosmic Ray Running (Jan & Feb) • Need Cosmic Ray background measurement for W physics • Cosmic/W estimated to be 1/1 for p>=10 GeV, but estimate is unreliable – need measurement! • Also Cosmic ray in EMCal looks much like high-pT photon PHENIX - MJL
J/’s in AuAu Collisions at PHENIX PRL96, 012304 (2006) PRL98, 232301 (2007) Statistical & systematic precision of new Run7 AuAu data will improve this picture – But will also benefit enormously from new dAu data that can constrain the cold nuclear matter baseline accurately PHENIX - MJL
From Tony Frawley, heavy PWG, Jan 4th Expected Results for J/ flow from Run7 PHENIX - MJL
unlike-sign pairs like-sign pairs (randoms) thanks to Catherine Silvestre J/ for ~8% of present Run7 integrated luminosity (~16,000 J/ for present luminosity sum) PHENIX - MJL
J/ e+e- about 15% of level-2 data thanks to Ermias Atomssa & Raphael Granier de Cassagnac PHENIX - MJL
0’s & ‘s thanks to Justin Franz from about 16% of present data 0 extended range in pT PHENIX - MJL
signal electron Cherenkov blobs e- partner positron needed for rejection e+ qpair opening angle Hadron Blind Detector (HBD) • A “hadron-blind” detector to detect and track electrons near the vertex.” • Dalitz rejection via opening angle • Identify electrons in field free region • Veto signal electrons with partner • HBD: a novel detector concept: • windowless CF4 Cherenkov detector • 50 cm radiator length • CsI reflective photocathode • Triple GEM with pad readout • The HBD will improve our S/Bby a factor of ~100 Submitted to PRL PHENIX - MJL
West side of HBD taken out Apr 25th for repairs • HV trips with large stored energy damaged detector • Now being refurbished with new GEM’s & fixed HV • ½ of the East side of HBD still in Hadron Blind Detector (HBD) hadrons electrons PHENIX - MJL
PHENIX Issues & Failures • HV problems • Slow or dead servers • SA1 screen slow, or dead • Non-standard subsystem HV control – HBD, ToF-W, ToF-E • Unclear subsystem standing orders • LV problems • Connections or burned out LV modules • DAQ front end • HBD event size and zero suppression • DC large packets • MPC fiber split, muTr & EmCal new formats done • SEB memory leaks • Buffer Boxes • Confusion about Box7 (LVL-2) & its transfers • Weird transfer impact on DAQ speed when trigger rate high • Several disk failures • Event builder & ATP’s • Did not reach near 5khz event rate until last few weeks of run! • Only one expert, many changes • Will performance survive for Run8 and Run9?? • Trigger/level-2 configuration complicated – few know how to do it • Diagnostics weak for DAQ operator PHENIX - MJL
PHENIX Issues & Failures - 2 • muTr HV trips & dead channels (capacitor removal in progress) • Level-2 analysis slow starting; partly because of slow DAQ level-2 start caused by struggles to get DAQ to run fast • SA2 under utilized • Communication in English difficult for some young subsystem specialists and shifters • recommend one person in subsystem team be fluent in English • Never had a chance to start new mandatory shift assignment scheme because of run start uncertainties • HBD data size • Already implemented more compact format, but will (hopefully) have many more good channels next year (~24/6) • Drop to fewer than 12 time samples? • Reduce large tail in event size with light baffling? • More sophisticated zero-suppression scheme • Haggerty-less operation next year – a challenge to us all PHENIX - MJL
Other Issues • Water cooling • Availability of chiller & evaporator status to shift crews so they diagnose cooling problems quickly & call for help • Coupling of magnet and electronics cooling • Air conditioning • Humidity swings in IR, can they be minimized to alleviate HV problems? • Get all four air conditioners to run (most of the time) • Flammable gas detectors • Many recalibrations or head replacements • New technology that is stable at levels being monitored? • Fire Alarms & power shutdowns • HSSD smoke detectors? • Fix light bulb coupling to PHENIX power shutoff system • Magnet trips – CMI mostly • Access to MCR logbooks (readonly) for PHENIX shift crews • New xterm for acnlinxx access? • Communications between workers in IR and PHENIX control room for debugging problems quickly and efficiently (old radios not allowed)? • POTS with long cords or wireless phones? PHENIX - MJL
Rough Survey of PHENIX Problems in Last 2 weeks of Run7 HV trips 161 HBD,muTr,DC,PC server/MF 10 massive trips 9 Front end feed 60 muTr AMU & glink Back end EB,BB,RC 34 EB,BB SEB,Corba Oncs Cleanup Magnet trips 14 CMI Cooling Water,A/C 8 or more… Power Off Fire Alarms 3 HSSD smoke detectors & Light bulbs PHENIX - MJL
Concluding Remarks • Over 3 times Run4 luminosity (~813b/241b) PLUS new capabilities from new detectors • E.g. 3-4 times better Reaction plane resolution • Full /K/p PID up to 9 GeV/c • major advances in our physics should result • Analysis in progress already thanks to level-2 filtering & mature analysis model • HBD a very state-of-the-art detector, but lessons learned in Run7 should allow full operation in Run8 & beyond • Excellent stores when they could be delivered, but too many breakdowns • Stochastic cooling - a step towards the future • Low energy (9.2 GeV) running feasible PHENIX - MJL
Backup PHENIX - MJL
centrality selections are given by BBC charged multiplicity z-vertex selections by BBC [-40,40] cm [-30, -20] cm [-5,5] cm [20,30] cm total [~500] [500~1500] [1500~] RXN north charged mult. (a.u.) charged multiplicity in RXN (a.u.) RXN south charged mult. (a.u.) mid-central collisions < cos 2(Fsouth - Fnorth ) > Fnorth (rad) Fsouth (rad) PHENIX Reaction Plane Detector (RXNP) 200GeV Au+Au collisions RUN7 - 2007/Mar PHENIX - MJL
Luminosity fraction captured by PHENIX DAQ saturation in red • Fraction of luminosity for late April stores (at bottom) • 97.8% for 4.8 khz DAQ rate • for ½ hr turn-on time 0 min 32 min 16 min 21 min 18 min 26 min 6 min starts at 10 am Fri Apr 27th PHENIX - MJL
Average Improvement with SC: Improvement in integrated luminosity for PHENIX with Stochastic Cooling (SC) Store 8879 (no cooling) Store 8886 (cooling on) PHENIX - MJL
Differentiation of vertex into distinct peaks due to Stochastic Cooling T. Roser’s vertex shape ZDC vertex (ZDC Wide) BBC vertex (BBC no vertex cut) BBC vertex (BBC ±30 cm vertex cut) PHENIX - MJL
Data flow Input prdf flow Output plan A Output plan B HPSS To HPSS TB phenix Online filtered PRDF (21TB) srm/dcache 10 TB Offline filtered PRDF DST, 7 MB/s, srmcp srmcp ??? dccp srm/dcache @RCF bqs workers sps disk 4.1 TB cp srmcp Aggregation not done rftpexp DB snapshot, scp or bbftp ccphenix (database server) PHENIX - MJL
Vanderbilt Farm 1600 CPUs, 80 TBytes disk FDT FDT 45 MB/s 45 MB/s 45TB and 200 CPUs Available for Run7 Reconstruction RCFRHIC computing facility Reconstruction 200 jobs/cycle PRDFs nanoDSTs 18 hours/job 3 1 770 GBytesper cycle PRDFs Raw data files GridFTP to VU 30 MBytes/sec 2 nanoDSTs Reco output to RCFGridFTP 23 MB/sec Dedicated GridFTP ServerFirebird 4 4.4TB of buffer disk space PHENIX - MJL
HBD Status • We believe we have determined the main cause of the sparking problems with the both detectors: • Normal GEM spark would cause Lecroy HV to trip • Mesh also trips leaving large stored energy on filter capacitor • As GEM voltage goes to zero, large DV develops across gap between top GEM and mesh, ultimately resulting in a large spark • This spark induces sparks in other GEMs (massive trips) by propagation of scintillation light • There is however a danger in the “One source of all troubles” theory and we are still looking for more possible causes of the problems we had during the run from T.Hemmick PHENIX - MJL
Pock Marks from T.Hemmick • Human eye could see the holes. • Holes smaller than pock parks. • Pocks almost certainly from meshGEM PHENIX - MJL
EvB bufferbox Low Energy Running at PHENIX • 9.19 GeV/nucleon • PHENIX RXNP trigger • timed in at full energy • expect ~96% efficiency (compared to ~15% for BBC) • ZDC trigger should be very inefficient due to large Fermi motion wrt longitudinal momentum • Wednesday afternoon could run our DAQ with the “blue low-energy clock” • But Thursday morning, when beam was in the rings, we could not • Presumably due to glitches in the clock (associated with other clock events that were not there on Wednesday??) PHENIX - MJL