logging

Logging is done using the logger package.
Logging output goes to <code><a href="/link/stderr()?package=colorSpec&version=1.6-0" data-mini-rdoc="colorSpec::stderr()">stderr()</a></code>, just like the message stream;
but see <code><a href="/link/sink?package=colorSpec&version=1.6-0" data-mini-rdoc="colorSpec::sink">sink</a>()</code> (and the pitfalls of using it).

Calculate with spectral properties of light sources, materials, cameras, eyes, and scanners.
Build complex systems from simpler parts using a spectral product algebra. For light sources,
compute CCT, CRI, and SSI.  For object colors, compute optimal colors and Logvinenko coordinates.
Work with the standard CIE illuminants and color matching functions, and read spectra from
text files, including CGATS files.  Estimate a spectrum from its response. A user guide and 9 vignettes are included.

Glenn Davis

colorSpec

Color Calculations with Emphasis on Spectral Data

logging function

<dl></dl><dt><code>colorSpec.stoponerror</code></dt>
<dd>If the this option is <code>TRUE</code> (the default),
a log event with level <code>ERROR</code> stops execution;
otherwise, execution keeps going.
For interactive use, <code>TRUE</code> is probably better.
For long batch jobs, <code>FALSE</code> might be appropriate,
since then a single error may not force a complete repeat. 
A <code>FATAL</code> event always stops execution.</dd>
For examples on changing this option, see <code>cs.options</code>.

Logging Options

Logging is done using the logger package.
Logging output goes to <code><a href='https://rdrr.io/r/base/showConnections.html'>stderr()</a></code>, just like the message stream;
but see <code><a href='https://rdrr.io/r/base/sink.html'>sink</a>()</code> (and the pitfalls of using it).

Logging in colorSpec package — logging

<dl>

<dt><code>colorSpec.stoponerror</code></dt>
<dd>If the this option is <code>TRUE</code> (the default),
a log event with level <code>ERROR</code> stops execution;
otherwise, execution keeps going.
For interactive use, <code>TRUE</code> is probably better.
For long batch jobs, <code>FALSE</code> might be appropriate,
since then a single error may not force a complete repeat. 
A <code>FATAL</code> event always stops execution.</dd>


</dl>For examples on changing this option, see <code>cs.options</code>.

logging: Logging in colorSpec package

Description

Arguments

Logging Options

References

See Also

Examples