stan-dev / stan-dev/rstanarm

models with constant outcomes

Open
#149 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

minor bug question
Dominant language
R
Stars
401
Forks
136
PR merge metrics
No merged PRs in 30d

Description

Summary:

A rstanarm model will fail if any of the variables (including the outcome) are constant. But I'm not sure what we really want to do in this case.

Description:

Because of check_constant_vars

Reproducible Steps:

http://stackoverflow.com/questions/41354745/rstanarm-updating-priors-with-binary-data-without-any-events

RStanARM Version:

2.14.1

R Version:

3.3

Operating System:

Debian

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 reproducing the constant-variable failure described in the linked Stack Overflow example, then inspect the check_constant_vars behavior. The issue does not specify the desired handling for constant outcomes or predictors, so confirm the intended behavior with maintainers before defining what done means.

Written by the indexing model from the issue text.

Assessment

Tech stack
r
Domain
data
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.