Project

General

Profile

TrackerSoftwareReview-Mtg2 » History » Version 1

Rajaram, Durga, 24 May 2017 14:37

1 1 Rajaram, Durga
h1. TrackerSoftwareReview-Mtg2
2
3
h2. May 26, 2017: 1400 BST
4
5
h2. Agenda
6
7
8
# Introduction - K. Long
9
# Actions from previous meeting
10
# Kalman & track fitting overview: C. Hunt
11
# Pattern recognition update: A. Dobbs
12
# Next Steps for review
13
# AoB
14
15
h2. Additional documentation
16
17
* Tracker Software Paper: attachment:MICE-Tracker-Software-Publication.pdf
18
19
h2. Minutes from previous meeting
20
21
* Attendance: KL, PK, DR, CR, DC, AD, MU, EO, AB
22
23
* Algorithm:
24
    DC: In determining #turns, do we have enough information to tell if there could be > 1 rotation between stations? Has such a restriction been imposed — can it be imposed — in selecting “ideal events”?
25
26
* Efficiency:
27
    DC: Does MC show the same pattern of lower TKD efficiency? 
28
        — are dead channels and noise handled correctly in the MC?
29
        MU: Noise smearing added by Heidt; AD notes it’s not part of standard production
30
        KL: we don’t want to rely on the MC for this unless we really have to
31
        Action: Check dead channel & noise handling in MC
32
        Action: Check MC of this run 8681 & compare efficiencies with data
33
34
* Sources of error:
35
    CR: Need a list of sources of uncertainty: alignment, scattering, energy loss, field uniformity, etc and present what studies have been done — Action
36
37
* Unused spacepoints:
38
    DC: In adding unused spacepoint, show the distribution of distance of unused s.p & its correlation with #pe — Action
39
40
* Pt singularity:
41
    AB, DC: why not just run straight track fit 1st, if it satisfies chi2, then send to Kalman instead of trying to do a helical?
42
    Q: can Kalman reconstruct a helical from the straight?
43
    CH: Think so, if seeded properly.
44
    Action: This should be studied
45
46
47
h2. Dial-in information
48
49
http://mice.iit.edu/phonebridge.html
50
51
---