stan-dev / stan-dev/rstan

consider adding open_progress to options

Open
#720 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
R
Stars
1.1k
Forks
266
Avg merge
2h 56m
Merged PRs (30d)
1

Description

It would be nice be able to set open_progress globally inside options() instead that having to set it up in every call. While I can do formals(stan)$open_progress <- FALSE, I can't do it with sampling() for example that is called by brms.
See also https://github.com/paul-buerkner/brms/issues/796

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the existing options() and sampling() entry points, then compare how open_progress is currently passed in each call. Check the linked brms issue for the integration constraint. Done means a global open_progress setting works through sampling() without requiring callers to set it repeatedly, with behavior covered by the relevant tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
api
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.