-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Implement equivalent of model_pars and par_dims of stanfit from rstan #240
Comments
I agree this is useful information. I think some version of this could go in posterior but it's a little bit Stan-specific in that the dimension of And maybe we can combine # assume the draws object has variables
# alpha, beta[1], beta[2], beta[3], Sigma[1,1], Sigma[1,2], Sigma[2,1], Sigma[2,1], lp__
> variable_structure(draws)
$alpha
[1] 1
$beta
[1] 3
$Sigma
[1] 2 2
$lp__
[1] 1 Paul will also probably have suggestions if you open an issue over at posterior. |
Although maybe we should also add the equivalent of |
Agree. That also makes read_cmdstan_csv a more complete function standalone. |
I think our current way forward in posterior is to implement those dimensional draws arrays (stan-dev/posterior#13) via rvars (stan-dev/posterior#8). On these decisions it will likely depend on how we represent the dims in posterior best. |
@rok-cesnovar This is currently listed under the beta release milestone, but this could probably wait for 1.0 right? That way we could go forward with the beta release sooner. |
Agreed, can move to 1.0. I was expecting I would have time to work on this in July, that is why I put the milestone on beta. But then other stuff got in the way. |
Running:
prints
Should we implement the equivalent of this? If yes, any name suggestions?
Or are there any plans to add this to posterior (like posterior::variables()). Retrieving dimensions and names of parameters/variables isn't Stan specific. I can also add this to posterior if it would be better to live there.
The text was updated successfully, but these errors were encountered: