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.
We have fixed a (small) incorrect conversion of X, Y, Z color coordinates to sR, sG and sB computer screen values when the field of view has a cone angle of 10°. The routines for 2° cone angles have not been changed.
Temporary data fields that are part of spectrometer objects are now saved in configuration files. You can close and open the program and continue to acquire spectra, without repeating dark and reference measurements.
Starting with object generation 4.50 our software products SCOUT and CODE can handle the latest type of Avantes spectrometers. The new functions are contained in the DLL file avaspec.dll which must be present in the program directory.
If you try to run CODE, SCOUT or SPRAY with object generation 4.50 or higher and you get this message please install the Visual C++ Redistributable package for Visual Studio 2013. Here is the link:
If you follow the ‘Download’ section you have to select the vcredist_x86.exe. Running this will install the required DLL files.
The gamma value of the OJL model had been limited to values above 150 1/cm to avoid numerical problems. This restriction has been removed in the following way: As a new available option you can set the limit yourself, executing the menu command File/Options/Optical model/Set minimum value of gamma in OJL models. The new limit is applied to all OJL models that you use in this particular configuration. Note, however, that the new value is not stored as a general setting – it is only active and stored in the configuration you are working with.
If you have used the option to export measured spectra in CODE using Excel format you can now import these spectra in batch mode.
There is a restriction, however: The spectra must be stored in the first worksheet of the Excel document, with the first wavelength in cell A1.
The number of the file format to be used in the batch control sheet is 27.
This feature is available starting with object generation 4.48.