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
GE21-ME21 segment reconstruction #39441
GE21-ME21 segment reconstruction #39441
Conversation
- Implement the GE21-ME21 segment reconstruction the same way as the GE11-ME11 segment reconstruction. - Add `fillDescription` to `GEMCSCSegmentProducer`. - Add `GEMCSCCoincidenceRateAnalyzer` for GEM-CSC coincidence rate study
-code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39441/32148
Code check has found code style and quality issues which could be resolved by applying following patch(s)
|
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-39441/32152
|
A new Pull Request was created by @slowmoyang (slowmoyang) for master. It involves the following packages:
@micsucmed, @emanueleusai, @ahmad3213, @cmsbuild, @AdrianoDee, @srimanob, @jfernan2, @clacaputo, @syuvivida, @pmandrik, @mandrenguyen, @rvenditti can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-774acf/27649/summary.html Comparison SummarySummary:
|
Hi @slowmoyang can you provide a recipe to test this PR? |
Hi @mandrenguyen, I tested this PR using cfg files here The step1-3 cfg files are the output of wf 42021.0 with a bit modification (removing redundant steps like cmsrel CMSSW_12_6_0_pre2
cd CMSSW_12_6_0_pre2/src
cmsenv
git-cms-merge-topic slowmoyang:ge21-me21-seg-reco__from-CMSSW_12_6_0_pre2
scram b
curl -OJ https://raw.githubusercontent.com/slowmoyang/GEM-Workspace/main/SW-Dev/220722_GE21-ME21-Segment-Reco/test/CMSSW_12_6_0_pre2/TenMu_phase2_realistic_T21/step1_GEN_SIM.py
curl -OJ https://raw.githubusercontent.com/slowmoyang/GEM-Workspace/main/SW-Dev/220722_GE21-ME21-Segment-Reco/test/CMSSW_12_6_0_pre2/TenMu_phase2_realistic_T21/step2_DIGI_L1TrackTrigger_L1_DIGI2RAW_HLT.py
curl -OJ https://raw.githubusercontent.com/slowmoyang/GEM-Workspace/main/SW-Dev/220722_GE21-ME21-Segment-Reco/test/CMSSW_12_6_0_pre2/TenMu_phase2_realistic_T21/step3_RAW2DIGI_RECO.py
curl -OJ https://raw.githubusercontent.com/slowmoyang/GEM-Workspace/main/SW-Dev/220722_GE21-ME21-Segment-Reco/test/CMSSW_12_6_0_pre2/TenMu_phase2_realistic_T21/step4_GEMCSCSegmentRECO.py
curl -OJ https://raw.githubusercontent.com/slowmoyang/GEM-Workspace/main/SW-Dev/220722_GE21-ME21-Segment-Reco/test/CMSSW_12_6_0_pre2/TenMu_phase2_realistic_T21/step5_Analysis.py
cmsRun step1_GEN_SIM.py
cmsRun step2_DIGI_L1TrackTrigger_L1_DIGI2RAW_HLT.py
cmsRun step3_RAW2DIGI_RECO.py
cmsRun step4_GEMCSCSegmentRECO.py
cmsRun step5_Analysis.py First of all, I'm okay to drop |
Also, wf42021.0 exists in the upgrade set. $ runTheMatrix.py --what upgrade --showMatrix | grep '42021\.0'
42021.0 2026D94PU+TenMuE_0_200_pythia8_GenSimHLBeamSpot+DigiTriggerPU+RecoGlobalPU+HARVESTGlobalPU |
I'm still trying to understand why this isn't tested in a relval workflow. Is there a plan to introduce |
GEMCSCSegment is being used in the online DQM for monitoring GEM efficiency, and this PR implements GE21-ME21 segment reconstruction for upcoming GE21 monitoring.
I added scripts for validation to this PR. The instruction can be found in the PR description.
I updated it. |
Pull request #39441 was updated. @perrotta, @rappoccio, @pmandrik, @mandrenguyen, @emanueleusai, @ahmad3213, @cmsbuild, @AdrianoDee, @srimanob, @jfernan2, @clacaputo, @syuvivida, @rvenditti, @micsucmed, @fabiocos, @davidlange6 can you please check and sign again. |
please test |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-774acf/28979/summary.html Comparison SummarySummary:
|
+1 |
+1
|
+Upgrade |
+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:
GEMCSCSegmentProducer::fillDescription
GEMCSCCoincidenceRateAnalyzer
for the GEM-CSC coincidence rate studyrunGEMCSCCoincidenceRateAnalyzer_cfg.py
andplotGEMCSCCoincidenceRate.py
to validateGEMCSCSegment
reconstruction codes. The instruction is shown in the PR validation part.PR validation:
Because
GEMCSCSegmentProducer
is not included in the standard reconstruction sequence, this PR cannot be validated byrunTheMatrix.py
.Therefore, wf 42021.0 was modified and used for the validation. The result was presented in the GEM DPG meeting.
via online DQM unittest
Also, because this PR touches
DQM/GEM
, this PR was valiated with the online DQM unit test. Logs and output files are here.cmsRun ${CMSSW_BASE}/src/DQM/Integration/python/clients/gem_dqm_sourceclient-live_cfg.py unitTest=True
via
runGEMCSCCoincidenceRateAnalyzer_cfg.py
andplotGEMCSCCoincidenceRate.py
This PR can be validated with
runGEMCSCCoincidenceRateAnalyzer_cfg.py
andplotGEMCSCCoincidenceRate.py
.runGEMCSCCoincidenceRateAnalyzer_cfg.py
takes RECO-tier files as input and then runsGEMCSCSegmentProducer
andGEMCSCCoincidenceRateAnalyzer
.GEMCSCCoincidenceRateAnalyzer
produces a root file containingTTree
. Then,plotGEMCSCCoincidenceRate.py
takes the resulting root file as input and produces efficiency plots.Results can be found here
The help message of
runGEMCSCCoincidenceRateAnalyzer_cfg.py
is as below. The era, global tag and geometry can be configured using arguments.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 will be backported.