The problem is that Rcpp functions created via sourceCpp can't be serialized (their backing shared library is gone when they are re-serialized). The solution to this is to either:
a) Rebuild them on the cluster nodes (i.e. just include a string with their source and then call sourceCpp on each node); or b) Move your C++ functions into an R package that's available on all the nodes. On Fri, Sep 11, 2015 at 7:55 AM, Rguy <r...@123mail.org> wrote: > I find that when I attempt to export Rcpp functions to a cluster using the > R clusterExport function I get the following error (or some variant > thereof): > > Error in checkForRemoteErrors(val) : > 5 nodes produced errors; first error: NULL value passed as symbol address > > I am running Windows 7, and the cluster is on a quadcore machine. > Exporting ordinary R functions is completely error-free in my setup. > > Has anyone else experienced this problem? Any suggestions on a fix? Thanks. > > _______________________________________________ > Rcpp-devel mailing list > Rcpp-devel@lists.r-forge.r-project.org > https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel >
_______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
