We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Is bias correction something wanted in pyirf?
If so, where should it be implemented? Directly as an option in the resolution functions? Or as separate functions?
Originally posted by @vuillaut in #184
The text was updated successfully, but these errors were encountered:
I think we could generalise this option in a similar way to what we did for resolution:
Regarding specifically what CTAMARS does see here. This happens after cuts optimisation, so in that case it fits with pyirf's scope.
Sorry, something went wrong.
No branches or pull requests
Is bias correction something wanted in pyirf?
If so, where should it be implemented?
Directly as an option in the resolution functions?
Or as separate functions?
Originally posted by @vuillaut in #184
The text was updated successfully, but these errors were encountered: