vtx run11 - indico2.riken.jp

VTX RUN11

15th Jul 2011 Rad Lab Meeting

1

Commissioning

Jan (pp) • Cooling chiller test (line, pressure…) • Turned on LV for all ladders and tested. • Optimized DAC setting values • FEM, DCM2 readout test • Turned on LV and HV for all ladders

Feb (pp)

• Threshold scan, timing scan • Test pulse could be seen through GTM+DCM2.

Mar (pp)

• Zero suppression code was implemented. • Test for multi-event buffer

Apr (pp/AuAu)

• Data taking in big partition

2

Threshold Scan and Timing Scan

• Hit rate is the ratio between “hit events” and “all events” for one readout chip.

• Noise rate was 0.01/8,192(pixel) = 10-6

Time in

Threshold (DAC)

hit

pix

els

/ e

ven

ts

• Ratio of hit pixels and events for one readout chip.

• Threshold scan had been done for all readout chips.

3

Detector Dead Area

Stripixel dead area fraction Pixel dead area map

Central arm acceptance

B0 (~0%) and B1 (~3%) in CA B2 (~1%) and B3 (~1%) in CA

4

Put in WEDGE between SAMTEC Conector and Big Wheel

SAMTEC connector

SPIRO board

Big wheel

WEDGE

8

Extender Bus

HIROSE connector

clamp

Clamp for HIROSE Connector

9

Beginning of 200 GeV Au Run

10

After 1st Repair(May 11)

11

After 2nd Repair(May 18)

12

After 3rd Repair (Jun 1)

13

Primary Z-Vertex vs BBC Z (Mean Position)

14

Performance NhitSVX vs BbcCharge

15

Nh

itP

ixel

(B0

)

Nh

itP

ixel

(B1

)

Nh

itSt

rip

(B2

)

Nh

itSt

rip

(B3

)

Bbc Charge

Bbc Charge

Bbc Charge

Bbc Charge

• Cut Condition – Run 344999

(AuAu200GeV)

– Cut

• |Zbbc|<5cm

• Trig= BBC>1hit(MB)

– Hot Channels are removed in pixel.

• Hot channels are still included in strip.

• Clear correlation can be seen.

Zbbc

Stripixel Performance

16

Figures from Akitomo ENOKIZONO

Charge correlation between X-U strip In Au+Au 200GeV

ADC from Clusters in Stripixel

MIP peak ~ 90

Clear MIP peak can be seen

Event Display (200 GeV AuAu)

Online DST Production

• Daily production (Automatic script) • For data QA and detector QA

• Create hot and dead channel map for pixel and stripixel. • Pixel 2D hit map : http://logbook.phenix.bnl.gov/vtx/svxpixel/

• DST were made for first and last 5 segments in a run. • Each DST has 5,000 events

• DST with PHCentral track (CompactCNT)

• Only peripheral events within |z| < 5 cm • Can be used for alignment. • All events for 4 runs (348283, 348455 , 349044, 349598)

• For VTX QA on muon production

• Hot and dead map for pixel and stripixel. • Event by event status for checking hardware status. • 2D hit map • ADC for each channel

18

http://logbook.phenix.bnl.gov/vtx/svxpixel/

http://logbook.phenix.bnl.gov/vtx/svxpixel/

• /common/s7/phnxreco/run11_autovtx_online/ – run_0000340000_0000341000 – p+p – run_0000346000_0000347000 – Au+Au 200GeV (346977 zeroF) – run_0000347000_0000348000 – Au+Au 200GeV

• /common/s8/phnxreco/run11_vtx_online/ – run_0000340000_0000341000 – p+p(~340515), Au+Au 19.6GeV – run_0000341000_0000342000 – Au+Au 19.6 – run_0000342000_0000343000 – Au+Au 19.6 – run_0000343000_0000344000 – Au+Au 200GeV

• /common/s9/phnxreco/run11_vtx_online/ – run_0000343000_0000344000 – Au+Au 200GeV – run_0000344000_0000345000 – Au+Au 200GeV

• /common/s9/phnxreco/run11_autovtx_online/ – run_0000344000_0000345000 – Au+Au 200GeV – run_0000345000_0000346000 – Au+Au 200GeV – run_0000346000_0000347000 – Au+Au 200GeV

• /common/s7/phnxreco/run11_svtx_online/ – Run_0000347000_0000348000 – Au+Au 200GeV – Run_0000348000_0000349000 – Au+Au 200GeV (compactCNT) – Run_0000349000_0000350000 – Au+Au 200GeV (compactCNT)

• /common/s10/phnxreco/run11_svtx_online/ – Run_0000349000_0000350000 – Au+Au 200GeV (compactCNT)

DST Online Production Summary

19

Luminosity Counting (200GeV AuAu)

• Au+Au 200GeV

– 1) Start from May 6, run 343058

– 2) First repair: May 11, run 343784

– 3) Second repair: May 18, run 344891 – 346478 (May 30)

• Good runs are chosen (marked_invalid<4)

• Active acceptance is ~50% of the pixel detector.

• Readout problem on strip :

The readout problem happen in last 10% for long run (Nevent > 10Mevents)

in last 20% for short run (Nevent < 10Mevents)

Effective events were roughly estimated (total * 50% * 15%)

The problem was fixed at run 345873 (May 26)

Nevents in period NscaledTrig (BBLL1>1) NscaledTrig (BBLL1 narrow)

1) 264,034,845 165,693,136 62,350,785

2) 606,722,607 380,737,261 344,104,423

3) 1,689,832,880 613,808,729 1,279,388,967

Total (nevent) 2,560,590,333 1,160,239,127 1,685,844,177

Effective 1,088,250,891 493,101,629 716,483,775 20

For DST Production

Need to check if • all the reconstruction codes work well with real data • all the variables are correctly stored in to DST including the error code.

SvxDecode RawHit

SvxReco Clustering

StandAloneReco Standalone

Tracking

GlobalTracking Vtx <-> Central

Arm

Reconstruction Chain

Update code, Hot/Dead

Update code, Alignment

Update Algorithm

Update Global Tracking

The basic codes exist. But currently not well checked with real data. We have a lot of things to be checked, modified and implemented.

• Codes … • Calibrations …

We, RIKEN group, discussed what we need to do. The list we concern are shown in the next page.

Concern Concern Concern Concern

21

People

o Baruch College • Stefan Bathe, Jason Bryslawskij, Mark Kanner

o BNL • Rachid Nouicer

o ISU • Alex Shaver, Alexandre Lebedev, M. Shimomura

o University of Colorado • Michael P. McCumber, Matt Wysocki

o JAEA • H. Sako, S.Sato

o ORNL • A. Enokizono

o RIKEN • Y. Akiba, R. Akimoto, H. Asano, T. Hachiya, M. Kurosawa

o SBU • Lei Ding, Xiaoyang Gong

22

Current Status

• Hot / Dead map Created hot and dead map by using several long runs. Need to create map for whole run and store them to database.

• Clustering

Updated clustering algorithm and created cluster correctly for pixel. Need to check clustering code for stripixel.

• Standalone Tracking

Tuned parameter for stand alone tracking.

• Global Tracking (Association with central arm track) Segment + Central arm track Cluster + Central arm track

• Alignment

Alignment using segment Alignment using global tracks

• Simulation

Need to update VTX geometry in PISA Production of simulation data 23

Analysis (rad) (rad)

(cm

)

(cm

)

24

DCA distribution with ideal geometry.

(Unit:radian)

(Un

it:c

m)

L0 L1 L2 L3 L4 L0 L9

Layer 0 Layer 1

/direct/phenix+subsys+vtx/asano/alignmet/sim/svxalignmentStandalone_idealgeo100k.root

25

Repair Plan in Summer

• VTX services will be disassembled ~22nd Jul. • VTX will be moved from IR around 25th Jul. • SPIRO rework, LDTB rework • Clamp for HIROSE connector (not need to disassemble any of pixel barrel)

3 weeks 1.5 week 2 weeks 1 week 1 week 7/25

QA test before disassemble • Pulse injection test • Sense voltage measurements • It will take 1 week

Disassemble VTX (Pixel / Stripixel) • Same test will be done • After the test, all SPIRO modules will

be dismounted. • Some bad LDTB boards will be

replaced and tested • It will take1 week

SPIRO will go to rework company • HIROSE clamp will be attached • One ladder will be replaced • Leakage current measurement

with cooling in a N2 gas • It will take 2 weeks

Start to mount SPIRO modules and QA test will be done. • QA test for repaired SPIRO will be

done before mounting • Same QA test will be done • It will take 1.5 weeks

Assemble 4 layers • Same QA test will be

done for 2 sub-layers before full assembly

• It will take 3 weeks • Survey will start

26

SPIRO Rework

• All modules will be send to BEST ( a company that specialized in PCB rework)

• Re-soldering test will be done before full repair work.

• Preheat the board and directly solder the pins by hand.

• Company person says they can complete the work in 2 weeks.

27

Stripixel Repair

• Replace 6+2 bad LDTB boards. • 6 will be available for replacement

• New 20 LDTBs will be fabricated additionally

• Parts and PCB have been ordered • Test all LDTB boards

• One bad ladder will be investigated

• If necessary, replace it with spare ladder.

28

Back Up Slides

29

100)(825632

_cov__

HalfLadderchipsrowcol

pixelsedreofnumberrecovered ratio = (%)

History of Repair Work (WEST NORTH)

History of repair work until 1st June recovered ratio Improved no way (Jumper) : cannot access jumper)

recovered ratio No Change

12 Bad

Access Day

WEST Grounding Cable WEDGE (SAMTEC) Clamp (HIROSE) gnd_sense

11st-May 18th-May 23th-May 1st-Jun 11st-May 18th-May 23th-May 1st-Jun 11st-May 18th-May 23th-May 1st-Jun 23rd-May 1st-Jun

B0-L0-N 0.614 0.614

B0-L1-N +2.5 % 0 % 0.623 0.614

B0-L2-N +3.2 % +1 % 0.598 0.622

B0-L3-N 0.633 0.641

B0-L4-N + 17% -94 % +94 % +94 % 0.618 0.641

B1-L0-N no way

(Jumper) +78 % +78 % -78 % 0.946 0.633

B1-L1-N no way 0.858 0.627

B1-L2-N +37 % no way no way 0.651 0.688

B1-L3-N no way

(Extender) no way 0 % 0.820 0.790

B1-L4-N +20% no way no way 0.636 0.658

B1-L5-N +84 % no way no way 0.761 0.650

B1-L6-N no way no way 0.692 0.709

B1-L7-N +7.2 % no way +0.3 % 0.786 0.782

B1-L8-N 0 % -80 % +74 % +80 % - 80 % 0.840 0.681

B1-L9-N no way

(Jumper) +94 % no way +94 % Power Off 0.754

30

History of Repair Work (WEST SOUTH)

WEST Grounding Cable WEDGE (SAMTEC) Clamp (HIROSE) gnd_sense


B0-L0-S +5.2 % -1.7 % 0.687 0.699

B0-L1-S no way 0.772 0.712

B0-L2-S +3.2 % 0.659 0.654

B0-L3-S -1.7 % -1.7 % 0.738 0.712

B0-L4-S 0.732 0.690

B1-L0-S 0 % +31 % 0.680 0.698

B1-L1-S +81 % no way 0.639 0.648

B1-L2-S +1 % no way 0.637 0.633

B1-L3-S +49 % no way 0.691 0.650

B1-L4-S +1 % 0.656 0.688

B1-L5-S no way no way 0.673 0.674

B1-L6-S -1 % 0.650 0.683

B1-L7-S +3.7 % no way +3.7 % 0.587 0.601

B1-L8-S 0.685 0.674

B1-L9-S no way 0.688 0.662

31

History of Repair Work (EAST NORTH)

EAST Grounding Cable WEDGE (SAMTEC) Clamp (HIROSE) gnd_sense


B0-L5-N +90.2 % +90.2 % 0.605 0.575

B0-L6-N 0 % 0 % 0 % 0.640 0.611

B0-L7-N 0.809 0.757

B0-L8-N 0 % +80 % 0.732 0.724

B0-L9-N 0.724 0.734

B1-L10-N no way

(Jumper) +47.8 % no way Power Off 0.729

B1-L11-N +7.4 % - 23 % 0 % already 0.723 0.638

B1-L12-N no way 0.648 0.662

B1-L13-N +11.1 % no way -7 % 0.632 0.718

B1-L14-N no way 0.661 0.678

B1-L15-N +25 % 0.645 0.699

B1-L16-N +2 % no way 0.669 0.681

B1-L17-N -1 % no way 0.732 0.746

B1-L18-N +2 % no way 0.809 0.820

B1-L19-N +1 % 0.513 0.513

B1-L15-N was applied only clamp. Two dead chips were recovered.

32

History of Repair Work (EAST SOUTH)

EAST Grounding Cable WEDGE (SAMTEC) Clamp (HIROSE) gnd_sense


B0-L5-S 0 % +80 % -80 % +0.4 % 1.098 0.951

B0-L6-S 0 % no way 0.855 0.851

B0-L7-S +56 % no way 0.815 0.832

B0-L8-S -3 % 0 % 0.724 0.705

B0-L9-S +11 % -2 % 0.674 0.705

B1-L10-S no way

(Jumper) 0 % no way 0.692 0.670

B1-L11-S +2.8 % +3 % 0.651 0.714

B1-L12-S no way 0.582 0.549

B1-L13-S 0.746 0.670

B1-L14-S +39 % -39 % no way no way 0.535 0.601

B1-L15-S +47 % +6 % no way 0.833 0.914

B1-L16-S no way

(Extender) no way no way 0.765 0.776

B1-L17-S 0.743 0.754

B1-L18-S +3.5 % no way 0 % 0.692 0.688

B1-L19-S -8 % 0% +10 % 0.752 0.735

33

SPIRO board

HV connector

LV connector

Detector Side

original LV cable

To LV rack 6”

New grounding cable

To pin header on extender

New Grounding Wire

jumper

The difficulty of connection at an extender side doesn’t change, but it become easy at SPIRO connector side.

35

Failure Mode of HIROSE Connector

• Basically, there had been a weak electrical connection around the edge of HIROSE connector for some ladders at QA test. When this happened, recovered it by reconnecting the connector • And this type of weak connection had happened during run. In this case, we recovered it by applying clamp. • At the edge of HIROSE connector, there are some important signal pins.

READOUT BUS

There are two pins to set DAC value of reference voltage for readout chip at the edge. At least, it is known that one half ladders has completely bad connection of these pins. To work this ladder, clamp had been applied for this ladder.

There are chip enable pins which are used to enable the readout of the corresponding chip. During the run, connection of these pins for one half ladders became weak. We fixed it by applying clamp.

HIR

OSE

HIR

OSE

36

HIROSE Connector

Another solution is put a spacer between connectors. 100um thickness of Kapton tape was used as spacer to apply pressure to connector pins. One half ladder has bad connection pin (DAC_REF_MID) and already apply Kapton tape. But during run, hit information were completely lost. So clamp was applied, then the response of this ladder was back. This ladder is working now. Thinking of structure of the connector, it seems that thick spacer is effective.

Insert spacer

Cross section of HIROSE connector

37

Clamp

Clamp which we used for repair Clamp which we used for repair

Most important thing is to apply pressure on HIROSE connector pins. To apply pressure on connector, we used clamp as shown in below picture.

38

Au(19.6) P+p No beam Au(200)

First repair Second repair

Run by Run Live Rate for Pixel Detector

B0 West B0 East B1 West B1 East

40

Recover : 10 %

Hit Map (RUN 347376 2011-06-05 21:01:08)

41

Recover : 10 %

Hit Map (RUN 347376 2011-06-05 21:01:08)

42

Recover : 3.3 %

Hit Map (RUN 347376 2011-06-05 21:01:08)

43

Recover : 2 %

Hit Map (RUN 347376 2011-06-05 21:01:08)

44

Beam Profile (Intersection Point with X-Z and Y-Z Plane)

Pixel

Stripixel

46

proj_y vs phi0

• Since beam center is not at (0,0), there is a clear correlation between phi and track projection at x=0

50

Beam position and shift

X

Y

vtxy = yoffset - xoffset*tan(phi)

Beam (xoffset,yoffset)

vtxy

vtxy: projection of track at y=0 vtxy = y0 – x0*(y1-y0)/(x1-x0) (x0,y0) hit at L0 (pixel) (x1,y1) hit at L1 (pixel)

51

Fit

• y = [0]*tan(x) + [1]

[0] x_offset; [1] y_offset 52

After correction

• Correction applied to East and West separately West: (0.23,0.055) East: (0.13,0.032) • Is remaining structure due to alignment of ladders?

53

Set up

-Phpythia p+p 100k events.

-RMS of x,y vertex ~ 250um (larger than actual beam size) -no beam offset -pisaeventfile :

/direct/phenix+subsys+vtx/asano/pisa/pisafile

-GEANT assumes ideal geometry of VTX, and misalignment is introduced in svxPISA.par. (i.e. misalignment is introduced on reconstruction code.) - Example macro to change svxPISA.par : /direct/phenix+subsys+vtx/asano/alignmet/sim/manualchangegeo.C

54

vtx run11 - indico2.riken.jp

Documents