-
Notifications
You must be signed in to change notification settings - Fork 31
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
Multiple matches with family argument in ggs() #73
Comments
Hi @mdodrill-usgs . Thank you very much for using ggmcmc and for reporting issues. In this case the behaviour is the one that I had in mind. Maybe the documentation is misleading and certainly I would have to change it depending on how this conversation goes. The idea with
So unless you have a strong preference and for changing its behaviour to return only what is in between the brackets in the What do you think? |
Hi @xfim, Thank you for the prompt reply and your work on ggmcmc. I think just some small changes to the documentation would help to clarify the behavior when Also, for those not as familiar with building regular expressions (like me), maybe a condensed version of your response, above, could be added to the example in the documentation of Building off the little Stan model above, maybe something like this:
|
Hi,
When using the family argument to pull only a set of named parameters from a fitted model object, the function ggs() returns multiple matches when the parameter names are similar (see example below). This isn't the behavior I expected when looking at the documentation for ggs() (i.e., A family of parameters is considered to be any group of parameters with the same name but different numerical value between square brackets (as beta[1], beta[2], etc).)
Maybe this is the desired behavior, but a nice feature would be to only return the parameters that match the string before the square brackets (provided as the family argument). not multiple parameters (multiple matches, "alpha" and "alpha_2" in the example).
Thanks
The text was updated successfully, but these errors were encountered: