Report ~first collision Kotaro Kijima 2010/01/25 Local lab meeting

2 Before the first collision

3 Check Internal Q-scan & T-scan Interlock system works fine –N2 air flow –Temperature HV –HV modules works –Noise shape seems fine for all PMTs. Laser data –All raw PMTs shape for laser signal are fine. –We took laser data by DAQ. Laser signal Adc tdc0tdc1 Q-scan T-scan Laser signal

4 After the first collision

5 Time in Change MTM timing by v124(ch7) –Fine Delay 132 → 116 (8ns) Time in at 12/28!! ch1: BBC GTM ch2: Discriminator output ~60ns ~68ns Change delay But, BBLL1 trigger has problem… Above figure is obtained by ZDCLL1 trigger

6 Online monitor Trigger is ZDCLL1 BBLL1 has problem. We can NOT take data with BBLL1 trigger –prescale of BBLL1 set to –LL1 expert is working Now, we are taking data with ZDCLL1 trigger. The missing plots on BBC monitor is due to BBCLL1. BBC is working fine!!

7 ADC distribution Some PMT channels have overflow –Same HV with Run9 –Fraction of overflow is less 0.1% (see attached file “ hvopt_ pdf ”) ch0 ch8

8 PmtGain (pC/MIP) Calibration have done (Run298917) –Same HV with RUN9 –Note: ZDCLL1 trigger events was used is typically 15% larger of Run9 –Large fluctuation Need new optimized HV of Run9 (Run10–Run9)/Run9 x100 ch0

9 Determination of HV Gain Curve was Obtained –For 6 settings -100, -50, 0, +25, +50, +75V Optimized HV was obtained –Inner ring :30pC/MIP HV –mid&outter: 40pC/MIP HV ADC distribution Gain curve Determined Optimized HV pC / MIP Used as normalization point for blue curve

10 Operational HV RUN10 for +- field (30, 40pC/MIP HV) HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N The operational HV was calculated by using pC/MIP obtained from # S3,S7,N3,N7(inner) are applied 30pC/MIP HV, others are applied 40pC/MIP HV. Valid 2009/12/31 06:45~, #299319~

11 Time table New HV applied 2009/12/31, 06:45~ #RUN299319~ LUT update 2010/01/01,20:36~ #RUN299480~ DB update 2010/01/01 Valid:2009/12/31, 06:45~ MTM timing turning 116  /01/02, 20:07~ #RUN299603~ MTM timing turning 132  /12/28, 09:59~ RUN298902~ BBLL1 fixed 2009/12/31 #RUN299317~ First Collision 2009/12/27 TIME Happy new year !!

12 Outputs #RUN working fine!! ch0 Q-scanT-scan

13 FEM board problem 2010/01/08 –Complete feed, LV recycle could not solve 2010/01/09 –IR access –exchange fuse on FEM board Fixed this problem

14 First PHYSICS Run –Start: 2010/01/10, 01:36:52~ –Fixed FEM problem –Everything FINE!

15 Back Up

16 GTM LL1 Trigger System 1clock 前のデータ 2clock 前のデータ 3clock 前のデータ (40-14)clock 前の データ 40clock 前のデータ 41clock 前のデータ : : : : Latency : 40beam clock (4.24  s) Level 1 delay : 14 beam clock Level1 sync clock 106ns LL1 GL1 GTM LL1 write to AMU MTM RHIC Beam clock FEM DCM

17 ADC distribution ch26 ch121 Channels which have relatively larger fraction of overflow Full range

18 Expected edge of HV Maximum #MIP is obtained from Run –Weighted mean of top 0.5% I guess, weighted mean does not work well for the ch which have overflow. ch8 red: pedestal Blue: weighted mean of top 0.5%

19 To do Need comments and suggestion!! –IF you need bbctree, location of tree is blow /direct/phenix+subsys+bbc/phnxbb/Y10DB/tmp/BbcCalib_29 (sorry for inconvenience…) * still have not applied new HV. to take data with new HV –Check MIP & overflow After solved BBLL1 problem, I will do calibration again by using BBLL1 triggered event to obtain LUT and DB constants. （ I might also do timing tuning of MTM ） 12/ 29

20 Status New HV is applied –MIP & overflow: within acceptable region LUT & DB is updated –Valid range DB: 2009/12/31, 06:45~ (#RUN299317~) LUT: 2010/01/01, 20:36~ (#RUN299480~) BBLL1 problem fixed Fine turning of MTM timing –116  112 (Fine Delay) 2010/01/04

21 Operational HV RUN10 for zero-field HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_S HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N HV_BB_N