-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sequence-based simplified HLT phase2 menu. #44025
Sequence-based simplified HLT phase2 menu. #44025
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44025/38955
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44025/38956
|
A new Pull Request was created by @rovere for master. It involves the following packages:
The following packages do not have a category, yet: 24834.0_TTbar_14TeV+2026D98/genericPhase2SinglePath.py @cmsbuild, @mmusich, @Martin-Grunewald can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@cmsbuild please test |
I'm not sure why the bot is convinced that we need a new package. The file he is complaining about is part of the git history (and was needed while developing the PR), but it is not part of the final set of changes of this PR. |
Remove and force-push? |
Do we need the whole history? Otherwise squash the commits to 1. |
Ciao @mmusich @Martin-Grunewald I added to the git history for a reason and would rather have it in. |
Hmm, the bot should not create a |
@rovere This PR touches 430 files, thus causing the bot to fail. If this is intentional, I think the best course of action would be to split it this PR two or more - e.g., move 1a2126e into a separate PR and remove it from history. You can use |
Ciao @iarspider thanks for your reply.
|
@rovere In order to reduce the number of GitHub API calls used per PR, the bot keeps a cache of some information regarding the PR (list of all commits, including squashed; list of files changed in each commit; reactions). That information is stored inside a comment, and thus is limited to 65k bytes. The bot will fail, i.e. it will not process a PR, if cache size is too big to be stored. |
-1 Failed Tests: RelVals RelVals
|
Pull request has been put on hold by @mmusich |
Ciao @mmusich thanks for these further checks. For completeness, these are the changes I made to the collections (to try and have a uniform approach and naming convention, far from being finalized, yet):
I wrote a Python script that compares the entries (and their members) of these collections before/after the PR, and they are identical. On a side note, I just realized that the new naming convention is such that the Should we consider this as a shower-stopper for this PR to be merged or can we have another PR to fix this? |
Thanks @rovere for the checks.
Can you link this from here?
Let's go ahead, but please open a bug-fix PR as soon as possible. |
unhold |
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. @rappoccio, @sextonkennedy, @antoniovilela (and backports should be raised in the release meeting by the corresponding L2) |
It is bread and butter, but it helped quite a bit: |
REMINDER @rappoccio, @sextonkennedy, @antoniovilela: This PR was tested with #44041, please check if they should be merged together |
Let's move on with this, but for our knowledge: what is automatically generated and what is manually maintained from the 430 files? |
+1 |
|
we're not using confDB (yet) for phase-2, so this is completely manual (of course I guess @rovere used scripts to adjust and cross-check the configurations) @antoniovilela |
@antoniovilela I mentioned the script used in the PR description. It is called |
I guess what I wanted to make sure (just because of my current hat in ORP) is that there is no risk of affecting modules that can be used outside of the Phase 2 processing. I guess so, but it does not hurt to confirm. |
PR description:
This (large) PR is a rewrite of the Simplified Phase2 HLT Menu using sequences and abandoning the
cms.ConditionalTask
s almost completely. The notable exceptions are the Muons paths for which more expert help is needed to perform this transition.The
timing
variant of the menu has been updated to include the recent move to L1P2GT and converted to using sequences as well.Some of the
pset
configurations have been included in the PR even if they contain 0 changes. This is due to how the tooledmConfigSplit
internally dumps thosepset
s. Rather than chasing all of them one by one, I decided to let it do its job.Unused modules have been removed. If needed, they could be extracted from git.
PR validation:
Run before/after this PR on some 100 events and the results are identical.
All paths have been tested one-by-one to verify that they could run alone, w/o any other paths present.