-
Notifications
You must be signed in to change notification settings - Fork 28
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
Avoiding numerical issues in show
for problematic chains
#410
Comments
At first glance (haven't checked anything), it seems we should just fix the implementation in MCMCDiagnosticTools? |
Agreed this should be fixed upstream. @torfjelde can you by any chance share an MWE? |
I don't have an MWE atm, but the model is the SDE example from https://turinglang.org/v0.24/tutorials/10-bayesian-differential-equations/ that I ran without adaptation 😕 |
Thanks @torfjelde , that should be enough for me to reproduce the issue when I get to a computer. |
@torfjelde I just tried and wasn't able to reproduce this. Could you write your chains to a file and share them with me? |
@torfjelde gentle reminder to send the problematic chains when you get the chance |
@torfjelde slightly less gentle reminder to send the problematic chains |
Haha yeah sorry. Basically my computer with the thingy crashed and so I couldn't access it until after I got back from BayesComp, and I've yet to be able to reproduce the example:/ |
I'm not certain what the original issue is, but if it's the same as #447, then MCMCDiagnosticTools v0.3.10 contains a fix for this: TuringLang/MCMCDiagnosticTools.jl#119 |
#401 is dope stuff (thanks @sethaxen ) but the tail ess in many cases seem to cause errors upon trying upon calling
show
, e.g. I just got the following trying a modelThis is for a problematic chain of course (I believe the variance is very high?). I also ran into a bug somewhere earlier, again, in the ESS computation.
Maybe we should provide a way to convert these errors into warnings in
MCMCChains.describe
?MCMCChains.jl/src/stats.jl
Lines 286 to 331 in ddac60f
Maybe just add try-catch statements to all of these and do
@warn
+NaN
in case of failure?The text was updated successfully, but these errors were encountered: