Now it wasn't. I'm not sure whether it was because of the lack of time at the end of the summer or because the gain from using weighted transfer seemed to be negligible. My personal opinion is that the weakest spot (both performance- and quality-wise) is the python module which calculates the coverages and is used in the weight training tool. Regarding this, it seems like an idea to adapt the C++ code from the core to calculate the coverages during training instead of using that python module.
On 06.02.2017 11:42, [email protected] wrote: > Was the code merged into trunk ? > > I'm working out how to describe a continuation of the project. > > http://wiki.apertium.org/wiki/Ideas_for_Google_Summer_of_Code/Weighted_transfer_rules > > > > e.g. coding challenge and other stuff. > > Fran ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Apertium-stuff mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/apertium-stuff
