Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
In particular, adapt the display of parameter boxplots
for saem fits using mkin transformations to the way
used for saem fits using saemix transformations, i.e.
always show parameters on the natural scale, and normalised them by
dividing by the median from the multiple runs.
|
|
- Split out llhist and parhist documentation
- Add example code for multistart
- Create a multistart vignette, because the example code fails when run
by pkgdown
- Fix multistart for the case of mkin transformations in the saem fit
|
|
|
|
|
|
|
|
|
|
|
|
- 'R/mhmkin.R': New method for performing multiple hierarchical mkin fits in one function call, optionally in parallel.
- 'R/saem.R': 'logLik' and 'update' methods for 'saem.mmkin' objects.
- 'R/illparms.R': Add methods for 'saem.mmkin' and 'mhmkin' objects.
tests: Use 2 cores on travis, should work according to docs
|
|
This cleans up the startup message. Loading parallel is not
that important, users wanting to use it will know what to do.
Also, add codemeta.json to .Rbuildignore
|
|
Also, add a method for gathering convergence information
and a method for gathering information on ill-defined parameters
|
|
This also adds the first benchmark results obtained on my laptop system
|
|
Documentation and test results were updated, the latter with regard
to the previous work on plot.mixed.mmkin.
|
|
- New argument 'default_log_parms' for mean_degparms()
- 'plot.mixed.mmkin': Pass the frame argument also to residual plots,
take the 'default_log_parms' argument for 'mean_degparms' used for
constructing approximate population curves, plot population curve last
to avoid that it is covered by data
|
|
|
|
|
|
|
|
I am postponing my attempts to get the nlmixr interface to CRAN, given
some problems with nlmixr using R-devel under Windows, see
https://github.com/nlmixrdevelopment/nlmixr/issues/596
and
https://github.com/r-hub/rhub/issues/512,
which is fixed by the removal of nlmixr from the testsuite.
For the tests to be more platform independent, the biphasic mixed
effects models test dataset was defined in a way that fitting
should be more robust (less ill-defined).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The EFSA URL failed on winbuilder because some cookie sets a different
domain, so I am now using \href{} with the full link as link text instead
of \url{}
|
|
|
|
After the merge, run make test and accept the new snapshot for the mixed
model fit for an nlme object
|
|
Also adapt summary.nlmixr.mmkin to correctly handle the way
formation fractions are translated to nlmixr
|
|
|
|
- All degradation models are specified as ODE models. This appears to be
fast enough
- Error models are being translated to nlmixr as close to the mkin error
model as possible. When using the 'saem' backend, it appears not to be
possible to use the same error model for more than one observed variable
- No support yet for models with parallel formation of metabolites, where
the ilr transformation is used in mkin per default
- There is a bug in nlmixr which appears to be triggered if the data are
not balanced, see nlmixrdevelopment/nlmixr#530
- There is a print and a plot method, the summary method is not finished
|
|
|
|
|
|
|
|
- fit_with_errors for saem()
- test_log_parms for mean_degparms() and saem()
|
|
|
|
Also bump version to 1.0.3.
|
|
Also after the upgrade from buster to bullseye of my local system, some
test results for saemix have changed.
|
|
The errors in the example code were in the \dontrun sections, so they
were not caught by CRAN checks. In addition, the static help files
generated with pkgdown were cached, so I noticed the errors only
after completely regenerating the documentation for version 1.0.0.
|
|
- Improve authorship and copyright information
- Prepare pkgdown config
- Remove dependence on saemix as we need the development version which
is not ready for CRAN
- Temporarily remove saemix interface to check code coverage of the rest
|
|
See NEWS.md. Closes #12
|
|
This makes fitting with saem within parallel::mclapply much faster
and, surprisingly, much less hungry for RAM.
|
|
|
|
Address release critical check and test issues
|
|
|
|
|
|
|