stan-dev / stan-dev/rstantools
write_stan_json and to_stan_json to rstantools?
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 48
- Forks
- 24
- Avg merge
- 1h 17m
- Merged PRs (30d)
- 1
Description
CmdStanR has write_stan_json(). BridgeStan could use that, too. In addition, BridgeStan would benefit from a to_stan_json() function that would not write to file, but just return a string. I made an issue to bridgestan https://github.com/roualdes/bridgestan/issues/202, but @WardBrian suggested putting it somewhere else, and maybe rstantools would be appropriate?
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 reviewing the linked BridgeStan issue and CmdStanR's existing write_stan_json() function. Determine whether rstantools is the appropriate home and define the scope and interface for both file-writing and string-returning helpers; the issue is complete only once that placement and API are agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100