Takes the ubiquity system object and other optional inputs to verify the system is running at steady state. This also provides information that can be helpful in debugging systems not running at steady state.
Usage
system_check_steady_state(
cfg,
parameters = NULL,
zero_rates = TRUE,
zero_bolus = TRUE,
output_times = seq(0, 100, 1),
offset_tol = .Machine$double.eps * 100,
derivative_tol = .Machine$double.eps * 100,
derivative_time = 0
)Arguments
- cfg
ubiquity system object
- parameters
optional set of parameters (
NULL) to check at steady state (if set toNULLthen the parameters for the currently selected parameter set will be used)- zero_rates
Boolean value to control removing all rate inputs (
TRUE)- zero_bolus
Boolean value to control removing all bolus inputs (
TRUE)- output_times
sequence of output times to simulate for offset determination (
seq(0,100,1))- offset_tol
maximum percent offset to be considered zero (
.Machine$double.eps*100)- derivative_tol
maximum derivative value to be considered zero (
.Machine$double.eps*100)- derivative_time
time to evaluate derivatives to identify deviations (
0), set toNULLto skip derivative evaluation
Value
List with the following names
steady_stateBoolean indicating weather the system was at steady statestates_derivativeDerivatives that had values greater than thederivative_tolstates_simulationStates that had values greater than theoffset_tolsomSimulated outputderivativesDerivativesstates_derivative_NA_NaNStates that had derivatives that evaluated as either NA or NaNstates_simulation_NA_NaNStates with simulation values that had either NA or NaNderivative_tcData frame with the timecourse of states where the derivative was found to be greater than tolerance (states_derivative)
