-
Notifications
You must be signed in to change notification settings - Fork 2
Description
@sybenzvi noted a spike in the effective volume table that ASTERIA uses, and posted the following while discussing #102 .
ASTERIA/python/asteria/data/detector/effectivevolume_benedikt_AHA_normalDoms.txt
Lines 53 to 57 in ab595ea
| -382.47 0.195505618 | |
| -399.49 0.2123595506 | |
| -416.51 0.3073033708 | |
| -433.53 0.2303370787 | |
| -450.56 0.2314606742 |
This spike occurs at a z-coordinate of -416.5 m, which corresponds to the position of DOM 55 on string 43, as specified in the geometry file used by ASTERIA. String 43 was used to generate this table (See, B. Riedel's PhD Thesis Fig 4.17) This DOM is an HQE DOM on a non-deepcore string. The person who originally wrote the effective volume table that ASTERIA uses replaced the normal effective volume with a DeepCore effective volume.
Since ASTERIA reads this table and assigns effective volume to DOMs according to z-position, any DOM at position 55 or in the z position range (-399.5 m, -433.5 m) may have an inflated effective volume. Additionally, since DeepCore effective volume is assigned by scaling a normal DOM's effective volume by 1.35, a DeepCore DOM at this position will have even higher effective volume.
Segev suggested changing this data point to a more reasonable value, which would resolve the error. Some additional checks on the expected hit rate may be warranted, as ASTERIA overestimates the rates of DOMs in a layer near z position -416.5 m.
