Hi Tony,
On Tue, Feb 14, 2006 at 05:06:51PM -0800, Johnson, Tony S. wrote:
> HI, maybe I had to leave before we discussed this, but what is
>
> > which would look like:
> >
> > public interface ParticleEnergyCalibration {
> > public double energy(ReconstructedParticle part);
> > }
> >
> > public interface ClusterEnergyCalibration {
> > public double energy(Cluster clus);
> > }
>
> going to do that, part.getEnergy() doesn't (or can't)?
Well, you could use part.getEnergy(), but then earlier in the code you
would have to figure out what the actual energy of the particle is and
set it. This is a complex problem which depends on the type of particle,
which detector you're using, and your reconstruction algorithm; we don't
yet have a general solution. So for now what people do is use one of a
small number of calibration methods (Ron's, Lei's, ...), generally with
constants hard-coded for a particular detector or set of detectors. But
that's rather ugly -- you have to change your reconstruction code if you
want to try a different detector or calibration, and it's kind of hard
to put code like that in CVS (c.f. today's discussion). So it would be
good if we could abstract that part out, defining a common interface so
that I could change between calibrations just by passing my particle
reconstructor a different calibration object...
That's the thinking.
Cheers,
Mat.
|