- 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 : V0 and cascade
• The idea is to look for another channel for the D+ : D+ --> K0spi+
• The main difference/advantage with D0->Kpi is that we can have a clear sample of K0s and somehow avoid the Pid identification that leads to background
First we have to reconstruct K0s : previous studies (here and here) using TCFIT clearly show that a cut on the signed decay length significance of (pipi) pairs remove background (as opposed as a cut on length only)
- cuts for K0s
Fig 1 : all (pipi) pairs w/o cuts
Fig 2 : same (pipi) pairs with cuts based on signed decay length and track significance
SL = decay length / error of decay length
St = dcaXY / error of dcaXY
Blue and green curves are ~ the same means dcaXY(Pion)*dcaXY(Kaon) has no effect after SL and St cuts
- update : 06/17 : rerun with loose cuts to determine the best [unbiased] cuts to apply for quick/efficient K0s reco.
This means , no cut on :
- silicon hits
- SL and St
- probability, chi2 of Fit
The cuts applied are :
- triggerId = 200001,200003 and 200013
- first vertex only
- |ZVertex|<10 cm and its resolution sigmaZVERTEX < 0.1 cm
- Loop over primary tracks then take the global associated
- NFit/NPoss > 0.51 (from TPC)
- |eta|<1.2
- dEdxTrackLength >40cm
- |nsigmapion|<2
- 0.2 < Mpipi < 0.8
- |ypipi| <1
- sum of Pt daughters > 1 GeV/c
- results
from left to right : no cut ; cuts based on St of tracks (used to removed tracks from PV) ; + cut based on SL
The conclusion is that there is no peak seen ; the reason is explained with the following plots
It shows the probability of the fit ; there is a *huge* peak below Probability < 0.0001 (I used probability > 0.01 for D0)
Then redoing the same exercise with a cut on probability > 0.0001 [and 0.01] (and still trying to keep other cuts as low as possible to avoid bias)
Plots with loose cuts (in the middle) do not show again a invariant mass peak ; the next try was to increase St from 1 to 3
we see that for probability > 0.0001 and St > 3 (upper middle), a tiny peak can be seen --> this set of cut will be the default to run over the run 7
- bouchet's blog
- Login or register to post comments