Implement as_draws generics in other packages?

未关闭
#183 13 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
r
领域
api

调研方向

首先比较 posterior 现有的 as_draws/as_draws_XXX 泛型与 brms、rstanarm、rstan 和 cmdstanr 中的转换 API。定义每个集成应支持的对象类和 draws 格式,然后在实现之前与维护者确认该提案;完成的标准是达成一个跨包接口共识。

由索引模型根据 Issue 内容生成。

描述

interface

(Note: I'm opening this here for discussion first rather than opening a bunch of essentially duplicate issues in several packages)

Now that posterior is on CRAN, would it make sense to have as_draws() / as_draws_XXX() implementations for objects in brms, rstanarm, rstan, cmdstanr, etc? I think it would help fulfill part of the promise of {posterior}; that is, users don't have to remember what particular function for a given model type gets them draws in what format, they can just chuck the object into as_draws_XXX() for whatever format they want.

E.g. with cmdstanr, rather than doing this:

model$draws(format = "XXX")

People could (optionally) do:

model %>% as_draws_XXX()

The advantage of the latter code is that as more packages also implement these generics it becomes easier for users to move between packages. @paul-buerkner @jgabry thoughts? I dunno if this was already the plan anyway.

主要语言
R
星标
172
派生
27
平均合并
5 天 12 小时
30 天内合并 PR
5

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

stan-dev/posterior 的其他 Issue

查看 stan-dev/posterior 的全部 Issue

相似的 Issue

更多 R Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。