-
Notifications
You must be signed in to change notification settings - Fork 221
Add EMCal BadChi2 IB Propagation - CaloTowerStatus #3806
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
base: master
Are you sure you want to change the base?
Add EMCal BadChi2 IB Propagation - CaloTowerStatus #3806
Conversation
- Add feature to flag each tower in the EMCal interface board as having badChi2 if the majority of the towers in the interface board have a badChi2. - Default threshold is set to 0.5 (half of the interface board), but can be adjusted as desired.
- Compute the ratio of the towers with badChi2 in an IB with respect to the avalible towers in the IB. - This way if 70% of an IB is flagged as dead, then the ratio of badChi2 towers is made relative to the 30% of the IB that is alive for the threshold check.
- Ensure that no division by 0 occurs, and skip the IB if no towers are ok.
|
Is there a particular problem this is trying to solve? It would seem easier to modify the maps before adding them to the CDB. |
Hi Blair, yes, @vbailey2 requested this feature. The issue is occurring on the level of individual events, where the majority of the interface board is marked as isBadChi2, however, a few towers slip through, and these are occasionally reconstructed into high pT jets. We can't address this issue by modifying the cdb maps because they represent an aggregate behavior over the entire run. The idea is to check if the majority of the towers in an interface board are marked as having isBadChi2 for an event, then set all towers in the interface board as having isBadChi2 so they would fail the isGood check and not produce these fake high pT jets.
|
Build & test reportReport for commit bc526c3b3645b8d01151383937756edb0824b94a:
Automatically generated by sPHENIX Jenkins continuous integration |
Build & test reportReport for commit 97648bbcac23f117ca7c2a4c315131805d0c3158:
Automatically generated by sPHENIX Jenkins continuous integration |
Build & test reportReport for commit 6d5b0ef06b8547f64d64d8fa9dd56268f206acf4:
Automatically generated by sPHENIX Jenkins continuous integration |
|
After discussion at the Mini Calo meeting today, it was decided to hold off on merging this feature as:
|




Types of changes
What kind of change does this PR introduce? (Bug fix, feature, ...)
TODOs (if applicable)
Links to other PRs in macros and calibration repositories (if applicable)