...
- CalCluster
- Modify layer data for moments analysis output
- Energy, Radiation lengths, etc., per layer
- Output variables:
- Longitudinal and transverse moments
- X0,Y0 at face of Cal
- Distance to nearest edge
- Others?
- Who: Tracy
- Status: ?
- Modify layer data for moments analysis output
- Review status bits usage
- avoid unnecessary/redundant status bits
- Define status bits Type of trajectory used (Cal or Tkr)
- Who: Bill, TracyDavid
- Status: ?PENDING COMMIT
- CalEventEnergy
- Mechanism to allow multiple cluster analysis Allow multiple instances of CalEventEnergy (e.g. pi0 analysis)
- Who: Tracy, David
- Status: need more discussion.PENDING COMMIT
- Relational Tables
- Implement tables
- Who: David
- Status: STUDY OF EXISTING CLASSES.
Algorithms
- UNDER WORK
Algorithms
- Moments Analysis
- Replace current Cal axis calculation with Moments Analysis
- Ideally: define Moments Analysis and implement in new code utilizing the new data structures
- Expedient: Integrate existing code into current structure (~done)
- Who: Tracy
- Status: ?
- CalValsTool
- Integrate latest AnalysisNtuple CalValsCorTool into new CalRecon structure
- Identify minimum set of output variables
- Who: Tracy, Bill
- Status: ?
- Iterative Moments Analysis for improved cluster parameter determination
- Introduce the "old" iterative moments analysis into CalRecon tool structure to provide "standalone" CalRecon analysis
- Who: Tracy
- Status: ?
- CalEventEnergyAlg
- Review the way we manage passes.
- Who: David
- Status: UNDER WORKPENDING COMMIT
Lower Priority
Documentation
- Update Cal Confluence pages to reflect structure of CalRecon
- Who: David, Tracy
- Status: not started
Likelihood tools
- Integrate in cvs the calib code
- Who: Pol, David
- Status: NOT STARTED
Geometry Service
- Convert TkrGeometrySvc into a general Glast geometry service
- "clean up" interface?
- Move to GlastSvc?
- Who: David
- Status: not started.NOT STARTED
Code Review
- Review internal code of the new correction tools
- Who: David
- Status: not started
...
- NOT STARTED
Allow for job options iterative processing "loop"
- Can Gaudi algorithm "execute" methods be called more than once per event? Allow for job options iterative processing "loop"
- Who: David
- Status: standalone prototype done, Gaudi compatibility not proved, and not demonstrated it is worth for the simple use-cases of Glast.