-
-
Notifications
You must be signed in to change notification settings - Fork 269
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
Deprecate plotting functions in RStan or just replace backends? #517
Comments
Deprecate! We can always backtrack on that if someone decides to go to town and update rstan to use bayesplot. |
The only reason I can currently think of for not deprecating is that one feature in particular, unconstraining parameters, needs to be done with a stanfit object rather than the inputs bayesplot accepts. I suppose getting around that would involve providing a user friendly way to get a matrix/array of posterior draws in the unconstrained space to pass to bayesplot? It’s super annoying to do that currently. |
@jgabry Is the current method documented somewhere (sorry, I mostly use CmdStan...) |
That would be a helpful function anyway. |
@sakrejda http://mc-stan.org/rstan/reference/stanfit-method-logprob.html But it’s annoying to use. Sent with GitHawk |
Here are the two main problems with Sent with GitHawk |
@paul-buerkner I think in addition to bayesplot brms used to use some of the RStan plotting functions. Is that still the case? If so would you be ok with deprecating those in brms too if we go the route of deprecating the plotting in RStan? Sent with GitHawk |
@jgabry riiiiiight.. this can't really be pulled apart until a) rstan tags parameter names with transforms; and b) transforms become available, ideally by being pulled out from the var_context stuff in Stan itself. I think this is doable over a few months (so like end of summer :) ) |
@sakrejda yeah that’s exactly what we need! |
I will work on this soon. Except for the |
I’m thinking deprecate with a message pointing to the analogous bayesplot function to the one the user called in rstan. Perhaps I can even get the message to be the exact call they would need for bayesplot. |
Any opposition to that? |
Since we have bayesplot now there's no reason to also maintain all the old ggplot2 code currently in RStan. I guess we can
or we can
Personally I'm in favor of (A) since it simplifies RStan's code base (we'd keep the deprecated functions for quite some time of course, but wouldn't plan to maintain that code in the long term). I'd like to do one or the other soon. What do people think of (A), (B), or some other option I haven't thought of?
The text was updated successfully, but these errors were encountered: