Correct pred_measure values after post-hoc LOO methods - #399
Draft
florence-bockting wants to merge 1 commit into
Draft
florence-bockting wants to merge 1 commit into
florence-bockting wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #399 +/- ##
=======================================
Coverage 92.50% 92.50%
=======================================
Files 31 31
Lines 3107 3107
=======================================
Hits 2874 2874
Misses 233 233 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
This is how benchmark results would change (along with a 95% confidence interval in relative change) if ed2da5b is merged into master:
|
pred_measure values after post-hoc LOO methodspred_measure values after post-hoc LOO methods
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The problem
This issue refers to loo v3.0.0. It comes from my work on the new
pred_measurefamily.A post-hoc method corrects PSIS-LOO for the observations with a high Pareto k. Examples are moment matching and reloo.
loo_pred_measure()takesypred,mupred, andylpfrom the original draws. It takes the weights frompsis_object.looobject comes from a post-hoc method,ypredstill refers to the original draws. It does not refer to draws from the updated parameters.psis_object. Thuspsis_objectdoes not match the updatedlooobject.Only
elpd,mlpd, andicare correct. They come directly fromloo$pointwise. For all other measures, users get mismatched values. They cannot correct them.What I currently do instead
If moment matching or reloo is used, the current code (branch
integrate-loo_compare) warns the user when a measure other thanelpd,mlpd, oricis used. The warning offers no way to get the correct values.Proposed solution
The design doc in the attached .md file provides a solution for this problem.
It proposes:
ylp,ypred, andmupredcolumns in thelooobject.loo_pred_measure()then replaces the matching columns of the user's matrices with the stored columns.The design suggests changes in
looandbrms.Feedback wanted:
Timing: we could do this after we merge
integrate-loo_compareandpred_measureinto loo-v3.0.0.Tagging: @jgabry, @avehtari, @VisruthSK, @paul-buerkner