On 12 Nov, 2013, at 5:24 PM, ianna <notifications@github.com> wrote:

> In Geometry/CaloGeometry/interface/CaloCellGeometry.h:
> 
> >  private:
> >    GlobalPoint         m_refPoint ;
> > +  mutable GlobalPoint         m_backPoint ;
> 
> indeed, it is a mess :-(
> Also, calculating a back point for a calo cell will give different results for different sub-detectors, or even for the same one - ES+ vs ES-. The order of corners is not consistent across them.
> 
At the moment I need to cache what CaloTower uses.
Can be cashed elsewhere (or CaloTower can not use that code anymore)
CaloCell is the natural place
(and I saw that some children have their own code to compute shower location along the axis)
We cannot continue to have each reconstruciton code redo geometry and redo it and run time for each hit (and sometime in a wrong way).
I am personally in favour that geometry, as other conditions, do cache quantities specific for their users (after all geom and conditions are there to serve reconstruction)
Need just coordination and feedback.

v.