Category Archives: BREIN

New fit option

We have included a new fit option which helps to increase the speed of analysis in time critical applications: In methods which use pre-fit sets in the list of fit parameters you can now include the current fit parameter values in the pre-fit search. This eventually avoids many fit iterations if differences between consecutive measurements are small.

The new feature can be turned on or off in the dialog of fit options.


Climate settings, window tilt angle, pane absorption and temperature computations

We have upgraded several CODE functions related to the technical performance of glazing products.

You can now compute solar pane absorption and pane temperatures for up to 6 glass panes.

The list of integral quantities in CODE features new menu items (in File/options):

  • set global climate parameters used for U-value, g-value and temperature computations
  • set the window tilt angle for all U-value, g-value and temperature computations

You can display climate values using labels in a view with the following names:

  • ‘selected_climate’ (shows the name of the climate)
  • ‘selected_climate_parameters’ (shows values of outside temperature, external heat exchange coefficient he, inside temperature, internal heat exchange coefficient, solar power
  • ‘selected_climate_ISO52022’ (shows the name of the climate settings for ISO 52022-3 computations)
  • ‘selected_climate_parameters_ISO52022’ (shows values of outside temperature, external heat exchange coefficient he, inside temperature, internal heat exchange coefficient, solar power, used for ISO 52022-3 computations)

You can display the value of the window tilt angle using a label called ‘window tilt angle’.

Finally, you can call the following new script commands to open user dialogs in the main view:

  • edit climate
  • edit window tilt angle

Optoplex SQL spectrum scanner more flexible

We have made the import of measured traverse spectra from the Zeiss SQL database more flexible. Up to now the scanner processed all new spectra not analyzed by BREIN. In order to do so it sends an SQL search command to the Optoplex Q database filtering out spectra with IDs larger than the last processed ID,

You can now inject more search criteria into the SQL search command filtering in a more complex manner. In order to inject additional search conditions you have to add 2 lines to the optoplex_sql_spectrum_scanner,ini file, The first line is ‘Optoplex Q where phrase’ and the second line the injected SQL fragment. Here is an example:

Optoplex Q where phrase
and (measpointindex = 1 or measpointindex = 10)

When you re-start the scanner it will only process spectra recorded at measurement positions 1 and 10 – all other spectra are ignored.

Filtering results table

The table of results can now be filtered: You can type in a pane ID or select a bright eye (or both) and check the ‘filter’ option – the table will then show results for the selection only. Unchecking the filter option brings you back to the display of all results.

Optoplex spectrum scanner: New version

A new version of the scanner has been released. We have verified that this one can process reflectance measurements taken at 55° angle of incidence, in addition to the ‘normal’ transmission and reflectance spectra recorded at 8° angle of incidence.

Make sure that your BREIN product contains 4 spectra, and that you enter Optoplex names correctly in the conversion tables ‘BE assignment’ and ‘Spectrum nicknames’: Sometimes the database column ‘Resultname’ is ‘OFR155° SB Reflection’, and sometimes it appears as ‘OFR155° SB Reflection Glass’.



Inspection of historic fit results: New BREIN feature

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).