-
Notifications
You must be signed in to change notification settings - Fork 2
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
adds support for posterior::as_draws() #51
Conversation
Thank you so much, this is wonderful!! I'd love to customize further so that the extracted samples are even easier to work with. The main one would be the names of the extracted variables, these are currently in a format like
You can take a look at Or maybe we can define something like Since we are changing the variable names and there aren't great flexibility in model structure anyways, I think we can drop the While doing this it would be good to add unit tests to make sure name mappings are done as expected. Thanks! |
Hi @yoshidk6 - thanks for the suggestions! Following up from this and our chat, I've made the following changes:
Informally, I've also checked that relabelling the variables in this fashion doesn't seem to break any internal object representation expected by the posterior package. I didn't try to be too thorough about this but from what I can tell:
In both cases, when we call Let me know what you think! 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is wonderful, thank you so much for incorporating my feedback and going extra miles to ensure compatibility with as_draws_rvars!
main changes in this PR:
posterior::as_draws_*()
methods for stanemax objectsvariable
,regex
, andinc_warmup
arguments for filtering and subsetting, as per brms methodsancillary changes:
@docType
tag to prevent deprecation warningcloses #49