Store information about which sampling method or algorithm was used
还没有人认领这个 Issue。
评估
调研方向
首先查看 issue #130 中的讨论，以及这里提到的当前 pointwise 矩阵和 diagnostics 结构。确定每个观测的采样方法元数据应存放在哪里，以及应如何表示 psis、refit、psis-mm 和子采样等方法。确定了存储位置和命名方案后，即视为完成。
由索引模型根据 Issue 内容生成。
描述
This was briefly discussed in #130 , but I am making it a separate issue so that the discussion does not get lost. I will copy what was discussed there:
It would be convenient to store information about which algorithm the elpd values come from. Since moment matching and refitting operate on individual observations, the information should be stored separately for each observation. For example, by default this value could be the same as is_method for all observations, but moment matching or refitting could change it from, say, psis to refit or psis-mm for some observations.
Details to discuss that come to my head at this moment
- Where to store it?
pointwiseis currently a matrix, could we make it a data frame to include a column with text? It could also be an element indiagnostics? - What kind of information to include and how to name the different options (is method/moment matching/refit)? It seems that even
is_methodis currently not stored anywhere. Probably subsampling would be indicated here as well?
- 主要语言
- 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 小时以内 新手友好度 88/100
OHDSI/CohortSymmetry#351 ·
-
难度 1/5 1 小时以内 新手友好度 85/100