SpaDES
simulationsAs part of a reproducible work flow, caching of various function
calls are a critical component. Down the road, it is likely that an
entire work flow from raw data to publication, decision support, report
writing, presentation building etc., could be built and be reproducible
anywhere, on demand. The reproducible::Cache
function is
built to work with any R function. However, it becomes very powerful in
a SpaDES
context because we can build large, powerful
applications that are transparent and tied to the raw data that may be
many conceptual steps upstream in the workflow. To do this, we
have built several customizations within the SpaDES
package. Important to this is dealing correctly with the
simList
, which is an object that has slot that is an
environment. But more important are the various tools that can be used
at higher levels, i.e., not just for “standard” functions.
SpaDES
Some of the details of the simList
-specific features of
this Cache
function include:
The function converts all elements that have an environment as
part of their attributes into a format that has no unique environment
attribute, using format
if a function, and
as.list
in the case of the simList
environment.
When used within SpaDES
modules, Cache
(capital C) does not require that the argument cacheRepo
be
specified. If called from inside a SpaDES module, Cache
will use the cacheRepo
argument from a call to
cachePath(sim)
, taking the sim
from the call
stack. Similarly, if no cacheRepo
argument is specified,
then it will use getOption("spades.cachePath")
, which will,
by default, be a temporary location with no persistence between R
sessions! To persist between sessions, use
SpaDES::setPaths()
every session.
In a SpaDES
context, there are several levels of caching
that can be used as part of a reproducible workflow. Each level can be
used to a modeller’s advantage; and, all can be – and are often – used
concurrently.
spades
levelAnd entire call to spades
can be cached. This will have
the effect of eliminating any stochasticity in the model as the output
will simply be the cached version of the simList
. This is
likely most useful in situations where reproducibility is more important
than “new” stochasticity (e.g., building decision support
systems, apps, final version of a manuscript).
library(raster)
library(reproducible)
library(SpaDES.core)
<- simInit(
mySim times = list(start = 0.0, end = 5.0),
params = list(
.globals = list(stackName = "landscape", burnStats = "testStats"),
randomLandscapes = list(.plotInitialTime = NA),
fireSpread = list(.plotInitialTime = NA)
),modules = list("randomLandscapes", "fireSpread"),
paths = list(modulePath = system.file("sampleModules", package = "SpaDES.core"))
)
This functionality can be achieved within a spades
call.
# compare caching ... run once to create cache
system.time({
<- spades(Copy(mySim), cache = TRUE, notOlderThan = Sys.time())
outSim })
## Aug18 12:39:00 Using setDTthreads(1). To change: 'options(spades.DTthreads = X)'.
## Aug18 12:39:00 chckpn total elpsd: 0.00088 secs | 0 checkpoint init 0
## Aug18 12:39:00 save total elpsd: 0.002 secs | 0 save init 0
## Aug18 12:39:00 prgrss total elpsd: 0.0032 secs | 0 progress init 0
## Aug18 12:39:00 load total elpsd: 0.0043 secs | 0 load init 0
## Aug18 12:39:00 rndmLn total elpsd: 0.0053 secs | 0 randomLandscapes ini
## Aug18 12:39:00 frSprd total elpsd: 0.05 secs | 0 fireSpread init 1
## Aug18 12:39:00 frSprd total elpsd: 0.057 secs | 1 fireSpread burn 5
## Aug18 12:39:00 frSprd total elpsd: 0.066 secs | 1 fireSpread stats 5
## Aug18 12:39:00 frSprd total elpsd: 0.069 secs | 2 fireSpread burn 5
## Aug18 12:39:00 frSprd total elpsd: 0.078 secs | 2 fireSpread stats 5
## Aug18 12:39:00 frSprd total elpsd: 0.081 secs | 3 fireSpread burn 5
## Aug18 12:39:00 frSprd total elpsd: 0.092 secs | 3 fireSpread stats 5
## Aug18 12:39:00 frSprd total elpsd: 0.094 secs | 4 fireSpread burn 5
## Aug18 12:39:01 frSprd total elpsd: 0.11 secs | 4 fireSpread stats 5
## Aug18 12:39:01 frSprd total elpsd: 0.11 secs | 5 fireSpread burn 5
## Aug18 12:39:01 frSprd total elpsd: 0.12 secs | 5 fireSpread stats 5
## simList saved in
## SpaDES.core:::.pkgEnv$.sim
## It will be deleted at next spades() call.
## user system elapsed
## 0.303 0.008 0.316
Note that if there were any visualizations (here we turned them off
with .plotInitialTime = NA
above) they will happen the
first time through, but not the cached times.
# vastly faster 2nd time
system.time({
<- spades(Copy(mySim), cache = TRUE)
outSimCached })
## ...(Object to retrieve (f0b0f74107588044.rds))
## loaded cached result from previous spades call
## user system elapsed
## 0.263 0.008 0.274
all.equal(outSim, outSimCached)
## [1] TRUE
If the parameter .useCache
in the module’s metadata is
set to TRUE
, then every event in the module will
be cached. That means that every time that module is called from within
a spades()
call, Cache
will be called. Only
the objects inside the simList
that correspond to the
inputObjects
or the outputObjects
from the
module metadata will be assessed for caching. For general use,
module-level caching would be mostly useful for modules that have no
stochasticity, such as data-preparation modules, GIS modules etc.
In this example, we will use the cache on the
randomLandscapes
module. This means that each subsequent
call to spades will result in identical outputs from the
randomLandscapes
module (only!). This would be useful when
only one random landscape is needed simply for trying something out, or
putting into production code (e.g., publication, decision
support, etc.).
# Module-level
params(mySim)$randomLandscapes$.useCache <- TRUE
system.time({
<- spades(Copy(mySim), .plotInitialTime = NA,
randomSim notOlderThan = Sys.time(), debug = TRUE)
})
## Aug18 12:39:01 Using setDTthreads(1). To change: 'options(spades.DTthreads = X)'.
## Aug18 12:39:01 chckpn eventTime moduleName eventType eventPriority
## Aug18 12:39:01 chckpn 0 checkpoint init 0
## Aug18 12:39:01 save 0 save init 0
## Aug18 12:39:01 prgrss 0 progress init 0
## Aug18 12:39:01 load 0 load init 0
## Aug18 12:39:01 rndmLn 0 randomLandscapes init 1
## Aug18 12:39:02 frSprd 0 fireSpread init 1
## Aug18 12:39:02 frSprd 1 fireSpread burn 5
## Aug18 12:39:02 frSprd 1 fireSpread stats 5
## Aug18 12:39:02 frSprd 2 fireSpread burn 5
## Aug18 12:39:02 frSprd 2 fireSpread stats 5
## Aug18 12:39:02 frSprd 3 fireSpread burn 5
## Aug18 12:39:02 frSprd 3 fireSpread stats 5
## Aug18 12:39:02 frSprd 4 fireSpread burn 5
## Aug18 12:39:02 frSprd 4 fireSpread stats 5
## Aug18 12:39:02 frSprd 5 fireSpread burn 5
## Aug18 12:39:02 frSprd 5 fireSpread stats 5
## simList saved in
## SpaDES.core:::.pkgEnv$.sim
## It will be deleted at next spades() call.
## user system elapsed
## 0.406 0.003 0.413
# vastly faster the second time
system.time({
<- spades(Copy(mySim), .plotInitialTime = NA, debug = TRUE)
randomSimCached })
## Aug18 12:39:02 Using setDTthreads(1). To change: 'options(spades.DTthreads = X)'.
## Aug18 12:39:02 chckpn eventTime moduleName eventType eventPriority
## Aug18 12:39:02 chckpn 0 checkpoint init 0
## Aug18 12:39:02 save 0 save init 0
## Aug18 12:39:02 prgrss 0 progress init 0
## Aug18 12:39:02 load 0 load init 0
## Aug18 12:39:02 rndmLn 0 randomLandscapes init 1
## Aug18 12:39:02 rndmLn ...(Object to retrieve (59205317bb6f188f.rds))
## Aug18 12:39:02 rndmLn loaded cached copy of randomLandscapes module adding to memoised copy
## Aug18 12:39:02 frSprd 0 fireSpread init 1
## Aug18 12:39:02 frSprd 1 fireSpread burn 5
## Aug18 12:39:02 frSprd 1 fireSpread stats 5
## Aug18 12:39:02 frSprd 2 fireSpread burn 5
## Aug18 12:39:02 frSprd 2 fireSpread stats 5
## Aug18 12:39:02 frSprd 3 fireSpread burn 5
## Aug18 12:39:02 frSprd 3 fireSpread stats 5
## Aug18 12:39:02 frSprd 4 fireSpread burn 5
## Aug18 12:39:02 frSprd 4 fireSpread stats 5
## Aug18 12:39:02 frSprd 5 fireSpread burn 5
## Aug18 12:39:02 frSprd 5 fireSpread stats 5
## simList saved in
## SpaDES.core:::.pkgEnv$.sim
## It will be deleted at next spades() call.
## user system elapsed
## 0.355 0.000 0.358
Test that only layers produced in randomLandscapes
are
identical, not fireSpread
.
<- list("DEM", "forestAge", "habitatQuality", "percentPine", "Fires")
layers <- lapply(layers, function(l)
same identical(randomSim$landscape[[l]], randomSimCached$landscape[[l]]))
names(same) <- layers
print(same) # Fires is not same because all non-init events in fireSpread are not cached
## $DEM
## [1] TRUE
##
## $forestAge
## [1] TRUE
##
## $habitatQuality
## [1] TRUE
##
## $percentPine
## [1] TRUE
##
## $Fires
## [1] FALSE
If the parameter .useCache
in the module’s metadata is
set to a character or character vector, then that or those
event(s), identified by their name, will be cached. That means that
every time the event is called from within a spades
call,
Cache
will be called. Only the objects inside the
simList
that correspond to the inputObjects
or
the outputObjects
as defined in the module metadata will be
assessed for caching inputs or outputs, respectively. The fact that all
and only the named inputObjects
and
outputObjects
are cached and returned may be inefficient
(i.e., it may cache more objects than are necessary) for
individual events.
Similar to module-level caching, event-level caching would be mostly
useful for events that have no stochasticity, such as data-preparation
events, GIS events etc. Here, we don’t change the module-level caching
for randomLandscapes
, but we add to it a cache for only the
“init” event for fireSpread
.
params(mySim)$fireSpread$.useCache <- "init"
system.time({
<- spades(Copy(mySim), .plotInitialTime = NA,
randomSim notOlderThan = Sys.time(), debug = TRUE)
})
## Aug18 12:39:03 Using setDTthreads(1). To change: 'options(spades.DTthreads = X)'.
## Aug18 12:39:03 chckpn eventTime moduleName eventType eventPriority
## Aug18 12:39:03 chckpn 0 checkpoint init 0
## Aug18 12:39:03 save 0 save init 0
## Aug18 12:39:03 prgrss 0 progress init 0
## Aug18 12:39:03 load 0 load init 0
## Aug18 12:39:03 rndmLn 0 randomLandscapes init 1
## Aug18 12:39:03 frSprd 0 fireSpread init 1
## Aug18 12:39:03 frSprd 1 fireSpread burn 5
## Aug18 12:39:03 frSprd 1 fireSpread stats 5
## Aug18 12:39:03 frSprd 2 fireSpread burn 5
## Aug18 12:39:03 frSprd 2 fireSpread stats 5
## Aug18 12:39:03 frSprd 3 fireSpread burn 5
## Aug18 12:39:03 frSprd 3 fireSpread stats 5
## Aug18 12:39:03 frSprd 4 fireSpread burn 5
## Aug18 12:39:03 frSprd 4 fireSpread stats 5
## Aug18 12:39:03 frSprd 5 fireSpread burn 5
## Aug18 12:39:03 frSprd 5 fireSpread stats 5
## simList saved in
## SpaDES.core:::.pkgEnv$.sim
## It will be deleted at next spades() call.
## user system elapsed
## 0.291 0.000 0.297
# vastly faster the second time
system.time({
<- spades(Copy(mySim), .plotInitialTime = NA, debug = TRUE)
randomSimCached })
## Aug18 12:39:03 Using setDTthreads(1). To change: 'options(spades.DTthreads = X)'.
## Aug18 12:39:03 chckpn eventTime moduleName eventType eventPriority
## Aug18 12:39:03 chckpn 0 checkpoint init 0
## Aug18 12:39:03 save 0 save init 0
## Aug18 12:39:03 prgrss 0 progress init 0
## Aug18 12:39:03 load 0 load init 0
## Aug18 12:39:03 rndmLn 0 randomLandscapes init 1
## Aug18 12:39:03 rndmLn ...(Object to retrieve (59205317bb6f188f.rds))
## Aug18 12:39:03 rndmLn loaded cached copy of randomLandscapes module adding to memoised copy
## Aug18 12:39:03 frSprd 0 fireSpread init 1
## Aug18 12:39:03 frSprd ...(Object to retrieve (fc3e78ce2e055ab2.rds))
## Aug18 12:39:03 frSprd loaded cached copy of init event in fireSpread module.
## Aug18 12:39:03 frSprd 1 fireSpread burn 5
## Aug18 12:39:03 frSprd 1 fireSpread stats 5
## Aug18 12:39:03 frSprd 2 fireSpread burn 5
## Aug18 12:39:03 frSprd 2 fireSpread stats 5
## Aug18 12:39:03 frSprd 3 fireSpread burn 5
## Aug18 12:39:03 frSprd 3 fireSpread stats 5
## Aug18 12:39:03 frSprd 4 fireSpread burn 5
## Aug18 12:39:03 frSprd 4 fireSpread stats 5
## Aug18 12:39:03 frSprd 5 fireSpread burn 5
## Aug18 12:39:03 frSprd 5 fireSpread stats 5
## simList saved in
## SpaDES.core:::.pkgEnv$.sim
## It will be deleted at next spades() call.
## user system elapsed
## 0.134 0.004 0.144
Any function can be cached using:
Cache(FUN = functionName, ...)
.
This will be a slight change to a function call, such as:
projectRaster(raster, crs = crs(newRaster))
to
Cache(projectRaster, raster, crs = crs(newRaster))
.
<- raster(extent(0, 1e3, 0, 1e3), res = 1)
ras system.time({
<- Cache(NLMR::nlm_mpd,
map ncol = ncol(ras),
nrow = nrow(ras),
resolution = unique(res(ras)),
roughness = 0.5,
rand_dev = 10,
rescale = FALSE,
verbose = FALSE,
cacheRepo = cachePath(mySim),
userTags = "nlm_mpd",
notOlderThan = Sys.time())
})
## user system elapsed
## 0.618 0.015 0.636
# vastly faster the second time
system.time({
<- Cache(NLMR::nlm_mpd,
mapCached ncol = ncol(ras),
nrow = nrow(ras),
resolution = unique(res(ras)),
roughness = 0.5,
rand_dev = 10,
rescale = FALSE,
verbose = FALSE,
cacheRepo = cachePath(mySim),
userTags = "nlm_mpd")
})
## user system elapsed
## 0.049 0.000 0.053
all.equal(map, mapCached)
## [1] TRUE
Since the cache is simply a DBI
database table, all
DBI
functions will work as is. In addition, there are
several helpers in the reproducible
package, including
showCache
, keepCache
and
clearCache
, and the more advanced createCache
,
loadFromCache
, rmFromCache
, and
saveToCache
that may be useful. Also, one can access cached
items manually (rather than simply rerunning the same Cache
function again).
<- showCache(mySim) cacheDB
## Cache size:
## Total (including Rasters): 2.3 Mb
## Selected objects (not including Rasters): 2.3 Mb
## get the RasterLayer that was produced with the NLMR::nlm_mpd function:
<- loadFromCache(cachePath(mySim), cacheId = cacheDB[tagValue == "nlm_mpd"]$cacheId)
map
clearPlot()
Plot(map)
In general, we feel that a liberal use of Cache
will
make a reusable and reproducible work flow. shiny
apps can
be made, taking advantage of Cache
. Indeed, much of the
difficulty in managing data sets and saving them for future use, can be
accommodated by caching.
simInit() --> many .inputObjects calls
spades() call --> many module calls --> many event calls --> many function calls
Lets say we start to introduce caching to this structure. We start
from the “inner” most functions that we could imaging Caching would be
useful. Lets say there are some GIS operations, like
raster::projectRaster
, which operates on an input
shapefile. We can Cache the projectRaster
call to make this
much faster, since it will always be the same result for a given input
raster.
If we look back at our structure above, we see that we still have
LOTS of places that are not Cached. That means that the
spades()
call will still spawn many module calls, and many
event calls, just to get to the one Cache(projectRaster)
call which is cached. This function will likely be called many times.
This is good, but Cache
does take some
time. So, even if Cache(projectRaster)
takes only
0.02 seconds, calling it hundreds of times means maybe 4 seconds. If we
are doing this for many functions, then this will be too slow for some
purposes.
We can start putting Cache
all up the sequence of calls.
Unfortunately, the way we use Cache at each of these levels is a bit
different, so we need a slightly different approach for each.
spades
callspades(cache = TRUE)
This will cache the spades
call, causing
stochasticity/randomness to be frozen.
Pass .useCache = TRUE
as a parameter to the module,
during the simInit
Some modules are inherently non-random, such as GIS modules, or parameter fitting statistical modules. We expect these to be identical results each time, so we can safely cache the entire module.
= list(
parameters FireModule = list(.useCache = TRUE)
)<- simInit(..., params = parameters)
mySim <- spades(mySim) mySimOut
The messaging should indicate the caching is happening on every event in that module.
Note: This option REQUIRES that the metadata in inputs
and outputs be exactly correct, i.e., all inputObjects
and
outputObjects
must be correctly identified and listed in
the defineModule
metadata
If the module is cached, and there are errors when it is
run, it almost is guaranteed to be a problem with the
inputObjects
and outputObjects
incorrectly
specified.
Cache(<functionName>, <other arguments>)
This will allow fine scale control of individual function calls.
Once nested Caching is used all the way up to the
experiment
(see SpaDES.experiment
package)
level and even further up (e.g., if there is a shiny
module), then even very complex models can be put into a complete
workflow.
The current vision for SpaDES
is that it will allow this
type of “data to decisions” complete workflow that allows for deep,
robust models, across disciplines, with easily accessible front ends,
that are quick and responsive to users, yet can handle data changes,
module changes, etc.