The new OLE command export_spectra_via_variants has been introduced in both SCOUT and CODE (object generation 5.14). The command takes 5 parameters:
- input: the index of the spectrum object in the list of spectra (counting 1, 2, 3, …)
- output: a variant array holding the spectral positions (e.g. wavelengths)
- output: a variant array with simulated spectral values
- output: a variant array with measured spectral values at the same spectral positions as the simulated values, obtained by linear interpolation between the closest available points
- output: a string with the spectral unit
Following the Dutch protocol NEN 2675 we have introduced the new integral quantity ‘Hemispherical T (NEN 2675)’. It computes the transmittance of a glazing product averaged for both wavelength and angle of incidence.
Starting with object generation 5.12, you can store fit parameter sets in a list called ‘Fit parameter pool’. This list is stored as part of the SCOUT or CODE configuration file. Using fit parameter sets from the pool avoids the necessity to load them from separate files.
Instead of specifying a filename for the fit parameter set (which is still possible) you can use phrases like ‘pool(step 1)’ or ‘pool(oscillator strengths only)’ to load fit parameter sets with names ‘step 1’ or ‘oscillator strengths only’.
Using file based fit parameter sets is possible after all, of course.
The dialog that sets the parameters for ‘rating’ has been updated in object generation 5.12.
‘Rating’ is the transformation of the fit deviation (a floating point number) to a text-based category like ‘Good’, ‘Bad’ or ‘Perfect’.