aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Ranke <jranke@uni-bremen.de>2023-08-17 08:53:15 +0200
committerJohannes Ranke <jranke@uni-bremen.de>2023-08-17 08:53:15 +0200
commit448e47e756c0c67fc658f93575092973aa455fb1 (patch)
tree8a9c976fe406773ddefd26fb77f2fe60b0e7caca
parent263613da9ac7f169dbaea875c897ff698aa10720 (diff)
Point to the dmta pathway vignette in the dmta test
-rw-r--r--tests/testthat/test_dmta.R7
1 files changed, 5 insertions, 2 deletions
diff --git a/tests/testthat/test_dmta.R b/tests/testthat/test_dmta.R
index cd6de341..3941cae1 100644
--- a/tests/testthat/test_dmta.R
+++ b/tests/testthat/test_dmta.R
@@ -85,9 +85,12 @@ test_that("Different backends get consistent results for SFO-SFO3+, dimethenamid
"Iteration 5, LME step.*not converge")
ints_nlme_mets <- intervals(nlme_sfo_sfo3p_tc, which = "fixed")
- skip("Fitting this ODE model with saemix takes about 15 minutes on my system")
+ skip("Fitting this ODE model with saemix takes about 5 minutes on my new system")
+ # August 2023: Please refer to the mkin vignette for the currently
+ # recommended way to fit the DMTA pathway data with saemix
+
# As DFOP is overparameterised and leads to instabilities and errors, we
- # need to use SFO.
+ # need to use SFO with nlme
# saem_saemix_sfo_sfo3p_tc <- saem(dmta_sfo_sfo3p_tc)
# The fit above, using SFO for the parent leads to low values of DMTA_0
# (confidence interval from 84.4 to 92.8) which is not consistent with what

Contact - Imprint