-
After a long journey of configuring different software versions on HPC (cf. #333 ), I ended up finding countless and inconsistent errors across nodes and sessions in HPC. Now I am trying to move on to…
-
+ Bridging python packages (`dask-geopandas`, `geopolars`, `cuSpatial`) to R workflow
+ Optimal splitting of computational regions regarding shape complexity and input data resolutions
+ Streamlined…
-
R-CMD-CHECK give a build note commenting on the large number of dependencies we have. It would be sensible to review this and reduce them where possible. We should take a systematic approach and where…
-
# Issue
```sh
$ R_FUTURE_PLAN=future.callr::callr R CMD build future.apply
* checking for file ‘future.apply/DESCRIPTION’ ... OK
* preparing ‘future.apply’:
* checking DESCRIPTION meta-informat…
-
we should be able during toposort to asynchronoulsy start jobs with future / callr
-
Thanks for automating this task and for giving it a nice UI! I learned of it via the responses to [this tweet](https://twitter.com/JennyBryan/status/1343636610982662144).
The package I'm interested…
-
They should not be red if our global calling handler is working right
```r
rlang::inform("hi")
callr::r(function() { rlang::inform("hi") }, show = TRUE)
```
Like `pkgdown::build_site()`
-
I am really happy to see `future` extend to so many forms of parallelism!
Is there anything we can do about overhead?
```r
library(future.callr)
library(microbenchmark)
library(parallel)
n…
-
-
Hi,
I'm trying to launch some processes that can sometimes throw a segfault (And this can't be predicted or modified since I don't have the source code).
This MWE code is behaving has I want using…