New functions for better support for different scores and metrics
@VisruthSK 已经在做这个了。
开始于 2025年6月25日。
评估
这个 Issue 还没有评估数据。
描述
This is related to issues #223, #220, #213, #201, #135, #106
We have discussed rewriting CRPS and SCRPS functions to use better computation (probability weighted moment form). As new functions are needed, this has lead to thinking overall improvement of metric and score functions. Some thoughts
- Keep the current loo for elpd, as it does not have arguments for the predictions and observations
- a) Deprecate loo_predictive_metric and create new loo_predictive_measure, or
b) create new loo_predictive_score- (a) might be better if we change the output
- Noa thinks we could drop loo_
- I think we could drop predictive_ but should not drop loo_
- For all measures, return a loo object with pointwise and estimates
- With pointwise information, we can do model comparisons
- Should we extend the current loo object or make a new object type?
- One challenge might be the sub sampling loo, which increase the amount of
of work when implementing other measures
- Extend loo_compare to work with other measures, as we know how to compute diff_se for all current
metrics and scores. Currently, loo_predictive_metric returns only estimate and se for one model
predictions- Or do we need a new function
- Include MAE, RMSE, MSE, R2, ACC, balanced ACC, and Brie score to metrics
- Include RPS, SRPS, CRPS, SCRPS, and log score to scores
- When computing S?C?RPS or current metrics, maybe store function specific diagnostics?
- All measures need psis object or log weights, and thus
should we always compute p_loo, too? Or should we compute measure specific value describing
amount of fitting? - I have a minimal function that computes loo versions of RPS, SRPS, CRPS, SCRPS and includes documentation for the equations with references (but no argument checking, and computes it only for one scalar y, etc)
tagging @n-kall and @jgabry
- 主要语言
- R
- 星标
- 157
- 派生
- 38
- 平均合并
- 4 天 16 小时
- 30 天内合并 PR
- 2
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
stan-dev/loo 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 5/5 一周以上 新手友好度 25/100
-
难度 3/5 1-2 天 新手友好度 45/100
-
难度 3/5 1-2 天 新手友好度 68/100
-
Clean up issues 未关闭
难度 4/5 3-5 天 新手友好度 25/100
相似的 Issue
-
Affects Web App documentation PRIORITY LOW
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 2/5 1-3 小时 新手友好度 75/100
-
难度 1/5 1 小时以内 新手友好度 80/100
hubverse-org/hubCI#36 ·
-
难度 1/5 1 小时以内 新手友好度 85/100
-
Release 1.4.0 未关闭
难度 2/5 1-3 小时 新手友好度 70/100
pharmaverse/pharmaverseadam#170 ·