...
- Perform the start xtal rec step.
- We'll put in all the new bits to keep track of what's happening, according to the scheme outlined above. Chul and Tracy will follow up on this and get it done.
- If there's one or more saturated xtal(s), the first thing we'll do in CalRecon is a fit using the transverse information only with the full xtal collection (i.e. before the clustering) to be used to fix the position for saturated xtals.
- This will require moving the current fitting routine (now living in CalRecon/src/Clustering/MomentsClusterInfo.cxx) in some common area (Tracy suggests CalRecon/src/Utilities/) to be used in more than one place. Luca B. will take care of this.
- As a side project, the possibility of not using Minuit for the fit will be investigated, in order to gain in speed and avoid a dependency on ROOT. This is low-priority project that Luca B. will take a look into.
- At this point (if there are saturated xtals) from CalRecon we will call a dedicated tool in XtalRecData to set the longitudinal position to our best value, based on the transverse fit.
- After this point the xtalRecData objects in the TDS will have a reasonable longitudinal position information even for the saturated xtals, and the correct information will propagate trasparently to the downstream code (with the proper status bit set).
- The next step is the calorimeter clustering (i.e. the splitting of the xtal collection in clusters).
- And after that we'll go through the standard transverse fit/moments analysis/classification on a cluster by cluster basis.
- Further possible adjustments to the xtals that need transverse fit at the cluster level will be done by calling the proper tool at this point.