caf_trigger modifications

• p21-br-102 October 19, 2010 (MB):
  Updated EM SPCs for Run2a-Run2b3, using newest EM ID operating points.
  
• p21-br-101 October 19, 2010 (MB):
  Multi-epoch processing for remaining triggers.
  
• p21-br-100 October 18, 2010 (MB):
  Multi-epoch processing for SingleMuonOR triggers.
  
• p21-br-99 October 15, 2010 (MB):
  Yunhe's fix for v15-v16 ElectronTau triggers.
  
• p21-br-98 October 15, 2010 (MB):
  Slava's changes to implement multi-epoch *data* processing.
  Updates to the following files:
  caf_trigger/src/MuonTriggerORMatch.cpp
  caf_trigger/caf_trigger/MuonTriggerORMatch.hpp
  caf_trigger/caf_trigger/TriggerSelection.hpp
  caf_trigger/src/TriggerSelection.cpp
  caf_trigger/src/TriggerSelection_linkdef.h
  caf_trigger/caf_trigger/TriggerMap.hpp
  caf_trigger/src/TriggerMap.cpp
  
• p21-br-97 October 4, 2010:
  Typo fixes.
  
• p21-br-96 October 4, 2010:
  Fixed header in mkruntrigvlist.py script
  
• p21-br-95 October 4, 2010:
  Added 16d and 16e epochs to parameters/trignames.txt
  
• p21-br-94 September 30, 2010:
  Updated parameters/runvstriglistX100.txt
  
• p21-br-93 September 30, 2010:
  Updates for L2 track matching and jet matching
  
• p21-br-92 September 2, 2010:
  Added latest v16 EM trigger SPCs
  
• p21-br-91 July 20, 2010:
  The following definitions have been changed:
  MuonTriggerORMatch_p20_MUHI1_ITLM10_a --> Changed trigger version range from [15.00,15.99] to [15.00,16.99]
  MuonTriggerORMatch_p20_MUHI1_ITLM10_b --> Changed trigger version range from [16.00,16.99] to [15.00,16.99]
  MuonTriggerORMatch_p20_MUHI1_ITLM10 --> Added
  
• p21-br-90 June 29, 2010:
  Removed debug option
  
• p21-br-88 May 5, 2010:
  Updated caf_trigger/parameters/results_muor/pT20/
  eff_SingleMuonOR_SingleMuonTriggersOR_3D_lumi_phi_deteta_Binned_pT20.spc -> eff_SingleMuonOR_SingleMuonTriggersOR_3D_lumi_phi_deteta_Binned.spc
  
• p21-br-85 Mar 30, 2010:
  Updates for new SingleMuoOR SPCs:
  - Changes in caf_trigger/parameters/trignames.txt
  New v15 trigger epochs (15a2, 15b2)
  - Changes in caf_trigger/parameters/results_muor/
  Added new pT20 sub-directory.
  Added new SingleMuOR SPCs in pT20 sub-directory
  - Bug fix and updates to: caf_trigger/caf_trigger/...
  ...L1MuTerms.hpp
  ...L1MuTerms.cpp
  ...MuonTriggerMatch.cpp
  ...MuonTriggerORMatch.cpp
  
• p21-br-84 Mar 4, 2010:
  Fixing trigger epoch specification bug discovered by Ken in MuJetsOR and SuperOR
  Changes in caf_trigger/src/Probability_MuJets.cpp and (MuJetsOR)
  caf_trigger/src/Probability_MuJetsORSingleMuonOR.cpp (SuperOR)
  Updated caf_trigger/parameters/runvstriglistX100.txt
  
• p21-br-82 Feb 22, 2010:
  Updated vjets_cafe and caf_trigger to take care of the v16 single mu and mu+jet trigger selections and matching:
  For single mu:
  MM10 was missing the trigger's track match in the matching.
  For mu+jets:
  One trigger was missing in the data selection (MUHI1_2J20LM3DR3), and the L1 matching for the MUJ1 triggers was done assuming the trigger
  accepts events in the entire eta range, while it is actually forward only.
  
• p21-br-80 Jan 2, 2010:
  Add the possibility to vary the trigger efficiency variation in the syst errors for muon triggers.
  
• p21-br-79 Jan 22, 2010:
  Lot of update. New single muon OR spc files. Correct bugs in muon matching...
• p21-br-76 Dec 14, 2009:
  Lot of debugging. Update new single muonOR efficiencies. Turns-on vs new EMid.
  
• p21-br-74 Sep 16, 2009: update trigger version number vs. run number list
• p21-br-73 July 20, 2009: update EMid spc files.
• p21-br-69 June 12, 2009: the electron trigger efficiencies for all (Run2a+2b) trigger versions and all (old+new) EMIDs are now in CVS, in caf_trigger p21-br-69 caf_trigger/parameters/results_emor/
• p21-br-68 June 8, 2009: Adding ability to read lumi numbers from lumicache files
• p21-br-63 May 15, 2009: Update EM triggers
• p21-br-62 March 27, 2009: Correct uninitlaized variable in proProcessor.cpp
• p21-br-61 Feb 10, 2009: First, just a reminder: caf_trigger's p18 branch development has been *stopped* and no longer maintained --- all p18 functions and processors have been transfered to p21 branch and tested for backward compatibility. All p18 users are encouraged to switch to the latest p21 branch.
  Second, a new probability processor for ORing Mu+Tau Triggers and Single MU OR Triggers has been released: "Probability_MuTauORSingleMuonOR" and "TauTriggerMatch" (thanks to the author: Ken Herner). This is the third "Super-OR" processors available so far (the first two are "Probability_MuJetsORSingleMuonOR" and "Probability_EJetsORSingleEMOR").
  The configs going together with this new "Super-OR" are here:
  caf_trigger/configs/MuTauTriggerMatch.config (for doing trigger matching)
  caf_trigger/configs/MuTau_TriggersOR_TurnOns-base.config (for applying turn-ons)
  The configs have been made compatible with the common vjets_cafe configs however they have not been *thoroughly* tested with the vjets_cafe framework, please report if you have a problem.
  For SPCs: please contact the author, so far only v15 SPCs are available. V16 SPCs are being derived at the moment (Diego Menezes).
  Finally, the "run number out of the range" problem has been fixed for the "extended" Moriond2009 dataset (see CVS log for details).
  Includes the v15 MuTau "Super-OR" SPCs derived by Ken:
  caf_trigger/parameters/results_mutauor
  You can start using them together with the configs I mentioned in the previous notice.
  Please read caf_trigger/parameters/results_mutauor/README *first*.
• p21-br-57 Jan 8, 2009: Dear caf_trigger users, we found a problem in the MatchEMTrigger processor. It might have happened that some electrons in the EC passed the SH and SHT trigger matching while they should not. This should only be a minor change, but please upgrade your caf_trigger version to p21-br-57
• p21-br-54 Dec 5, 2008: Some minor bug fixes, shouldn't have any significant effect.
  Fixed a minor problem that a prescaled v16 mu+jets trigger was accidentally included in the ORing (see my email about Winter2009 trigger efficiency Part 2), it's now removed from the ORing.
  Updated the v16 EM/MU MegaOR trigger list (only partially) and asked Ike to continue updating the list. This task is not that urgent since MegaOR has a few hundred triggers, missing 10-20 triggers shouldn't be a problem.
• p21-br-53 Nov 26, 2008: Finally, part 2 is ready. SPCs, configs & setup are all in the usual places, please update to latest vjets_cafe and caf_trigger p21-br-53.
  V16 muon trigger turn-ons are now complete: Single MU OR, MuJets_OR, Mu Super-OR, matching routine also updated.
  Note: we added more triggers to Single MU OR, thus efficiencies increased by ~5% compared to previous release. Super-OR efficiency also increased by roughly the same amount (compared to v15). One caveat: one mu+jets trigger (auxiliary trigger with low rates, not main signal trigger) is prescaled for lumi > 200E30, this has not been taken into account by MuJets_OR (or Super-OR) yet, thus the overall efficiency may be slightly overestimated. We expect the effect to be small, especially in the Super-OR case (there the effect probably aren't even noticeable since majority of the events are taken by Single MU triggers). Single MU OR is not affected of course.
  The list for v16 EM triggers has been updated, as well as v16 e+jets matching routine (minor changes).
• p21-br-51 Nov 19, 2008: v16 trigegr efficiency for the Moriond2009 dataset.
• p21-br-48 June 18, 2008: Codes cleaning, minor fixes for EJets & EJetsORSingleEMOR processor
• p21-br-45 June 16, 2008: Added support for v15 postshutdown dataset; Added safety check for runno.vs.triggerversion; Put all trigger SPCs into caf_trigger/parameters
• p21-br-44 June 6, 2008: Updated run to triggerlist conversion for em triggers
• p21-br-43 June 2, 2008: Major updates:
  1. Updated Run2b Muon OR SPCs for pre/post-shutdown data, located at caf_trigger/parameters/results_muor. These SPCs contain important bug fixes (especially in the eta> 1.6 region), previous users should switch to this version immediately. Thanks to Ike and Jorge for the debugging!
     Note that this version currently does not contain v16 data, we will implement the v16 trigger turn-ons in the next release (which should happen in a week or so).
  2. Three caf_trigger weights (per event) are saved when super-OR processor is run: SingleLeptonOR, Lepton+jets, Lepton Super-OR, users can access them via event.get() method:
     event.get(caf_triggerWeight_$channel,...)
     where $channel can be: EJetsOR_p20/p17, SingleEMOR_p20/p17, EJets_p20/p17 and MuJetsOR_p20/p17, SingleMUOR_p20/p17, MuJets_p20/p17. (see vjets_cafe/configs/trigger/*TriggersOR*.config for details)
  3. Ken Herner updated Probablity_nMuon process so one can apply a single muon trigger with an isolation requirement.
  4. Other updates: runvstriglistX100.txt updated (until v16.05); Run2a v8-v11 Single EM OR lumi number fix (from Mark Owen); v8-v11 electron super-OR SPCs fix (from Robert Wagner).
  Again, just a reminder, caf_trigger is backward compatible, i.e. you can use p21 branch to run both p17 and p20 jobs, for this reason, there will be minimum p18 branch update in the future. If you do encounter a problem when using p21 branch to run your p17 jobs, please let me know right away. Vjets_cafe v01-07-03 is recommended to use together with this new tag.
• p18-br-25, p21-br-40 Apr 4, 2008:
  • p17 --- JES conversion tool added which enables us to apply preliminary JES turn-ons to final JES jets, many thanks to Alexander Kupco for providing the prototype of the tool. Preliminary tests show no siginificant changes in the average trigger efficiencies (before and after the JES conversion) but some shape differences at low pT are expected, analysers are encouraged to try it out and send feedback.
    For details, see Liang's talk at TSG meeting
    It is currently only done for Run2a, i.e. only for SPCs from "jet_eff/p17.09.03".
  • p20 --- Updated Run2b Single Muon OR SPCs released (preshutdown data, located at caf_trigger/parameters/results_muor). Those SPCs were generated with a better sample (more statistics and minimal isolation bias) and with optimized binning, all isolation points are available (from deltaR to NPTight). A new trigger epoch (v15.6) was added to reflect the change in L3 tracking. We also included 3D parameterization (as in pT, eta, phi) as a test release (2D parameterization is still the default selection).
    Vjets_cafe v01-06-04 is recommended to use those new SPCs.
  • Other update: updated runvstriglistX100.txt from Marc-Andre (thanks).
• p21-br-37 Feb 20, 2008: Adding JetActAs Switch to control which JES correction is applied to jet energy when applying jet turn-on curves
• v04-00-06 : Take care of underflows and overflows for trigger efficiencies. Set values to last bin entry if actual value is > highest bin or < lowest bin. Allow matching in DPhi only for L3 to offline objects.
• v04-00-05 : ixed bugs in v12-13 E3_* triggers and v13 (not v12) E2_SHT20, found by Marc
• v04-00-03 : TriggerTermMap : feature update by Mikko Voutilainen. Consider the blank space a valid separator for .JetVars. New processor for calculating the jet trigger efficiencies in inclusive jet trigger cross section measurement.
• v04-00-02 : Proper matching to L3 tracks requires a veto on a specific experimental L3 track tool. This is fixed in this version.
• v04-00-01 : An important bug fix for the MuonTriggerMatch processor. Matching to L3 muon was done irrespective of the muon tool name, thus matching to both MUON and MUON_CM tools, which leads to a several percent overestimate of the matching efficiency.
• v04-00-00 : This version has the ability to vary the curves up by one sigma and down by one sigma, thereby giving you a conservative estimate on the systematic uncertainty for the mu+jets and e+jets analyses.
• v02-04-17 : It was found that someone reintroduced a serious bug in caf_trigger that completely corrupts all efficiencies parameterized as a function of vertex z. (One example: L3 track trigger efficiencies.) All versions from v02-04-09 to v02-04-16 are affected and should not be used. Updates for L[1,2,33]JetTerms and the JetTriggerMatch processor.

  ---

  shary
  Last modified: Mon Jun 15 10:07:23 CDT 2009