stan-dev / stan-dev/docs

clarify advice on stationarity constraints for AR(k) processes (User's Guide)

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

Nobody has claimed this yet.

enhancement
Dominant language
TeX
Stars
43
Forks
133
Avg merge
11h 32m
Merged PRs (30d)
4

Description

Summary:

Ravi Sastry on Discourse pointed out an inconsistency in the User's Guide:

In the Stan User’s Guide v2.32, the last line in Section 2.4 recommends adding a constraint on the AR coefficient phi to ensure stationarity. But in Section 2.1, the same constraint on the AR coefficient (beta in this case) is given but “… is not recommended. If the data are not well fit by a stationary model it is best to know this. Stationary parameter estimates can be encouraged with a prior favoring values of beta near zero.”

Description:

My response on the forum:

If you know you're dealing with a stationary process, the constraint can make sense and even help guide the fit (it'll keep all the uncertainty within stationary parameter values). If you don't know you have a stationary process, this can be dangerous and will likely lead to instability in fit due to probability mass bunching up at constraint boundaries. So if you're unsure if your data are from a stationary process, it can help to not enforce the constraints and see what the data implies for a fit.

Current Version:

v2.32

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 comparing Sections 2.1 and 2.4 of the Stan User’s Guide, especially their advice on stationarity constraints for AR(k) processes. Revise the guidance so it distinguishes known stationary processes from cases where stationarity is uncertain, then check the rendered User’s Guide for consistent wording.

Written by the indexing model from the issue text.

Assessment

Tech stack
tex
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.