-
-
Notifications
You must be signed in to change notification settings - Fork 12
Move more LOO functions into the array layer
#275
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
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #275 +/- ##
==========================================
+ Coverage 83.88% 84.11% +0.23%
==========================================
Files 42 42
Lines 5454 5560 +106
==========================================
+ Hits 4575 4677 +102
- Misses 879 883 +4 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
array layer
array layerarray layer
|
I think the RTD failure is unrelated to this |
aloctavodia
left a comment
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.
I was not able to notice any obvious issue. In tests we trust!
Continuation of #267.
Migrates
loo_score,loo_pit,loo_expectation,loo_quantile,loo_r2, andloo_summaryinto the base layer, making these functions accessible via.azstatswithout requiring the full LOO orchestration machinery.Core functions require pre-computed PSIS weights rather than computing them internally. This enables weight reuse, e.g., users can compute PSIS once and pass the weights to multiple metrics, avoiding redundant computation. The exception to this is
_loo, which can compute PSIS internally since it's the foundational function that producespareto_k.