-
-
Notifications
You must be signed in to change notification settings - Fork 10
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
Prior predictive keyword arg not used in from_mcmcchains #146
Comments
Thanks for the issue! Lines 254 to 271 in 17f2e7e
I'll push a fix, though it might wait until after the holidays. For now, you can make it work by providing also the |
@bgroenks96 the latest ArviZ release should resolve this issue. Please let me know if it persists. |
Ok will do. I temporarily stopped using the package, though, because I ran into difficulties with the interface to |
I agree. Unfortunately, wrapping xarray really well essentially involves writing an XArray.jl package that wraps all xarray types, which is beyond the scope of this package, especially since we're working to drop Python as a dependency (see e.g. #128, #130). Unfortunately, there's really no clear best xarray drop-in alternative in the Julia ecosystem yet. If you have the time, issues documenting the specific problems would be very useful, because I might be able to add simple workarounds that would make this package more useful in the interim. |
I would also be happy with a pure-Julia I actually wanted to take a crack at creating an XArray.jl packge. I already have some code lying around which half-implements a wrapping scheme. I hope that I will soon have some time to work on this... I am really not happy with and am constantly bothered by the limitations and instability of DimensionalData.jl, the closest Julia alternative to xarray, at the moment. |
When using
from_mcmcchains(chain; prior_predictive=prior_pred_chain)
, the prior predictive chain is not stored in the resultingInferenceData
.Looking at
mcmcchains.jl
, it's pretty clear why; the keyword arg is listed in the documentation but I don't see it handled anywhere in the code?The text was updated successfully, but these errors were encountered: