Differing behavior of `extract_model_data()` for `"stanreg"` fits and `"brmsfit"`s
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 114
- Forks
- 31
- PR merge metrics
- No merged PRs in 30d
Description
See this comment in paul-buerkner/brms#1230: Do we want the behavior of predict.refmodel(), proj_linpred(), and proj_predict() to be the same for "stanreg" and "brmsfit" fits? If yes, how should that common behavior look like: The current "stanreg" or the current "brmsfit" behavior?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked brms comment and comparing the behavior of predict.refmodel(), proj_linpred(), and proj_predict() for "stanreg" and "brmsfit" fits. Done means the project has a decided common behavior for both fit types and the affected entry points are consistent with that decision.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- backend-api-design, data
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100