vincecr0ft
commented
9 years ago I currently apply the following filters... GRLFilter CoreFlags EmbeddingPileupPatch averageIntPerXingPatch PileupTemplates RandomSeed BCHSampleRunNumber RandomRunNumber Triggers PileupReweight PriVertex LArError TileError TileTrips JetCopy JetCalibration JetIsPileup LArHole JetCleaning PileupScale MCWeight JetPreselection NonIsolatedJet JetSelection BCHCleaning TauVeto (NEW)
DiLeptonSelection (To Be Added) OppositeSignLeptons (To Be Added)
Have I removed any filters that I really shouldn't have? e.g. the met recalculation. and HiggsPT and MCWeight.
Are there any of these that I would need to modify to make them fit leplep?
qbuat
most of my actions are concerned with applying event selection filters in higgstautau/leplep/filters.py mimicking the selection procedure in the leplep code seen here: https://svnweb.cern.ch/trac/atlasphys/browser/Physics/Higgs/HSG4/software/leplep/MVA_8TeV/Preselection/trunk/Common/analysis.C
the required filters are listed as
Cut[0] = "begin"; Cut[1] = "GRL/Filt"; Cut[2] = "trigger"; Cut[3] = "primVtx"; Cut[4] = "jet-clean"; Cut[5] = "LArError"; Cut[6] = "tau-veto"; Cut[7] = "2-lepton"; Cut[8] = "OS"; Cut[9] = "trigMatch"; Cut[10] = "AuxiCut";
I believe that cuts 1-5 are already implemented in hhntup but when I start checking the trigger matching code I will also check the trigger cut mentioned here. I guess the primary Vertex calculation will remain the same?
I've already implemented a TauVeto (minus some overlap information) And shares many similarities with the Tau selection criteria in higgstautau/filters.py but is isolated such that it only effects the leplep specific code.
Next I implement the selection of 2 leptons and the requirement that these be opposite sign. This should be done before the weekend.