From 8c772fd5b1083602231b4d18e4b8b8a7c7a47aca Mon Sep 17 00:00:00 2001 From: erex Date: Fri, 8 Nov 2024 16:47:44 +0000 Subject: [PATCH] typo in alt-optimiser vignette --- vignettes/web-only/alt-optimise/mcds-dot-exe.Rmd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/vignettes/web-only/alt-optimise/mcds-dot-exe.Rmd b/vignettes/web-only/alt-optimise/mcds-dot-exe.Rmd index 184e9b7..a3379ce 100644 --- a/vignettes/web-only/alt-optimise/mcds-dot-exe.Rmd +++ b/vignettes/web-only/alt-optimise/mcds-dot-exe.Rmd @@ -230,7 +230,7 @@ MCDS.opt.time <- Sys.time() - start.time summary(uni3.mcds) ``` -This took a little less time: `r format(MCDS.opt.time, digits = 1)`. Hence, for some datasets, it may be quicker to use the `MCDS.exe` optimizer. This could make a significant difference if using the nonparametric bootstrap to estimate variance. However, after making improvemts to the optimizer in `mrds` 3.0.0 and `Distance` 2.0.0 the difference is generally small, and in many cases the `R` optimizer is faster than `MCDS.exe` so this is likely not a productive avenue to pursue in general. +This took a little less time: `r format(MCDS.opt.time, digits = 1)`. Hence, for some datasets, it may be quicker to use the `MCDS.exe` optimizer. This could make a significant difference if using the nonparametric bootstrap to estimate variance. However, after making improvements to the optimizer in `mrds` 3.0.0 and `Distance` 2.0.0 the difference is generally small, and in many cases the `R` optimizer is faster than `MCDS.exe` so this is likely not a productive avenue to pursue in general. # Discussion