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
[HGCAL] EDAnalyzer for TICL tracksters validation #33360
[HGCAL] EDAnalyzer for TICL tracksters validation #33360
Conversation
Code Format
For every CaloParticle that has been associated to a Trackster/MultiCluster, add a plot showing the fraction of the shared energy. The plot is filled once per CaloParticle by taking the Trackster/MultiCluster with the best score. This plot is useful to judge the quality of the score threshold in terms of effective shared energy.
Make it compile
Make it compile
It would be good to know if someone in the Track reco group has some problem with our changes in |
I have informed Mia Tosi and Valentina Mariani when I did the change. |
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-250d84/14105/summary.html Comparison SummarySummary:
|
+reconstruction
|
+1 |
+1 |
Looking at DQM as attached, two of them have no directory name, is this because they are empty? |
@srimanob No, just the names of the folders are too large for the letter size chosen. Please select large or fill in the Size menu at the left of the tool bar |
+Upgrade Thanks @jfernan2 |
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. @silviodonato, @dpiparo, @qliphy (and backports should be raised in the release meeting by the corresponding L2) |
+1 |
PR description:
This PR introduce an EDAnalyzer for TICL Tracksters. In this moment the tracksters are validated using the MultiClusters object, while this analyzer takes directly the trackster objects. It also include a validation of the edges, this is why it is specified in the name. Currently we do not save the edges information and for this reason the analyzer is not run by default.
Once the analyzer is run, additional plots are included in the DQM root file and produced automatically with the
makeHGCalValidationPlots.py
script:In the future, we plan to review time and memory to save the edges and to run analyzer by default.
PR validation:
@apsallid @lecriste @rovere @felicepantaleo