Description Usage Arguments Value See Also
The sub-folders under a given path are iteratively processed.
For each folder, the function check.directory
returns either
TRUE
if we should investigate it (recursively) or FALSE
, if
we should ignore it. By default we assume TRUE
. Files in a folder
can either be processed one-by-one (via file.single
) or all together
(via file.in.folder
). Both file.single
and
file.in.folder
are environments. The names in these environments are
regular expressions which are matched against the files in the folders. The
values are handler methods of the type function(root, path(s))
.
(paths
for file.in.folder
, path
for
file.single
). These handlers are applied to all the single files
(file.single
) or the list of files in a folder
(file.in.folder
) that match to their names. The names could, e.g.,
be regular expressions matching to file extensions created by
path.extensionRegExp
.
The processing can either take place sequentially (for values of
core<=1L
) or in parallel (cores>1L
). In the latter case, we
first gather all handler applications that need to be done and then pass
them to mclapply
.
This function is not supposed to return anything useful. Instead, the idea is that the handlers would read their input files and create output files storing their result.
1 2 3 |
path |
the path to explore recursively |
file.single |
an environment or named list with file consumers of the
form |
file.in.folder |
an environment or named list with file consumers of the form
|
check.directory |
a function of the form |
cores |
the number of cores to use. If |
logging |
the logging setup, see |
an unnamed and recursively unlisted vector of the results of all the processors, with no pre-defined order
path.extensionRegExp
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.