similar to: Get Logical processor count correctly whether NUMA is enabled or disabled

Dear Tomas, thank you for looking into this. Here's the output: # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors", intern=TRUE) [1] "NumberOfLogicalProcessors \r" "22 \r" "22 \r" [4] "20 \r"

Dear Tomas, thank you very much. I installed r-devel r75201 and tested. The machine with 88 cores has NUMA disabled. It therefore has 2 processor groups with 64 and 24 processors each. require(parallel) detectCores() # [1] 88 This is great! Then I went on to test with a simple 'foreach()' loop. I started with 64 processors (max limit of 1 processor group). I ran with a simple function

Dear Arun, thank you for checking the workaround scripts. I've modified detectCores() to use GetLogicalProcessorInformationEx. It is in revision 75198 of R-devel, could you please test it on your machines? For a binary, you can wait until the R-devel snapshot build gets to at least this svn revision. Thanks for the link to the processor groups documentation. I don't have a machine

A summary for reference: the new detectCores() for Windows in R-devel seems to be working both for logical and physical cores on systems with >64 logical processors? (thanks to Arun for testing!). If the feature is important for anyone particularly using an older version of Windows and/or on a system with >64 logical processors, it would be nice if you could test and report any

Dear Arun, thank you for the report. I agree with the analysis, detectCores() will only report logical processors in the NUMA group in which R is running. I don't have a system to test on, could you please check these workarounds for me on your systems? # number of logical processors - what detectCores() should return out <- system("wmic cpu get numberoflogicalprocessors",

Hi, Both under the current R-devel (r66456) and a version from about 3 months ago, I experience the following behavior: > parallel::detectCores(TRUE) Error in system(cmd, TRUE) : error in running command > traceback() 3: system(cmd, TRUE) 2: gsub("^ +", "", system(cmd, TRUE)[1]) 1: parallel::detectCores(TRUE) > This is on Ubuntu 14.04. Does anybody else see this? [I

In the 'parallel' package there is detectCores(), which tries its best to infer the number of cores on the current machine. This is useful if you wish to utilize the *maximum* number of cores on the machine. Several are using this to set the number of cores when parallelizing, sometimes also hardcoded within 3rd-party scripts/package code, but there are several settings where you wish to

Dear members, I am using arfima in an mclapply construction (from the parallel package): Browse[2]> LYG <- mclapply(LYGH, FUN = arfima, mc.cores = detectCores()) ^C Browse[2]> LYG <- mclapply(LYGH[1:10], FUN = arfima, mc.cores = detectCores()) ^C Browse[2]> LYG <- mclapply(LYGH[1:2], FUN = arfima, mc.cores = detectCores()) ^C You can see that I am

Dear expeRts, I struggle with the following problem using snow clusters for parallel computing: I would like to specify l'Ecuyer's random number generator. Base R creates a .Random.seed of length 7, the first value indicating the kind fo random number generator. I would thus like to use the components 2 to 7 as the seed for l'Ecuyer's random number generator. By doing so, I

In R 3.3.2 detectCores() in package parallel reports 2 rather than 1 on Raspberry Pi B+ running Raspbian. (This report is just 'for the record'. The model is superseded and I think no longer produced.) The problem seems to be caused by grep processor /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) (On Raspberry Pi 2 and 3 there is no error because

Hi all, I can't get the functionality of the package parallel to work. Specifically, makeCluster() hangs when I run it. I first noticed the problem when trying to run Rstan with multiple cores and the traced it back to the core package parallel. The following results in R hanging after the call to makeCluster. library(parallel) # Calculate the number of cores no_cores <-

Background: As of Windows 10 version 2004, the wmic client no longer works. It gets the following error - [wmi/wmic.c:196:main()] ERROR: Login to remote object. NTSTATUS: NT code 0x80010111 - NT code 0x80010111 This seems to be an RPC header error. Presumably Microsoft changed something that broke wmic. Since I found wmic.c in the samba source I thought that it might be able to be compiled as

I see that the Samba sources include the WMI client (wmic), but I have not succeeded in getting the configure/make to build it. Does anyone know if this feature is supported in current (4.7.4) Samba, and, if so, how to build it? Steve Koehler

I've started to use the parallel package and it works very well speeding things up. Thank you for making this easy to do. Should I have expected that parCapply would return a vector when parApply returns a matrix? library(parallel) x <- matrix(rnorm(8), nc = 2) apply(x, 2, function(y) y) [,1] [,2] [1,] -0.9649685 0.91339851 [2,] -1.4313140 0.13457671 [3,] 1.0499248

Thanks for the pointer. I will take a look. Steve Koehler On Wed, Feb 21, 2018 at 2:44 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Wed, 2018-02-21 at 14:05 -0600, Stephen Koehler wrote: > > Andrew, > > > > Thanks very much. After sending my question, I discovered that the DCOM > area was disabled in the build as of 8 years ago, so it became clear

Hi R-developers In the package Parallel, the function parLapply(cl, x, f) seems to allow transmission of only one parameter (x) to the function f. Hence in order to compute f(x, y) parallelly, I had to define f(x, y) as f(x) and tried to access y within the function, whereas y was defined outside of f(x). Script: library(parallel) f <- function(x) { z <- 2 * x + .GlobalEnv$y # Try to

Hi, I have a question on wmic, the linux wmi client, which uses samba. Is this mailing list the right place to ask? or there is a better forum or mailing list to ask? Basically, I want to ask if wmic supports UTF-8 for its output or not. If yes, how to turn it on? By default, it doesn't return UTF-8 for extended ascii characters. I tried to put "unix charset?=?UTF8" in a config

Dear Henrik, thank you, for the quick reply. Bizarrely enough, the problem vanished when I woke the computer from sleep (I had previously replicated the problem after several restarts of both R and the MacOS). I will follow-up if I can again replicate the problem. Florian On 2/10/18 4:39 PM, Henrik Bengtsson wrote: > A few quick comments: > > * You mention R --vanilla, but make sure

Well, this is interesting (to me, at least). I joined a W10 machine to the domain (4.8/4.9.4 mix, I'm working on it), then renamed it via "WMIC /node:<computer> computersystem where name="<computer>" call rename name="<newname>". Doing so changed the displayName, sAMAccountName, dNSHostName, and assorted servicePrincipalNames, but did not change the

Henrik, the whole point and only purpose of mc* functions is to fork. That's what the multicore package was about, so if you don't want to fork, don't use mc* functions - they don't have any other purpose. I really fail to see the point - if you use mc* functions you're very explicitly asking for forking - so your argument is like saying that print() should have an option to