Re: [computer-go] Learning : was Chess programs versus go programs

["Frank de Groot" <frank@xxxxxxxxxxxxx>]

----- Original Message ----- 
From: "Chris Fant" <chrisfant@xxxxxxxxxxxxxxxxx>
Subject: Re: [computer-go] Learning : was Chess programs versus go programs


> In a learning system (at least in mine), the bugs are not in the
> patterns, the bugs are in the code that generates the patterns.  Fix
> one bug, benefit many/most/all patterns.

Truly spoken.
I had an idea, took a week to code something up, got a pro prediction in the
single digits and spent two years of bugfixing to reach almost 50% now. The
code still is the same number of lines (or got slightly smaller since I
started to use pointers instead of arrays).

I thought that Thoman Wolf had a similar coding-to-bugfixing ratio with his
GoTools. Something like ten years of bugfixing.

When the last bugs are out (perhaps now), I will decrease the code, in order
to speed things up.
I will combine 8 class instances (for each pattern size) into a single class
that used more complex code but will be smaller and twice as fast (because
the work for the smaller patterns is part of the work for the larger
patterns and at the moment, that is re-done for every pattern).


_______________________________________________
computer-go mailing list
computer-go@xxxxxxxxxxxxxxxxx
http://www.computer-go.org/mailman/listinfo/computer-go/