You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is related to #150 but slightly more general. In versions prior to version 3, it was possible to calculate the following five standard diagnostics, as recommended by Michael Betancourt:
In the current output, I see divergent__, treedepth__, and energy__. This probably means that the first three can be computed even in version 3. However, with energy, it is not as clear, at the code seems to assume some particular ordering of the energy values; mostly likely, each chain has to be processed separately, which is what the API does not allow. The remaining two, the effective number of samples and R hat, require Stan’s summary, which is not provided.
I am curious if the above is a fair summary of the current situation. In addition, if anybody has insight into what the underlying C++ code is doing, are any of these checks performed automatically with warnings if appropriate?
The text was updated successfully, but these errors were encountered:
This is related to #150 but slightly more general. In versions prior to version 3, it was possible to calculate the following five standard diagnostics, as recommended by Michael Betancourt:
https://github.com/betanalpha/jupyter_case_studies/blob/master/pystan_workflow/stan_utility.py
In the current output, I see
divergent__
,treedepth__
, andenergy__
. This probably means that the first three can be computed even in version 3. However, with energy, it is not as clear, at the code seems to assume some particular ordering of the energy values; mostly likely, each chain has to be processed separately, which is what the API does not allow. The remaining two, the effective number of samples and R hat, require Stan’s summary, which is not provided.I am curious if the above is a fair summary of the current situation. In addition, if anybody has insight into what the underlying C++ code is doing, are any of these checks performed automatically with warnings if appropriate?
The text was updated successfully, but these errors were encountered: