Skip to content

MT Safe L1Topo Simulation Monitoring

Under the code migration for Athena master, we implemented MT safe monitoring for L1Topo simulation as discussed in the following L1Topo commissioning meeting. https://indico.cern.ch/event/912424/contributions/3837365/attachments/2025448/3388182/l1topo_sw_230420.pdf

Basically Gaudi/LockedHandle tool is used in Trigger/TrigT1/L1Topo/L1TopoSimulation/src/AthenaL1TopoHistSvc.cxx and histograms are initialized through the L1TopoAlgorithms by registerHist function as it is done before. Only new fillHist1D and fillHist2D functions are included and proceed for all relevant algorithms to fill the histogram in the event loop.

Although this is done by LockedHandle through the Trigger/TrigT1/L1Topo/L1TopoSimulation/src/AthenaL1TopoHistSvc.cxx in L1TopoSimulation, we kept the StandAlone tool Gaudi independent and filling histograms are proceeding by Trigger/TrigT1/L1Topo/L1TopoCoreSim/Root/StandaloneL1TopoHistSvc.cxx where TH1 and TH2 objects are stored and saved locally.

Job option is in the attach.

Cheers, Anil

cc @orlando , @cmorenom , @stelzer , @iriu

L1TopoSimStandAlone.py

P.S. New job option available in L1TopoSimulation/share/L1TopoSimulationTest.py
Changes are tested by : athena.py --threads=4 L1TopoSimulation/L1TopoSimulationTest.py --evtMax=1000
Related files can be found in this path : /afs/cern.ch/work/a/asonay/public/trig-test/

Edited by Anil Sonay

Merge request reports