Recent Updates to VS FrameWork

May 13th

  • Have implemented a new N-1 Plot Maker
    • Uses the Bits from the Paths to make N-1 Plots
    • Stores them using TFileService?
    • Completely configurable:
nMinus1PlotMaker = cms.EDAnalyzer('NMinus1PlotMaker',
    #Make me more specific if more TriggerResults exist
    src = cms.untracked.InputTag('TriggerResults'),

    #A list of paths by name to skip
    toSkipNames = cms.untracked.vstring(
        'genMuGt40Skim',
        'gen2mEtaSkim',
        'hltMuSkim'
    ),
    toSkipBits = cms.untracked.vuint32( 0,3,6,7,8,10,11 ),   #A list of paths by bit to skip

    #Must inherit from reco::Candidate:
    plotsInfo = cms.untracked.VPSet(
        cms.PSet(
            src = cms.untracked.InputTag("zToElpElm"),
            plotVariable = cms.untracked.string("mass"),
            nbins = cms.untracked.uint32(50),
            low = cms.untracked.double(31.19),
            high = cms.untracked.double(151.19),
            title = cms.untracked.string("Z-Mass"),
            xtitle = cms.untracked.string("M_{Z} [GeV]")
        ),
        cms.PSet(
            src = cms.untracked.InputTag("zToElpElm"),
            plotVariable = cms.untracked.string("pt"),
            nbins = cms.untracked.uint32(50),
            low = cms.untracked.double(0),
            high = cms.untracked.double(200),
            title = cms.untracked.string("Z P_{T}"),
            xtitle = cms.untracked.string("P_{T} [GeV]")
        )
    ),
    debug = cms.untracked.bool(False)
)
  • Based completely on TriggerResults? :
TrigReport ---------- Path   Summary ------------
TrigReport  Trig Bit#        Run     Passed     Failed      Error Name
TrigReport     1    0       4498          0       4498          0 genMuGt40Skim
TrigReport     1    1       4498       4498          0          0 genElGt40Skim
TrigReport     1    2       4498       4498          0          0 gen2eEtaSkim
TrigReport     1    3       4498         15       4483          0 gen2mEtaSkim
TrigReport     1    4       4498         26       4472          0 hltMuSkim
TrigReport     1    5       4498       4007        491          0 hltElSkim
TrigReport     1    6       4498       4007        491          0 hltLepSkim
TrigReport     1    7       4498       4498          0          0 hltAllSkim
TrigReport     1    8       4498       4498          0          0 hltNoSkim
TrigReport     1    9       4498       2630       1868          0 zMassSkim
TrigReport     1   10       4498       4498          0          0 customPAT
TrigReport     1   11       4498       4498          0          0 hypoPath

May 12th

  • No longer have customPatLayer1 and customPatLayer0, now have single cff file: customPatSequence
  • HLT Matching is now done on the reco::Leptons instead of the layer0Leptons, changed our script accordingly
  • I made a new cff that includes our entire sequence. To use it, make a new cfg file like normal, define your input and output modules, and then add the following code (you can use :

#----------------------------- Begin Setup ------------------------------------
from VSConfiguration.StandardSequences.fullSequence_cff import *
vsSetup(process)
#------------------------------ End Setup -------------------------------------


#------------------------- Begin Path Setup ------------------------------------
process.outpath = cms.EndPath(process.out)
process.schedule = cms.Schedule()
process.schedule.extend(process.vsSchedule)
process.schedule.extend(cms.Schedule(process.outpath))
#-------------------------- End Path Setup -------------------------------------
You can find an example in VSConfiguration/StandardSequences/test/vsZExample_cfg.py
  • The Event Content style changed.

May 1st

  • Added Lepton Selection filters (both μ and electron) --> not checked in yet

April 29th

  • Added InputZmumuSummer08() to summer08RecoInputs_cfi for testing purposes
    (/Zmumu/Summer08_IDEAL_V11_redigi_v2/GEN-SIM-RECO)

-- RyanKelley - 2009/04/30

Topic revision: r6 - 2009/05/13 - 19:02:03 - MatthewLeBourgeois
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback