Explicit calls to parallel:: (should not be?)

[the-magister]

Hi Andy,

We're working through using Rmpi under snow, and noted that there's a lot of explicit calls to parallel:: that I think should not be explicit. If they're not explicit, then the overloads from snow:: should work properly.

Would you be willing to consider a pull request to change the behavior to allow Rmpi as the parallel backend?

Warm Regards,
Mike Dodds

library(snow)
The following objects are masked from ‘package:parallel’:

clusterApply, clusterApplyLB, clusterCall, clusterEvalQ,
clusterExport, clusterMap, clusterSplit, makeCluster, parApply,
parCapply, parLapply, parRapply, parSapply, splitIndices,
stopCluster

[andrewhooker]

Hi Mike, Sure. That sounds reasonable. Thanks for the help! Best regards, Andy

…

On 15 Dec 2017, at 3:15 , the-magister ***@***.***> wrote: Hi Andy, We're working through using Rmpi under snow, and noted that there's a lot of explicit calls to parallel:: that I think should not be explicit. If they're not explicit, then the overloads from snow:: should work properly. Would you be willing to consider a pull request to change the behavior to allow Rmpi as the parallel backend? Warm Regards, Mike Dodds library(snow) #The following objects are masked from ‘package:parallel’: clusterApply, clusterApplyLB, clusterCall, clusterEvalQ, clusterExport, clusterMap, clusterSplit, makeCluster, parApply, parCapply, parLapply, parRapply, parSapply, splitIndices, stopCluster — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#18>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFLmZD7atRmghxnzda09YtxIAa00kfpGks5tAdZNgaJpZM4RC7Sx>.