If you've clicked on the "guidelines for contributing" link from the GitHub issue tracker, you're in the right place. These guidelines will help the development team fix the issue.
These links will pre-populate an issue with a template:
| Libraries | Interfaces | Other |
|---|---|---|
| Stan (bug report) Stan (feature request) |
CmdStan RStan PyStan |
shinyStan |
Use this template for describing problems with the Stan library. Please be as specific as possible. If you're able to provide a simple reproducible example, this will go a long way to helping the developers fix the bug.
Title
Please give a descriptive summary of the bug.
Version
For tagged versions, please report the version number in src/stan/version.hpp.
For git cloned versions, report the result of typing git rev-parse HEAD from the command line.
Description
Describe the problem as clearly as possible.
Steps
Steps to reproduce the bug, if possible. If not, a description of how you discovered the bug.
If you have a reproducible example, put it here.
Output
Output you get from triggering the bug. Knowing what Stan currently does is useful.
Expected Output
Describe what you expected to happen. Knowing what the correct behavior should be is also very useful.
Additional Information
Provide any additional information here.
Use this template for requesting new features in Stan.
Title
Please give a descriptive summary of the feature.
Version
For tagged versions, please report the version number in src/stan/version.hpp.
For git cloned versions, report the result of typing git rev-parse HEAD from the command line.
Category
Use one of the following or make up something reasonable:
- language
- new function
- algorithm
Description
Describe the feature you'd like in Stan. Be descriptive.
Example
Provide at least one example. Also mock up the expected result from that example.
Additional Information
Provide any additional information here.