- bouchet's home page
- Posts
- 2016
- 2015
- December (1)
- November (3)
- October (2)
- September (2)
- August (2)
- June (2)
- April (5)
- March (2)
- February (3)
- January (2)
- 2014
- December (2)
- November (2)
- October (3)
- September (2)
- August (3)
- July (1)
- June (3)
- May (6)
- April (6)
- March (1)
- February (2)
- January (1)
- 2013
- December (2)
- November (3)
- October (3)
- September (4)
- August (1)
- July (1)
- May (4)
- April (6)
- March (4)
- February (3)
- 2012
- 2011
- December (2)
- November (2)
- October (4)
- September (1)
- August (2)
- July (6)
- June (2)
- May (3)
- April (3)
- March (2)
- 2010
- 2009
- December (2)
- November (1)
- October (3)
- September (1)
- August (1)
- July (1)
- June (2)
- April (1)
- March (2)
- February (2)
- January (1)
- 2008
- My blog
- Post new blog entry
- All blogs
run 7 : QA ⚠
Goal : make a fine QA of run 7 in order to :
- remove junk runs
- decrease the number of runs/events to analyze
- from list1(all runs) ➞ list2(event-based QA) ➞ list3(track-based QA) ➞ list4 (D0 candidates-based QA)
This can be done by making a cut on nsigma of a given distribution VS sequence to remove the outliers.
The variables to QA that I've chosen are :
- Vr = √(Vx2 + Vy2)
- Vz
- widths of Vr and Vz fit
- ResVr, ResVz : primary vertex resolution
- mean number of tracks (per sequence) with SSD hits , same for SVT
note :
- the rank Id will be set to the first vertex (see plot below)
- we can also monitor the sequences vs TriggerId
- there are still some hard cuts used :
- |Vz|<30 cm
- triggerId = 200001,200003, 200013
- pt >0.1 GeV/c
- |η|<1.2
- NTPCfit / NTPCposs >0.51
- |DCAXY|<3 cm
A RunId is coded as (for example) : 8102017, where :
- is the year
- is the day number
- is the sequence Id
A) preparation plots
Fig. 1 : Vertex Z resolution vs vertex rank
Vertices with rank >0 have large vertex Z resolution
Fig. 2 : Vertex Z position vs sequence id of day 8109
From this plot, a double gauss is used to get the mean and width of the distribution, for each sequence
Fig3 . : <Vz> vs sequence Id for day 8109 : the error bar are the width of the double gauss fit (the narrower one)
The rest of the plots for day 102 to day 109 is here
note : plots for day 102 are almost empty because the vertex Z distribution is not centered at 0,
B) other preparation plots
Not exhaustive but :
- Vr vs sequence id : here
- Resolution Vz vs sequence id : here ; for this kind of distribution, I will use a landau fit. The fit is not really good but the MPV of the Landau fit is closed the peak of this distribution
- SSD hits vs sequence : here
note : the plots for the SSD hits is similar to previous studies
C) plots for Vr
The distribution of Vr vs sequence is here.
The results of a double gaus fit is here
update 9/5 : Vr for day 100 to day 120 : here
D) results for level 1 QA
- This pass will be based only on the primary vertex resolution in XY and Z
- a 2σ window is chosen to keep or reject runnumbers : outliers for Vr , outliers for Vz
- for ResVz : list before and list with runs to remove
- for ResVr : list before and list with runs to remove
- final list to remove , matched between ResVr and ResVz
E) improvements for level1 QA : here
F) QA -level 2
We used a cut based on the number of silicon hits per tracks.
At this step, I'm evaluating the mean (per run number) of the following quantity :
Bool_t conditionK1 = (NoFSvtHits>1); Bool_t conditionK2 = (NoFSsdHits==1 && NoFSvtHits>0); Bool_t conditionK3 = conditionK1 || conditionK2;
So a track should have 2 silicon hits :
- 2 SVT hits
- or 1 SSD hit and 1 SVT hit
A preliminary plot is here (for day 98 to day 109)
- bouchet's blog
- Login or register to post comments