Standalone setup for running MAHI debugger for pulse display Checkout a CMSSW release (140X for Run3 2024) and use the env to run the below commands.
- First, find where an event of interest is using
edmPickEvents.py
.
edmPickEvents.py "/JetMET0/Run2024B-v1/RAW" 379058:426:82018200
- Second, run the command output to the terminal from the first command:
edmCopyPickMerge outputFile=pickevents.root \
eventsToProcess=379058:82018200 \
inputFiles=/store/data/Run2024B/JetMET0/RAW/v1/000/379/058/00000/974bdcae-ff6c-458d-b199-64441159c8e1.root
-
Use CMSSW and the provided python config to run on the
pickevents.root
in order to run the MAHI debugger and make flat ntuple with useful output to plot. This will yield yet another ROOT filemahidebugger.root
. N.B. There is a bug in the MahiDebugger that needs to be resolved locally. The description at https://cmssdt.cern.ch/lxr/source/RecoLocalCalo/HcalRecAlgos/test/MahiDebugger.cc#L368 needs to readthEnergeticPulses
(plural). So check out this package locally and build. -
Assuming knowledge of the iphi and ieta of interest, edit
pulsedisplay.C
to print out specifically for that tower and run.
root pulsedisplay.C