-
Notifications
You must be signed in to change notification settings - Fork 3
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
Piecewise linear quantiles #134
Conversation
…PDF location offset in `quant_gen._compute_derivs` to account for the forward difference calculation of numerical derivatives.
For some screenshot comparisons of with and w/o the x offset in PDF, see this comment in #8. |
Codecov ReportBase: 100.00% // Head: 100.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #134 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 25 25
Lines 2049 2047 -2
=========================================
- Hits 2049 2047 -2
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
…obably do not need to test this `except` code branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Drew.
This PR is a byproduct of taking on qp issue #8. As a result of the exploration, there is a minor code change included in this PR to introduce an x offset in the locations used when return PDF values for a
quant_gen
object.Visually, this offset makes the qp approximation of a PDF and the original PDF align better. Mathematically, it's a byproduct using a forward difference to calculate the numerical derivative. (the need for the offset could be eliminated if we used a central difference, such as that provided by numpy.gradient)
This PR does not address the concerns brought up in qp issue #65. I have an approach that does address this called out in a comment in #8 but I would like to review that as a PR separate from this one.