Unify prior definitions within code base
Open
Nobody has claimed this yet.
nice to have
- Dominant language
- Python
- Stars
- 124
- Forks
- 24
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 60
Description
Within hssm, priors can be defined in multiple ways: using a dict with relevant fields, an instance of the Prior class, or the bmb.Prior constructor. While this flexibility benefits end-users, it can be confusing for developers new to the project. Standardizing the method for defining priors would enhance the codebase's readability.
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 comparing the three prior-definition forms named in the issue: dictionaries, the Prior class, and the bmb.Prior constructor. Decide which representation should become standard across hssm and verify that the remaining definitions and their user-facing behavior are consistently handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100