Adding 2025 Data Wfs#48281
Conversation
|
cms-bot internal usage |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48281/45123
|
|
A new Pull Request was created by @AdrianoDee for master. It involves the following packages:
@AdrianoDee, @Moanwar, @cmsbuild, @DickyChant, @miquork, @srimanob, @subirsarkar can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
| # the files used as input | ||
|
|
||
| ###2025 | ||
| pds_2025 = ['BTagMu', 'DisplacedJet', 'EGamma0', 'HcalNZS', 'JetMET0', 'Muon0', 'MuonEG', 'NoBPTX', 'ParkingDoubleMuonLowMass0', 'ParkingHH', 'ParkingLLP', 'ParkingSingleMuon0', 'ParkingVBF0', 'Tau', 'ZeroBias','JetMET1'] |
There was a problem hiding this comment.
Sure, do I remember correctly and for 2024 this would not be possible since some inputs are missing? To understand if I have to touch 2024 too.
There was a problem hiding this comment.
and for 2024 this would not be possible since some inputs are missing? To understand if I have to touch 2024 too.
that's correct, for 2024 we had to workaround to get an input file done by hand for 145.415.
There was a problem hiding this comment.
It's included now, for testing it here we'll have to wait the RAW are copied to disk to CERN.
| @@ -2306,6 +2321,8 @@ def lhegensim2018ml(fragment,howMuch): | |||
|
|
|||
| steps['HLTDR3_2024']=merge( [ {'-s':'L1REPACK:Full,HLT:@%s'%hltKey2025,},{'--conditions':'auto:run3_hlt_relval'},{'--era' : 'Run3_2024'},steps['HLTD'] ] ) | |||
There was a problem hiding this comment.
if we have 2025 data maybe we send back this to use hltKey2024 (though the new 2025 relvals should get into the short matrix).
There was a problem hiding this comment.
I'd prefer to keep it with 2025 for the moment until we accumulate some more eras in 2025 since the bulk of the data validations would still be done with 2024 data. I'd turn it back to 2024 by 15_1_0_pre5 at the latest.
|
test parameters:
|
|
please test |
AdrianoDee
force-pushed
the
data_2025_wfs
branch
from
05279db to
1010209
Compare
cmsbuild
added
tests-pending
code-checks-pending
and removed
tests-started
code-checks-approved
labels
|
please abort |
|
please test |
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48281/45126
|
AdrianoDee
force-pushed
the
data_2025_wfs
branch
from
1010209 to
3c3854f
Compare
|
please test |
cmsbuild
added
pdmv-pending
tests-started
code-checks-pending
and removed
tests-approved
pdmv-approved
code-checks-approved
labels
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-48281/45243
|
|
Pull request #48281 was updated. @AdrianoDee, @Moanwar, @DickyChant, @miquork, @srimanob, @subirsarkar can you please check and sign again. |
|
+1 Size: This PR adds an extra 72KB to repository Comparison SummarySummary:
|
|
+pdmv
|
|
+Upgrade |
cmsbuild
added
fully-signed
upgrade-approved
and removed
pending-signatures
upgrade-pending
labels
|
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, @mandrenguyen, @antoniovilela, @sextonkennedy (and backports should be raised in the release meeting by the corresponding L2) |
|
+1 |
5 participants
This PR proposes to add a few new wfs for 2025 data. At the moment only
Run2025BandRun2025Care really functional, being the only eras for which some certification is available in https://cms-service-dqmdc.web.cern.ch/CAF/certification/. Still the workflows are defined up to an hypothetical era 2025I so that they are ready to be used for the RelVals.Also, for the moment, I'd keep the 2024 wfs running the 2025 HLT key since we use them in release validation and I'd prefer to accumulate some eras before turning them back to the fake menu. The same applies to online/offline conditions: I'd keep around the 2024 data (F,G,H,I) wfs using the online ones.