Exotica HLT validation : latest developments

We monitor di-electron, single electron, di-photons, single photon, di-muon paths.
The validation plots are in general reasonable, although we still need to fix some features.
We plan to fix all features and fully fix our currently buggy trigger paths (others than the paths mentioned above) by our next pull request (should come at the end of next week).
This will be extremely useful to us to help further developments to have our current version integrated in the validation workflow.
There was some confusion about the exact thresholds, this is fixed now, I'm
putting this path back.

2014-09-15 11:49 GMT+02:00 perrotta <notifications@github.com>:

> In HLTriggerOffline/Exotica/python/analyses/hltExoticaHighPtDimuon_cff.py:
>
> > @@ -2,20 +2,15 @@
> >
> >  HighPtDimuonPSet = cms.PSet(
> >      hltPathsToCheck = cms.vstring(
> > -        #"HLT_Mu17_Mu8_v",
> > -        #"HLT_Mu17_TkMu8_v",
> > -        "HLT_Mu17_TrkIsoVVL_Mu8_TrkIsoVVL_v",
> > -        "HLT_Mu17_TrkIsoVVL_TkMu8_TrkIsoVVL_v",
> > -        "HLT_Mu30_TkMu11_v",
>
> This PR had been reverted, and therefore it is not in the IB.
> Anyhow, is it normal that you remove the monitoring of this
> HLT_Mu30_TkMu11 path, which is one of those requested for the Run2 HLT menu
> and already included in GRun since a while? Perhaps slipped out? Please
> check.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cms-sw/cmssw/pull/5105/files#r17533326>.
>