DGT-OmegaT 3.5-DEV-4.2 published

Download : 3.4-DEV-4.2

This release re-introduces the new score algorithm, with some optimisations. The goal is to test it (reason why it is not in 3.4-TEST, it is not designed to be in production soon).

Last year we introduced in test a new score algorithm, for reasons explained in the article above the link. We were satisfied about the accuracy of the algorithm but we noticed that it significantly decreased performances of matches pane and matches statistics. For this reason it was removed when release 3.3 came to production.

Even if it was not present in releases 3.4-TEST nor 3.5-DEV, the new score was not abandoned: I simply waited the moment where I could find the time to check whenever I can improve performances. And the new algorithm for statistics gives a good occasion to test the new score, because now statistics are strictly based on one score (previous releases always calculated all scores, exactly as the matches pane) so we can now compare and check whenever the slowness is really due to new score or to the way we call it.

Now after tests and some optimisations, we can say that improved score seems almost 3 times slower than adjusted score, and less than 2 times slower than calculating the 3 old scores.

For the moment we introduce it as an optional alternative: if you select another score as main one, improved score will not be calculated unless you explicitly ask for for display in matches area. For statistics, now only one score is calculated, so it can be improved score if you select it as main score, else only another score is calculated.