Bug fix to avoid duplicated clusters on the same track in upgraded FPIX

This pull request includes a bug fix and a few changes in an analysis package
Can I ask to keep this pull request on hold until the Tracking POG has checked its impact on the usual efficiency, fake rate and duplicate plots both for phase 1 and phase 2? This is because if something is sizeably affected by that (I don't think so) some decisions have to be taken concerning the Technical Proposal results.

                                 Andrea

On Oct 20, 2014, at 10:55 , Volker Adler <notifications@github.com<mailto:notifications@github.com>> wrote:


In RecoTracker/TkDetLayers/src/PixelForwardLayer.cc:

> @@ -203,7 +203,7 @@ PixelForwardLayer::groupedCompatibleDetsV( const TrajectoryStateOnSurface& tsos,
>    if(!closestResult_outer.empty()){
>      DetGroupElement closestGel( closestResult_outer.front().front());
>      float window = computeWindowSize( closestGel.det(), closestGel.trajectoryState(), est);
> -    searchNeighbors( tsos, prop, est, crossings_inner, window, result_outer, false);
> +    searchNeighbors( tsos, prop, est, crossings_outer, window, result_outer, false);


These have been introduced with 2ebe99f<https://github.com/cms-sw/cmssw/commit/2ebe99f5c10d2b0ba7cf601cca3918a8a7c3f350> , which is only in 62XSLHC.

—
Reply to this email directly or view it on GitHub<https://github.com/cms-sw/cmssw/pull/5889/files#r19073779>.