Open helske opened 1 week ago
Actually I think the same issue is also present in cmdstanr
, at least I don't see any information about the number of used iterations there either. Note also that cmdstan
(and thus rstan
and cmdstanr
) output return code 0 (success) in case of hitting the maximum number of iterations, so checking that does not help. There is also an old issue about these return codes: https://github.com/stan-dev/stan/issues/2197
It would be great if the output of
optimizing
contained the number of iterations the optimizer ran. This could be then to check whether the optimization terminated because of hitting the maximum number of iterations. Even better solution would be to get the actual reason for the termination from the output, which is currently only available in the print whenverbose = TRUE
, but I understand that this is likely more difficult due to the wayrstan
works.Example
RStan Version:
2.32.6
R Version:
4.3.0
Operating System:
Windows 10