Displaying 3 results from an estimated 3 matches for "batchtools".
2019 Dec 15
1
system2 doesn't quote stdin on unix, unlike stdout, stderr & input and on Windows
...h?q=org%3Acran+system2%28+stdin&type=Code
The search is probably computationally expensive and thus might only be available to GitHub account holders. The results are:
- BatchJobs: R/WorkerLinux.R; stdin is "" by default, filenames generated by
cfBrewTemplate aren't quoted
- batchtools: callers of runOSCommand actually quote the stdin argument!
https://github.com/mllg/batchtools/commit/4a5818d70c82c8842c0b8bded224dbb423b79f33
- nat: R/cmtk.R, R/xformpoints.R; stdin is tempfile(...)
- credentials: R/credential-api.R; stdin is passed as-is, tempfile() or
"" in def...
2020 Apr 29
0
mclapply returns NULLs on MacOS when running GAM
...amework tries to take this
developer-end-user separation one step further and with a lower level
API - future(), value(), resolved() - for which different parallel
backends have been implemented, e.g. multicore, multisession
("PSOCK"), cluster (any parallel::makeCluster() cluster), callr,
batchtools (HPC job schedulers), etc. All these have been tested to
conform to the Future API specs, so we know our parallel code works
regardless of which of these backends the user picks. Now, based on
these basic future low-level functions, other higher level APIs have
been implemented. For instance, th...
2020 Apr 29
2
mclapply returns NULLs on MacOS when running GAM
Thanks Simon,
I will take note of the sensible default for core usage. I?m trying to achieve small scale parallelism, where tasks take 1-5 seconds and make fuller use of consumer hardware. Its not a HPC-worthy computation but even laptops these days come with 4 cores and I don?t see a reason to not make use of it.
The goal for the current piece of code I?m working on is to bootstrap many