-
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
EnergyInDeadE{B,E}_FE
warnings from hltEcalRecHit
#45880
Comments
cms-bot internal usage |
A new Issue was created by @missirol. @Dr15Jones, @antoniovilela, @makortel, @mandrenguyen, @rappoccio, @sextonkennedy, @smuzaffar can you please review it and eventually sign/assign? Thanks. cms-bot commands are listed here |
assign RecoLocalCalo/EcalRecProducers |
New categories assigned: reconstruction @jfernan2,@mandrenguyen you have been requested to review this Pull request/Issue and eventually sign? Thanks |
assign hlt |
New categories assigned: hlt @Martin-Grunewald,@mmusich you have been requested to review this Pull request/Issue and eventually sign? Thanks |
@cms-sw/ecal-dpg-l2 |
These warnings are caused by channels that are already masked in reco but not the trigger, so they report the energy calculated from the TP. The level of these should be downgraded from |
@ReyerBand
For my education, It is not very clear what trigger means in this context. These messages appear in the trigger (HLT) logs. Do you mean in the trigger primitives?
Should these channels be masked at HLT as well, instead? In other worlds is it safe to remove the warnings? |
@mmusich Sorry for my imprecise description - I did mean the trigger primitives. These channels have a dead data readout but the TP energy info can be used. These "warnings" are just reporting that TP energy, and it's safe to remove them. |
Looking at log files of HLT jobs running online, one can find the following warnings. I see these warnings already in a log from 2023, so they are not new. In fact, they were already mentioned in #41456. Still, I would kindly ask experts to comment on what these warnings mean, and whether or not any action should be taken.
@cms-sw/ecal-dpg-l2
The text was updated successfully, but these errors were encountered: