Project

General

Profile

Feature #13831

R006: kTrack rate in the periods of "resolved" signal-timing shift

Added by Kenichi Nakano about 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Start date:
09/10/2016
Due date:
% Done:

0%

Estimated time:
Duration:

Description

The (large) signal-timing shift happened twice in roadset 59 and once in roadset 70, as recorded in
http://twiki.npl.illinois.edu/bin/view/E906/DamagedDataList
It has been (mostly) resolved by shifting the measured drift time in kTracker.

I checked the number of reconstructed kTracks to judge if these data are fine for physics analysis.
I applied a R005-like selection as follows to count only good target kTracks;
select spillID, count(*) from kTrack where roadID != 0 and z0 between -200 and -50 and chisq/(numHits-5) < 5 and numHits >= 15 and (numHits = 18 or pz1 > 18) group by spillID

Two plots attached show the kTrack rate in roadsets 59 and 70. The periods of signal-timing shifts are drawn. The kTrack rate is lower by a few percent (by eye) than the normal period. Is it high enough and fine for physics analysis?

ktrk_rate_rs59.png (51.6 KB) ktrk_rate_rs59.png kTracks/spill in roadset 59 Kenichi Nakano, 09/10/2016 04:36 PM
nktrk_rs70.png (52.5 KB) nktrk_rs70.png kTracks/spill in roadset 70 Kenichi Nakano, 09/10/2016 04:36 PM

History

#1 Updated by Kenichi Nakano about 4 years ago

  • Tracker changed from Bug to Feature
  • Status changed from New to Closed

This was discussed at the analysis meeting on Sep. 13. No one claimed any problem on this kTrack rate. Just we should check it again once the track/dimuon selection is updated/fixed for R006.

Also available in: Atom PDF