|
95 | 95 | "shutdown" code resource specifications via character vectors |
96 | 96 | `resources[["startup"]]` and `resources[["shutdown"]]`. When |
97 | 97 | specified, corresponding lines are injected in the generated job |
98 | | - script and the beginning and end, respectively. |
| 98 | + script at the beginning and end, respectively. |
99 | 99 |
|
100 | 100 | - All built-in template job scripts support a "details" resource |
101 | 101 | specification via logical scalar `resources[["details"]]`. If |
|
131 | 131 | `fs.latency` seconds (default 65 seconds) to give job schedulers |
132 | 132 | and any global file system time to write output to file. Now |
133 | 133 | **future.batchtools** will no longer wait for such files and only |
134 | | - read their content if they exists when checked. |
| 134 | + read their content if they exist when checked. |
135 | 135 |
|
136 | 136 | ## Deprecated and Defunct |
137 | 137 |
|
138 | 138 | * R option `future.delete` is deprecated. Please use new R option |
139 | | - `future.batchtools.delete` instead. For backward compatible |
140 | | - reasons, if R option `future.delete` sets option |
141 | | - `future.batchtools.delete` when the packages is loaded and the |
| 139 | + `future.batchtools.delete` instead. For backward compatibility |
| 140 | + reasons, R option `future.delete` sets option |
| 141 | + `future.batchtools.delete` when the package is loaded, if the |
142 | 142 | latter is not already set. If `future.delete` is FALSE, then |
143 | 143 | `future.batchtools.delete` is set to `"never"`. If `future.delete` |
144 | 144 | is TRUE, then `future.batchtools.delete` is set to `"on-success"`. |
|
149 | 149 | ## Bug Fixes |
150 | 150 |
|
151 | 151 | * Attempts to cancel batchtools futures via `cancel()` would result |
152 | | - in "Interruption of futures require a backend implementing the |
| 152 | + in "Interruption of futures requires a backend implementing the |
153 | 153 | FutureBackend API". Until this package implements the new |
154 | 154 | FutureBackend API of future (>= 1.40.0), any calls to `cancel()` |
155 | 155 | will be silently ignored. |
|
170 | 170 | * Improved performance of batchtools futures by avoiding re-checking |
171 | 171 | the **batchtools** status if the **batchtools** job has already |
172 | 172 | been observed to be resolved. Checking the **batchtools** status |
173 | | - is fairly expense, especially since each status check queries a set |
| 173 | + is fairly expensive, especially since each status check queries a set |
174 | 174 | of files on the file system. |
175 | 175 |
|
176 | 176 | * Improved performance of batchtools futures by making the removal of |
|
189 | 189 | * `R_FUTURE_BATCHTOOLS_*` environment variables are now only read |
190 | 190 | when the **future.batchtools** package is loaded, where they set |
191 | 191 | the corresponding `future.batchtools*` option. This is in line |
192 | | - with how all packages in the Futureverse works. |
| 192 | + with how all packages in the Futureverse work. |
193 | 193 |
|
194 | 194 | * Add `nbrOfFreeWorkers()` for batchtools futures. |
195 | 195 |
|
|
205 | 205 | `batchtools_multicore` worker. |
206 | 206 |
|
207 | 207 | * `print()` for BatchtoolsFuture now reports on the batchtools |
208 | | - configuration file (an R script) and the the batchtools job template |
| 208 | + configuration file (an R script) and the batchtools job template |
209 | 209 | file (a shell script) with info on location, file size, and number |
210 | 210 | of lines, if they exist. |
211 | 211 |
|
212 | | - * `run()` for BatchtoolsFuture now produce an informative |
| 212 | + * `run()` for BatchtoolsFuture now produces an informative |
213 | 213 | BatchtoolsFutureError in case `batchtools::submitJobs()` fails, for |
214 | 214 | instance, due to invalid job-scheduler resource specifications. |
215 | 215 |
|
|
261 | 261 |
|
262 | 262 | ## Significant Changes |
263 | 263 |
|
264 | | - * Lazy batchtools futures only creates the internal **batchtools** |
| 264 | + * Lazy batchtools futures only create the internal **batchtools** |
265 | 265 | registry when the future is launched. |
266 | 266 |
|
267 | 267 | * Removed S3 generic functions `await()`, `finished()`, and |
|
455 | 455 | * The period between each poll of the scheduler to check whether a |
456 | 456 | future (job) is finished or not now increases geometrically as a |
457 | 457 | function of number of polls. This lowers the load on the scheduler |
458 | | - for long running jobs. |
| 458 | + for long-running jobs. |
459 | 459 |
|
460 | | - * The error message for expired batchtools futures now include the |
| 460 | + * The error message for expired batchtools futures now includes the |
461 | 461 | last few lines of the logged output, which sometimes includes clues |
462 | 462 | on why the future expired. For instance, if a TORQUE/PBS job use |
463 | 463 | more than the allocated amount of memory it might be terminated by |
|
0 commit comments