Convert 'colorSpec::colorSpec' objects into spectral objects (xxxx_spct, xxxx_mspct) as defined in package 'photobiology' and vice veersa preserving as much information as possible.
1 2 3 4 5 6 7 8 9 10 11
colorSpec2mspct(x, multiplier = 1, ...) colorSpec2spct(x, multiplier = 1, ...) colorSpec2chroma_spct(x, multiplier = 1, ...) mspct2colorSpec(x, spct.data.var = NULL, multiplier = 1, ...) spct2colorSpec(x, spct.data.var = NULL, multiplier = 1, ...) chroma_spct2colorSpec(x, spct.data.var = NULL, multiplier = 1, ...)
numeric A multiplier to be applied to the 'spc' data to do unit or scale conversion.
character The name of the variable to read spectral data from.
Always check the sanity of the imported or exported data values, as guessing is needed when matching the different classes, and the functions defined here are NOT guaranteed to return valid data wihtout help from the user through optional function arguments.
Objects of class
colorSpec::colorSpec do not contain metadata or
class data from which the units of expression could be obtained. When using
this function the user needs to use parameter
multiplier to convert
the data to what is expected by the object constructors defined in package
'photobiology' but should only rarely need to use parameter
spct.data.var to select the quantity.
colorSpec::colorSpec objects may use memory more efficiently than
spectral objects of the classes for collections of spectra defined in
package 'photobiology' as wavelengths are assumed to be the same for all
member spectra, and stored only once while this assumption is not made for
collections of spectra, allowing different wavelengths and lengths for the
component spectra. Wavelengths are stored for each spectrum, but as
spectral classes are derived from 'tbl_df' in many cases no redundant
copies of wavelength data will be made in memory in spite of the more
flexible semantics of the objects.
1 2 3 4 5
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.