photobiologyWavebands 0.5.0

The main changes from version 0.4.5 the previous CRAN release, are:

  • Minor edits to documentation.
  • Rebuilt manual to comply with HTML 5.
  • Recognize Landsat mission "L9" as equal to "L8" as wavelengths are the same.
  • On bad arguments to parameter std the returned value is no-longer NA (a logical value) but instead a waveband object with its wavelength fields set to NA_real_, as returned by a call to waveband(). This potentially code-breaking change ensures that the class of the returned objects is the same irrespective of the arguments passed in the call, and that missing values more easily propagate to downstream computations without triggering errors.

Package documentation web site at:

NOTE: The updated package is on its way to CRAN.

Please raise issues concerning bugs or enhancements to this package through Bitbucket at


HTML5 compliance of R packages

As of R 4.0.0 there is a requirement for compliance with the HTML5 standard. Until recently, package ‘Roxygen2’, that is used to automatically generate the documentation, included in its output in some HTML4 tags that have been removed in the upgrade to HTML5.

For compliance with CRAN requirements I had to rebuild packages ‘ggspectra’, ‘photobiologyWavebands’, ‘photobiologyInOut’, ‘photobiologyLamps’ and ‘photobiologyLEDs’. There were no other changes in ‘ggspectra’. Some minor changes were included in the updates to ‘photobiologyLamps’, ‘photobiologyLEDs’ and ‘photobiologyInOut’. Changes to ‘photobiologyWavebands’ were more and are described in a separate post.

The updated packages have been submitted to CRAN.

ggpmisc 0.5.0

Version 0.5.0 (previously announced as 0.4.8) brings enhancements to the annotations based on model fits. The most significant change for all users is the new convenience function use_label() that greatly simplifies the assembly of labels from components and their mapping to aesthetics. We examplify its use and some of the other new features. It also contains two changes that are not backwards compatible and that can in isolated cases break existing code (hence the version-number change into 0.5.0).

Continue reading