From 263ef287177c7994c2329ec253042a2a9d9fd2db Mon Sep 17 00:00:00 2001 From: Sandro Wenzel Date: Thu, 12 Mar 2026 16:03:05 +0100 Subject: [PATCH] Event-pools: Consistency fix for vertexing For event pools, the vertex applied to events should (0,0,0). We tried to do this by setting 'kNoVertex' to the collision context... which unfortunately was not doing what we wanted. Instead of putting (0,0,0) this simply does not put a vertex into the collision context. This lead to the consequence that the vertex was fixed during event generation later. Problem fixed by imposing `kNoVertex` also on the event generation step **in case of event pool generation**. --- MC/bin/o2dpg_sim_workflow.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MC/bin/o2dpg_sim_workflow.py b/MC/bin/o2dpg_sim_workflow.py index e793f17f6..9126bd4e9 100755 --- a/MC/bin/o2dpg_sim_workflow.py +++ b/MC/bin/o2dpg_sim_workflow.py @@ -615,7 +615,7 @@ def getDPL_global_options(bigshm=False, ccdbbackend=True, runcommand=True): # No vertexing for event pool generation; otherwise the vertex comes from CCDB and later from CollContext # (Note that the CCDB case covers the kDiamond case, since this is picked up in GRP_TASK) vtxmode_precoll = 'kNoVertex' if args.make_evtpool else 'kCCDB' -vtxmode_sgngen = 'kCollContext' +vtxmode_sgngen = 'kNoVertex' if args.make_evtpool else 'kCollContext' # preproduce the collision context / timeframe structure for all timeframes at once precollneeds=[GRP_TASK['name']]