===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-157-| ------------- | :-------------: |
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd:158:| `addRegistryPackages` | Set `reg$packages` or `reg$namespaces`, call [saveRegistry()](https://mllg.github.io/batchtools/reference/saveRegistry) |
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-159-| `addRegistrySourceDirs` | - |
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd:160:| `addRegistrySourceFiles` | Set `reg$source`, call [saveRegistry()](https://mllg.github.io/batchtools/reference/saveRegistry) |
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-161-| `batchExpandGrid` | [batchMap](https://mllg.github.io/batchtools/reference/batchMap): `batchMap(..., args = CJ(x = 1:3, y = 1:10))` |
##############################################
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-510-This can be done by prototyping locally ([`testJob()`](https://mllg.github.io/batchtools/reference/testJob) or submit subsets via [`submitJobs()`](https://mllg.github.io/batchtools/reference/submitJobs)).
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd:511:To deploy to the cluster, just copy the file directory (as reported by `reg$file.dir`) to the remote system.
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-512-Next, log in on the cluster (typically via `ssh`), `cd` to the copied directory and call `loadRegistry("<file.dir.on.remote">, "<work.dir.on.remote>", writeable = TRUE)`.
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd:513:This function will (a) source the local configuration file so that you can talk to the cluster (verify by checking the output of `reg$cluster.functions`) and (b) adjust the paths to the new system if argument `update.paths` is set.
r-cran-batchtools-0.9.14+dfsg/vignettes/batchtools.Rmd-514-After loading the Registry, it is advised to test some jobs again with [`testJob()`](https://mllg.github.io/batchtools/reference/testJob) before submitting all of them with `submitJobs(resources = list())` (remember you now need to set resources!).
##############################################
r-cran-batchtools-0.9.14+dfsg/R/Worker.R-72- update = function(reg) {
r-cran-batchtools-0.9.14+dfsg/R/Worker.R:73: "!DEBUG [Worker]: Updating Worker '`self$nodename`'"
r-cran-batchtools-0.9.14+dfsg/R/Worker.R-74- res = private$run(c("status", reg$file.dir))
##############################################
r-cran-batchtools-0.9.14+dfsg/R/Registry.R-185- reg$file.dir = fs::file_temp("registry", tmp_dir = reg$temp.dir)
r-cran-batchtools-0.9.14+dfsg/R/Registry.R:186: "!DEBUG [makeRegistry]: Creating directories in '`reg$file.dir`'"
r-cran-batchtools-0.9.14+dfsg/R/Registry.R-187-
##############################################
r-cran-batchtools-0.9.14+dfsg/R/waitForJobs.R-98- pb$update(mean(ids$terminated), tokens = as.list(stats))
r-cran-batchtools-0.9.14+dfsg/R/waitForJobs.R:99: "!DEBUG [waitForJobs]: batch.ids: `stri_flatten(batch.ids$batch.id, ',')`"
r-cran-batchtools-0.9.14+dfsg/R/waitForJobs.R-100-
##############################################
r-cran-batchtools-0.9.14+dfsg/NEWS.md-60-* Removed functions `getProblemIds()` and `getAlgorithmIds()`.
r-cran-batchtools-0.9.14+dfsg/NEWS.md:61: Instead, you can just access `reg$problems` or `reg$algorithms`, respectively.
r-cran-batchtools-0.9.14+dfsg/NEWS.md-62-* The number of the maximum concurrent jobs can now also be controlled via setting resources.
##############################################
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-157-| ------------- | :-------------: |
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd:158:| `addRegistryPackages` | Set `reg$packages` or `reg$namespaces`, call [saveRegistry()](https://mllg.github.io/batchtools/reference/saveRegistry) |
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-159-| `addRegistrySourceDirs` | - |
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd:160:| `addRegistrySourceFiles` | Set `reg$source`, call [saveRegistry()](https://mllg.github.io/batchtools/reference/saveRegistry) |
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-161-| `batchExpandGrid` | [batchMap](https://mllg.github.io/batchtools/reference/batchMap): `batchMap(..., args = CJ(x = 1:3, y = 1:10))` |
##############################################
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-510-This can be done by prototyping locally ([`testJob()`](https://mllg.github.io/batchtools/reference/testJob) or submit subsets via [`submitJobs()`](https://mllg.github.io/batchtools/reference/submitJobs)).
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd:511:To deploy to the cluster, just copy the file directory (as reported by `reg$file.dir`) to the remote system.
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-512-Next, log in on the cluster (typically via `ssh`), `cd` to the copied directory and call `loadRegistry("<file.dir.on.remote">, "<work.dir.on.remote>", writeable = TRUE)`.
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd:513:This function will (a) source the local configuration file so that you can talk to the cluster (verify by checking the output of `reg$cluster.functions`) and (b) adjust the paths to the new system if argument `update.paths` is set.
r-cran-batchtools-0.9.14+dfsg/inst/doc/batchtools.Rmd-514-After loading the Registry, it is advised to test some jobs again with [`testJob()`](https://mllg.github.io/batchtools/reference/testJob) before submitting all of them with `submitJobs(resources = list())` (remember you now need to set resources!).
##############################################
r-cran-batchtools-0.9.14+dfsg/debian/tests/run-unit-test-6-if [ "$AUTOPKGTEST_TMP" = "" ] ; then
r-cran-batchtools-0.9.14+dfsg/debian/tests/run-unit-test:7: AUTOPKGTEST_TMP=`mktemp -d /tmp/${debname}-test.XXXXXX`
r-cran-batchtools-0.9.14+dfsg/debian/tests/run-unit-test-8- trap "rm -rf $AUTOPKGTEST_TMP" 0 INT QUIT ABRT PIPE TERM