From e6a235be99d1a0875e6a874bf634b7e320dea683 Mon Sep 17 00:00:00 2001 From: aferrero2707 Date: Tue, 18 Feb 2025 11:29:31 +0100 Subject: [PATCH] [MUON] added option for storing nCandidates in the MFT-MCH matching The number of candidates to be stored is specified in the `MUON_MATCHING_NCANDIDATES` environment variable. By default the variable is not set, and no option is passed to the global forward matching workflow for storing multiple candidates. Hence the default behaviour of the forward matching is unchanged. --- DATA/common/setenv.sh | 3 +++ 1 file changed, 3 insertions(+) diff --git a/DATA/common/setenv.sh b/DATA/common/setenv.sh index 2f11efdf8..3cefedeca 100755 --- a/DATA/common/setenv.sh +++ b/DATA/common/setenv.sh @@ -169,6 +169,9 @@ ITSMFT_STROBES="" [[ ! -z ${ITS_STROBE:-} ]] && ITSMFT_STROBES+="ITSAlpideParam.roFrameLengthInBC=$ITS_STROBE;" [[ ! -z ${MFT_STROBE:-} ]] && ITSMFT_STROBES+="MFTAlpideParam.roFrameLengthInBC=$MFT_STROBE;" +MFTMCH_NCANDIDATES_OPT= +[[ ! -z ${MUON_MATCHING_NCANDIDATES:-} ]] && MFTMCH_NCANDIDATES_OPT+="FwdMatching.saveMode=3;FwdMatching.nCandidates=${MUON_MATCHING_NCANDIDATES};" + # Set active reconstruction steps (defaults added according to SYNCMODE) for i in `echo $LIST_OF_GLORECO | sed "s/,/ /g"`; do