[Rivet] correction on ATLAS_2011_I944826 routine

[Frank Siegert]

Hi Sercan,

Thanks for noticing this inconsistency. I take it, you're familiar
with the analysis? Maybe I can ask a follow-up question... if we
extend the cfs acceptance, this would also affect the nstable>2 cut
(which would now also count particles in the extended acceptance).
Would that be correct? If so, I'll make the change in the cfs
constructor directly.

Cheers,
Frank

On 23 October 2012 11:08, Sercan Sen <Sercan.Sen at cern.ch> wrote:
>
> Hello,
>
> I think there is a small correction needed on ATLAS_2011_I944826 routine.
>
> It applies charged final states projection for the particles in |\eta| <
> 2.5, however, search for the hits in MBTS rapidity region 2.09 < |\eta| <
> 3.84. see below.. In this case, trigger cut is limited to the
> 2.09<|\eta|<2.5.
>
>       ChargedFinalState  cfs(-2.5, 2.5, 100*MeV);
>       addProjection(cfs, "CFS");
>
>       const ChargedFinalState& cfs =
> applyProjection<ChargedFinalState>(event, "CFS");
>
>       // ATLAS MBTS trigger requirement of at least one hit in either
> hemisphere
>       const ChargedFinalState& cfs =
> applyProjection<ChargedFinalState>(event, "CFS");
>       int n_mbts = 0;
>       foreach (const Particle& p, cfs.particles()) {
>         const double eta = fabs(p.momentum().eta());
>         if (inRange(eta, 2.09, 3.84)) n_mbts++;
>       }
>
>       if (n_mbts < 1) {
>         MSG_DEBUG("Failed trigger cut");
>         vetoEvent;
>       }
>
> Cheers,
> Sercan
>
> _______________________________________________
> Rivet mailing list
> Rivet at projects.hepforge.org
> http://www.hepforge.org/lists/listinfo/rivet