The prediction feature of BREIN transfers the latest fit results and spectra to an internal CODE instance. This can be used to do various kinds of computations, based on the properties of the pane that was investigated last.
In a similar way the new ‘Inspection’ mechanism re-loads historic fit results (and the spectra that were used to obtain these numbers) to a separate CODE instance. This can be configured to let the operators verify the fit results and try what happens if some parameters were modified.
For details please see the updated documentation (page 55 at the moment).
The computation of the total solar heat gain coefficient (g-value) following the rules of standard ISO 52022-3 (2017) has been implemented. The procedure takes into account the temperature change of panes and gases due to absorption and re-emission of solar radiation. The absorbed solar power and the final temperature of each pane are side-results of the routine and are available in addition to the g-value.
The BREIN prediction page now forwards mouse clicks and mouse moves to the underlying CODE window. This opens the route to interactive operator work.
However, the prediction page of BREIN is updated every second only. This means the user interface is not as responsive as that of CODE itself.
We have developed a new scanner software that connects the Zeiss Optoplex SQL system to BREIN. The program scans database tables for inline and exsitu spectra and feeds new spectra into the corresponding BREIN input folders.
The definition of the trigger event that initiates the re-computation of the prediction page has been improved: You can now specify a range of x, y or z values, in addition to fixed values.
A setting of “1500 … 1600” for y means that the trigger event is fired whenever the condition 1500<=y<=1600 holds. This new feature is useful to handle traverse systems which do not measure at exactly the same positions when scanning a sample.
You can still set unique values like “1567” for the x, y or z coordinates.
This problem has been described in a previous post. The recommended installation of the Microsoft redistributable package does not seem to solve the problem in every case.
We have made the missing DLLs available on our website. You can download the files here and copy them to your SCOUT or CODE program folder directly, without executing any installation routine.
The relevant program folders are (very likely) c:\scout\ (in the case of SCOUT) or c:\code\ (for the CODE software).
On monitors with high dpi values (small pixel size) Windows 10 sometimes decides to scale text output on graphics pages. In this case main view graphics of SCOUT, CODE and BREIN may look ugly, like on low resolution screens.
If this happens on your computer you can right-click the program file (scout.exe, code.exe or brein.exe) and select ‘Properties’ (or ‘Options’) and then open the tab ‘compatibility’. Check the option ‘Disable display scaling on high DPI settings’ as shown below:
That should solve the problem.
Thanks to S. Eraslan for pointing out this solution!
Starting with object generation 4.58, SCOUT and CODE can export data like fit parameters or values of optical functions (in CODE also integral quantities) to external SQL databases. If you have done a measurement with a spectrometer system and performed a fit of a model you can send the results to your company database.
We have implemented an ADO database connection which lets you contact Microsoft, Oracle and Informix databases. Before you can do that the corresponding client software has to be installed on your computer.
Which values are exported to which columns of the open database table is defined in scripts. Scripts are view elements which appear like a button in the main view. When clicked they execute a sequence of commands, including calling other scripts.
XRR objects in CODE and SCOUT can now import measured XRR data reading xrdml files.
With version 4.56 we have removed a bug in master models for optical constants. Saving a successful model and re-loading it could lead to a strange mix-up of parameter values in some situations, leaving the poor user with a useless configuration. We recently taught CODE and SCOUT to correctly count master and slave parameters – saving and loading should work now.