What have we done?for Run9

around first collision~2009/03/01

Kotaro Kijima

Masaya Nihashi

2

Time Table• After first collision, what we have done is

shown in this slides.

02/24#272063First collision

02/25AM9#272242(EVENTDATA)For HV decision

2/25 PM10IR AccessSwitch board ID16

2/2618:54~NEW HV applied

02/27AM6#272627(EVENTDATA)For LUT

02/2815:26~LUT Update

2009/01/21Received FEM#6from Chi

DATE

FEM board ID problem

BBLL1 Masked for 8ch (103-111) [2/25.16:xx ~ 2/26.9:50]

3

Board ID• FEM board #6 was repaired by Chi in Janualy. Th

en, the DIP switch was reset from “6” to “1” for the Test. But after the test, it was not switched back it…

• We found this problem around 2/24. • This problem affect BBCLL1 trigger too.• I would like to mention that the data is able to corr

ectly read if we don’t use “bbcEvent” class. • At 2/25 night, we access to IR with John Haggerty

and Jimmy, to switch back DIP switch to “6”.

• After that, we can see board ID “6” in PRDF!!

should be “6” , not “1”

in PRDF file

Fixed!

DIP switch

4

Operational HV for +- field

• At first of Run9, CM(+-) Magnetic field is operating.

• We calculated new operational group HV value for +- field as 30pC/MIP HV for inner ring.

• The gain curve was obtained by laser data. But then, magnetic field was not operated. So, we assume that gain curve (shape) dose not vary so much by magnetic field.

• To calculate operational group HV, we used pC/MIP obtained by run272242.

5

Comparison of pC/MIPexpected and measured

• We can calculated Expected pC/MIP value from gain curve when we will applied New group HV.

• #272627 was applied new HV.• It is consistent within 5% betwe

en expected and measured value.

• We decided to operate this new HV for Run9 +- field.

• You can see the monhisto of #272627 at

– http://www.hepl.hiroshima-u.ac.jp/phx/bnl/calibration/rundep/RUN9/CalibratorOut/PN/BbcCalib_272627/monhist_272627.pdf

(Mea

sure

d –

Exp

ecte

d) /

Exp

ecte

dpC

/MIP Red: Measured (#272627)

Blue: Expected

6

Operational HV for +- field(30, 40pC/MIP HV)

• HV_BB_S-1 -1634.2• HV_BB_S-2 -1885.1• HV_BB_S-3 -1667.1• HV_BB_S-4 -2123.4• HV_BB_S-5 -2004.3• HV_BB_S-6 -1462.4• HV_BB_S-7 -1637.1• HV_BB_S-8 -1951.7

• HV_BB_N-1 -1588.4• HV_BB_N-2 -2360.5• HV_BB_N-3 -1705.9• HV_BB_N-4 -1853.6• HV_BB_N-5 -1530.1• HV_BB_N-6 -2200.0• HV_BB_N-7 -1880.4• HV_BB_N-8 -1692.6

•The operational HV was calculated by using pC/MIP obtained from #272242

•S3,S7,N3,N7(inner) are applied 30pC/MIP HV, others are applied 40pC/MIP HV.

•Valid 2/26 18:54~, #272619[EVENTDATA]~

7

run272627

LUT ver.0 is used. applied NEW HV

Bbctree is located at/w11/BBC/Run9/calib/BbcCalib_272627

8

LUT version1 for +- field

• Making new LUT– Used #272627– Updated BbcCalib.config

• New HV value

– Bbc.offset: -0.57[cm]• Same as Run8

• Valid Range– 2009/02/28 15:26~

• Please see below about LUT version– http://www.hepl.hiroshima-u.ac.jp/phx/bnl/calibr

ation/DB/run9_LUT.html

Input: bbctree_272627.root

9

run272983

LUT ver.1 is used.Constant of online motor are also updated.It is seems like GOOD.

ONLY BBLL1 trigger is enabled.

So far latest run

10

summary

• What we have done is following– board ID problem was fixed– new HV for +- field was calculated and

applied– LUT was updated– constants of online monitor were also updated

• We will update DB soon.

11

12

time_reso vs pmtgain