Implement MIP Timing Detector reconstruction sequence for Phase-2 HLT #51170
Implement MIP Timing Detector reconstruction sequence for Phase-2 HLT #51170mmusich wants to merge 7 commits into
Conversation
|
cms-bot internal usage |
|
A new Pull Request was created by @mmusich for master. It involves the following packages:
@AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @cmsbuild, @ctarricone, @davidlange6, @fabiocos, @ftenchini, @gabrielmscampos, @kfjack, @mandrenguyen, @miquork, @mmusich, @rseidita, @sroychow can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
test parameters:
|
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 252KB to repository Comparison SummarySummary:
|
|
test parameters:
|
|
@cmsbuild, please test |
|
Pull request #51170 was updated. @AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @cmsbuild, @ctarricone, @davidlange6, @fabiocos, @ftenchini, @gabrielmscampos, @kfjack, @mandrenguyen, @miquork, @mmusich, @rseidita, @sroychow can you please check and sign again. |
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 172KB to repository Comparison SummarySummary:
|
|
+hlt |
PR description:
The goal of this PR is provide the configuration to run the MTD reconstruction (from local reconstruction down to 4D vertexing with mass hypothesis) in the Phase-2 HLT. The configuration parameters are taken from the respective offline sequences.
Such setup can be enabled by using the novel
mtd_at_hltprocess modifier and it is not active by default.This development is purely meant to help POG developers when willing to use MTD information at HLT.
To this effect I provide a new runTheMatrix workflow (with offset
.7522) in order to be able to test it. The workflow is for convenience included in theph2_hltrelval matrix.Together with the HLT configuration I also enable basic 4D vertexing validation (together the minimal changes needed to make it run together with the HLT step). Some configuration is provided to be able to run also the
MTDTrackValidationbut more work is needed to enable in workflows it in order to protect failures upon missing input (that might happen in the HLT as we don't run the same reconstruction on all the events).PR validation:
I've run successfully the new workflow
runTheMatrix.py -l 34434.7522 -t 4 -j 8and observed in the resulting DQM file the expected plots for the 4D vertices.I also benchmarked this configuration using a NGT node equipped with 2x AMD EPYC 9534 64-Core Processor + 4x NVIDIA L40S GPUs using 16 jobs with 16 threads/streams each by using the following script:
The resulting pies are available here:
The overall cost of the addition is definitely not negligible +536 ms, out of which:
unassignedin the plots above), withhltTrackExtenderWithMTDbeing the largest contributor.hltUnsortedOfflinePrimaryVertices4D)If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:
Not a backport, it might be backported to CMSSW_20_0_X for MC production purposes.
Cc: @cms-sw/mtd-dpg-l2