Rivet API documentation

Rivet 4.1.3
Rivet::ATLAS_RUN2_MUON_PT_RES Class Reference

#include <ExptResolutionFunctions.hh>

Inheritance diagram for Rivet::ATLAS_RUN2_MUON_PT_RES:
Rivet::ResolutionFunctor< Particle >

Public Member Functions

double resolution (const double pT2, const double eta, const double phi) const
double resolution (const Particle &mu) const override
 Get muon pt resolution given a Particle.
const T2 & refData (const string &hname) const
LoggetLog () const

Detailed Description

Based on implementation (and data files adapted from) https://gitlab.cern.ch/atlas-sa/framework/-/blob/3c261d70940b42e216d7205af9f5d6882a88700d/src/ObjectResolutions.cxx In turn based on ATLAS 2018 data. Obtains the resolution based on a combination of MS and ID resolutions, which are different depending on whether it is a barrel/endcap muon.

Member Function Documentation

◆ refData()

const T2 & Rivet::ResolutionFunctor< Particle >::refData ( const string & hname) const
inlineinherited

Get reference data for a named histo If the overwhelming majority of Functors end up not needing refdata, maybe we should factorise?

Todo
ensure that the type inherits from YODA::AnalysisObject?

◆ resolution() [1/2]

double Rivet::ATLAS_RUN2_MUON_PT_RES::resolution ( const double pT2,
const double eta,
const double phi ) const
inline

Get electron pt resolution given pt2, eta, and phi. Obtains the resolution based on a combination of MS and ID resolutions, which are different depending on whether it is a barrel/endcap muon and vary differently with pT2. See SA code for further justification.

References Rivet::Kin::eta().

Referenced by resolution().

◆ resolution() [2/2]

double Rivet::ATLAS_RUN2_MUON_PT_RES::resolution ( const Particle & mu) const
inlineoverridevirtual

The documentation for this class was generated from the following file: