Trackersoftwarereview-mtg7 » History » Version 4
Dobbs, Adam, 08 September 2017 12:23
1 | 1 | Rajaram, Durga | h1. Tracker Software Review: Meeting 7 |
---|---|---|---|
2 | |||
3 | 3 | Rajaram, Durga | h2. September 8, 2017: 1400 BST |
4 | 1 | Rajaram, Durga | |
5 | h2. Agenda |
||
6 | |||
7 | # *Introduction* - K. Long |
||
8 | # *Actions from previous meetings* |
||
9 | * *PR*: |
||
10 | 4 | Dobbs, Adam | |
11 | 1 | Rajaram, Durga | ### AD: Optimize Chi2 cut for “MINUIT” variant |
12 | ### AD: Show individual residual distributions to understand details - is the station 1 distribution a binning artifact or a constraint from the fit? |
||
13 | ### AD, CH: Check and implement MCS errors |
||
14 | ### AD: Plot chisq per dof for 'perfect' events |
||
15 | ### Define multi-track requirements |
||
16 | 4 | Dobbs, Adam | ### -AD: Compare data/MC efficiencies for 8681- _Done_ |
17 | ### -AD: Show distributions with sign per station per tracker- _Done_ |
||
18 | 1 | Rajaram, Durga | * *Track fit*: |
19 | ### Repeat study that was done to investigate whether field integration (e.g. using Runge Kutta) is required to compensate for magnetic field non-uniformity |
||
20 | ### Make study of magnetic-field alignment with a view to establishing whether the present algorithm is sufficiently insensitive to reasonable assumptions of maximum field-misalignment |
||
21 | ### Study p-value: split up contributions to p-value shape using MC and study shape in data, e.g. is there an error in the resolution per plane, handling of MCS, handing of energy loss, b field.. |
||
22 | * *Tracker, MC*: |
||
23 | ## MU/EO: Understand reasons for shape of hits-per-station histogram - low-level |
||
24 | ## PK: Check dead channel & noise handling in MC. |
||
25 | ## Tracker group: Summarize, show what has been studied so far for systematics (alignment, scattering, energy loss, field uniformity, etc). |
||
26 | |||
27 | |||
28 | # *Report on actions: Pattern recognition*: A. Dobbs |
||
29 | # *Report on actions: Track fit*: C. Hunt |
||
30 | # *Next Steps for review* |
||
31 | # *AoB* |
||
32 | |||
33 | --- |
||
34 | |||
35 | h2. Dial-in information |
||
36 | |||
37 | http://mice.iit.edu/phonebridge.html |
||
38 | |||
39 | --- |
||
40 | |||
41 | h2. Attendance: KL, CR, PK, AD, CH, MU, DR |
||
42 | |||
43 | h2. Notes from Meeting 5: Aug 16, 2017: |
||
44 | |||
45 | * AD: Compare data/MC efficiencies for 8681 |
||
46 | ** done. 8681, 2.8.5 MC reprocessed with 2.9.1-PatRec,Kalman -- results consistent with 2.9.1 reco |
||
47 | ** Illustrative plots added |
||
48 | |||
49 | * AD: Optimize Chi2 cut for “MINUIT” variant |
||
50 | ** pushing cuts lower gives higher efficiencies, though purity may be an issue. Noted that critical parameter is efficiency |
||
51 | ** Q: how loose should the LSQ cuts be? AD points to loosest cut in table from previous meeting. |
||
52 | |||
53 | * AD: Show residual distributions with sign per station per tracker |
||
54 | ** sent to email list, added to meeting wiki |
||
55 | |||
56 | * AD: Plot chisq per dof for 'perfect’ events |
||
57 | 2 | Rajaram, Durga | ** stands |
58 | 1 | Rajaram, Durga | |
59 | * Define multi-track requirements |
||
60 | 2 | Rajaram, Durga | ** stands. Need discussion and inputs on how to define |
61 | 1 | Rajaram, Durga | |
62 | * Adding errors: |
||
63 | ** for circle fit: suggestion is to define a mean error and apply to every station rather than station-by-station errors. |
||
64 | ** Q: how to define mean error? based on the geometric mean of the errors? |
||
65 | ** Q: does taking the chi^2/mean_error^2 bias the pr fit? |
||
66 | ** errors on the resulting circle fit parameters will feed into the longitudinal fit |
||
67 | |||
68 | * Discussion about aperture cut |
||
69 | 2 | Rajaram, Durga | ** CR notes that aperture cut should be standardized by tracker group. AD notes that the cut in PR is loose -- 150. |
70 | 1 | Rajaram, Durga | ** PK suggests a flag to indicate if track passed or failed an aperture cut |
71 | ** All agree that fiducial cut should be standardized, |
||
72 | ** Q: does the current aperture cut throw out any potential tracks? If it does, cut should be loosened, but consensus seems to be that tracking should not do any "analysis-style" cuts but rather optimize track-finding. |
||
73 | |||
74 | * Effect of magnetic field non-uniformity, alignment on track fit -- CH had issues reading mag field map from Joe Langland's program. CH will check against comsol map for 7469. |