You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
The ring background analysis that is demonstrated in the corresponding tutorial is incorrect. The OFF is correlated twice (one with the RingBackgroundMaker and the other with the ExcessMapEstimator because the latter use incorrectly the default value correlate_off=True. The estimated significance is therefore artificially large.
Wile using instead correlate_off=False removes the double OFF counting, it creates residual features where the acceptance is discontinuous (mostly because of FoV masking).
Expected behavior ExcessMapEstimator should provide images without artifacts using the proper correlate_off=False and the tutorial should be updated accordingly.
To Reproduce
Modify the ring background tutorial to include an offset-max cut and add the correct option to compute Li-Ma excess and significance map correlate=False.
when computing the correlated maps in ExcessMapEstimator
A caveat
this does not say what to do with the ON and OFF acceptances, in Gammapy we assume that the stacked acceptances are: $$\bar{A}cc_{ON} = 1 \quad \text and \quad \bar{A}cc_{OFF} = \frac{1}{\bar{\alpha}}$$
This choice is problematic as it removes all information on where the events actually come from
We should instead stack $Acc$ to represent the sum of acceptances taking into account the safe mask:
Gammapy version
v1.0 and beyond
Bug description
The ring background analysis that is demonstrated in the corresponding tutorial is incorrect. The OFF is correlated twice (one with the
RingBackgroundMaker
and the other with theExcessMapEstimator
because the latter use incorrectly the default valuecorrelate_off=True
. The estimated significance is therefore artificially large.Wile using instead
correlate_off=False
removes the double OFF counting, it creates residual features where the acceptance is discontinuous (mostly because of FoV masking).Expected behavior
ExcessMapEstimator
should provide images without artifacts using the propercorrelate_off=False
and the tutorial should be updated accordingly.To Reproduce
Modify the ring background tutorial to include an offset-max cut and add the correct option to compute Li-Ma excess and significance map
correlate=False
.You will obtain this figure:
Other information
Any other information you think will be useful for us to fix the issue can go here.
The text was updated successfully, but these errors were encountered: