Age | Commit message (Collapse) | Author | Files | Lines |
|
The special case occurs if not observed data for time zero
are available. Fixes #16. Write NEWS and update docs.
A lot of html was regenerated, because I had checked out
the main branch in between, which made pkgdown believe that
I have changed the help files.
|
|
- Another test for analytical solution of SFO-SFO
This is a bit redundant, because we have tests using those solutions
in test_analytical.R, where mkinfit is used. But nevertheless, it is
good to know that using mkinpredict directly also passes the test.
- A more explicit testing of the warning message that is issued
if a use turns of transformation of formation fractions
|
|
|
|
|
|
|
|
|
|
Closes #13
|
|
|
|
is only one random effect in the model. Also add a test for this.
|
|
This even a bit faster.
|
|
|
|
|
|
The vignette illustrates pH dependent degradation (covariate modelling)
with some detail for the parent compound.
Also, a bug in the saem method of the illparms function was fixed, which
prevented to find ill-defined parameters in cases where e.g. slopes of
covariate models have a negative estimate.
|
|
|
|
It took too long, and this solution method is not recommended. We are
saving 140 seconds here on my system, so more time is saved on travis.
|
|
Also, using mkin analytical solutions for more than one observed
variable is not supported (but could be if out_values would be
reordered).
|
|
|
|
|
|
We still need to create a parallel processing cluster _after_ creating a
compiled model that is moved to a user defined location, at least I did
not find another way to make it work. This is not a problem with
parallel processing without a cluster, which is not available on
Windows.
|
|
|
|
Update platform dependent test plots
|
|
Thanks to Sebastian Meyer for spotting it.
|
|
|
|
llquant argument, improved legend text, tests
|
|
|
|
Also update tests to the changes in mhmkin (see NEWS)
|
|
|
|
Save winbuilder/CRAN check time...
|
|
|
|
To ensure that tests on different platforms work on the same data, the
mixed modelling test data previosly generated in
tests/testthat/setup_script.R were generated once using the script in
inst/dataset/generation/ds_mixed.R, and are now distributed with the
package.
|
|
This will hopefully make the test pass on all relevant platforms.
|
|
Due to an oversight, error.init was not really passed to saemix_model in
saem.mmkin. The new initial values were reverted to c(1, 1), in order to
avoid changing the test results. Initial values for error model
parameters are now shown in parplot.multistart.
|
|
The previous test lead to an error on the Fedora test systems (gcc and
clang) on CRAN:
...
Results have changed from known value recorded in 'print_dfop_saemix_1.txt'.
old[13:24] vs new[13:24]
""
"Fitted parameters:"
" estimate lower upper"
- "parent_0 100.09 98.94 101.25"
+ "parent_0 100.17 99.01 101.33"
- "log_k1 -2.68 -2.91 -2.45"
+ "log_k1 -2.66 -2.89 -2.43"
"log_k2 -4.12 -4.24 -4.00"
- "g_qlogis -0.41 -0.63 -0.20"
+ "g_qlogis -0.43 -0.65 -0.21"
- "a.1 0.91 0.67 1.15"
+ "a.1 0.91 0.67 1.16"
"b.1 0.05 0.04 0.06"
- "SD.log_k1 0.36 0.21 0.50"
+ "SD.log_k1 0.35 0.21 0.50"
and 2 more ...
|
|
|
|
|
|
|
|
with the custom lsoda call, avoiding repeated getNativeSymbolInfo calls.
It's just that we should not be calling foreign functions from different
packages, because the may change without notice. Using
getNativeSymbolInfo for "call_lsoda" avoids the CRAN note, and a similar
call could probably be used for "unlock_solver", avoiding the NOTE in
checks for cran, but we should not do this in a CRAN package.
|
|
For the case of mkin transformations. This gives faster convergence,
and appears to avoid problems with numeric ODE solutions
|
|
|
|
Based on parameters in the separate fits that fail the t-test.
|
|
|
|
|
|
For the case of single fits and no ill-defined parameters found
|
|
As the last update failed on travis. Now we should be more robust,
as rounding to one digit works better when parameters are
log-transformed (mkin transformations) in the output.
|
|
As mentioned in d44c17da6d62568b
|
|
That parhist name was not the brightest idea, as it does
not show histograms.
|
|
|
|
|
|
|
|
|