-
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
Add ScoutingMuonNoVtx and ScoutingMuonVtx in Run3Scouting Nano starting from 2024 data taking #44970
Add ScoutingMuonNoVtx and ScoutingMuonVtx in Run3Scouting Nano starting from 2024 data taking #44970
Conversation
cms-bot internal usage |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44970/40251
|
A new Pull Request was created by @patinkaew for master. It involves the following packages:
@rappoccio, @hqucms, @fabiocos, @vlimant, @antoniovilela, @cmsbuild, @davidlange6 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
@@ -0,0 +1,3 @@ | |||
import FWCore.ParameterSet.Config as cms | |||
|
|||
run3_scouting_nanoAOD_post2023 = cms.Modifier() |
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.
please remove the intermediate run3_scouting_nanoAOD_post2023
modifier, unless there's a citable policy to do so
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.
Sorry I might be completely wrong here. From here, I understand that top level like Run3
as ModifierChain
has no method like toModify
or toReplaceWith
. Therefore, I create run3_scouting_nanoAOD_post2023
as Modifier
and call toReplaceWith
to replace the tables.
please include a test workflow in the nano matrix |
enable nano |
our initial comment in #44817 about having |
@patinkaew : please go ahead and modify back to |
This is what was already done in #43761 (now amended to comply with PPD prescription). This PR could simply piggy-back on that one (once merged). |
Thanks. I'm waiting for #43761 to get merged and then I will make changes accordingly. |
@patinkaew, #43761 is now merged. |
8e75a28
to
c71b006
Compare
@vlimant, I rebased to latest IB release (CMSSW_14_1_X_2024-06-12-1900) with #43761 merged and changed from I re-validated this change with
and the output NanoAOD file looks good. |
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-44970/40563 |
Pull request #44970 was updated. @hqucms, @fabiocos, @rappoccio, @antoniovilela, @ftorrresd, @davidlange6, @vlimant, @cmsbuild can you please check and sign again. |
thanks. next step is to add the nano in the scouting scenario for that era. @drkovalskyi ; what is the scenario currently being run on the scouting dataset, if any ? |
ping again. |
+Upgrade |
+pdmv |
please test |
+1 Size: This PR adds an extra 12KB to repository Comparison SummarySummary:
NANO Comparison SummarySummary:
Nano size comparison Summary:
|
@mandrenguyen do you think we can get this by having ORP signing for operations? (TSG / Scouting request @kelmorab @elfontan ). |
+1 |
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 be automatically merged. |
PR description:
This PR adds two versions of scouting muon collections, ScoutingMuonNoVtx and ScoutingMuonVtx, following this change CMSHLT-3089:Add hltScoutingMuonPackerVtx to Scouting EventContent.
This fixes issue Missing "hltScoutingMuonPacker" in ScoutingNANO using recent Run-3 data#44817.
This PR also introduces
run3_scouting_nanoAOD_post2023
Modifier used to modify configuration and top levelRun3_post2023
ModifierChain based onRun3
withrun3_scouting_nanoAOD_post2023
Modifier.PR validation:
Tested by producing scouting NanoAOD from a 2024 scouting HLTSCOUT datatier file using the following
cmsDriver.py
command: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:
This PR is not a backport, but backport to 140X will follow.
cc: @elfontan @karim @silviodonato @vlimant