isoband | R package to generate contour lines | Computer Vision library

What you are looking for is as.polygons() from the terra package, the raster package's successor. terra handles large data sets better than raster does.

I think this is ultimately a small bug in renv. Here's my guess at what's happening:

1. While this project has been initialized as an renv project, it does not have a lockfile for some reason. (Perhaps renv::activate() was called to initialize renv without explicitly creating a lockfile?)

2. The project has an renv autoloader; this is from a script at renv/activate.R. That script is configured to load renv 0.11.0.

3. When the project is loaded, renv finds that renv 0.12.0 is installed in the project library, not the expected version 0.11.0. This causes the warning to be emitted. (Perhaps renv was updated in that project previously?)

So, ultimately, the warning is misleading here -- the request for renv 0.11.0 comes directly from the autoloader, not from the lockfile (which does not exist). As for why the lockfile does not exist, I'm not sure -- but it most likely implies the project was initialized via renv::activate(), and not by renv::init().

All that said -- you can safely re-generate the lockfile via renv::snapshot().

I'm not sure this fully answers your question, but there has been a change in behaviour between ggplot v3.2.1 and v3.3.0 due to the way the contour bins are calculated. In the earlier version, the bins are calculated in StatContour$compute_group, whereas in the later version, StatContour$compute_group delegates this task to the unexported function contour_breaks. In contour_breaks, the bin widths are calculated by the density range divided by bins - 1, whereas in the earlier version they are calculated by the range divided by bins.

We can revert this behaviour by temporarily changing the contour_breaks function:

Before

Solved. The cause of the problem was that after a series of Ubuntu and R upgrades there were some outdated packages installed from source remained on my system.

First I opened up an R console and looking for the paths for R packages built with pre 3.6 version:

The issue was caused by ggupset, and has since been fixed.

If anyone else has encountered this, you can use the current development version: remotes::install_github("const-ae/ggupset"), or wait for the CRAN release in the near future.