-
Notifications
You must be signed in to change notification settings - Fork 78
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
Implementing suggestions for better evaluation of energy-dependent theta cuts #1035
Conversation
…uction and a maximum theta value to evaluate percentile cuts
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1035 +/- ##
==========================================
+ Coverage 74.36% 74.37% +0.01%
==========================================
Files 124 124
Lines 12163 12170 +7
==========================================
+ Hits 9045 9052 +7
Misses 3118 3118
☔ View full report in Codecov by Sentry. |
…er and update the docstring
…ign filter or max_theta_range as default usage
@chaimain after discussing in private, I think this PR can be closed, right? |
Sorry, I couldn't recheck it yet. Will do it today |
…ly for getting energy dependent theta cuts with the option of not doing so
After discussing with @moralejo, I have removed the |
…tory/cta-lstchain into update_theta_eff_cut
With taking suggestions from #997 to redefine the "100% range of gamma events" to be used to evaluate percentile cuts on theta value of events, and adding the following -
disp_sign
value after reconstruction (applied to only MC).DL3Cuts
component:max_theta_range
to create a custom maximum limit of theta value to be considered as "100% of central PSF region", based on which, percentile cuts can be evaluated for eachreco_energy
bins