stan-dev / stan-dev/posteriordb
Follow-up on problematic posteriors
Open
Nobody has claimed this yet.
- Dominant language
- Stan
- Stars
- 232
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
Models:
- dogs-dogs_log
Contributor guide
No contributing guide indexed for this repository
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 locating the dog-dogs_log model in the posterior database and inspect its stored posterior and metadata. The issue does not describe the problem, expected behavior, relevant files, or tests, so first determine what is problematic and define a reproducible criterion for completion.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100