Tag Archives: BREIN

Bugfix SQL export of results

While processing new results the main application brein.exe was blocked if the export to an external SQL database went wrong for some reason. The new results did not arrive in BREIN at all.

Every SQL export command is now embedded in a so-called “try-finally” statement. This way the internal processing of new results should not be disturbed by SQL problems any more.

BREIN prediction window gets measured spectra

Measured spectra are now passed to the prediction window. In order to get this working the prediction configuration has to have spectrum objects with the same names as the Bright Eye which triggers the prediction update. Only the spectra recorded at the “trigger position” are sent.

In order to use this feature you have to get brein.exe and bright_eye_traverse.exe programs generated after September 13, 2014.

Here is the BREIN download page.

Improved start behavior

If BREIN was started after a long break during which a large number of results have been generated, the software was not responsive for a long period of time (because it was reading many result files). You can now limit the number of result files to be processed during one timer event (which happens every second). A number of 20 is reasonable and has been set as default value. You can change this choice in the Settings submenu.

Archive options

While BREIN is running, it produces a lot of files in the archive and the database folder. These directories are subfolders of the BREIN program directory (up to now). In order to avoid that this directory blows up over time you can use the following options to store all permanent data outside the program folder. Within the BREIN program folder only temporary files are used – so it should not increase in size any more. Make sure that the Cleaner program is running, and connect BREIN to an external SQL database if you can.

The archive can now be located anywhere in your file system – it need not be a subdirectory of the BREIN program folder.

You can switch off writing result files to the archive.

You can switch off writing scan files to the archive.

The database history files can be stored to the archive as well, instead of being stored in the product folder within the database.