/
Noisy topology:  (1) coherent Noisy topology:  (1) coherent

Noisy topology: (1) coherent - PowerPoint Presentation

ginocrossed
ginocrossed . @ginocrossed
Follow
345 views
Uploaded On 2020-06-30

Noisy topology: (1) coherent - PPT Presentation

Spikes in trigger rate Periodic With B ON in 2008 Without B on during MWGR18 Sporadic MWGR 19 Strip noise profile 6 may 22 April REASON HV problem in RB1 out sect 12 Noisy topology ID: 790054

noisy noise amp data noise noisy data amp run strips 83081 coherent rb4 rb3 monitor mwgr test chambers planned

Share:

Link:

Embed:

Download Presentation from below link

Download The PPT/PDF document "Noisy topology: (1) coherent" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Noisy topology: (1)coherent

Spikes in trigger rate

Periodic:

With B ON in 2008

Without B on during MWGR18

Sporadic

Slide2

MWGR 19

Strip noise profile

6 may

22 April

REASON: HV problem in RB1 out sect 12

Noisy topology

: (

2)

coherent

High rate:

constant like during MWGR19 or in 2008 because of DT HV problem in one sector)

Slide3

Run history (MWGR 18)

Done by Seungen

Noisy

OK

No data

Noisy topology: (3) non coherent (?)

Slide4

W+2 RUN 83079 - 83081

S5

83079

83081

TH = 230 mV to all TH changed on some chambers

Slide5

S5 @ RUN 83081

LV = off

Noisy in the some

channels

in:

RB4 - & RB3- back

RB4 + & RB 3 + back

FORW OK

RB4 16 strips x

feb

RB3 14 strips x

feb

These SIGNAL CABLES are near each only into the LB

Slide6

Sect 6 @ RUN 83081

Forw

OK

LV ON Noisy in some channels

RB4- & RB3- backRB4+ & RB3+ back

Slide7

S5 @ RUN 83081

Occupancy

vs

time

Slide8

What was done and what has to be done

Coherent

Noise:

Hardware interventions: a lot actions done. Other tests will be done this week or when someone has

other idea..(DT cables) From data point of view:

periodic. It was already studied.

Sporadic: we have 6 months of data and monitor on line

Silvia is taking care of the monitor data.

Seungen and (Salvatore ?) is taking care of the data

Noisy chamber/strips (have to be done):

Map

of average

noise

at

different FEB threshold and different applied voltages.

Map

of dead strips and noisy strips

Slide9

Mean average noise

vs

TH

Slide10

Planning for data taking (this week)Day

ItemWheels/disks

Who (respons.)

With What

MonHard intervention HV-LV barrel & endcapAllAllTues

LV system

All

Pigi

CCU

shielding

W-2

Marcin

LV CAEN Firw1 tower -1 farGiovanni +

Wed

Noise

studies

Few

chs

on W?

Pigi

Monit

. on line

Thurs

MWGR (?)

Barrel +

endcap

Noise

LV (cont.)

Few chambers on W?

Pigi

Monitor on line +

Fri

Connectivity test

Disk -1/-2

Filip

XDAQ

Noise test:

Turbine OFF

Read out test

1

Wheels

(?)

marcin

MINIDAQ

Slide11

MWGR is planned for Monday and Tuesday. We can decide to not go in.

Noise map for barrel and

endcap

with MiniDAQ

& random trigger with Monitor online However

No date for missing (few) chambers in

endcap

TTU commissioning can not be done. It can be planned for the week after (25 of May).

in principle the noise should be studied in // with the efficiency. For the chamber performance we need DT or with TTU

(when and if will be ready). It can be planned for June during CRUZET1 or between CRUZET1 and CRUZET2.

Data taking (coming

Weeks

)