arviz-devs / arviz-devs/priorDB
Add interpretations of parameters
Open
- Dominant language
- TeX
- Stars
- 14
- Forks
- 2
- Avg merge
- 1h 42m
- Merged PRs (30d)
- 12
Description
When possible, we should add explanation and interpretation of parameters in the models. In particular for GLMs we can add what the relation between the beta and the outcome will be (depending on the link)
Contributor guide
Research direction
Start by locating the model entries and identifying which GLMs and parameters the issue refers to; the issue names no files or tests. Determine how the link function relates beta to the outcome, then consider the work done when relevant model parameters have explanations and interpretations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- tex
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100