Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: subscript out of bounds #88

Closed
bgoodri opened this issue Aug 13, 2015 · 3 comments
Closed

error: subscript out of bounds #88

bgoodri opened this issue Aug 13, 2015 · 3 comments
Milestone

Comments

@bgoodri
Copy link

bgoodri commented Aug 13, 2015

If you do

fit1 <- stan_glm(Volume ~ log(Girth) + log(Height), data = trees,  family = gaussian(link = 'log'))
launch_shinystan(fit1)

and go to NUTS (Plots), you get the error message and in the console it says

Error in samps_post_warmup[if (!is.null(sel)) sel, , "lp__"] : 
  subscript out of bounds

This may have to do with it being renamed "log-posterior"?

@jgabry
Copy link
Member

jgabry commented Aug 14, 2015

It definitely has to do with the name change. I had not noticed that. Is
this changing in rstan too or are you just renaming it in rstanarm? If it's
just rstanarm then I can put in a special case for that.

On Thursday, August 13, 2015, bgoodri notifications@github.com wrote:

If you do

fit1 <- stan_glm(Volume ~ log(Girth) + log(Height), data = trees, family = gaussian(link = 'log'))
launch_shinystan(fit1)

and go to NUTS (Plots), you get the error message and in the console it
says

Error in samps_post_warmup[if (!is.null(sel)) sel, , "lp__"] :
subscript out of bounds

This may have to do with it being renamed "log-posterior"?


Reply to this email directly or view it on GitHub
#88.

@bgoodri
Copy link
Author

bgoodri commented Aug 14, 2015

It is just in rstanarm at the moment, but I could imagine any number of
packages the depend on Stan doing something like that. It may be best to
just call get_log_posterior() rather than rely on hard-coded names.

On Thu, Aug 13, 2015 at 8:13 PM, Jonah Gabry notifications@github.com
wrote:

It definitely has to do with the name change. I had not noticed that. Is
this changing in rstan too or are you just renaming it in rstanarm? If it's
just rstanarm then I can put in a special case for that.

On Thursday, August 13, 2015, bgoodri notifications@github.com wrote:

If you do

fit1 <- stan_glm(Volume ~ log(Girth) + log(Height), data = trees, family
= gaussian(link = 'log'))
launch_shinystan(fit1)

and go to NUTS (Plots), you get the error message and in the console it
says

Error in samps_post_warmup[if (!is.null(sel)) sel, , "lp__"] :
subscript out of bounds

This may have to do with it being renamed "log-posterior"?


Reply to this email directly or view it on GitHub
#88.


Reply to this email directly or view it on GitHub
#88 (comment).

@jgabry
Copy link
Member

jgabry commented Aug 14, 2015

If get_log_posterior is sticking around then yeah I'll just use that.

On Thursday, August 13, 2015, bgoodri notifications@github.com wrote:

It is just in rstanarm at the moment, but I could imagine any number of
packages the depend on Stan doing something like that. It may be best to
just call get_log_posterior() rather than rely on hard-coded names.

On Thu, Aug 13, 2015 at 8:13 PM, Jonah Gabry <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');>
wrote:

It definitely has to do with the name change. I had not noticed that. Is
this changing in rstan too or are you just renaming it in rstanarm? If
it's
just rstanarm then I can put in a special case for that.

On Thursday, August 13, 2015, bgoodri <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');> wrote:

If you do

fit1 <- stan_glm(Volume ~ log(Girth) + log(Height), data = trees,
family
= gaussian(link = 'log'))
launch_shinystan(fit1)

and go to NUTS (Plots), you get the error message and in the console it
says

Error in samps_post_warmup[if (!is.null(sel)) sel, , "lp__"] :
subscript out of bounds

This may have to do with it being renamed "log-posterior"?


Reply to this email directly or view it on GitHub
#88.


Reply to this email directly or view it on GitHub
<#88 (comment)
.


Reply to this email directly or view it on GitHub
#88 (comment).

@jgabry jgabry mentioned this issue Aug 14, 2015
@jgabry jgabry modified the milestone: 2.0.1 Aug 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants