log for RUN11

1

pedestalthreshold scan

• Data for threshold scan were taken by Nihashi-kun.

• data: 5data points for theshold 5, 10, 15, 20, 25mV

2

pedestal :: comparison with RUN10• almost channels are within 5% difference comparing with RUN10• 3ch are out of this range

– ch11: 7% up– ch27: 8% down– ch92: 12% up– see detatils

Ratio of pedestal : RUN11/RUN10

pedestal :: RUN11, RUN10

In RUN10, we did not exchange any FEM boards and daughter cards, but only exchange fuse on board#10(ch8-15). There is no relation.

3

2011/01/16

details

4

ch0 as reference

ch11 : 7% up

I just mention that the fluctuation of the Adc distribution dose not come from statistics.I think it due to systematics, ex. resolution of internal charge injector or ADC.

pedestal = 944.9[ch]

pedestal = 707.5[ch]

ADC [ch]

Q-scanDAC vs ADC

Q-scanDAC vs ADC

details

5

ch27 : 8% down

ch92: 12% up

pedestal = 829.5[ch]

pedestal = 779.4[ch]

The results seems fine. we will use these pedestal for RUN11.

ADC [ch]

ADC [ch]

Q-scanDAC vs ADC

Q-scanDAC vs ADC

trouble??

• ch27 has some strange behavior. – like lack of bit

• keep on eyes.

6

Q-scan taken on Jan 7thlaser #324219

online monitor • modified code (BbcMonDrow.C & BbcMon.C )

to ignore the laser hit rate of 0 for ch68, ch75, ch96, ch97

7PRDF for test located on

/common/s1/TestPRDFF/Run9pp500/EVENTDATA_P00-0000279947-0030.PRDFF

error message will not be shown even if the laser hit rate is 0 for ch68, 75, 96, 97 (North)

01/21

comparison of overflow1between RUN10 & RUN11

8

• typically lower than RUN10• this difference never affect BBLL1

over

flow

: RU

N11

– R

un10

[ch] in makebbmap.C

timing threshold [ns] for BBLL1 tmax[loop] = (pedestal[loop] - STEP)*tvc2ns[loop] - tzeroAdc[loop]; • pedestal -> overflow1• STEP -> 50[ch] • tvc2ns -> conversion factor ch to ns

to do for “time in”

• make pre-LUT including new overflow1– done. – /data2/phnxbb/USERS/phnxbb/Run11/BBLL1/

MakingTool/wrk/trig20110123– checked by CheckingTool and seems fine

9

HV gain curve

• scan– -100, -50, 0, +25, +50, +75V

• 1) lack of laser– ch68, 75, 96, 97 – (ID:: N5, N12, N33, N34)

• 2) +75 HV point fail– ch29 (ID:: S30)

• for 1) & 2), used gain curve taken in RUN1110

Trip of 1 HV Group (N-2)

• 2011/01/23 ~0:00

• HV_BB_N-2– N13,N18,N21,N24,N28, N31,

N32– (ch76, 81, 84, 87, 91, 94, 95)

• located in outer ring

• status 40Trip for voltage error

• could NOT recover it. need to access

11

Station Board ID Location Cable ID

0 Non Up N1

1 BBC1 Up N3

1 BBC1 Down N4

2 BBC3 Up N5

2 BBC3 Down N6

3 Non Up N7

3 Non Down N8

4 BBC5 Up S1

4 BBC5 Down S2

5 BBC6 Up S3

5 BBC6 Down S4

6 BBC7 Up S5

6 BBC7 Down S6

7 BBC8 Up S7

7 BBC8 Down S8

11 BBC2 Down　→　 UP N212

2011/01/26 IR access : switch BBC2(N-2) to station11-up

First collision• collision is provided in 1/24 early morning.• something wrong??

13

BBC LL1 delay 14 → 13

issue for LL1 delayAll figures show correlation of hit timing of BBC north and south. The difference of left and right is only selected trigger, BBCLL1 or ZDCLL1. We can’t simultaneously see collision event in BBC by BBCLL1 and ZDCLL1.

14

BBC LL1 delay = 13 : #327570 : fine delay of v124 = 170

BBC LL1 delay = 14 : #327569 : fine delay of v124 = 170

ArmHitTime North [ns]ArmHitTime North [ns]

ArmHitTime North [ns] ArmHitTime North [ns]

Arm

HitT

ime

Sou

th [n

s]

Arm

HitT

ime

Sou

th [n

s]Ar

mH

itTim

e S

outh

[ns]

Arm

HitT

ime

Sou

th [n

s]

triggered by BBCLL1

triggered y BBCLL1 triggered by ZDCLL1

triggered by ZDCLL1

collision events! at LL1 delay =13

In contrast, can’t see collision events at LL1 delay =14

but not here

can see collision events

Time in

• BBCLL1 and ZDCLL1 seem to be timed in correctly

15

BBC LL1 delay = 14 : #327745 : fine delay of v124 = 170 : GL1 Output delay = 5

ArmHitTime North [ns]ArmHitTime North [ns]

Arm

HitT

ime

Sou

th [n

s]

Arm

HitT

ime

Sou

th [n

s]

triggered by BBCLL1

triggered by ZDCLL1

01/25 ~2AM

lost MIP peak on ch40 in monhist• ch40(S41) : low gain ?? • Same HV in RUN10 is applied. : (HV-BB-S7: -1631.7[V] )

16

In #327745@ RUN11

• What’s happened!? • comparison with ch58(S59) : same HV group, opposite location

In #316499@ RUN10

In #316499@ RUN10

In #327745@ RUN11

ch40 ch40

ch58 ch58

raw Adc comparison with RUN10

• The shape of the BG is not same between RUN10 & RUN11, but I think it’s ok since collision type is different.

• We already know pC/MIP is fluctuate within 20%, But this case, we can’t see any MIP peak in RUN11.

• There is no difference of ch/DAC value between RUN10 and RUN11 taken by Q-scan. (taken in today). And laser gain curve looks fine.

• I hope to take laser data without beam condition and compare with data taken on Dec. I guess there are difference of peak position of laser in Adc distribution between before and after “beam in”...

• In addition, try to apply +50V higher HV. It corresponds to x1.2 higher gain.

17

Can’t see MIP peak in RUN11

red:: RUN11blue:: RUN10

red:: RUN11blue:: RUN10

ch58(S59)same HV group with ch40

ch40(S41)

Adc distribution in collision data

• The problem is that we can’t see MIP peak in ch40 at RUN11.– the Adc distribution at RUN10 is overwritten to compare.

• below looks fine– Raw signal of laser and thermal noise by oscilloscope – Q-scan and T-scan outputs and gain curve – We already confirmed that PMT gain is almost same with RUN10.

18

Can’t see MIP peak in RUN11

red:: RUN11blue:: RUN10

red:: RUN11blue:: RUN10

ch58(S59)same HV group with ch40

ch40(S41)

Adc [ch]Adc [ch]

Adc distribution for Laser (not collision data)

19

ch40

ch58(as reference)

• Adc distributions for laser signal are shown for ch40 and ch58.

• overwritten Adc distribution for 3 runs which setting of HV and laser intensity was not changed.

• The peaks on ch58 and other channels(except ch40) are stable. In contrast, the peaks for ch40 was often shifted lower side(red).

• After Low Voltage recycle and compete feed, the peak position come back “base” position.

Adc [ch]

Adc [ch]

NOT working fine…

• black : base• red : next run of “base”. not changed any

setting with “base”. • blue : after LV recycle and complete feed.

Adc distribution of Laser signal

Adc distribution of Laser signal

Tdc0 & Tdc1 timing for Laser (not collision data)

• Tdc0 & Tdc1 distributions for laser signal are shown for ch40 and ch58.• The peaks of laser timing for ch40 was also often shifted(red).

• We doubt that FEM for ch40 have something trouble. 20

ch40Tdc0

ch40Tdc1

ch58Tdc0

ch58Tdc1

Tdc [ch] Tdc [ch]

NOT working fine… NOT working fine…

summary & question• The problem is that we can’t the MIP peak on Adc distribution

of ch40 in collision data.

• Laser data for Adc, Tdc0 and Tdc1 of ch40 are often and suddenly shifted. – it was fixed after LV recycle and complete feed.

• We doubt that FEM is NOT working fine. And It lead the problem that we can’t see MIP peak.

• We have IR access in Wednesday morning. – still not find exact origin of the problem.

– What can we do to fix this problem at access??21

Laser signal (in collision data)

• Adc and Tdc1 distribution(ch40) of Laser taken by PPG(laser) trigger in collision data are shown.

• expected peak position is known, but can’t see on the position.• I guess the data of ch40 was always shifted at taking collision data. And it lead

the problem that we can’t see MIP peak.

• FEM have something problem. 22

ch40 Tdc1

ch40 Tdc1

expected peak position ~1100ch expected

peak position ~2200ch

threshold is working ??in #328755

23

Black :: threshold=15mV (tdc0)Red :: threshold =30mV (tdc1)pedestal = 802[ch]

Looks fine.

100V higher HV setting for S-7

• We can see correlation of HV value and gain. 24

BBCLL1, |Zvertex|<30, nHitPmt[0]<4, Tdc0<2500

laser event (ScaledTrig&0x40000000)

Blue : Normal HV settingRed : +100V higher

IR access : 2011/02/03 : issue(2)

• 2) replaced ADC daughter card of ch27(S28)– FEM board ID #12, ch3

25

afterreplacement

before replacement

ADC [ch]

• after replacement, ch27 looks fine for Q,T-scan and Laser event.

Q-scan

IR access : 2011/02/03 : issue(2)

• change pedestal value. • need to pedestal scan again for this ch.

26

IR access : 2011/02/03

• we exchanged input register of ch40

27

25 (24R9) 25

• After IR access. (No bema condition), we took laser, T&Q-scan data and it looks fine.

• But at the collision data taking, the gain of ch40 dropped… I mean problem is still on (can’t see MIP peak).

gain for ch40

28Time (2/6)

Adc

– pe

dest

al [c

h] :

Lase

r sig

nal

beam

on

• This plot shows the mean position of laser signal for ch40 and ch43 as a function of time

• Gain of ch40 is unstable.– the gain is drop off when

beam is injected. – In addition, gain is

getting up after beam lost. • 15% up for 30minites

beam

on

2011/02/06

ch43

ch40

30 minutes

gain at collision• we found gain of ch40 is extremely and suddenly drop off when both blue and yellow beam

is injected. • Plots show ADC distribution of laser signal continuously taking data during beam injection.

29

ch40ADC (Laser signal)

pede

stal

2011/02/06

growing up

Adc[ch]

taking laser data continuously

both peaks are signal of laser.

summary

• We found the problem appear at collision data.

• But we can’t decouple the source of problem, whether PMT or FEM.

• If the problem is due to FEM, we have possibilities to be able to fix at next IR access

• Can you explain this phenomenon by FEM problem??

30

modify injection rate of internal charge injector

• phnxrc@phoncs• /export/software/oncs/online_configuration/GTM/

– GTM.BB.1kHz_INITQFA• START: # Start of schedular code• C;BRANCH # init once,• Ax78 # then do nothing for 78x120x106ns,

– injected 1./(78 x 120clock x 106ns) ~ 1000Hz

• B;RESET # then fire test pulse and return to A

– need to compile to make GTM.BB.1kHz_INITQFA.gtm

• modified “BBC_Qscan.csh” • BBC_Qscan_1kHz.csh

– # GTM setup– set gtmfile = GTM.BB.1kHz_INITQFA.gtm– set gtmsect = "GTM.BB" 31

Q-scan output

• There is no difference between– Red: 1KHz Q-scan with beam (collision rate : order ~10KHz)– Blue: 1kHz Q-scan without beam– Black: 78Hz Q-scan without beam

32Adc[ch]

2011/02/08

plan for IR access (2/9)

• only 2 hours• 1) measure hit rate dependence by using pulse generator to

check FEM• 2) re-connect signal cable of ch40 to unused channel of ZDC

FEM

• We did not work in IR.• We will do test of cable swap after end of p+p run.• High hit rate test will be done at next IR access (2/16)

• decide to do “mask” of BBLL1 for ch4033

2011/02/08

34

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

• HV_BB_S-1 -1644.4• HV_BB_S-2 -1901.6• HV_BB_S-3 -1690.3• HV_BB_S-4 -2134.3• HV_BB_S-5 -2019.1• HV_BB_S-6 -1522.0• HV_BB_S-7 -1636.8• HV_BB_S-8 -1940.8

• HV_BB_N-1 -1598.1• HV_BB_N-2 -2380.4• HV_BB_N-3 -1707.2• HV_BB_N-4 -1856.1• HV_BB_N-5 -1522.8• HV_BB_N-6 -2263.5• HV_BB_N-7 -1899.2• HV_BB_N-8 -1680.0•The operational HV was calculated by using pC/MIP obtained from #329639

•S3,S7,N3,N7(inner) are applied 30pC/MIP HV, others are applied 40pC/MIP HV. •Valid 2011/02/07 04:35~, #329939~

•ke

ep in

eye

s fo

r MIP

of t

hese

cha

nnel

•#3

2993

9 : n

ew H

V se

tting

35

ch25S26HV-S3

ch51S52HV-S7

ch58S59HV-S7

ch83N20HV-N3

ch90N27HV-N3

ch115N52HV-N7

MIP for ch40

• Red : +100V higher• Blue : +150V higher• OK, we can see MIP peak in ch40

36

SubSystemControl.plについて• 実体は↓にある– /export/software/oncs/R11.0.6/install/

Linux.i686.3.2.3-sl5.3.0/bin

• /home/phoncs/hv_stuff/hvcontrol_BB– quick_init の部分に書かれている HVの値を変更

37

38

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

• HV_BB_S-1 -1656.7• HV_BB_S-2 -1932.5• HV_BB_S-3 -1716.5• HV_BB_S-4 -2153.9• HV_BB_S-5 -2059.3• HV_BB_S-6 -1485.6• HV_BB_S-7 -1665.4• HV_BB_S-8 -1975.8

• HV_BB_N-1 -1615.2• HV_BB_N-2 -2417.9• HV_BB_N-3 -1734.2• HV_BB_N-4 -1886.0• HV_BB_N-5 -1535.5• HV_BB_N-6 -2283.5• HV_BB_N-7 -1925.6• HV_BB_N-8 -1704.5•The operational HV was calculated by using pC/MIP obtained from #329939

•S3,S7,N3,N7(inner) are applied 30pC/MIP HV, others are applied 40pC/MIP HV. •Valid 2011/02/10 04:45~, #330555 (calibration)

comparing ch/MIP • measured ch/MIP value is obtained from #330557• within 10% difference between expected and measured

39

Red: measured #330557 , Blue : expected

deviation (red – blue)/blue

ch/M

IP [c

h]

PMT ID

PMT ID

Dev

iatio

n

summary for physics• applied new optimized HV (done)

– #330555~ • LUT update (done)

– used run #330557• update of constants of online monitor (done)• mask for ch40 (done)

• ***PHYSICS ON*** starting, 2/12 12:30PM~

• need to update DB• need to update some plots in online monitor

– please see Chirs’ mail

40

2011/2/12