*** empty log message ***
*** empty log message ***
*** empty log message ***
1) implemented a way to store the bitset of all matched triggers for the leptons in the FO branches (using TBits, since root doesn't seem to yet support bitsets). See some commented lines in applyZPlusX.cc and ZPlusX.cc (more or less moot -- see below) 2) These bitsets are almost entirely zeroes, but root didn't compress them as much as I was hoping -- adding them tripled the file size, so I had to implement another way to store trigger info in the ntuples. I decided to store info for only a few triggers in an unsigned value in SimpleLepton, with the def of the bits at the bottom of TriggerUtils.cc in the function initAnalysisTriggers (http://cmssw.cvs.cern.ch/cgi-bin/cmssw.cgi/UserCode/MitHzz4l/Util/src/TriggerUtils.cc?r1=1.15&r2=1.16) 3) added the same (info for a few triggers) for HLT Info to an unsigned value in InfoStruct 4) added all versions of the emu cross triggers to TriggerUtils.cc
Add denominator def with Dz and D0 but no IP, move some things from Various to PlotHeaders, clean up plotters
*** empty log message ***
Added a PlotHeader that my plot exe's use heavily, and cleaned up the plotters. Cleaned up my fake rate code so it almost all runs off of ntuples made by applyZPlusX in one of either ZPlusF or ZPlusFF mode, rather than different selectors. Added a plotter for their fakes, NonMCBackground/src/plotTheirFakes.cc Made some adjustments to fake selector to be in sync tih ZPlusX and vice versa. Removed all the json_spirit and RunLumiRangeMap stuff from Util -- it was only there because we were compiling without MitCommon, now that we pick up MitCommon, it just causes problems to have this in two different places.
*** empty log message ***
*** empty log message ***
switch json file to arg, add in npu, switch to new denom
move PU stuff to selectionFuncs, add 2012
*** empty log message ***
*** empty log message ***
*** empty log message ***
*** empty log message ***
*** empty log message ***
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, select a symbolic revision name using the selection box, or choose 'Use Text Field' and enter a numeric revision.