|
55 | 55 |
|
56 | 56 | ## Bug Fixes |
57 | 57 |
|
58 | | - * `plan(batchtools_multicore)` did not support `workers` argument |
59 | | - being a function. |
| 58 | + * `plan(future.batchtools::batchtools_multicore)` did not support |
| 59 | + `workers` argument being a function. |
60 | 60 |
|
61 | 61 |
|
62 | 62 | # Version 0.12.0 [2023-02-24] |
|
93 | 93 |
|
94 | 94 | * It is now possible to tweak arguments used by an underlying |
95 | 95 | `batchtools::makeClusterFunctionsNnn()` function for some of the |
96 | | - `batchtools_nnn` backends, e.g. `plan(batchtools_slurm, |
97 | | - scheduler.latency = 60)`. |
| 96 | + `batchtools_nnn` backends, e.g. |
| 97 | + `plan(future.batchtools::batchtools_slurm, scheduler.latency = 60)`. |
98 | 98 |
|
99 | | - * `plan(batchtools_multicore, workers = I(1))` overrides the fallback |
100 | | - to `batchtools_local` and forces a single `batchtools_multicore` |
101 | | - worker. |
| 99 | + * `plan(future.batchtools::batchtools_multicore, workers = I(1))` |
| 100 | + overrides the fallback to `batchtools_local` and forces a single |
| 101 | + `batchtools_multicore` worker. |
102 | 102 |
|
103 | 103 | * `print()` for BatchtoolsFuture now reports on the batchtools |
104 | 104 | configuration file (an R script) and the the batchtools job template |
|
142 | 142 |
|
143 | 143 | ## Bug Fixes |
144 | 144 |
|
145 | | - * Using `plan(batchtools_nnn, finalize = FALSE)` would give a warning |
146 | | - on `Detected 1 unknown future arguments: 'finalize'`. |
| 145 | + * Using `plan(future.batchtools::batchtools_nnn, finalize = FALSE)` |
| 146 | + would give a warning on `Detected 1 unknown future arguments: |
| 147 | + 'finalize'`. |
147 | 148 |
|
148 | 149 | * Template files in `system.file(package = "future.batchtools", |
149 | 150 | "templates")` were not found. |
|
198 | 199 | `future.batchtools.workers` or environment variable |
199 | 200 | `R_FUTURE_BATCHTOOLS_WORKERS`. |
200 | 201 |
|
201 | | - * It is now possible to configure the **batchtools** registries that are |
202 | | - used by batchtools futures via new argument `registry` to `plan()`. |
203 | | - This argument should be a named list of parameters recognized by |
204 | | - the **batchtools** package, e.g. `plan(batchtools_sge, registry = |
| 202 | + * It is now possible to configure the **batchtools** registries that |
| 203 | + are used by batchtools futures via new argument `registry` to |
| 204 | + `plan()`. This argument should be a named list of parameters |
| 205 | + recognized by the **batchtools** package, |
| 206 | + e.g. `plan(future.batchtools::batchtools_sge, registry = |
205 | 207 | list(...))`. For notable example, see below news entries. |
206 | 208 |
|
207 | 209 | * The default working directory for batchtools futures is the current |
208 | 210 | working directory of R _when_ the batchtools future is created. |
209 | | - This corresponds to specifying `plan(batchtools_nnn, registry = |
210 | | - list(work.dir = NULL)`. Sometimes it is useful to use a explicit |
211 | | - working directory that is guaranteed to be available on all workers |
212 | | - on a shared file system, e.g. `plan(batchtools_nnn, registry = |
| 211 | + This corresponds to specifying |
| 212 | + `plan(future.batchtools::batchtools_nnn, registry = list(work.dir = |
| 213 | + NULL)`. Sometimes it is useful to use a explicit working directory |
| 214 | + that is guaranteed to be available on all workers on a shared file |
| 215 | + system, e.g. `plan(future.batchtools::batchtools_nnn, registry = |
213 | 216 | list(work.dir = "~"))`. |
214 | 217 |
|
215 | 218 | * It is possible to control if and how **batchtools** should use file |
216 | 219 | compression for exported globals and results by specifying |
217 | | - **batchtools** registry parameter `compress`. For example, to turn off |
218 | | - file compression, use `plan(batchtools_nnn, registry = |
219 | | - list(compress = FALSE))`. |
| 220 | + **batchtools** registry parameter `compress`. For example, to turn |
| 221 | + off file compression, use `plan(future.batchtools::batchtools_nnn, |
| 222 | + registry = list(compress = FALSE))`. |
220 | 223 |
|
221 | 224 | * The default location of the `.future` folder can be controlled by R |
222 | 225 | option `future.cache.path` or environment variable |
223 | 226 | `R_FUTURE_CACHE_PATH`. |
224 | 227 |
|
225 | 228 | * `batchtools_custom()` and BatchtoolsFuture gained argument |
226 | | - `conf.file`. Using `plan(batchtools_custom)` will now use any |
227 | | - **batchtools** configuration file (an R script) found on the |
228 | | - `batchtools::findConfFile()` search path. |
| 229 | + `conf.file`. Using `plan(future.batchtools::batchtools_custom)` |
| 230 | + will now use any **batchtools** configuration file (an R script) |
| 231 | + found on the `batchtools::findConfFile()` search path. |
229 | 232 |
|
230 | 233 |
|
231 | 234 | ## Documentation |
|
322 | 325 |
|
323 | 326 | * Argument `workers` of future strategies may now also be a function, |
324 | 327 | which is called without argument when the future strategy is set up |
325 | | - and used as-is. For instance, `plan(callr, workers = halfCores)` |
326 | | - where `halfCores <- function() { max(1, round(availableCores() / |
327 | | - 2)) }` will use half of the number of available cores. This is |
328 | | - useful when using nested future strategies with remote machines. |
| 328 | + and used as-is. For instance, `plan(future.callr::callr, workers = |
| 329 | + halfCores)` where `halfCores <- function() { max(1, |
| 330 | + round(availableCores() / 2)) }` will use half of the number of |
| 331 | + available cores. This is useful when using nested future |
| 332 | + strategies with remote machines. |
329 | 333 |
|
330 | 334 |
|
331 | 335 | ## Code Refactoring |
|
395 | 399 |
|
396 | 400 | ## Bug Fixes |
397 | 401 |
|
398 | | - * Under `plan(batchtools_*)`, when being created futures would |
399 | | - produce an error on `all(is.finite(workers)) is not TRUE` due to an |
400 | | - outdated sanity check. |
| 402 | + * Under `plan(future.batchtools::batchtools_nnn)`, when being created |
| 403 | + futures would produce an error on `all(is.finite(workers)) is not |
| 404 | + TRUE` due to an outdated sanity check. |
401 | 405 |
|
402 | 406 |
|
403 | 407 | ## Software Quality |
|
424 | 428 | decide how many futures should be used to best partition the |
425 | 429 | elements, this means that `future_lapply()` will always use one |
426 | 430 | future per element. Because of this, it is now possible to specify |
427 | | - `plan(batchtools_*, workers = n)` where `n` is the target number of |
428 | | - workers. |
| 431 | + `plan(future.batchtools::batchtools_nnn, workers = n)` where `n` is |
| 432 | + the target number of workers. |
429 | 433 |
|
430 | 434 |
|
431 | 435 | # Version 0.2.0 [2017-02-23] |
|
0 commit comments