Description Usage Arguments Details Value Examples
View source: R/data_handling.R
lookup_table
creates a table that summarises simulation parameters.
The final table will have a line for each scenario and one column for each
parameter requested with SVs
.
1 2 3 4 5 6 7 8 9 | lookup_table(
data,
project,
scenario,
pop = "Population 1",
SVs = c("SV1"),
save2disk = TRUE,
dir_out = "ProcessedData"
)
|
data |
The output from |
project |
Vortex project name (used to name the output) |
scenario |
Vortex scenario name (used to name the output) |
pop |
The name of the pop to be used as reference |
SVs |
The parameters to include in the table |
save2disk |
Whether to save the output to disk, default: TRUE |
dir_out |
The local path to store the output. Default: ProcessedData |
If the name of the populations were changed, the user has to indicate a
population to be used as reference, otherwise lookup_table
will look
for a population named 'Population 1' (i.e. Vortex default name for the first
population).
lookup_table
reports the values of SVs at year zero. This is done
because parameters may take value 'zero' if the relevant population
goes extinct.There are cases where Vortex may not evaluate some parameters at
year 0. This may happen, for example, when a population is empty at
initialization (i.e. the initial population size is zero), or when K is set
to zero at the beginning of the simulation. The user should check the values
reported and check the Vortex input files if these do not look correct.
SVs
can be any variable included in the data, including GS or PS set up
in Vortex.
A data.frame with scenario names and parameter values
1 2 3 4 5 6 |
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.