fix Note on CRAN about too many threads used by scoringutils

.Rbuildignore

@@ -17,3 +17,4 @@
 ^\.devcontainer$
 ^CODE_OF_CONDUCT\.md$
 ^inst/manuscript/output$
+^CRAN-SUBMISSION$

R/summarise_scores.R

@@ -279,6 +279,7 @@ check_summary_params <- function(scores,
 #' summary is present according to the value specified in `by`.
 #' @examples
 #' library(magrittr) # pipe operator
+#' data.table::setDTthreads(1) # only needed to avoid issues on CRAN
 #' score(example_quantile) %>%
 #'   add_coverage(by = c("model", "target_type")) %>%
 #'   summarise_scores(by = c("model", "target_type")) %>%

tests/testthat/setup.R

@@ -1,6 +1,7 @@
 # load common required test packages
 library(ggplot2, quietly = TRUE)
 suppressMessages(library(magrittr))
+data.table::setDTthreads(1) # only needed to avoid issues on CRAN
 
 # compute quantile scores
-scores <- suppressMessages(score(example_quantile))
+scores <- suppressMessages(score(example_quantile))

vignettes/scoringutils.Rmd

@@ -19,6 +19,7 @@ library(magrittr)
 library(data.table)
 library(ggplot2)
 library(knitr)
+data.table::setDTthreads(1) # only needed to avoid issues on CRAN
 ```
 
 The `scoringutils` package provides a collection of metrics and proper scoring rules that make it simple to score probabilistic forecasts against the true observed values. You can find more information in the paper [Evaluating Forecasts with scoringutils in R](https://arxiv.org/abs/2205.07090) as well as the [Metrics-Vignette](https://epiforecasts.io/scoringutils/articles/metric-details.html) and the [Scoring forecasts directly Vignette](https://epiforecasts.io/scoringutils/articles/scoring-forecasts-directly.html).