remove kriging example

[dankelley]

I see a failure in the CRAN checks (https://cran.r-project.org/web/checks/check_results_oce.html). It's because of a warning that is converted to an error. (see below).

My rhub checks did not reveal this problem. In case this will cause CRAN rejection, I'm going to remove this example so it won't appear in future versions.

> if (requireNamespace("automap", quietly=TRUE) && requireNamespace("sf", quietly=TRUE)) {
+ gsKriging <- sectionSmooth(gs, "kriging", xr=50, yr=200)
+ plot(gsKriging, which="temperature")
+ mtext("sectionSmooth(..., method=\"kriging\")", line=0.5)
+ }
OMP: Warning #96: Cannot form a team with 8 threads, using 2 instead.
OMP: Hint Consider unsetting KMP_DEVICE_THREAD_LIMIT (KMP_ALL_THREADS), KMP_TEAMS_THREAD_LIMIT, and OMP_THREAD_LIMIT (if any are set).

[dankelley]

Fixed in "develop" branch, commit 46774d3

[dankelley]

In "develop" commit f039406, the possibly-problematic example code is simply commented-out. That will ensure that the problem doesn't go away. Click 'Details' below for some notes on my reasoning.

oce and kriging

With version 1.8-0 we have a linux/debian check yielding an error (converted
from a warning about number of cores being used). I did some web searches, and
found Rdatatable/data.table#3300, which makes me think
oce will get a "change or else" message.

Presently I am using \dontrun{} but I need to learn whether that is obeyed. Here
are some references to check:

• https://stackoverflow.com/questions/12038160/how-to-not-run-an-example-using-roxygen2

• https://stackoverflow.com/questions/63693563/issues-in-r-package-after-cran-asked-to-replace-dontrun-by-dont
  test

  • devtools::check() running examples with --run-donttest when run_dont_test = FALSE r-lib/devtools#2216

The last of these has "I clarified the docs. Generally, now if you don't want to
run tests on CRAN \dontrun{} is more likely to work, but using \dontrun{} may
cause initial submission to fail." from Hadley. I am going to simply comment it
out, which I know will avoid the problem.

[dankelley]

I just noticed that this problem has disappeared on the CRAN report page. Still, the code change is useful.