-
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
DeepSC algorithm for ECAL SuperClusters #37115
Conversation
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37115/28616 |
A new Pull Request was created by @valsdav (Davide Valsecchi) for master. It involves the following packages:
@jpata, @cmsbuild, @clacaputo, @slava77 can you please review it and eventually sign? Thanks. cms-bot commands are listed here |
81edc20
to
99e4170
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37115/28618
|
Pull request #37115 was updated. @jpata, @cmsbuild, @clacaputo, @slava77 can you please check and sign again. |
99e4170
to
e4b67eb
Compare
+code-checks Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-37115/28619
|
Pull request #37115 was updated. @jpata, @cmsbuild, @clacaputo, @slava77 can you please check and sign again. |
test parameters: |
could you add a new test workflow with the modifier? |
Which number should be used for the test WF? |
AFAIk you can pick any number that is not already used by something else. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-80034b/25522/summary.html Comparison Summary@slava77 comparisons for the following workflows were not done due to missing matrix map:
Summary:
|
Dear @reconstruction-l2, @pdmv-l2 @operations-l2, @upgrade-l2 after the latest small improvement, on our side we are satisfied about the PR status. If you also are, can you please sign at your convenience? Thanks! |
+Upgrade |
+reconstruction
|
@cms-sw/pdmv-l2 changes since your last signature are minimal, and all included in this commit |
@cms-sw/pdmv-l2 if you have any remaing doubt, could you please report it here, so that we know we must wait for them being solved? Otherwise, could you please re-sign before the tests expire? |
+pdmv |
+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:
The PR introduces the implementation of the DeepSC algorithm in the ECAL SuperCluster reconstruction sequence.
The algorithm is based on graph NNs and it is evaluated through the vanilla CMSSW Tensorflow interface.
Three modules have been implemented to handle the ECAL PFClusters as a graph and to encapsulate the evaluation of the DeepSC algo.
A separate PR (cms-data/RecoEcal-EgammaClusterProducers#2) has been created for the model data.
A summary of the features implemented in the PR and the relative validation can be found at:
https://indico.cern.ch/event/1129736/#5-dnn-superclustering
The algorithm is intended to replace the Mustache (not in the short term) and it is OFF by default in the PR. It can be switched ON by the
ecal_deepsc
process modifier.The DeepSC algorithm has been presented in ECAL, PF and ML group meetings. More documentation and details can be find in the links below.
Recent talks and documentation:
PR validation:
No changes are expected in any standard workflow. The DeepSC model is only activated by the run3_ecalclustering process modifier. A summary of the features implemented in the PR and the relative validation can be found at:
https://indico.cern.ch/event/1129736/#5-dnn-superclustering
Added runTheMatrix workflow 11846.19 on Zee_14TeV.
Profiling
11846 workflow: 2021PU+ZEE_14TeV_TuneCP5_GenSim+DigiPU+RecoNanoPU+HARVESTNanoPU
11846.0 standard reco:
comment: I am not able to find a reference to the PFECALSuperCluster producer in the profiler output, probably given the small footprint of the standard Mustache.
11846.19 DeepSC SuperClusters
comment: evaluate the DeepSC takes 3.8% of the CPU time (https://dvalsecc.web.cern.ch/cgi-bin/igprof-navigator/DeepSC/step3_igprofCPU_w11846.19/100) , whereas the memory footprint is rather small 0.46% (https://dvalsecc.web.cern.ch/cgi-bin/igprof-navigator/DeepSC/step3_igprofMEM99_w11846.19/809).