From 0220b25f01a4451fa44a7b2f30f5849c4d822a9c Mon Sep 17 00:00:00 2001 From: Johannes Ranke Date: Fri, 1 Nov 2019 15:39:12 +0100 Subject: Another documentation fix --- R/confint.mkinfit.R | 5 ++--- docs/reference/confint.mkinfit.html | 9 ++++----- man/confint.mkinfit.Rd | 5 ++--- 3 files changed, 8 insertions(+), 11 deletions(-) diff --git a/R/confint.mkinfit.R b/R/confint.mkinfit.R index 07614306..84183808 100644 --- a/R/confint.mkinfit.R +++ b/R/confint.mkinfit.R @@ -27,9 +27,8 @@ #' @param backtransform If we approximate the likelihood in terms of the #' transformed parameters, should we backtransform the parameters with #' their confidence intervals? -#' @param cores The number of cores to be used for multicore processing. This -#' is only used when the \code{cluster} argument is \code{NULL}. On Windows -#' machines, cores > 1 is not supported. +#' @param cores The number of cores to be used for multicore processing. +#' On Windows machines, cores > 1 is currently not supported. #' @param quiet Should we suppress the message "Profiling the likelihood" #' @return A matrix with columns giving lower and upper confidence limits for #' each parameter. diff --git a/docs/reference/confint.mkinfit.html b/docs/reference/confint.mkinfit.html index 6015fbf6..13662adf 100644 --- a/docs/reference/confint.mkinfit.html +++ b/docs/reference/confint.mkinfit.html @@ -203,9 +203,8 @@ their confidence intervals?

cores -

The number of cores to be used for multicore processing. This -is only used when the cluster argument is NULL. On Windows -machines, cores > 1 is not supported.

+

The number of cores to be used for multicore processing. +On Windows machines, cores > 1 is currently not supported.

quiet @@ -255,13 +254,13 @@ machines, cores > 1 is not supported.

use_of_ff = "max", quiet = TRUE) f_d_1 <- mkinfit(SFO_SFO, subset(FOCUS_2006_D, value != 0), quiet = TRUE) system.time(ci_profile <- confint(f_d_1, method = "profile", cores = 1, quiet = TRUE))
#> User System verstrichen -#> 51.297 0.000 51.328
# Using more cores does not save much time here, as parent_0 takes up most of the time +#> 51.341 0.000 51.370
# Using more cores does not save much time here, as parent_0 takes up most of the time # If we additionally exclude parent_0 (the confidence of which is often of # minor interest), we get a nice performance improvement from about 50 # seconds to about 12 seconds if we use at least four cores system.time(ci_profile_no_parent_0 <- confint(f_d_1, method = "profile", c("k_parent_sink", "k_parent_m1", "k_m1_sink", "sigma"), cores = n_cores))
#> Profiling the likelihood
#> User System verstrichen -#> 0.006 0.003 11.435
ci_profile
#> 2.5% 97.5% +#> 0.001 0.007 11.432
ci_profile
#> 2.5% 97.5% #> parent_0 96.456003650 1.027703e+02 #> k_parent_sink 0.040762501 5.549764e-02 #> k_parent_m1 0.046786482 5.500879e-02 diff --git a/man/confint.mkinfit.Rd b/man/confint.mkinfit.Rd index e4a60556..60e82517 100644 --- a/man/confint.mkinfit.Rd +++ b/man/confint.mkinfit.Rd @@ -36,9 +36,8 @@ applied to the likelihood based on the transformed parameters?} transformed parameters, should we backtransform the parameters with their confidence intervals?} -\item{cores}{The number of cores to be used for multicore processing. This -is only used when the \code{cluster} argument is \code{NULL}. On Windows -machines, cores > 1 is not supported.} +\item{cores}{The number of cores to be used for multicore processing. +On Windows machines, cores > 1 is currently not supported.} \item{quiet}{Should we suppress the message "Profiling the likelihood"} -- cgit v1.2.1