Difference between revisions of "BCAL reconstruction 9/21/11"
From GlueXWiki
(One intermediate revision by the same user not shown) | |||
Line 3: | Line 3: | ||
** Can easily switch between 1234/334/whatever configurations | ** Can easily switch between 1234/334/whatever configurations | ||
** Breaks KLOE algorithm at the moment (worth fixing?) | ** Breaks KLOE algorithm at the moment (worth fixing?) | ||
− | * | + | * pi0 reconstruction/fitting |
− | ** Made some changes, still error in phi is overestimated by 25% | + | ** created a sample of events with a single pi0 |
− | * | + | ** kinematic fit to pi0 requires errors |
− | ** Suggestions? | + | *** Made some changes to error calculation, still error in phi is overestimated by 25% |
+ | *** Suggestions? | ||
==Issues== | ==Issues== | ||
− | * Deterior in time resolution/energy resolution/etc. when changing from FINE to 1234 summing. How much is inevitable and how much due to | + | * Deterior in time resolution/energy resolution/etc. when changing from FINE to 1234 summing. How much is inevitable and how much due to unoptimized algorithm? |
** Decouple c | ** Decouple c | ||
* How to deal with stuff at the very forward edge of BCAL? | * How to deal with stuff at the very forward edge of BCAL? |
Latest revision as of 13:34, 21 September 2011
Update
- Modified DBCALGeometry to allow 1234 summing (not checked in)
- Can easily switch between 1234/334/whatever configurations
- Breaks KLOE algorithm at the moment (worth fixing?)
- pi0 reconstruction/fitting
- created a sample of events with a single pi0
- kinematic fit to pi0 requires errors
- Made some changes to error calculation, still error in phi is overestimated by 25%
- Suggestions?
Issues
- Deterior in time resolution/energy resolution/etc. when changing from FINE to 1234 summing. How much is inevitable and how much due to unoptimized algorithm?
- Decouple c
- How to deal with stuff at the very forward edge of BCAL?