V0branch - modifications to V0Fitter (V0Producer) for PU

1) added new cuts and modified old  default values to purify the V0 collection in presence of PU (optimized for PU25). for slides from a tracking POG meeting see:
https://indico.cern.ch/event/337839/
https://indico.cern.ch/event/337839/contribution/3/material/slides/0.pdf
2) deleted code that was no longer relevant to the module
3) rearranged code to apply selection cuts sooner to help speed the execution of the module
yes, that can go back in. i just checked & it doesn't affect my results at
all.

On Wed, Nov 5, 2014 at 10:56 AM, Slava Krutelyov <notifications@github.com>
wrote:

> In RecoVertex/V0Producer/src/V0Fitter.cc:
>
> > -
> > -      /*double posESq = posTSCP.momentum().mag2() + piMassSquared;
> > -      double negESq = negTSCP.momentum().mag2() + piMassSquared;
> > -      double posE = sqrt(posESq);
> > -      double negE = sqrt(negESq);
> > -      double totalE = posE + negE;*/
> > -      double totalE = sqrt( posTSCP.momentum().mag2() + piMassSquared ) +
> > -	              sqrt( negTSCP.momentum().mag2() + piMassSquared );
> > -      double totalESq = totalE*totalE;
> > -      double totalPSq =
> > -	( posTSCP.momentum() + negTSCP.momentum() ).mag2();
> > -      double mass = sqrt( totalESq - totalPSq);
> > -
> > -      //mPiPiMassOut << mass << std::endl;
> > -
> > -      if( mass > mPiPiCut ) continue;
>
> can this be put back?
> Do we have to make a fit before being able to make a loose cut?
> The cost is apparently a factor of ~5 increase in the number of fits.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cms-sw/cmssw/pull/5951/files#r19891627>.
>