![]() The error messages that I get are “ Error in FUN(X]. ![]() If mc.cores = parallel::detectCores(), then the behavior is almost the same as with RStudio, but the messages differ. If I open up a terminal and run R from that terminal, I get different behavior: If I don’t set mc.cores, then each chain runs in serial, one after the other, and they all finish without any apparent problems. When each chain starts, I get a (presumably benign) message like “ starting worker pid=6810 on localhost:11280 at 09:48:12.300”. doTr圜atch -> sendData -> sendData.SOCK0node -> serialize, and Execution halted. Depending on the model, I may also get the error messages: Error in serialize(data, node$con, xdr = FALSE) : ignoring SIGPIPE signal, Calls. I get the error message “ Error in unserialize(socklist]) : error reading from connection” after one of the chains dies. With one model, 2 out of 4 chains complete, and with my other model, all of the chains just die. If mc.cores = parallel::detectCores(), then some or all of the chains will die prematurely. If I sample a couple of my models from within RStudio (given simulated data), then one of two things happens: ![]() Hopefully, I’ll have clarified things here.įirst off, platform and versions: macOS High Sierra, version 10.13.6 R, version 3.6.1 RStudio, version 1.1.456 RStan, version 2.18.2. This is a continuation of the problem that I poorly described here: Complaints about slot "mode" rearing their head again
0 Comments
Leave a Reply. |