From e6401c39dec9a07fc8fdf836983cc03f141306c7 Mon Sep 17 00:00:00 2001 From: Matt Kramer Date: Wed, 20 Mar 2024 08:03:33 -0700 Subject: [PATCH] Increase max_contrib_segments to 300 In MR5 there were six files where the previous value of 200 was insufficient. This change should go into `develop` but the memory/storage implications should be studied first. --- yamls/proto_nd_flow/reco/charge/CalibHitMerger.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/yamls/proto_nd_flow/reco/charge/CalibHitMerger.yaml b/yamls/proto_nd_flow/reco/charge/CalibHitMerger.yaml index 23ca7173..703f9ebb 100644 --- a/yamls/proto_nd_flow/reco/charge/CalibHitMerger.yaml +++ b/yamls/proto_nd_flow/reco/charge/CalibHitMerger.yaml @@ -13,7 +13,7 @@ params: # inputs events_dset_name: 'charge/events' hits_name: 'charge/calib_prompt_hits' - max_contrib_segments: 200 + max_contrib_segments: 300 merge_cut: 65 # merge hits with delta t < merge_cut [CRS ticks] max_merge_steps: 50 # max number of iterations when merging # adjacent packets in time on the same channel