-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update the autoSkim.py for the Run3 skims and removed unused PD #38792
Conversation
@sam7k9621, CMSSW_12_5_X branch is closed for direct updates. cms-bot is going to move this PR to master branch. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38792/31148
|
A new Pull Request was created by @sam7k9621 for master. It involves the following packages:
@cmsbuild, @bbilin, @kskovpen, @jordan-martins can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@sam7k9621 this is not true, we need these things in 12_4_X -- that is the release for data taking |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-38792/31149
|
'BTagMu' : 'LogError+LogErrorMonitor', | ||
'HTMHT' : 'LogError+LogErrorMonitor', | ||
'JetHT' : 'JetHTJetPlusHOFilter+LogError+LogErrorMonitor', | ||
'DisplacedJet' : 'EXODisplacedJet+EXODelayedJet+EXODTCluster+EXOCSCCluster+LogError+LogErrorMonitor', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
T0 only has
"EXODisplacedJet", "LogError", "LogErrorMonitor"
so EXODelayedJet+EXODTCluster+EXOCSCCluster
needs to be added for Run-3 from T0, is that correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, those are the new skims for Run3.
However, EXOCSCCluster has not yet been merged (#37782)
I have already notified the L2 convener to review the PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
However, EXOCSCCluster has not yet been merged
So these are the real kind of problems... How is expected to be used in the data taking with 12_4_X when the 12_5_X is not even merged? Why is #37782 not made urgent? Is there a request from PdmV to have a new release which includes this? (These are not really questions to you @sam7k9621 but more @bbilin @kskovpen @rappoccio )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will make it urgent
'BTagMu' : 'LogError+LogErrorMonitor', | ||
'HTMHT' : 'LogError+LogErrorMonitor', | ||
'JetHT' : 'JetHTJetPlusHOFilter+LogError+LogErrorMonitor', | ||
'DisplacedJet' : 'EXODisplacedJet+EXODelayedJet+EXODTCluster+EXOCSCCluster+LogError+LogErrorMonitor', | ||
'MET' : 'EXOHighMET+EXODelayedJetMET+LogError+LogErrorMonitor', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
T0 only has
"EXOMONOPOLE", "HighMET", "LogError", "LogErrorMonitor"
so EXOHighMET+EXODelayedJetMET
should be added, and EXOMONOPOLE
to be removed from T0, correct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, those two skims are new for Run3
And the monopole skim has been updated to EGamma PD
'JetHT' : 'JetHTJetPlusHOFilter+LogError+LogErrorMonitor', | ||
'DisplacedJet' : 'EXODisplacedJet+EXODelayedJet+EXODTCluster+EXOCSCCluster+LogError+LogErrorMonitor', | ||
'MET' : 'EXOHighMET+EXODelayedJetMET+LogError+LogErrorMonitor', | ||
'SingleElectron' : 'LogError+LogErrorMonitor', #to be updated if we will have EGamma as Run-2 (2018), or splitting as 2016,2017 | ||
'SinglePhoton' : 'EXOMONOPOLE+LogError+LogErrorMonitor', #to be updated if we will have EGamma as Run-2 (2018), or splitting as 2016,2017 | ||
'DoubleEG' : 'LogError+LogErrorMonitor', #to be updated if we will have EGamma as Run-2 (2018), or splitting as 2016,2017 | ||
'EGamma':'ZElectron+WElectron+EXOMONOPOLE+LogError+LogErrorMonitor', | ||
'Tau' : 'LogError+LogErrorMonitor', | ||
'SingleMuon' : 'ZMu+LogError+LogErrorMonitor', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
T0 has
"MuonPOGSkim", "MuTau", "ZMu", "LogError", "LogErrorMonitor"
so should MuonPOGSkim
, MuTau
be removed from T0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, those skims are dropped during Run3
T0 also has are these not needed anymore? |
I didn't see DoubleMuonLowPU and ParkingDoubleMuonLowMass0 in the PD list for run3. (https://github.com/cms-sw/cmssw/blob/CMSSW_10_6_X/HLTrigger/Configuration/python/HLTrigger_Datasets_GRun_cff.py) |
Why are you looking at 10_6_X ?
So maybe time to add it to the autoSkim file too? Please also adress my comments in the code review |
Hi @tvami , I have added the backport toward 12_4_X |
Are there any workflows that actually run these skims btw? |
Thanks, please include its number in the PR description |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-572a3e/26337/summary.html Comparison SummarySummary:
|
ok so apparently nothing really tests the |
Hi @kskovpen , do you know which workflow we can test with the autoSkim? |
Unless I am mistaken, such workflows never existed. I wonder if we can try to integrate autoSkim within runTheMatrix.py. |
Yes it can be done, in AlCa we have the AlCaRECO matrix that's the same kind of object (PD --> AlCaRECO) cmssw/Configuration/AlCa/python/autoAlca.py Lines 1 to 34 in c850e19
here it's defined to have them all in for
which then is applied in a RelVal |
I'd like to invite you to join the Joint Ops meeting this Friday: In the gDoc there, please report the summary of this PR under "PDMV" bullet point. Thanks! |
@kskovpen will you sign this, or you'd like the relval to happen first? Ideally the backport of this should be merged by next Tuesday, so whichever is more realistic |
@sam7k9621 please confirm that you can make this, thanks |
A dedicated implementation of skim checks in relval wfs is expected to come later. It would be good to have it, finally. |
+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. @perrotta, @dpiparo, @qliphy, @rappoccio (and backports should be raised in the release meeting by the corresponding L2) |
Hi yes I would attend |
+1
|
Hi @sam7k9621 should not be there for Run-3. Can you please confirm? |
Changes propagated to T0 in dmwm/T0#4722 |
You are right, it should be removed. |
I think it's fine to do it when you deal with the v1.3 situation. On the other hand, you could also already start to do that, and get it merged in master, the point is that it should not get merged in the backport yet (the master it's fine any day) |
PR description:
Addressed the comments in #38479
12_4_X backport (#38795)
PR validation:
None
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: