November
27, 2012
Combined runs
APV25 + VMM1.
First look with the Event
Browser on October runs.
1
M. Byszewski, MM Weekly
2
November 27, 2012
Introduction
Event browser
M. Byszewski, MM Weekly
3
November 27, 2012
event browser
 Offline
Event Display
 Run statistics
 APV25
 VMM1 tracking (“BNL DAQ mini”)
 VMM1 trigger (“BNL FPGA eval board”)
 VMM1calibration


charge offset
TAC slope, offset
M. Byszewski, MM Weekly
4
November 27, 2012
mmdaq3-tb-Oct2012.log
"9000", "2012-Oct-30", "16:58:28.330706", "Physics", "20033", "combined run"
"9001", "2012-Oct-30", "17:30:24.833311", "Physics", "20030", "combined run"
"9002", "2012-Oct-30", "18:08:51.883479", "Physics", "20020", "combined run"
"9003", "2012-Oct-30", "18:35:42.611935", "Physics", "20054", "combined run int time =50ns, time at threshld"
"9004", "2012-Oct-30", "19:04:33.193084", "Physics", "20082", "combined run int time =100ns, time at threshld"
"9005", "2012-Oct-30", "19:27:53.756725", "Physics", "20023", "combined run int time =100ns, time at peak"
"9006", "2012-Oct-30", "20:14:16.041270", "Physics", "20079", "same as run 9005, but with trigger delay 48 ns"
"9007", "2012-Oct-30", "20:50:45.366863", "Physics", "20045", "same as run 9003, but with trigger delay 48 ns"
"9008", "2012-Oct-30", "23:38:25.509078", "Physics", "20041", "50ns,Neigh=ON, ART=thr, TAC=500 "
"9009", "2012-Oct-31", "00:04:18.965522", "Physics", "20017", "100ns,Neigh=ON, ART=thr, TAC=500 "
"9010", "2012-Oct-31", "00:43:45.410269", "Physics", "20029", "50ns,Neigh=ON, ART=thr, TAC=1000 "
"9011", "2012-Oct-31", "01:09:31.192469", "Physics", "20026", "100ns,Neigh=ON, ART=thr, TAC=1000 "
"9012", "2012-Oct-31", "01:46:08.216422", "Physics", "20085", "50ns,Neigh=OFF, ART=thr, TAC=500 "
"9013", "2012-Oct-31", "02:12:25.875076", "Physics", "20085", "100ns,Neigh=OFF, ART=thr, TAC=500 "
"9014", "2012-Oct-31", "02:51:14.903866", "Physics", "20043", "50ns,Neigh=ON, ART=peak, TAC=500 "
"9015", "2012-Oct-31", "04:39:30.107116", "Physics", "20065", "50ns,Neigh=ON, ART=thr, TAC=500 thL1=20"
"9016", "2012-Oct-31", "05:06:22.940650", "Physics", "20079", "100ns,Neigh=ON, ART=thr, TAC=500 thL1=20"
"9017", "2012-Oct-31", "05:44:32.372826", "Physics", "20079", "50ns,Neigh=ON, ART=thr, TAC=1000 thL1=20"
"9018", "2012-Oct-31", "06:14:04.769177", "Physics", "9824", "100ns,Neigh=ON, ART=thr, TAC=1000 thL1=20”
…
M. Byszewski, MM Weekly
/data/2012/testbeam_October/APV25-VMM1
Screenshot
5
November 27, 2012
TMM2,
XY
M. Byszewski, MM Weekly
Full Event
6
November 27, 2012
Tmm2
Tmm3
T1
M. Byszewski, MM Weekly
Statistics (APV25)
7
November 27, 2012
TMM2, Y
M. Byszewski, MM Weekly
8
November 27, 2012
run 9005
VMM1 tracking + trigger
M. Byszewski, MM Weekly
9
time
November 27, 2012
TDO
t(ns) = TAC – (T(TDO) - toffset )/ tslope
Toffset, Tslope from G.I. / K.N. calibration root file
M. Byszewski, MM Weekly
from G.I. 20/11/2012
run 9005 event 68
RAW
time (tdo)
10
November 27, 2012
offsets removed
time(ns)
M. Byszewski, MM Weekly
Blue Bar and an empty Red Square – trigger (time units are ‘as is’ uncorrected)
Red Square with a star within – marks related point from tracking
run 9005 event 68
RAW
time (tdo)
11
November 27, 2012
offsets removed
time(ns)
(red) below
threshold?
M. Byszewski, MM Weekly
(blue) Why this strip has triggered ? And not the other one?
run 9005 event 102
RAW
time (tdo)
12
November 27, 2012
offsets removed
time(ns)
(red) reordered
time
M. Byszewski, MM Weekly
(blue)Why this strip has triggered ? And not the other one?
run 9005 event 104
RAW
time (tdo)
13
November 27, 2012
offsets removed
time(ns)
M. Byszewski, MM Weekly
(blue) Why this strip has triggered ? And not the other one?
14
November 27, 2012
summary




Most of events are ok
…but in some of the events strip address seen
in the trigger data seems not to be
correlated with strip with miniumum charge
from the tracking data
Calibration reorders strips wrt to time of the
signal
(Note on these slides - Units of time
measurements by trigger fpga to be
confirmed)
M. Byszewski, MM Weekly