#include <PowhegResHook.h>
Definition at line 5 of file PowhegResHook.h.
PowhegResHook::PowhegResHook |
( |
| ) |
|
|
inline |
PowhegResHook::~PowhegResHook |
( |
| ) |
|
|
inline |
bool PowhegResHook::canSetResonanceScale |
( |
| ) |
|
|
inline |
double PowhegResHook::scaleResonance |
( |
const int |
iRes, |
|
|
const Pythia8::Event & |
event |
|
) |
| |
Definition at line 11 of file PowhegResHook.cc.
References funct::abs(), i, min(), or, AlCaHLTBitMon_ParallelJobs::p, AnalysisDataFormats_SUSYBSMObjects::pa, q2, pileupReCalc_HLTpaths::scale, and mathSSE::sqrt().
12 calcScales_ = settingsPtr->flag(
"POWHEGres:calcScales");
16 int nDau =
event[iRes].daughterList().size();
29 else if (
abs(
event[iRes].
id()) == 6) {
31 int idw = -1, idb = -1, idg = -1;
33 for (
int i = 0;
i < nDau;
i++) {
34 int iDau =
event[iRes].daughterList()[
i];
35 if (
abs(
event[iDau].
id()) == 24) idw = iDau;
36 if (
abs(
event[iDau].
id()) == 5) idb = iDau;
37 if (
abs(
event[iDau].
id()) == 21) idg = iDau;
42 pw.bstback(
event[iRes].
p());
45 pb.bstback(
event[iRes].
p());
48 pg.bstback(
event[iRes].
p());
51 scale =
sqrt(2*pg*pb*pg.e()/pb.e());
54 else if (
abs(
event[iRes].
id()) == 24) {
56 int idq = -1, ida = -1, idg = -1;
58 for (
int i = 0;
i < nDau;
i++) {
59 int iDau =
event[iRes].daughterList()[
i];
60 if (
event[iDau].
id() == 21) idg = iDau;
61 else if (
event[iDau].
id() > 0) idq = iDau;
62 else if (
event[iDau].
id() < 0) ida = iDau;
67 pq.bstback(
event[iRes].
p());
73 pg.bstback(
event[iRes].
p());
78 double csi = 2*pg.e()/
sqrt(q2);
79 double yq = 1 - pg*pq/(pg.e()*pq.e());
80 double ya = 1 - pg*
pa/(pg.e()*
pa.e());
82 scale =
sqrt(
min(1-yq,1-ya)*pow2(csi)*q2/2);
The Signals That Services Can Subscribe To This is based on ActivityRegistry and is current per Services can connect to the signals distributed by the ActivityRegistry in order to monitor the activity of the application Each possible callback has some defined which we here list in angle e< void, edm::EventIDconst &, edm::Timestampconst & > We also list in braces which AR_WATCH_USING_METHOD_ is used for those or
Abs< T >::type abs(const T &t)
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger but the state exists so we define the behavior If all triggers are the negative crieriion will lead to accepting the event(this again matches the behavior of"!*"before the partial wildcard feature was incorporated).The per-event"cost"of each negative criterion with multiple relevant triggers is about the same as!*was in the past
bool PowhegResHook::calcScales_ |
|
private |