Open rodluger opened 9 years ago
@rodluger Sorry I didn't get a notification for this -- I suck!
Still having this issue? I've never seen this before but it'd be good to hear if you have any updates.
Hi Adrian,
No worries! I put this on the back burner a while ago -- no updates on my end. I asked the folks in charge of the cluster here and they'd never seen the issue, either. My workaround was to save the chain progress every hour or so and just restart it from the last savepoint whenever that happened, so it's not a big deal if this doesn't get resolved.
Thanks! Rodrigo
On Sat, Dec 12, 2015 at 1:08 AM Adrian Price-Whelan < notifications@github.com> wrote:
@rodluger https://github.com/rodluger Sorry I didn't get a notification for this -- I suck!
Still having this issue? I've never seen this before but it'd be good to hear if you have any updates.
— Reply to this email directly or view it on GitHub https://github.com/adrn/mpipool/issues/5#issuecomment-164104610.
I originally posted this on the emcee github but Dan mentioned I try it here. I'm on Red Hat 6.6 with a newly installed anaconda. I am running rather large parallel MCMC chains with ~100 dimensions, 500 walkers and 100,000 steps, and I run into this error once or twice per run. Any ideas?