Category Archives: CODE

Error messages in OLE automation

In object generation 4.97 we have implemented a new mechanism to pass error messages from SCOUT and CODE to OLE automation clients.

While it runs the OLE server (i.e. SCOUT or CODE) collects error messages in a list. We have introduced a view object (type ‘Error messages view’) to display the current list of error messages in a view.

Any OLE client (LabView, Excel, …) can retrieve information about the number of error messages, their type and text content. There is also a classification to separate critical errors and warnings. Once the OLE client has finished error handling it can clear the list in the OLE server.

New workbook functions

There are new script commands to write text and numbers to the workbook. The number to be written as well as row and column of the write action may be computed using user-defined expressions. You can refer to master parameters, fit parameters, optical functions and integral quantities in these expressions.

In the opposite direction, we have implemented new optical functions to compute average and standard deviation of rectangular blocks of cells, both in the workbook and the batch control window. As object names you have use the terms ‘workbook’ or ‘batch control’. The argument of the function call must specify the name of the worksheet as well as the start row and start column, and the end row and end column – all separated by commas.

New import routine for old Optoplex IIC files

Starting with object generation 4.91 the SCOUT and CODE software packages can import exsitu spectra reading text files generated by the Zeiss Optoplex IIC software. The routine can be called executing the menu command Actions/Spectra/Import/Import all spectra from an Optoplex IIC exsitu file.

Please note that in this format the wavelength range of the measured data always starts at 380 nm. Wavelength increment from point to point is 5 nm.

Spectral data are stored in % by Optoplex – you have to set the option to automatically divide incoming data by 100 in all receiving spectrum objects.

GenetiCode update: Master parameter optimization

Starting with version 1.40 GenetiCode can optimize master parameters of the underlying CODE configuration. Similar to the handling of thickness values, you have to specify a range of possible values [minimum … maximum] for each selected master parameter. During the evolution GenetiCode will then try to find the best solution.

Master parameters can be used to compute model parameters by the evaluation of user-defined expressions. You can use this mechanism to express restrictions of the design like one layer must have twice the thickness of another layer, or you can introduce temperature as a master parameter that governs optical constants and thickness values of a multilayer coating.

GenetiCode package 1.40 comes with an updated PDF that explains how the optimization of master parameters has to be defined.

Password protected views (object generation 4.88)

SCOUT and CODE are more and more used for routine work, often being operated by users not familiar with these software packages. You can protect the configuration against unwanted modifications by setting a global password (main menu: File/Options/Password). This option is available for a long time already.

In complex methods using several views you can now define individual passwords for each view. This way you can avoid every user being able to access every view. A typical scenario would be a measurement system that shows a few control elements in a view for routine measurements, and more details and controls for expert users in an advanced view. If the ‘expert view’ is password protected it can be seen and used by selected users only.