Difference between revisions of "Reconstruction Tasks and Topics for Further Development"
From GlueXWiki
(→Comments from Curtis) |
|||
Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
− | |||
− | |||
− | + | = Focus Areas = | |
− | + | ||
− | ## | + | We will try to broadly classify outstanding software issues and tasks into three focus areas: Tracking, Calorimetry, and PID. For each of these areas we have appointed a contact person: Simon (Tracking), Matt (Calorimetry), and Paul (PID). The contact person should report progress on the resolution of high-priority issues at each software meeting. A prioritized list of problems and tasks appears below. |
− | # χ<sup>2</sup> distributions from track fits | + | |
− | # | + | == Tracking == |
− | # | + | |
− | # | + | === Issues to Resolve === |
+ | |||
+ | # wrong track sign choice at pattern recognition stage in FDC | ||
+ | # poor proton reconstruction in b<sub>1</sub>π events | ||
+ | # incorrect χ<sup>2</sup> distributions from track fits: huge peak at zero | ||
+ | # validate propagation of errors from hit level through the fitting procedure to the track level | ||
+ | |||
+ | === Questions to Answer === | ||
+ | |||
+ | # How do we handle large single Coulomb scattering in tracking, e.g. between the CDC and FDC? | ||
+ | # How do we handle decays in tracking? (This might have similar resolution to the question above since the track shape is similar.) | ||
+ | |||
+ | == Calorimetry == | ||
+ | |||
+ | === Issues to Resolve === | ||
+ | |||
+ | # allow easy switch between 1-2-3-4 and 3-3-4 BCAL schemes; include calibrations for both | ||
+ | # tune new BCAL reconstruction algorithm, explore impact on shower multiplicity in b<sub>1</sub>π events | ||
+ | # include timing reconstruction in FCAL | ||
+ | # correct the error matrix calculation for both FCAL and BCAL | ||
+ | |||
+ | === Questions to Answer=== | ||
+ | |||
# When photons get split into multiple clusters, is all of the energy detected? | # When photons get split into multiple clusters, is all of the energy detected? | ||
− | |||
− | |||
# What is our efficiency for π<sup>0</sup> detection? η→γγ? | # What is our efficiency for π<sup>0</sup> detection? η→γγ? | ||
− | == | + | == PID == |
− | + | ||
− | + | === Issues to Resolve === | |
− | + | ||
− | + | ||
− | + | # develop convention for defining t<sub>0</sub> for each detector | |
− | # | + | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | |||
− | |||
− | |||
− | |||
− | + | === Questions to Answer === | |
− | + | # What is the general scheme (or schemes) that we want to support? | |
+ | # What is the nature of the user interface into particle ID information? |
Revision as of 07:24, 8 September 2011
Contents
Focus Areas
We will try to broadly classify outstanding software issues and tasks into three focus areas: Tracking, Calorimetry, and PID. For each of these areas we have appointed a contact person: Simon (Tracking), Matt (Calorimetry), and Paul (PID). The contact person should report progress on the resolution of high-priority issues at each software meeting. A prioritized list of problems and tasks appears below.
Tracking
Issues to Resolve
- wrong track sign choice at pattern recognition stage in FDC
- poor proton reconstruction in b1π events
- incorrect χ2 distributions from track fits: huge peak at zero
- validate propagation of errors from hit level through the fitting procedure to the track level
Questions to Answer
- How do we handle large single Coulomb scattering in tracking, e.g. between the CDC and FDC?
- How do we handle decays in tracking? (This might have similar resolution to the question above since the track shape is similar.)
Calorimetry
Issues to Resolve
- allow easy switch between 1-2-3-4 and 3-3-4 BCAL schemes; include calibrations for both
- tune new BCAL reconstruction algorithm, explore impact on shower multiplicity in b1π events
- include timing reconstruction in FCAL
- correct the error matrix calculation for both FCAL and BCAL
Questions to Answer
- When photons get split into multiple clusters, is all of the energy detected?
- What is our efficiency for π0 detection? η→γγ?
PID
Issues to Resolve
- develop convention for defining t0 for each detector
Questions to Answer
- What is the general scheme (or schemes) that we want to support?
- What is the nature of the user interface into particle ID information?