moduleCodeFiles

This can be used e.g., for Caching, to identify which files have changed.

Provides the core framework for a discrete event system to
implement a complete data-to-decisions, reproducible workflow.
The core components facilitate the development of modular pieces,
and enable the user to include additional functionality by running user-built modules.
Includes conditional scheduling, restart after interruption, packaging of
reusable modules, tools for developing arbitrary automated workflows,
automated interweaving of modules of different temporal resolution,
and tools for visualizing and understanding the within-project dependencies.
The suggested package 'NLMR' can be installed from the repository
(<https://PredictiveEcology.r-universe.dev>).

Eliot J B

SpaDES.core

Core Utilities for Developing and Running Spatially Explicit
Discrete Event Models

Alex M Chubaty

Eliot J B McIntire

Yong Luo

Steve Cumming

Ceres Barros

His Majesty the King in Right of Canada, as represented by the Minister of Natural Resources Canada 

moduleCodeFiles function

<dl><dt>paths</dt>
<dd>An optional named list with up to 4 named elements,
<code>modulePath</code>, <code>inputPath</code>, <code>outputPath</code>, and <code>cachePath</code>.
See details. NOTE: Experimental feature now allows for multiple <code>modulePath</code>s
to be specified in a character vector. The modules will be searched for sequentially
in the first <code>modulePath</code>, then if it doesn't find it, in the second etc.</dd>
<dt>modules</dt>
<dd>A named list of character strings specifying the names of modules to be loaded
for the simulation.
Note: the module name should correspond to the R source file from which the module is loaded.
Example: a module named "caribou" will be sourced form the file <code class="file">caribou.R</code>,
located at the specified <code>modulePath(simList)</code> (see below).</dd></dl>

Arguments

Extract the full file paths for R source code — moduleCodeFiles

<dl>

<dt>paths</dt>
<dd>An optional named list with up to 4 named elements,
<code>modulePath</code>, <code>inputPath</code>, <code>outputPath</code>, and <code>cachePath</code>.
See details. NOTE: Experimental feature now allows for multiple <code>modulePath</code>s
to be specified in a character vector. The modules will be searched for sequentially
in the first <code>modulePath</code>, then if it doesn't find it, in the second etc.</dd>


<dt>modules</dt>
<dd>A named list of character strings specifying the names of modules to be loaded
for the simulation.
Note: the module name should correspond to the R source file from which the module is loaded.
Example: a module named "caribou" will be sourced form the file <code class="file">caribou.R</code>,
located at the specified <code>modulePath(simList)</code> (see below).</dd>

</dl>

moduleCodeFiles: Extract the full file paths for R source code

Description

Usage

Value

Arguments