We have introduced some new commands to manage spectra:
Objects of type ‘color box’ (members of the list of special computations) can now compute the average spectrum and average values of a* and b* for fluctuating layer thickness values. This helps to understand spectral drifts due to production uncertainties.
There was a problem with Windows usernames which sometimes are returned in capital letters and sometimes not. Unfortunately this caused legal users to be rejected. We have relaxed the checking procedure in order to keep you going …
A CODE design can now be exported to the rendering software “Ocean 2015” (made by Eclat Digital).
Starting with a CODE configuration like the one shown below
you can export all data (angular dependence of reflectance and transmittance) needed for realistic simulations in the visible. As an example, the appearance of a bank building (equipped with the simple low-e stack shown above) has been simulated for different weather conditions.
Gray sky:
Sunny day:
If you overlay several ‘special computation objects’ in a view (like a bunch of parameter variation graphs) and you have de-activated their option ‘Automatic re-computation’, the view update requires many mouse clicks.
Not any more: You can now use a script to update all objects with a single click. Define a script and pass the object command ‘update’ to all objects. Here is an example showing how to re-compute 3 special computation objects named sc1, sc2, and sc3:
object command, sc1,update
object command, sc2, update
object command, sc3,update
update plot
If you synchronize a parameter variation object to another one, the graphics settings are copied so that they are the same for both objects. However, size and position of the corresponding view objects are not synchronized automatically up to now. This missing feature has been implemented today.
Writing results to batch control tables has been improved: The receiving cells are now formatted to use the number of digits which have been set for the individual fit parameters.
The definition of fit parameters in the list of fit parameters allows you to specify a factor. This number multiplies the original value in such a way that the value displayed in the first column of the list is the product of the original value and the factor. However, fit parameter values written to the batch control tables or extracted by OLE automation did not take into account the factor.
The behaviour has been improved in the following way: The dialog for fit options (File/Options/Fit) now allows you to check the option ‘Apply factor in fit parameter transfers’. If active, the factor is used in the batch control and for OLE automation transfers (in both directions, i.e. setting or reading values). If the option is unchecked, the program behaves as before.
The option is not stored as part of the configuration, but is stored for each user as default setting. Once switched on it stays on until you switch it off.
In addition, you can check or uncheck this option by new OLE automation methods called ‘apply_factor_in_fit_parameter_transfers’ and ‘do_no_apply_factor_in_fit_parameter_transfers’.
We have added some new hardware controllers which operate components used in optical setups. Together with the built-in spectrometer controls you can now automate optical measurements. All hardware controllers are objects in the list of spectrometers.
These are the new controllers:
In addition, objects called ‘WOSP triggers’ can automatically start scripts if a pre-defined condition becomes true. Triggers are used together with the automation timer. You can, for example, record a reflectance spectrum at each timer event. The average reflectance will be almost zero when there is no sample and higher once a sample is present. A trigger can now use the average reflectance value to verify the presence of a sample and execute a sample measurement with automatic saving of the recorded spectrum.
We have modified the import and export routines for optical constants (n + i k) using the OceanOptics NanoCalc format.