Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Starting at CalClusters level, objects are less numerous in the event (as
compared to lower level objects) and can be a little bigger. This is why,
for each data object, we would like to store the name of the producer as a
std::string, and remove the equivalent status bits. Such a mechanism
can adapt to any change in the algorithms, and be used with new
user algorithms, a lot more easily than status bits.

To be removed:

  • CalCluster::*CLUSTER

Avoid algo-oriented status bits

We should avoid status bits saying things about algorithms, because
this reduce our freedom with the way we arrange and change those
algorithms. We should prefer eventually status bits which say
things about the "state" of the data.

...

To be investigated :

  • CalCluster::MIPTRACK
  • CalCluster::MOMENTS
  • CalCluster::ENERGYCORR
  • CalCluster::MIPFIT

Etc.

It seems CalCluster::ISOLATEDCLUSTER is redundant, and equivalent
to !ALLXTALS.

For the remaining useful status bits (for example the ones saying
if this or
that data is valid), the methods signatures could be
made more
uniform in the various CalRecon classes.

...