documenting missing function

This commit is contained in:
Hollos Roland 2019-12-10 22:10:15 +01:00
parent 2f65f656a6
commit a34f7a3afb
13 changed files with 110 additions and 34 deletions

View File

@ -28,7 +28,7 @@ Imports:
LinkingTo: Rcpp LinkingTo: Rcpp
SystemRequirements: C++11 SystemRequirements: C++11
Maintainer: Roland Hollo's <hollorol@gmail.com> Maintainer: Roland Hollo's <hollorol@gmail.com>
RoxygenNote: 6.1.1 RoxygenNote: 7.0.0
Suggests: knitr, Suggests: knitr,
rmarkdown, rmarkdown,
VignetteBuilder: knitr VignetteBuilder: knitr

View File

@ -22,6 +22,7 @@ export(paramSweep)
export(plotMuso) export(plotMuso)
export(plotMusoWithData) export(plotMusoWithData)
export(randEpc) export(randEpc)
export(readObservedData)
export(runMuso) export(runMuso)
export(rungetMuso) export(rungetMuso)
export(saveAllMusoPlots) export(saveAllMusoPlots)
@ -32,6 +33,8 @@ export(updateMusoMapping)
import(ggplot2) import(ggplot2)
import(utils) import(utils)
importFrom(Rcpp,evalCpp) importFrom(Rcpp,evalCpp)
importFrom(data.table,data.table)
importFrom(data.table,fread)
importFrom(digest,digest) importFrom(digest,digest)
importFrom(dplyr,'%>%') importFrom(dplyr,'%>%')
importFrom(dplyr,filter) importFrom(dplyr,filter)

View File

@ -4,8 +4,14 @@
\alias{changemulline} \alias{changemulline}
\title{This is the function which is capable to change multiple specific lines to others using their row numbers.} \title{This is the function which is capable to change multiple specific lines to others using their row numbers.}
\usage{ \usage{
changemulline(filePaths, calibrationPar, contents, fileOut, fileToChange, changemulline(
modifyOriginal = FALSE) filePaths,
calibrationPar,
contents,
fileOut,
fileToChange,
modifyOriginal = FALSE
)
} }
\description{ \description{
The function uses the previous changspecline function to operate. The function uses the previous changspecline function to operate.

View File

@ -4,9 +4,15 @@
\alias{compareMuso} \alias{compareMuso}
\title{compareMuso} \title{compareMuso}
\usage{ \usage{
compareMuso(settings = NULL, parameters, variable = 1, compareMuso(
calibrationPar = NULL, fileToChange = "epc", skipSpinup = TRUE, settings = NULL,
timeFrame = "day") parameters,
variable = 1,
calibrationPar = NULL,
fileToChange = "epc",
skipSpinup = TRUE,
timeFrame = "day"
)
} }
\arguments{ \arguments{
\item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.} \item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.}

View File

@ -4,8 +4,14 @@
\alias{musoDate} \alias{musoDate}
\title{It generates BiomeBGC-MuSo dates} \title{It generates BiomeBGC-MuSo dates}
\usage{ \usage{
musoDate(startYear, numYears, timestep = "d", combined = TRUE, musoDate(
corrigated = TRUE, format = "en") startYear,
numYears,
timestep = "d",
combined = TRUE,
corrigated = TRUE,
format = "en"
)
} }
\arguments{ \arguments{
\item{timestep}{timestep, which can be daily ("d"), monthly ("m"), yearly("y")} \item{timestep}{timestep, which can be daily ("d"), monthly ("m"), yearly("y")}

View File

@ -4,11 +4,24 @@
\alias{musoMonte} \alias{musoMonte}
\title{musoMonte} \title{musoMonte}
\usage{ \usage{
musoMonte(settings = NULL, parameters = NULL, inputDir = "./", musoMonte(
outLoc = "./calib", iterations = 10, preTag = "mont-", settings = NULL,
outputType = "moreCsv", fun = mean, varIndex = 1, outVars = NULL, parameters = NULL,
silent = TRUE, skipSpinup = TRUE, debugging = FALSE, inputDir = "./",
keepEpc = FALSE, constrains = NULL, ...) outLoc = "./calib",
iterations = 10,
preTag = "mont-",
outputType = "moreCsv",
fun = mean,
varIndex = 1,
outVars = NULL,
silent = TRUE,
skipSpinup = TRUE,
debugging = FALSE,
keepEpc = FALSE,
constrains = NULL,
...
)
} }
\arguments{ \arguments{
\item{settings}{A list of environmental variables for the Monte Carlo experiment. These settings are generated by the setupMuso function. By default the settings parameter is generated automatically.} \item{settings}{A list of environmental variables for the Monte Carlo experiment. These settings are generated by the setupMuso function. By default the settings parameter is generated automatically.}

View File

@ -4,9 +4,16 @@
\alias{musoQuickEffect} \alias{musoQuickEffect}
\title{musoQuickEffect} \title{musoQuickEffect}
\usage{ \usage{
musoQuickEffect(settings = NULL, calibrationPar = NULL, startVal, musoQuickEffect(
endVal, nSteps = 1, fileToChange = "epc", outVar, settings = NULL,
parName = "parVal") calibrationPar = NULL,
startVal,
endVal,
nSteps = 1,
fileToChange = "epc",
outVar,
parName = "parVal"
)
} }
\arguments{ \arguments{
\item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.} \item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.}

View File

@ -4,7 +4,7 @@
\alias{musoRand} \alias{musoRand}
\title{musoRand} \title{musoRand}
\usage{ \usage{
musoRand(parameters, constrains = NULL, iterations = 3000) musoRand(parameters, iterations = 3000, fileType = "epc", constrains = NULL)
} }
\arguments{ \arguments{
\item{parameters}{This is a dataframe (heterogeneous data-matrix), where the first column is the name of the parameter, the second is a numeric vector of the rownumbers of the given variable in the input EPC file, and the last two columns describe the minimum and the maximum of the parameter (i.e. the parameter ranges), defining the interval for the randomization.} \item{parameters}{This is a dataframe (heterogeneous data-matrix), where the first column is the name of the parameter, the second is a numeric vector of the rownumbers of the given variable in the input EPC file, and the last two columns describe the minimum and the maximum of the parameter (i.e. the parameter ranges), defining the interval for the randomization.}

View File

@ -4,12 +4,24 @@
\alias{musoSensi} \alias{musoSensi}
\title{musoSensi} \title{musoSensi}
\usage{ \usage{
musoSensi(monteCarloFile = NULL, parameters = NULL, settings = NULL, musoSensi(
inputDir = "./", outLoc = "./calib", outVars = NULL, monteCarloFile = NULL,
iterations = 30, preTag = "mont-", outputType = "moreCsv", parameters = NULL,
fun = mean, varIndex = 1, outputFile = "sensitivity.csv", settings = NULL,
plotName = "sensitivity.png", plotTitle = "Sensitivity", inputDir = "./",
skipSpinup = TRUE, dpi = 300) outLoc = "./calib",
outVars = NULL,
iterations = 30,
preTag = "mont-",
outputType = "moreCsv",
fun = mean,
varIndex = 1,
outputFile = "sensitivity.csv",
plotName = "sensitivity.png",
plotTitle = "Sensitivity",
skipSpinup = TRUE,
dpi = 300
)
} }
\arguments{ \arguments{
\item{parameters}{This is a dataframe (heterogen data-matrix), which first column is the name of the parameters, the second is a numeric vector of the rownumbers of the given variable in the epc-fie, the last two column consist the endpont of the parameter-ranges, where the parameters will be randomized.} \item{parameters}{This is a dataframe (heterogen data-matrix), which first column is the name of the parameters, the second is a numeric vector of the rownumbers of the given variable in the epc-fie, the last two column consist the endpont of the parameter-ranges, where the parameters will be randomized.}

View File

@ -4,9 +4,14 @@
\alias{paramSweep} \alias{paramSweep}
\title{paramSweep} \title{paramSweep}
\usage{ \usage{
paramSweep(inputDir = "./", parameters = NULL, outputDir = NULL, paramSweep(
iterations = 10, outVar = "daily_gpp", inputDir = "./",
htmlOutName = "paramsweep.html") parameters = NULL,
outputDir = NULL,
iterations = 10,
outVar = "daily_gpp",
htmlOutName = "paramsweep.html"
)
} }
\arguments{ \arguments{
\item{inputDir}{The directory which contains the MuSo model's ini files} \item{inputDir}{The directory which contains the MuSo model's ini files}

View File

@ -4,8 +4,13 @@
\alias{randEpc} \alias{randEpc}
\title{randEpc} \title{randEpc}
\usage{ \usage{
randEpc(parameterFile = "parameters.csv", location = "./epcDir", randEpc(
sourceEpc = "maize.epc", iterations = 1000, constrains = NULL) parameterFile = "parameters.csv",
location = "./epcDir",
sourceEpc = "maize.epc",
iterations = 1000,
constrains = NULL
)
} }
\arguments{ \arguments{
\item{parameterFile}{parameters.csv file location} \item{parameterFile}{parameters.csv file location}

View File

@ -4,9 +4,15 @@
\alias{saveAllMusoPlots} \alias{saveAllMusoPlots}
\title{saveAllMusoPlots} \title{saveAllMusoPlots}
\usage{ \usage{
saveAllMusoPlots(settings = NULL, plotName = ".png", silent = TRUE, saveAllMusoPlots(
type = "line", outFile = "annual.csv", colour = NULL, settings = NULL,
skipSpinup = FALSE) plotName = ".png",
silent = TRUE,
type = "line",
outFile = "annual.csv",
colour = NULL,
skipSpinup = FALSE
)
} }
\arguments{ \arguments{
\item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.} \item{settings}{RBBGCMuso uses variables that define the entire simulation environment. Those environment variables include the name of the INI files, the name of the meteorology files, the path to the model executable and its file name, the entire output list, the entire output variable matrix, the dependency rules for the EPC parameters etc. Using the runMuso function RBBGCMuso can automatically create those environment variables by inspecting the files in the working directory (this happens through the setupMuso function). It means that by default model setup is performed automatically in the background and the user has nothing to do. With this settings parameter we can force runMuso to skip automatic environment setup as we provide the environment settings to runMuso. In a typical situation the user can skip this option.}

View File

@ -4,8 +4,15 @@
\alias{stampAndDir} \alias{stampAndDir}
\title{stampAndCopy} \title{stampAndCopy}
\usage{ \usage{
stampAndDir(outputLoc, names, stampDir, wrongDir, type = "output", stampAndDir(
errorsign, logfiles) outputLoc,
names,
stampDir,
wrongDir,
type = "output",
errorsign,
logfiles
)
} }
\arguments{ \arguments{
\item{outputLoc}{This is the location of the output files.} \item{outputLoc}{This is the location of the output files.}