All posts by Wolfgang

Bugfix in BREIN

Depending on the configuration, it could happen that the main application brein.exe generated a *.csv file for each processed pane in the BREIN program folder. These files were meant to be generated for BREIN viewer, in the designated transfer folder, but happened to be generated even if BREIN viewer is not used at all.

We have removed this error in the latest version of brein.exe.

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.

Additional illuminants

Color computations were limited to illuminants A, D65 and C up to now. Additional illuminants could be imported and used for computations – however, this option was somewhat hidden and very likely overseen by many users.

With have now, starting with object generation 4.86, implemented 15 additional illuminants (D50, D55, D75, F1, F2, F3, F4, F5, F6, F7, F8, F9, F10, F11, F12).