11Package: future.batchtools
22==========================
33
4+ Version: 0.7.2 [2018-12-03]
5+
6+ DOCUMENTATION:
7+
8+ * Add a simple example(future_custom).
9+
10+ FIXES:
11+
12+ * Made internal code agile to upcoming changes in the future package on
13+ how a captured error is represented.
14+
15+ SOFTWARE QUALITY:
16+
17+ * FYI: Every release is tested against one Torque/PBS and one SGE scheduler.
18+
19+ BUG FIXES:
20+
21+ * resolve() on a lazy batchtools future would stall and never return.
22+
23+
424Version: 0.7.1 [2018-07-18]
525
626NEW FEATURES:
727
8- o The batchtools_* backends support the handling of the standard output as
28+ * The batchtools_* backends support the handling of the standard output as
929 implemented in future (>= 1.9.0).
1030
1131BUG FIXES:
1232
13- o A bug was introduced in future.batchtools 0.7.0 that could result in "Error
33+ * A bug was introduced in future.batchtools 0.7.0 that could result in "Error
1434 in readLog(id, reg = reg) : Log file for job with id 1 not available" when
1535 using one of the batchtools backends. It occurred when the value was
1636 queried. It was observered using 'batchtools_torque' but not when using
@@ -22,7 +42,7 @@ Version: 0.7.0 [2018-05-03]
2242
2343NEW FEATURES:
2444
25- o Argument 'workers' of future strategies may now also be a function, which
45+ * Argument 'workers' of future strategies may now also be a function, which
2646 is called without argument when the future strategy is set up and used as
2747 is. For instance, plan(callr, workers = halfCores) where
2848 halfCores <- function() { max(1, round(availableCores() / 2)) } will use
@@ -31,91 +51,91 @@ NEW FEATURES:
3151
3252CODE REFACTORING:
3353
34- o Preparing for futures to gather a richer set of results from batchtools
54+ * Preparing for futures to gather a richer set of results from batchtools
3555 backends.
3656
3757
3858Version: 0.6.0 [2017-09-10]
3959
4060NEW FEATURES:
4161
42- o If the built-in attempts of batchtools for finding a default template file
62+ * If the built-in attempts of batchtools for finding a default template file
4363 fails, then system("templates", package = "future.batchtools") is searched
4464 for template files as well. Currently, there exists a `torque.tmpl` file.
4565
46- o A job's name in the scheduler is now set as the future's label (requires
66+ * A job's name in the scheduler is now set as the future's label (requires
4767 batchtools 0.9.4 or newer). If no label is specified, the default job name
4868 is controlled by batchtools.
4969
50- o The period between each poll of the scheduler to check whether a future
70+ * The period between each poll of the scheduler to check whether a future
5171 (job) is finished or not now increases geometrically as a function of number
5272 of polls. This lowers the load on the scheduler for long running jobs.
5373
54- o The error message for expired batchtools futures now include the last few
74+ * The error message for expired batchtools futures now include the last few
5575 lines of the logged output, which sometimes includes clues on why the future
5676 expired. For instance, if a TORQUE/PBS job use more than the allocated
5777 amount of memory it might be terminated by the scheduler leaving the message
5878 "PBS: job killed: vmem 1234000 exceeded limit 1048576" in the output.
5979
60- o print() for BatchtoolsFuture returns the object invisibly.
80+ * print() for BatchtoolsFuture returns the object invisibly.
6181
6282BUG FIXES:
6383
64- o Calling future_lapply() with functions containing globals part of non-default
84+ * Calling future_lapply() with functions containing globals part of non-default
6585 packages would when using batchtools futures give an error complaining that
6686 the global is missing. This was due to updates in future (>= 1.4.0) that
6787 broke this package.
6888
69- o loggedOutput() for BatchtoolsFuture would always return NULL unless an error
89+ * loggedOutput() for BatchtoolsFuture would always return NULL unless an error
7090 had occurred.
7191
7292
7393Version: 0.5.0 [2017-06-02]
7494
75- o First version submitted to CRAN.
95+ * First version submitted to CRAN.
7696
7797SOFTWARE QUALITY:
7898
79- o Added more tests; test coverage now at 93%.
99+ * Added more tests; test coverage now at 93%.
80100
81101
82102Version: 0.4.0 [2017-05-16]
83103
84104NEW FEATURES:
85105
86- o Added batchtools_custom() for specifying batchtools futures using any type
106+ * Added batchtools_custom() for specifying batchtools futures using any type
87107 of batchtools cluster functions.
88108
89- o batchtools_template(pathname = NULL, type = <type>) now relies on the
109+ * batchtools_template(pathname = NULL, type = <type>) now relies on the
90110 batchtools package for locating the <type> template file.
91111
92- o nbrOfWorkers() for batchtools futures now defaults to +Inf unless the
112+ * nbrOfWorkers() for batchtools futures now defaults to +Inf unless the
93113 evaluator's 'workers' or 'cluster.functions' specify something else.
94114
95- o Renamed argument 'pathname' to 'template' for batchtools_<tmpl>() functions.
115+ * Renamed argument 'pathname' to 'template' for batchtools_<tmpl>() functions.
96116
97117BUG FIXES:
98118
99- o Under plan(batchjobs_*), when being created futures would produce an error
119+ * Under plan(batchjobs_*), when being created futures would produce an error
100120 on "all(is.finite(workers)) is not TRUE" due to an outdated sanity check.
101121
102122SOFTWARE QUALITY:
103123
104- o TESTS: Added test of future_lapply() for batchtools backends.
124+ * TESTS: Added test of future_lapply() for batchtools backends.
105125
106- o TESTS: Added optional tests for batchjobs_* HPC schedulers listed in
126+ * TESTS: Added optional tests for batchjobs_* HPC schedulers listed in
107127 environment variable 'R_FUTURE_TESTS_STRATEGIES'.
108128
109129CODE REFACTORING:
110130
111- o CLEANUP: Package no longer depends on R.utils.
131+ * CLEANUP: Package no longer depends on R.utils.
112132
113133
114134Version: 0.3.0 [2017-03-19]
115135
116136NEW FEATURES:
117137
118- o The number of jobs one can add to the queues of HPC schedulers is in
138+ * The number of jobs one can add to the queues of HPC schedulers is in
119139 principle unlimited, which is why the number of available workers for such
120140 batchtools_* backends is reported as +Inf. However, as the number of
121141 workers is used by future_lapply() to decide how many futures should be used
@@ -128,14 +148,14 @@ Version: 0.2.0 [2017-02-23]
128148
129149GLOBALS:
130150
131- o batchtools (>= 0.9.2) now supports exporting objects with any type of names
151+ * batchtools (>= 0.9.2) now supports exporting objects with any type of names
132152 (previously only possible if they mapped to to strictly valid filenames).
133153 This allowed me to avoid lots of internal workaround code encoding and
134154 decoding globals.
135155
136156
137157Version: 0.1.0 [2017-02-11]
138158
139- o Package created by porting the code of future.BatchJobs. This version passes
159+ * Package created by porting the code of future.BatchJobs. This version passes
140160 'R CMD check --as-cran' with all OK after a minimal amount of adjustments
141161 to the ported code.
0 commit comments