-
-
Notifications
You must be signed in to change notification settings - Fork 374
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
"term_buffer = 0" leads to "# Step size = 1" in output csv #3023
Comments
warmup windows described here: https://mc-stan.org/docs/2_26/reference-manual/hmc-algorithm-parameters.html
if this update doesn't happen, then stepsize would remain at ??? iteration 50 (+- 1) |
All but the first few are generally in the same order. For a different run (same configuration, this csv is gone) we have for 48-52
and for the last one
|
I suspect the term_buffer = 0 thing is doing it. Like the stepsize is being reset at the end of a window with the assumption that there will be another window following. Here is where the stepsize gets reset at the end of each warmup window: https://github.com/stan-dev/stan/blob/develop/src/stan/mcmc/hmc/nuts/adapt_diag_e_nuts.hpp#L35 A lot of the adaptation logic is here https://github.com/stan-dev/stan/tree/develop/src/stan/mcmc |
Summary:
See title. A dense metric was used.
CSV header:
CSV End
Expected Output:
The step size should probably be different, something in the order of
0.381802
.See also this https://discourse.mc-stan.org/t/fitting-ode-models-best-efficient-practices/21018/80
Sorry for being terse.
Current Version:
v2.26.1
The text was updated successfully, but these errors were encountered: