Update DeadPMTID mask for WCSim #357
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at recent (since 2023) data, there are two PMTs (IDs 359 and 408) that show no (or very little) activity. The way we simulate dead PMTs from WCSim is to simply mask out their hits in the
LoadWCSimtool. To accurately model our data we therefore need to add them to the dead list.The activity loss in these PMTs are observed in the AmBe source data statistics (across many runs):
Total hits:
2235737Average hit rate per PMT (assuming 121 PMTs equally participating):
18477 (0.83%)Some examples of active channels:
14532 (0.65%)13775 (0.62%)17433 (0.78%)The two PMTs in question:
408 (0.018%)0 (0%), i.e. dead as a doornailWe see a similar statistical behavior in the beam data. The mapping of the dead PMT list references this file.
Describe your changes
Checklist before submitting your PR
newusage, there is a reason the data must be on the heapnewthere is adelete, unless I explicitly know why (e.g. ROOT or a BoostStore takes ownership)Additional Material
More information on the dead PMT rates can be found here (slide 33).
A good ToDo would be to determine when exactly these PMTs showed this behavior.