esqlabsR 5.0.0
New functionalities
-
New function
loadObservedDataFromPKML()
to load data from*.pkml
located in
the "PKML" sub-folder of the "Data" folder. -
New function
createScenarios()
to createScenario
objects fromScenarioConfiguration
objects -
Plots can be created by calling the new function
createPlotsFromExcel()
. It requires as input parameterssimulatedScenarios
(a list of simulated scenarios as returned byrunScenarios()
),observedData
(a list ofDataSet
objects) and aProjectConfiguration
objectprojectConfiguration
. -
New function
createDataCombinedFromExcel()
createsDataCombined
objects as
defined in thePlots.xlsx
file. -
New function
saveScenarioResults()
to save results produced by therunScenarios()
function to csv files and corresponding simulations to pkml files. -
New function
loadScenarioResults()
to load results from csv files into a structure
as produced by therunScenarios()
function. -
New function
compareSimulation()
to compare two simulations for differences. -
runScenarios()
also returns aPopulation
object for population simulations. -
runScenarios()
gets a new argumentsavePopulationToCSV
, with default valueFALSE
.
BREAKING CHANGES
- Field
setTestParameters
removed fromScenarioConfiguration
- Function
initializeScenario()
has been removed - Definition of simulation time in the
Scenarios.xlsx
file changed. The new expected format
is a triplet of values <StartTime, EndTime, Resolution>, whereResolution
is the number of
simulated points per time unit defined in the columnTimeUnit
. - Field
poinstPerMinute
ofScenarioConfiguration
has been removed. - Function
compareSimulationParameters()
has been removed and replaced bycompareSimulations()
Scenarios
excel file gets additional columnsSteadyStateTime
,SteadyStateTimeUnit
,
PopulationId
,OutputPathsIds
.readScenarioConfigurationFromExcel()
has a new signature and requires a list of
scenarioNames
and aProjectConfiguration
. The output is a named list ofScenarioConfiguration
objects.- Output paths are not set from global variable
OutputPaths
any more but
from the respective field ofScenarioConfgiruation
ProjectConfiguration
does not have field$outputDevice
any more.ScenarioConfiguration
does not storeSimulationRunOptions
any more. Simulation run options must be passed to therunScenarios()
function. Different run options cannot be used within one scenarios run.- Enum
GraphicsDevices
has been removed. - Function
initializeSimulation()
does not have argumentssimulateSteadyState
,steadyStateTime
andsimulationRunOptions
any more.
MAJOR CHANGES
-
New class
Scenario
that represents a scenario created from aScenarioConfiguration
-
ScenarioConfiguration
gets a new fieldoutputPaths
which is a list of
output paths for which the results will be calculated. IfNULL
(default),
outputs as defined in the simulation are used. -
Paths of model outputs are defined in the excel file
Scenarios.xlsx
. In the
sheetOutputPaths
, create an entry for each output. The columnOutputPath
is the full
path to the output, whileOutputPathId
is an identifier that conveniently allows
to select the correct output.
In theScenarios
sheet, enter the IDs of all paths the outputs should be generated for,
separated by a,
, e.g.Aciclovir_PVB, Aciclovir_fat_cell
.
If no outputs are specified, the outputs as defined in the simulation .pkml
file
will be produced.
-
ScenarioConfiguration
gets a new fieldpopulationId
, specifying the id of
the population as defined in thePopulationParameters.xlsx
file, sheetDemographics
.
If the field isNULL
, the scenario is simulated as an individual simulation,
otherwise a population simulation is performed. -
ScenarioConfiguration
gets a new fieldreadPopulationFromCSV
. IfFALSE
(default),
a new population is created from defined population demographics. IfTRUE
, a simulation
will be imported from a csv sheet located in the folderParameters/Populations
and
named as thePopulationId
. -
runScenarios()
supports scenario configurations for population simulations -
Target folder for saving
*.pkml
simulations whenrunScenarios(scenarioConfigurations, saveSimulationsToPKML = TRUE)
changed fromModels/Simulations/<DateSuffix>
toResults/SimulationResults/<DateSuffix>
. -
sensitivityCalculation()
- fixed bug in wrong calculation of sensitivity values.
Please be aware that the results produced by earlier versions are wrong.
- The workflow for running scenarios changed to:
-
Create a
ProjectConfiguration
withcreateDefaultProjectConfiguration()
-
Create
ScenarioConfigurations
, e.g. withreadScenarioConfigurationFromExcel(scenarioNames, projectConfiguration)
-
Run scenarios with
runScenarios(scenarioConfigurations)
-
Alternatively:
-
Create a
ProjectConfiguration
withcreateDefaultProjectConfiguration()
-
Create
ScenarioConfigurations
, e.g. withreadScenarioConfigurationFromExcel(scenarioNames, projectConfiguration)
-
-
ProjectConfiguration
gets a new fieldplotsFile
. It is the name of the excel file with plot definitions and must be located in theparamsFolder
. -
When defining an individual of other species than human in
ScenarioConfiguration
and applying it to a human model, missing species-specific parameters are applied and the
scaling works properly. Supported scalingsa are: Human to rat, human to monkey,
human to rabbit. -
initializeSimulation()
does not perform steady-state run any more. This is done as part of therunScenarios()
function.
MINOR CHANGES
-
Function
stringToNum()
gets additional argumentslloqMode
anduloqMode
that determine how entries of type "<number" and ">number" will be treated. -
readScenarioConfigurationFromExcel()
will read all scenarios defined in the
Scenarios.xlsx
file if no scenario names are specified (argumentscenarioNames = NULL
). -
Function
setApplications()
is deprecated. -
Dark grey frame around legends by default.