Usage
makeExperimentRegistry(id = "BatchExperimentRegistry", file.dir,
sharding = TRUE, work.dir, multiple.result.files = FALSE, seed,
packages = character(0L), src.dirs = character(0L),
src.files = character(0L), skip = TRUE)
Arguments
id
[character(1)]
Name of registry.
Displayed e.g. in mails or in cluster queue. Default is
BatchExperimentRegistry.
file.dir
[character(1)]
Path where files
regarding the registry / jobs should be saved. Default
is dQuote{_files} in current working
directory.
sharding
[logical(1)]
Enable sharding to
distribute result files into different subdirectories?
Important if you have many experiments. Default is
TRUE.
work.dir
[character(1)]
Working
directory for R process when experiment is executed.
Default is the current working directory when registry is
created.
multiple.result.files
[logical(1)]
Should a result file be generated for every list element
of the returned list of the algorithm function? Note
that your algorithm functions in
addAlgorithm must return seed
[integer(1)]
Start seed for
experiments. The first experiment in the registry will
use this seed, for the subsequent ones the seed is
incremented by 1. Default is a random number from 1 to
.Machine$integer.max/2.
packages
[character]
Packages that will
always be loaded on each node. Default is
character(0).
src.dirs
[character]
Directories
relative to your work.dir containing R scripts to
be sourced on registry load (both on slave and master).
Files not matching the pattern \.[Rr]$ are
ignored. Useful if you have ma
src.files
[character]
R scripts files
relative to your work.dir to be sourced on
registry load (both on slave and master). Useful if you
have many helper functions that are needed during the
execution of your jobs. These files sh
skip
[logical(1)]
Skip creation of a new
registry if a registry is found in file.dir.
Defaults to TRUE.