Closed fweber144 closed 4 years ago
Thank you for reporting this! This is most likely related to https://github.com/stan-dev/loo/issues/129 as you said. The PR https://github.com/stan-dev/loo/pull/152 fixed this issue, but there is a similar parallelisation structure in loo_moment_match_i_fun
, which was not updated in that PR.
I will look into it.
I think this is actually brms-related as you first guessed. I was not able to reproduce this without brms and found a solution for brms that may fix this. More details in https://github.com/paul-buerkner/brms/issues/1000 . Closing this for now at least.
At first, I thought this was related to brms (see paul-buerkner/brms#1000), but it seems this is rather an loo issue.
The problem is that
loo_moment_match()
(applied to a brmsfit object, though this might be unimportant) throws an error on Windows 10 (though I haven't tried it yet on other systems). On my machine, a reproducible example is:Perhaps this issue might be related to #129 and something like
might be missing in
loo::loo_moment_match.default()
.Perhaps this might also be related to #94 (so that something with the parallelization on Windows 10 in general is wrong).
My session info: