-
Notifications
You must be signed in to change notification settings - Fork 605
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
ulam fits giving odd errors #430
Comments
Some bug specific to binomial outcomes perhaps? I may not have time to figure it out today, but will make an issue of it. |
Quick assessment, two things going on: (1) not enough samples in model, so subscript error. this is a bug, but goes away if you sample more chains. (2) the logit(prob) <- p line generates only a single value, so postcheck generates only a single prediction. can hack it to work by doing something like: logit(prob) <- p + 0*density but will need to add special logic to somehow deal with this kind of thing in general. |
I have been thinking of replacing the old postcheck with Aki's PIT plots as default. But I need to make more time in my life to work through my dev notes. |
Huh - had not run across LOO-PIT yet. Damn this field keeps evolving. I had however, re-implemented Quantile Residual checks, much like in the DHARMa package.
This is nice because then you can make QQ plots like so:
But - I'm guessing this will have similar issues for binomial models? And, I suppose if you want to make a hot plot like the ones I now see in bayesplot - well, you could do it with quantil residuals as well
Which I suppose could serve the basis of a plotting function. Yes, yes, I know, I prefer ggplot2. I'm very tidy. Or try to be. I'm sure this could be done in base, but, wow, my base brain is.... stale. |
I'm working with ulam a bit to show mixed models in a few context. This example:
however, gives an odd error
I can up the number of chains and then postcheck it. However, I only get a single point, instead of looking at all rows of the reedfrogs data.
Here's my relevant sessioninfo
The text was updated successfully, but these errors were encountered: