Re: [gnugo-devel] do some work for gnugo

[Evan Berggren Daniel]

There is a todo list on the devel page that you can look at.

I started some work a while ago on one of the items, automatically
recognizing when a group goes from alive to dead without being critical
first, but that could use more work.  I modified the twogtp perl script
to detect this, but more could be done with that.  Also useful would be a
debug mode in the program to output such transitions while it is playing
normally.

Other smaller ideas:

Owl move ordering probably could use some tuning.  Currently this ordering
is done in a fairly static fashion; writing an order_owl_moves function
much like the tactical code has might help significantly.  Also, the owl
code could probably get sizeable improvements from things like the history
heuristic and killer heuristic.

The endgame needs work.  Unfortunately, we don't have the best test
suites, but I'm working on that slowly.

For things that don't involve much coding, tuning the pattern databases
can be interesting.  And the test suites are always in need of
extending...

I don't think anyone is working on these specifically, but I could be
wrong.

Hope this helps

Evan Daniel

On Tue, 25 Mar 2003, kevin yong wrote:

> Hi, Gunnar:
>
>   thank you again for all your replies to my email.
>
>   i really like to do some work for gnugo. if you
> have some small-middle size tasks handy, would you
> let me try one of them? everything i do, i will
> summit back to you, go through your inspection.
> if you feel it is possible, please give me
> instructions
> of the guidelines/requirements.
>
> best regards.
>
> kevin.
>
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
>
>
> _______________________________________________
> gnugo-devel mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/gnugo-devel
>
>