Remove trimmed tracking configuration for HLT Phase-2 - #51816
Conversation
|
cms-bot internal usage |
|
A new Pull Request was created by @JanGerritSchulz for master. It involves the following packages:
@AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @cmsbuild, @davidlange6, @fabiocos, @ftenchini, @kfjack, @mandrenguyen, @miquork, @mmusich, @sroychow can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
|
@JanGerritSchulz can you please tidy up also the readme file? https://github.com/cms-sw/cmssw/blob/master/Configuration/PyReleaseValidation/README.md?plain=1#L67 |
c1ef014 to
d4d59a3
Compare
Done! Thanks, I missed that one :-) |
|
Pull request #51816 was updated. @AdrianoDee, @DickyChant, @Martin-Grunewald, @antoniovagnerini, @cmsbuild, @davidlange6, @fabiocos, @ftenchini, @kfjack, @mandrenguyen, @miquork, @mmusich, @sroychow can you please check and sign again. |
|
test parameters:
|
|
great, this comes right in time for #51817 :) |
|
@cmsbuild, please test |
|
+1 Size: This PR adds an extra 88KB to repository Comparison SummarySummary:
AMD_MI300X Comparison SummarySummary:
AMD_W7900 Comparison SummarySummary:
NVIDIA_H100 Comparison SummarySummary:
NVIDIA_L4 Comparison SummarySummary:
NVIDIA_L40S Comparison SummarySummary:
NVIDIA_T4 Comparison SummarySummary:
Max Memory Comparisons exceeding threshold NVIDIA_H100@cms-sw/core-l2 , I found 1 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
Max Memory Comparisons exceeding threshold NVIDIA_L40S@cms-sw/core-l2 , I found 1 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
Max Memory Comparisons exceeding threshold NVIDIA_T4@cms-sw/core-l2 , I found 1 workflow step(s) with memory usage exceeding the error threshold: Expand to see workflows ...
|
|
+hlt
|
|
@cms-sw/pdmv-l2 kind reminder. |
|
+pdmv |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @mandrenguyen, @sextonkennedy, @ftenchini (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
PR description:
This PR is removing the trimmed tracking configuration for HLT Phase-2. This includes the procModifier
phase2_hlt_vertexTrimmingthat activates the tracking variant, all its custom HLT module configurations, and the related runTheMatrix workflow.This tracking option is largely outdated since newer tracking configurations like the current baseline outperform it with respect to timing and physics. Therefore from Tracking POG and HLT Upgrade sides, there is no motivation or need to keep it around any longer. Removing it simplifies maintenance and the intergration of new developments.
PR validation:
I ran a limited amount of tests locally using:
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.
FYI @VourMa @AdrianoDee