stan-dev / stan-dev/posteriordb
Write documentation on how to do efficiancy testing
Open
Nobody has claimed this yet.
- Dominant language
- Stan
- Stars
- 232
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
We should write down information on how to do efficiency testing of posterior algorithms. When we write this, we should remove some parts from the use case documents and then reference the use case document to this document instead.
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 use case documents referenced in the issue and review the existing material on efficiency testing of posterior algorithms. Document the testing process in a dedicated document, remove the duplicated parts from the use case documents, and add references from those documents to the new documentation.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing-qa
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100