---
title: "colorSpec User Guide"
author: "Glenn Davis"
date: "`r Sys.Date()`"
output:
rmarkdown::html_vignette:
css: widevignette.css # width 900px to match the included tables
toc: true
toc_depth: 2
number_sections: true
bibliography: bibliography.bib
csl: personal.csl
# csl: institute-of-mathematical-statistics.csl
# csl: transactions-on-mathematical-software.csl
vignette: >
%\VignetteIndexEntry{colorSpec User Guide}
%\VignetteEngine{knitr::rmarkdown}
---
```{r setup, include=FALSE}
knitr::opts_chunk$set(echo = TRUE)
library(colorSpec)
```
**colorSpec** is an **R** package providing an S3 class with methods for color spectra.
It supports the standard calculations with spectral properties of light sources, materials, cameras, eyes, scanners, etc..
And it works well with the more general action spectra.
Many ideas are taken from packages
**hsdar** @hsdar,
**hyperSpec** @hyperSpec,
**pavo** @pavo,
**photobiology** @photobiology, and
**zoo** @zoo.
Some features:
<ul>
<li>a clear classification of the common color spectra into 4 types</il>
<li>flexible organization for the spectra in memory, using an S3 class - **colorSpec**</li>
<li>a product algebra for the **colorSpec** objects</li>
<li>uniform handling of biological eyes, electronic cameras, and general action spectra</li>
<li>a few advanced calculations, such as computing optimal colors (aka MacAdam Limits)</li>
<li>_inverse colorimetry_, e.g. reflectance recovery from response
<li>built-in essential tables, such as the CIE illuminants and color matching functions</li>
<li>a package logging system with log levels taken from the popular **Log4J**</li>
<li>support for reading a few spectrum file types, including CGATS</li>
<li>bonus files containing some other interesting spectra</li>
<li>minimal dependencies on other **R** packages</li>
</ul>
The following packages are **Imports**:
<ul>
<li>**logger** @logger, used for all logging, see <a href="#appendix-g---logging">Appendix G</a> for more information.</li>
</ul>
The following packages are **Suggests**:
<ul>
<li>**spacesXYZ** @spacesXYZ, required for computing CCT, CRI, and for some vignettes</li>
<li>**rootSolve** @rootSolve, required for inverse colorimetry</li>
<li>**MASS** @MASS, required for camera emulation, which uses the matrix pseudoinverse `MASS::ginv()`</li>
<li>**rgl** @rgl, required for plotting optimal colors in 3D</li>
<li>**microbenchmark** @microbenchmark, for a timer with higher precision
than **R**'s built-in timer</li>
<li>**arrangements** @arrangements, makes the zonohedron calculations
for optimal colors a little bit faster</li>
<li>**quadprog** @quadprog, may be used in `responsivityMetrics()` to determine whether the
generators lie in an open linear halfspace</li>
<li>**knitr** @knitr, **rmarkdown** @rmarkdown, and **spacesRGB** @spacesRGB,
required for building the vignettes</li>
</ul>
Some non-features:
<ul>
<li>
There is no support for 3D colors spaces other than XYZ and RGB; see packages **colorspace** @colorspace,
**colorscience** @colorscience,
**spacesRGB** @spacesRGB,
and
**spacesXYZ** @spacesXYZ for more 3D spaces.
</li>
<li>
there are few non-linear operations.
The only such operations are conversion of absorbance to transmittance,
and the reparameterized wavelength $\omega$ from $\lambda$ in `computeADL()`.
The electronic camera model is purely linear with no dark current offset or other deviations.
</li>
<li>there is little support for scientific units; for these see packages
**photobiology** @photobiology
and **colorscience** @colorscience</li>
<li>photons are parameterized by wavelength in nanometers (nm);
other wavelength units (such as Ångstrom and micron)
and alternative parameterizations (such as wavenumber and electronvolt)
are not available.</li>
</ul>
```{r echo=FALSE, results='asis'}
includetable <- function( path, height ) {
tmp1 <- URLencode( paste(readLines(path,warn=FALSE), collapse="\n"), reserved = TRUE )
tmp2 <- sprintf( '", style="border: none; seamless:seamless; width: 900px; height: %s" ></iframe>', height )
# cat( '<iframe src="data:text/html;charset=utf-8,', tmp1 , tmp2 )
knitr::raw_html( c( '<iframe src="data:text/html;charset=utf-8,', tmp1 , tmp2 ), meta=NULL, cacheable=FALSE )
}
includeplain <- function( path ) {
tmp <- readLines(path,warn=FALSE)
writeLines( tmp )
}
```
<br>
# Spectrum Types
Pick up any book on color physics
(e.g. @wyszecki2000color, @packer2003, @oleari2016standard, or @koenderink)
or color management
(e.g. @giorgianni2009digital)
and you will see plots of many spectra.
Let's start with a simple division of these spectra into 4 basic types:
```{r echo=FALSE, results='asis'}
includetable( "tables/table-1.1.html", "550px" )
```
For the infinite-dimensional spaces, the interval [380,780] is used for illustration;
in specific calculations it can vary.
Note that of the 4 vector spaces, only $L^*$ and $M$ are isomorphic,
but we take the mathematical point of view that although they are isomorphic, they are not the same.
For a proof of this isomorphism, see **Appendix D**.
Multiplication operators are the infinite-dimensional generalization of diagonal matrices.
For more background on this functional analysis,
see @wiki:MO and @LangReal.
For the finite-dimensional spaces, it takes the full sequence of wavelengths and not just the endpoints. The wavelength sequence is typically regular not always.
In this case all 4 vector spaces are isomorphic (since
they are the same dimension), but we still take the mathematical point of view that they are not the _same_ space.
The last `type='responsivity.material'` is the least common.
There is an example in @giorgianni2009digital
(Figure 10.11a, page 141) of a scanner,
where the 3 spectra are called the _effective spectral responsivities_ of that scanner.
They are the pointwise product of the scanner light source and
the responsitivies of the scanner's RGB sensor; see also pages 146-147.
On page 335, in equation (B.4), there is a more general product.
In **colorSpec**, both of these products and more are peformed in the function `product()`.
Another example of effective spectral responsivities are those of a
reference scanner from SMPTE, see @7292043.
Every **colorSpec** object has one of these types, but it is not stored with the object.
The object stores a `quantity` which then determines the `type`;
see the next section for more discussion.
A synonym for `type` might be `space`, but this could be confused with _color space_.
**colorSpec** does not actually use the finite-dimensional representations in Table 1.1;
the organization is flexible.
And it would not be efficient memory use to store a diagonal matrix as such.
For discussion of the organization, see section 4.
Given 2 finite-dimensional spectra of types `'light'` and `'responsivity.light'` the response (a real
number) is their dot product multiplied by the step between wavelengths.
All materials in this document are non-fluorescent;
i.e. the outgoing photons reflected (or transmitted) only
come from incoming photons of the same wavelength.
A transparent material transmits an incoming light
spectrum and a new spectrum emerges on the other side. If the material is not fluorescent, the outgoing
spectrum is the same as the incoming, except there is a reduction of power that depends only on the
wavelength (and the material).
If the light power were divided into N bins, the transmitted power spectrum
would be a diagonal NxN matrix times the incoming spectrum.
A reflectance spectrum is mathematically the same as a transmittance spectrum,
except we compare the
outgoing light spectrum to that of a _perfect reflecting diffuser_.
Such a material does not exist, like many concepts in physics,
but it is a very useful idealization.
<br>
# Spectrum Quantities
Unfortunately there are two common metrics for quantifying spectra with `type='light'` -
_energy of photons_ and _number of photons_.
The former - _radiometric_ - is the oldest, being used in the 19^th^ century.
The latter - _actinometric_ - was not used until the 20th century
(after the modern concept of photons was proposed in 1905).
So colorimetry uses radiometric quantities by convention and actinometric ones are converted to
radiometric automatically for calculations.
The conversion is easy; see the function `radiometric()`,
@packer2003 pp. 93-94,
and @oleari2016standard p. 12.
Similarly, `'responsivity.light'` can be radiometric (e.g. the CIE color matching functions)
or actinometric (e.g. the quantum efficiency of a CMOS sensor).
These actinometric spectra are also converted to radiometric on the fly.
For responsivity, we distinguish between 3 types of response:
_electrical_, _neural_, and _action_.
In **colorSpec** this 3-way distinction is only used in a few places:
<ul>
<li>for the y label of the spectrum in `plot()`</li>
<li>to determine the default adaption method in `calibrate()`</li>
<li>for the conversion equations in `radiometric()` and `actinometric()`</li>
</ul>
Note that the `action` response is really a grab-bag for responses that are neither
`electrical` (a modern solid-state photosensor) nor `neural` (a biological eye).
Here are the valid types and their quantities:
```{r echo=FALSE, results='asis'}
includetable("tables/table-2.1.html", "640px" )
```
The **colorSpec** quantities are typically not the same as the SI quantities; they are more general.
First consider light sources (`type='light'`).
The **colorSpec** `quantity='energy'` includes all 5 of these _power_-based SI quantities:
radiant power (radiant flux), irradiance, radiant exitance, radiant intensity, and radiance.
And it also includes these _energy_-based quantities:
radiant energy, radiant exposure, and the time integrals of radiant exitance, radiant intensity, and radiance.
Thus `quantity='energy'` includes 10 true physical SI quantities,
which all include energy
and optionally include area, solid angle, and time.
Similary, the **colorSpec** `quantity='photons'` includes all 5 of these SI quantities:
photon flux, photon irradiance, photon exitance, photon intensity, and photon radiance.
It also includes these 5 quantities integrated over time, e.g. photon fluence.
Versions of **colorSpec** before 0.7-1 used `power` in place of `energy`.
But now we have switched to `energy`;
see <a href="#appendix-e---energy-vs-power">Appendix E</a> for the reasons why.
`power` and `power->*` are still supported, but deprecated,
and will eventually be phased out.
For `type='light' and type='responsivity.light'`,
each radiometric quantity has a corresponding actinometric quantity.
The following table shows the correspondences:
```{r echo=FALSE, results='asis'}
includetable("tables/table-2.2.html", "240px" )
```
The **colorSpec** functions `radiometric()` and `actinometric()` convert
back and forth between the two metrics.
For `energy` and `energy->electrical` and `energy->action`
the functions actually do assume the example units.
For `energy->electrical` the example units in the table are in common use
for electronic cameras.
Note that for `energy->action`, the action we have in mind is photosynthesis.
A quick internet search shows that the maximum theoretical photosynthesis response
is between 1/16 and 1/8 of an $\text{O}_2$ molecule per photon.
For `energy->neural` see the functions man pages for more discussion.
<br>
Since these are spectra parameterized by nm,
the example units should all add $\text{nm}^{-1}$ at the end,
but this is suppressed for simplicity.
<br>
Now consider materials (`type='material'`).
The situation here is simpler.
The **colorSpec** `quantity='reflectance'`, `'transmittance'`, and `'absorbance'` correspond directly to the SI quantities.
All reflecting materials are Lambertian and opaque,
and all transmitting materials have only direct transmission with no scatter.
<br>
# Construction of colorSpec objects
The user constructs a `colorSpec` object `x` using the function `colorSpec()`:
```
x <- colorSpec( data, wavelength, quantity='auto', organization='auto', specnames=NULL )
```
The arguments are:
`data`
a vector or matrix of the spectrum values.
In case `data` is a vector, `x` has a single spectrum and the number of points in that
spectrum is the length of `data`.
In case `data` is a matrix, the spectra are stored in the columns,
so the number of points in each spectrum is the number of rows in `data`.
It is OK for the matrix to have only 0 or 1 column.
`wavelength`
a numeric vector of wavelengths for all the spectra in `x`.
The length of this vector must be equal to `NROW(data)`,
and the unit must be nanometers.
The sequence must be increasing.
The `wavelength` of `x` can be changed after construction.
`quantity`
a character string giving the quantity of all spectra;
see Table 2.1 for a list of valid values.
In case `quantity='auto'`, a guess is made from the `specnames`.
The `quantity` of `x` can be changed later.
`organization`
a character string giving the desired organization of the returned colorSpec object. In case `organization='auto'`, the organization is `'vector'` or `'matrix'` depending on `data`.
The `organization` of `x` can be changed _after_ construction.
See the next section for discussion of all 4 possible organizations.
`specnames`
a character vector with length equal to the number of spectra in `data`,
and with no duplicates.
If `specnames=NULL` and `data` is a vector,
then `specnames` is set to `deparse(substitute(data))`.
If `specnames=NULL` and `data` is a matrix,
then `specnames` is set to `colnames(data)`.
If `specnames` is _still_ not a character vector with the right length,
or if there are duplicate names, then `specnames` is set to
`'S1', 'S2', ...` with a warning message.
Names can be changed after construction.
Compare `colorSpec()` with the function `stats::ts()`.
<br>
<br>
<br>
# colorSpec object organization
A spectrum is similar to a time-series (with time replaced by wavelength),
and so the organization of a `colorSpec` object is similar to that of the
time-series objects in package **stats**.
A single time-series is organized as a vector with class `ts`,
and a multiple time series is organized as a matrix (with the series in the columns) with class `mts`.
We decided to use a single class name `colorSpec`,
continue the idea of different organizations, and allow 2 _more_ organizations.
Here are the 4 possible organizations, in order of increasing complexity:
`'vector'`
The object is a numeric vector with attributes but no dimensions, like a time-series `ts`.
This organization works for a single spectrum only, which is very common.
The common arithmetic operations work well with this organization.
The length of the vector is the number of wavelengths.
The class of the object is `c('colorSpec','numeric')`.
`'matrix'`
The object is a matrix with attributes, like a multiple time-series `mts`.
This is probably the most suitable organization in most cases,
but it does not support extra data (see `'df.row'` below).
The common arithmetic and subsetting operations work well; and even `round()` works.
The number of columns is the number of spectra, and the spectrum names are stored as the column names. This organization can be used for any number of spectra, including 0 or 1.
The class of the object is `c('colorSpec', 'matrix')`.
`'df.col'`
The object is a data frame with attributes.
The spectra are stored in the columns.
But the first column is always the wavelength sequence, so the spectra are in columns 2:(M+1),
where M is the number of spectra.
This organization mirrors the most common organization in text files and spreadsheets.
The common arithmetic operations do not work, and the initial wavelength column is awkward to handle.
The spectrum names are stored as the column names of the data frame.
This organization can be used for any number of spectra, including 0 or 1.
This organization imitates the "long" format in package **hyperSpec**.
The class of the object is `c('colorSpec', 'data.frame')`.
`'df.row'`
The object is a data frame with attributes.
The last (right-most) column is a matrix with spectra in the rows.
This matrix is the transpose of the matrix used when the organization is `'matrix'`.
The common arithmetic operations do not work.
The spectrum names are stored as the row names of the data frame.
This organization can be used for any number of spectra, including 0 or 1.
This organization imitates the "tall" format in package **hyperSpec**.
This is the only organization that supports extra data associated with each spectrum,
such as physical parameters, time parameters, descriptive strings, or whatever.
This extra data occupies the initial columns of the data frame that come before the spectra,
and can be any data frame with the right number of rows.
This extra data can be assigned to any spectrum with the `'df.row'` organization.
The class of the object is `c('colorSpec', 'data.frame')`.
<br>
# colorSpec object attributes
The attribute list is kept as small as possible. Here it is:
```{r echo=FALSE, results='asis'}
includetable("tables/table-5.1.html", "430px" )
```
The user should never have to modify these using the function `attr()`.
<br>
# Spectrum File Import
There are 5 text file formats that can be imported; no binary formats are supported yet.
The function `readSpectra()` reads a few lines from the top of the file to try and determine the type.
If successful, it then calls the appropriate read function;
see the **colorSpec** reference guide for details.
The file formats are:
`XYY`
There is a line matching `'^(wave|wv?l)'` (not case sensitive) followed by the the names of the spectra.
This is the column header line.
All lines above this one are taken to be metadata.
This is probably the most common file format; see the sample file `ciexyz31_1.csv`.
`spreadsheet`
There is a line matching `'^(ID|SAMPLE|Time)'`.
This line and lines below must be tab-separated.
Fields matching `'^[A-Z]+([0-9.]+)nm$'` are taken to be spectral data and other fields
are taken to be extradata.
All lines above this one are taken to be metadata.
The organization of the returned object is `'df.row'`.
This is a good format for automated acquisition of many spectra, using a spectrometer.
See the sample file `E131102.txt`.
`scope`
This is a file format used by Ocean Optics spectrometer software.
There is a line `>>>>>Begin Processed Spectral Data<<<<<`.
The following lines contain wavelength and energy separated by a tab.
There is only 1 spectrum per file.
The organization of the returned object is `'vector'`.
See the sample file `pos1-20x.scope`.
`CGATS`
This is a standardized format for exchange of color data, covered by both ANSI and ISO standards,
see @CGATS.17 and @ISO28178.
It might be best understood by looking at some samples, such as `inst/extdata/objects/Rosco.txt`.
Unfortunately these standards do not give a standard way to name the spectral data.
The function `readSpectra()` considers field names that match the pattern `"^(nm|SPEC_|SPECTRAL_)[_A-Z]*([0-9.]+)$"` to be spectral data
and other fields are considered extra data.
The organization of the returned object is `'df.row'`.
`Control`
This is a personal format used for digitizing images of plots from
manufacturer datasheets and academic papers.
It is structured like a Microsoft `.INI` file.
There is a `[Control]` section establishing a simple linear map from the image pixels in the file
to the wavelength and spectrum quantities.
Only 3 points are really necessary.
It is OK for there to be a little rotation of the plot axes relative to the image.
This is followed by a section for each spectrum, in XY pixel units only.
Conversion to wavelength and spectral quantities happens during on-the-fly after read.
The organization of the returned object is `'vector'`.
<br><br>
# Package Options
There is a function `cs.options()` for setting options private to the package.
Currently there is only one option (before v 1.6-0 there were three).
By default, when a logging `ERROR` event occurs, execution stops.
But if the option `colorSpec.stoponerror` is `FALSE`, execution continues.
The logging level `FATAL` is reserved for internal errors,
and after a `FATAL` event, execution _always_ stops.
<br><br>
# Future Work
Here are a few possible improvements and additions.
wavelength
handling the wavelength sequence, e.g. for `product()` and `resample()`, is an annoyance.
We might consider adding a global wavelength option that all spectra are automatically resampled to.
fluorescent materials
Recall that a non-fluorescent material corresponds to a diagonal matrix,
which operates in a trivial way on light spectra.
A diagonal matrix can be stored much more compactly as a plain vector,
and multiplication of a diagonal matrix by a vector simplifies to entrywise (Hadamard) multiplication.
A fluorescent material corresponds to a non-diagonal matrix – called the _Excitation Emission Matrix_
or _Donaldson Matrix_.
The product in **Appendix C** is still multilinear,
but the material product in the middle is no longer symmetric,
so enhancements to the product computations must be made.
This is a new level of complexity and memory usage,
and may require a new type of memory organization.
comparisons
There should a metric of some kind that compares two material spectra.
There should be a way to compare 2 colorSpec objects of the same type,
especially `'responsivity.light'`.
For example, there would then be a way to evaluate how close an electronic camera
comes to satisying the _Maxwell-Ives Criterion_.
Possible metrics would be the principal angles between subspaces.
`plot()`
the `product()` function saves the terms with the product object,
but the `plot()` function ignores them.
It may be useful to have an option to plot the individual terms too.
<br><br>
# References
<div id="refs"></div>
<br>
\Appendix
<hr>
# Appendix A - Built-in colorSpec Objects
The following are built-in **colorSpec** objects that are commonly used.
They are global objects that are automatically available when **colorSpec** is loaded.
For more details on each see the corresponding help topic.
```{r echo=FALSE, results='asis'}
includetable("tables/table-A.1.html", "400px" )
```
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-A.2.html", "400px" )
```
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-A.3.html", "200px" )
```
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-A.4.html", "100px" )
```
<br>
<hr>
# Appendix B - Bonus Spectral Data
Each built-in **colorSpec** object in **Appendix A** takes time to fully document in `.Rd` help files.
Here are some bonus spectra files under folder `extdata` that users may find interesting and useful.
Use the function `readSpectra()` to construct a **colorSpec** object from the file,
for example:
```{r echo=TRUE}
sunlight = readSpectra( system.file( 'extdata/illuminants/sunlight.txt', package='colorSpec' ) )
sunlight
```
See the top of each file for sources, attribution, and other information.
Alternatively, one can run `summary()` on the imported object.
Some of the files in `Control` format have associated `JPG` or `PNG` images of plots.
```{r echo=FALSE, results='asis'}
includetable("tables/table-B.1.html", "480px" )
```
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-B.2.html", "450px" )
```
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-B.3.html", "500px" )
```
<br>
# Appendix C - Spectrum Products
This Appendix is a very formal mathematical treatment of spectra.
In infinite dimensions we use the terminology of functional analysis.
In finite dimensions we use the terminology of linear algebra.
For easier reference here is a repeat of Table 1.1:
```{r echo=FALSE, results='asis'}
includetable("tables/table-C.1.html", "550px" )
```
There are 5 natural binary products on these spaces:
<br>
```{r echo=FALSE, results='asis'}
includetable("tables/table-C.2.html", "350px" )
```
An equivalent way to handle these material diagonal matrices is to represent
them instead as simple vectors – the entries along the diagonal.
The above products with diagonal matrices then become the much simpler entrywise or Hadamard product.
This is how it is done in **colorSpec**, using R's built-in entrywise product operation.
The first 4 products can be strung together to get a product:
$$L \times M_1 \times ... \times M_m \times L^* \to R$$
It is not hard to show that this product is _multilinear_.
This means that if one fixes all terms except the $i^{th}$ material location, then the composition:
$$M \to L \times M_1 \times ... \times \bullet \times ... \times M_m \times L^* \to R$$
is linear, see @LangLinear.
The first inclusion map means to place the material spectrum in $M$
at the ith variable slot $\bullet$ in the product.
The composition map is a functional on $M$ which is an element of $M^*$,
i.e. a material responder.
This special method of creating a material responder - a spectrum in $M^*$ - plus all the
products in the above table,
are available in the function `product()` in **colorSpec**.
See that help page for examples.
Compare the previous equation with equation (B.4) (page 335) in @giorgianni2009digital.
The right-hand term $R$ can be thought of as standing for _Response_ or _Real numbers_.
In **colorSpec** the light responders can have _multiple_ channels,
e.g. _R_, _G_, and _B_,
and so there are conventions on the admissible numbers of spectra for each term in these products.
See the help page for `colorSpec::product()` for details.
<br>
# Appendix D - Proofs
```{r echo=FALSE, results='asis'}
includeplain("proofs.txt")
```
<br>
# Appendix E - Energy vs Power
Consider these subtle differences in the way light sources
and responders (detectors) are appropriately measured:
<ul>
<li>
*Power* is an appropriate way to measure constant light sources,
such as the lighting in an office, or a standard illuminant.
But *energy* is appropriate for variable sources, such as a pulsed light source.
</li>
<li>
The response to *power* is an appropriate way to measure non-integrating responders,
such as a
biological eye (`'power->neural'`),
a photovoltaic cell (`'power->electrical'`),
or photosynthesis (`'power->action'`).
All of these respond (almost) instantaneously.
<br>
The response to *energy* is an appropriate way to measure integrating responders,
such as an electronic camera (`'energy->electrical'`),
or erythemal exposure (`'energy->action'`).
For these responders there is a well-defined integration time.
</li>
</ul>
Since color science emphasizes constant light sources and biological eyes,
*power* has always seemed more appropriate to me than *energy*.
But starting with **colorSpec** version 0.7-1
I decided to switched to `energy` for these reasons:
<ul>
<li>
Energy is more fundamental than power.
Power is defined from energy by the messy process of differentiation.
The conversion between energy of photons and number of photons is straightforward,
without a messy integration time.
The terms *energy-based* and *photon-based* are well-established
in vision science, and in software packages like **photobiology** @photobiology.
</li>
<li>
In flash-based photography (`energy->electrical`)
what matters to the color of the photograph
is the integral of the spectrum (the energy) of the flash bulb
over the exposure interval of the camera.
This is a case when the light spectrum is not constant;
it can vary over that interval.
Similarly, in photosynthesis (`energy->action`) what matters
to the plant is the integral of daylight from sunrise to sunset.
Think of the daytime as a very long pulse.
For an example, see the file `solar.exposure.txt` in
<a href="#appendix-b---bonus-spectral-data">Appendix B</a>.
</li>
</ul>
<br>
I also considered allowing *both* `energy` and `power`,
and *both* `photons` and `photons/time`.
But this would force the user to decide whether a light source
is constant or variable,
and whether a responder/detector is integrating or non-integrating.
So things quickly got complicated.
These common radiant SI quantities
- radiant power, irradiance, radiant exitance, radiant intensity, radiance -
differ only in area and steradian.
Time is now grouped with these 2 geometric units.
<br>
# Appendix F - Continuous vs Discrete
In physics, wavelengths are in some interval of real numbers - an uncountable set.
But in engineering, one is forced to use wavelengths taken from a finite table of values.
Given a table of wavelengths and values, a software package must make some sort of choice
of what the physical interpretation of this table really is.
In **colorSpec** the choice is schizophrenic - there are multiple interpretations.
With few exceptions, a table of wavelengths and values is interpreted as a _step function_.
Such functions are sometimes called _piecewise-constant_.
This requires a lengthy explanation.
Suppose `X` is a **colorSpec** object with $N$ wavelengths:
$\lambda_1 < \lambda_2 < \ldots < \lambda_N$.
Define $N$ intervals $I_i := [\beta_{i-1},\beta_i]$
where
\begin{equation}
\beta_0 := \tfrac{3}{2}\lambda_1 - \tfrac{1}{2}\lambda_2 ~~~~~
\beta_i := (\lambda_i + \lambda_{i+1})/2, ~ i{=}1,\ldots,N-1 ~~~~~
\beta_N := \tfrac{3}{2}\lambda_N - \tfrac{1}{2}\lambda_{N-1}
\end{equation}
The intervals $I_i$ are a partition of $[\beta_0,\beta_N]$.
Note that $[\beta_0,\beta_N]$ is slightly bigger than $[\lambda_1,\lambda_N]$ because the endpoints are extended.
Define the $i'th$ step $\mu_i := \operatorname{length}(I_i), ~ i{=}1,\ldots,N$.
If the sequence $\{\lambda_i\}$ is _regular_ ($\lambda_{i+1}-\lambda_i$ is constant),
then $\mu_i$ is constant with the same value,
and each $\lambda_i$ is the center of $I_i$.
Now suppose `X` has $m$ spectra (channels) with vector values
$\mathbf{y}_i \in \mathbb{R}^m$.
Then the physical function realization of `X` is a function
$\mathbf{y}(\lambda) : [\beta_0,\beta_N] \to \mathbb{R}^m$ that takes the constant value $\mathbf{y}_i$ on $I_i$.
If the sequence $\{\lambda_i\}$ is regular, then all $\mathbf{y}_i$ have the same weight,
including the first and last.
This is the step function interpretation used in
`product()`, `interpolate()`, `bandSpectra()`, and many other places.
The exceptions are `resample()` and `plot()`.
In `resample()` the physical functions are piecewise-linear, piecewise-cubic, or piecewise-quintic,
depending on the argument `method` (a smoothing method is also available).
In `plot()` the spectra are plotted as piecewise-linear (using `lines()`) by default,
but an option to plot as step functions (using `segments()`) was added in v. 1.2-0.
The function `product()` often takes the product of spectra.
Note that the product of piecewise-linear functions is not piecewise-linear,
but the product of step functions is still a step function.
In lengthy calculations using both interpretations, there are inevitable numerical errors,
which are certainly larger than the usual numerical roundoff.
But we do not attempt carry the error analysis any further than that.
<br><br>
# Appendix G - Logging
Logging is performed using the package **logger** @logger.
This is a powerful package that allows a separate configuration
for logging from within **colorSpec**, and that is what I have done.
During package loading, the logging threshold is changed from `INFO` to `WARN`.
To change it back again, one can execute:
`logger::log_threshold( logger::INFO, namespace="colorSpec" ) # preferred`
or
`library( logger ) # not preferred`
`log_threshold( INFO, namespace="colorSpec" )`
The layout callback function is customized;
it adds the name of the calling function to the message.
To change it back again, one can execute:
`log_layout( layout_simple, namespace="colorSpec" )`
or to install ones own layout function, one can execute:
`log_layout( <your function>, namespace="colorSpec" )`.
The appender callback functions is also customized;
it comes to an immediate stop if the log event level is `FATAL`,
or if the level is `ERROR` and the global option `colorSpec.stoponerror` is `TRUE`.
To return to the default behavior, one can execute:
`log_appender( appender_console, namespace="colorSpec" )`
The formatter callback function is initialized to be `formatter_sprintf()`;
this should not be changed.
<br><br>
# Session Information
<pre>
```{r, echo=FALSE, results='asis'}
sessionInfo()
```
</pre>