-
Notifications
You must be signed in to change notification settings - Fork 0
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
user supplied priors and rrs parameterization of alpha_W and alpha_H #58
Comments
Hi @tbuehrens. Yes, it's true that the current implementation uses the same prior for To be clear, the deltas are defined as log-ratios, i.e. differences on the log scale, like Given this challenging and data-hungry estimation problem, I guess I'm not too surprised to see long-tailed posteriors (which are common enough even with |
Hard to say how problematic the asymmetry is without having looked at it... not optimal, but the benefit of making the log-ratio of productivities the primitive parameter would be that we can set rather informative priors, which may also help with estimation as it excludes a lot of unrealistic parameter space being sampled. |
Independent priors on the W and H parameters could also be informative, though. For example, if prior information suggests The advantage of this approach is that it still allows the option of setting identical, weakly informative priors on the W and H parameters to let the data speak. By contrast, suppose the primitive parameters and their priors are When I was developing these RRS S-R functions with the Snake Spring / Summer Chinook populations -- a very large and informative data set by the standards of such things -- I found that the baked-in asymmetry of this parameterization made it impossible to tell whether posterior differences between the W and H parameters were "real". Independent priors on the W and H parameters would give you the flexibility to represent evidence that H spawners are less productive, or to check prior sensitivity by using identical reference priors. |
hey all, had a good chat with Eric and he won me over to the idea that there are some downsides of both parameterizations but probably the lowest hanging fruit is to modify the existing parameterization to enable distinct priors for hatchery and wild fish, as well as the multivariate equivalent in the pp model (separate hyper means and variances)...then we give those models a test drive and see if life is good...happy to catch anyone up on the phone if they want to hear the play by play of my 1 hr call with Eric ;-) |
If user-specified priors are not provided, the default priors for W and H are the same Addresses #58
OK, the proposed approach of allowing independent priors on W and H S-R parameters has been implemented for the
(Relatedly, the Markdown table showing which parameters in each model can take user-defined priors is no longer rendering properly for some reason. 😕) |
right now, with user supplied priors, you can only give two shape parameters for alpha_W and alpha_H...meaning in effect you have to have the same prior on both...in effect this means that you MUST use very vague priors for alpha_W or the model will force alpha_H to be similar (and delta to be small) due to the inability to give separate priors to each. I remain convinced that it would be better to parameterize the model in terms of alpha_W and delta_alpha (where delta_alpha is calculated by diveision rather than subtraction) so that you can put a prior on alpha_W and a prior on the relative productivity of alpha_H as a percentage of alpha_W (i.e., alpha_H = alpha_W * delta_alpha).
in my real worked case where this is a problem, I have a short timeseries where alpha_W for chinook is being estimated at 11 with super vague priors and alpha_H is near zero... if I tighten the prior on alphas then alpha_W drops but alpha_H increases...part of this is that the model must assign more recruits to the hatchery spawners, but part of the reason is that I can only supply the SAME prior for both alphas.... @ebuhle, should we change this parameterization or leave....interested in your thoughts
The text was updated successfully, but these errors were encountered: