search for: checkclust

Hi! I recognized that the argument matching of clusterApply (and therefore parLapply) goes wrong when one of the arguments of the function is called "c". In this case, the argument "c" is used as cluster and the functions give the following error message "Error in checkCluster(cl) : not a valid cluster". Of course, "c" is for many reasons an unfortunate argument name and this can be easily fixed by the user side. See below for a small example. library(parallel) clu <- makeCluster(2, "PSOCK") fun <- function(x0, x1) (x0 + x1) cluster...

.... You can "alert" yourself when there's a mistake by using: options(warnPartialMatchArgs = TRUE) e.g. > clusterApply(clu, x = 1:2, fun = fun, c = 1) ## Error Warning in clusterApply(clu, x = 1:2, fun = fun, c = 1) : partial argument match of 'c' to 'cl' Error in checkCluster(cl) : not a valid cluster It's still only a warning, but an informative one. /Henrik On Wed, Mar 14, 2018 at 8:50 AM, Florian Schwendinger <Florian_Schwendinger at gmx.at> wrote: > Hi! > > I recognized that the argument matching of clusterApply (and therefore parLapply) goes...

...t;> >> options(warnPartialMatchArgs = TRUE) >> >> e.g. >> >>> clusterApply(clu, x = 1:2, fun = fun, c = 1) ## Error >> Warning in clusterApply(clu, x = 1:2, fun = fun, c = 1) : >> partial argument match of 'c' to 'cl' >> Error in checkCluster(cl) : not a valid cluster >> >> It's still only a warning, but an informative one. >> >> /Henrik >> >> On Wed, Mar 14, 2018 at 8:50 AM, Florian Schwendinger >> <Florian_Schwendinger at gmx.at> wrote: >>> Hi! >>> >>> I...

...You can "alert" yourself when there's a mistake by using: options(warnPartialMatchArgs = TRUE) e.g. > clusterApply(clu, x = 1:2, fun = fun, c = 1) ## Error Warning in clusterApply(clu, x = 1:2, fun = fun, c = 1) : partial argument match of 'c' to 'cl' Error in checkCluster(cl) : not a valid cluster It's still only a warning, but an informative one. /Henrik On Wed, Mar 14, 2018 at 8:50 AM, Florian Schwendinger <Florian_Schwendinger at gmx.at> wrote: > Hi! > > I recognized that the argument matching of clusterApply (and therefore parLapply) goes...

...) Find a way of running the meta function in parallel mode. Specifically, the code that I'm running is: urllist <- lapply(workingcorpus, meta, tag = "FeedUrl") Unfortunately, I receive the following error message when I try to use the command "parLapply" "Error in checkCluster(cl) : not a valid cluster Calls: parLapply ... is.vector -> clusterApply -> staticClusterApply -> checkCluster" 2) Alternatively, I wonder if there might be a way of extracting all of the meta data into a data.frame that would be faster for processing? Thanks for any suggestion...

Hello, is there any function in the package snow to check for a really running cluster? The function checkCluster only checks the variable cl. And the variable is still available after stopping the cluster! ( a simple solution would be deleting the cluster variable cl in the function stopCluster) > library(snow) > cl <- makeCluster(5) 5 slaves are spawned successfully. 0 failed. > c...

...n there's a mistake by using: > > options(warnPartialMatchArgs = TRUE) > > e.g. > >> clusterApply(clu, x = 1:2, fun = fun, c = 1) ## Error > Warning in clusterApply(clu, x = 1:2, fun = fun, c = 1) : > partial argument match of 'c' to 'cl' > Error in checkCluster(cl) : not a valid cluster > > It's still only a warning, but an informative one. > > /Henrik > > On Wed, Mar 14, 2018 at 8:50 AM, Florian Schwendinger > <Florian_Schwendinger at gmx.at> wrote: >> Hi! >> >> I recognized that the argument matching of...

...bject with foreach > Error in assign("data", data, pos = .foreachGlobals, inherits = FALSE) : > object 'cl' not found > Calls: registerDoSNOW -> setDoPar -> assign >> x<- foreach(i = 1:3) %dopar% { # simple test > + sqrt(i) > + } > Error in checkCluster(cl) : not a valid cluster > Calls: %dopar% -> <Anonymous> -> clusterCall -> checkCluster >> x > Error: object 'x' not found >> stopCluster(cl) # properly shut down the cluster > Error in stopCluster(cl) : object 'cl' not found >> >...