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
For the record: Our current approach of passing information about tuning/not-tuning via sample stats is brittle. It's a per-sampler thing, but in practice it's actually a per-iteration thing from the PyMC, ArviZ and McBackend perspective. IMO we should consider taking it out of the step method attributes and stats, and instead pass tune as a parameter to the astep method.
This line here assumes that the first sample has
tune
information, which is not necessarily the case (as the comment above states):pymc/pymc/sampling/mcmc.py
Lines 738 to 742 in 457421b
Example that fails (but could be fixed in a future PR without solving the underlying issue:
As the Slice sampler does not provide
tune
statsThe text was updated successfully, but these errors were encountered: