things were not as bad in v2_15 at expense of resolution. if we include
just everything that fits remotely to a curve somewhere, ofcourse we get
very very good efficiency.
however, remember the resolution we started with? resolution is improved
by improve tracking algorithm, calibration and in the sametime, by being
more selective on tracks to be considered. then those tracks fit to poor
quality show up and were removed from the track list.
dynamically cutting on stubs/segments/tracks may be a solution, if it dose
not
Chi
On Fri, 18 Jul 2003, Tancredi Botto wrote:
>
> Chris,
> I believe that blue means fast fit tracks, green means newton tracks
> (ie. not no fast fit, not no newton)
>
> It'd be very good if recon efficiencies are limited to events with less
> than a perfect hit distribution. I think it is a matter of learning how
> to deal with stubs only or even fake stubs and with crossing-cell tracks
>
> Somehow (this is limited statistics) I have the impression that things
> were not as bad for v2_15 back in march.
>
> But it should be use to plug boxes in and out of MC, which may be
> a useful debug for FF/newton. Also, a better FF may help on these
> issues
>
>
This archive was generated by hypermail 2.1.2 : Mon Feb 24 2014 - 14:07:29 EST