MET Reco: workaround to avoid unmerged CA
Work towards making !61689 (merged) pass. This time fixing MET reconstruction. Similar to !61828 (merged)
Merge request reports
Activity
added JetEtmiss NewConfig Reconstruction bugfix labels
This merge request affects 1 package:
- Reconstruction/MET/METReconstruction
This merge request affects 1 file:
- Reconstruction/MET/METReconstruction/python/METRecoCfg.py
Adding @goetz as watcher
added 23.0 review-pending-level-1 labels
- Resolved by Thomas Strebler
But where is
self.accumulator
consumed then? It will still stay unmerged (or am I missing something)?
This merge request affects 1 package:
- Reconstruction/MET/METReconstruction
This merge request affects 4 files:
- Reconstruction/MET/METReconstruction/python/METCalo_Cfg.py
- Reconstruction/MET/METReconstruction/python/METRecoCfg.py
- Reconstruction/MET/METReconstruction/python/METTrack_Cfg.py
- Reconstruction/MET/METReconstruction/python/METTruth_Cfg.py
Adding @goetz as watcher
mentioned in merge request !61689 (merged)
CI Result SUCCESS (hash 6ac1fb33)Athena externals cmake make tests Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 68845] CI Result SUCCESS (hash 7c65fcf0)Athena externals cmake make tests Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output [CI-MERGE-REQUEST-CC7 68852]added review-approved label and removed review-pending-level-1 label
added review-approved-tier0 label
added review-approved-point1 label
mentioned in commit 50cccae4
mentioned in merge request !61935 (merged)