-
Notifications
You must be signed in to change notification settings - Fork 6
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
ADMB recdev issue #701
Comments
Do we need to explain the non-zero sum simple dev approach more in the document? I think that they asked for this in passing but did not formally document it as a request. |
I don't recall any specifics that were said. I feel like we give it adequate treatment in the bridging section, but it may be beneficial to beef it up. I could go either way on this one. |
2021? |
I recall them (especially Trevor) asking for a more thorough write-up of it which is why I started this issue, linking the info in one place |
Given it wasn't a formal request I say we do it for next year ;) Be good to get submitted soon. |
As we don't refer to the rec dev issue really at all in this assessment, @kellijohnson-NOAA and I were thinking that there was no reason to add text to the document itself. However, it would be good to eventually add an explanation here so that we don't forget details. I'm earmarking this for the 2022 assessment, but we really should make some notes here before next year (not today though!). |
I opened this because I was left not fully understanding it, but it can wait until 2022... |
Reference the publication that will come out from the Stock Synthesis team. |
Problems with the sum to zero constraint wrt Bayesian inference and stan is talked about here on a google group for stan-users. |
Is the main issue described by the post (wrt sum to zero constraint): |
I think so. |
Lots more discussion on this topic here in google groups. Essentially, the sum to zero constraint should NOT be used in an MCMC context no matter what. |
See #590 which explains it and the ADMB issue: admb-project/admb#107
The text was updated successfully, but these errors were encountered: