gnugo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] Interested in GNU GO development


From: David G Doshay
Subject: Re: [gnugo-devel] Interested in GNU GO development
Date: Tue, 20 Apr 2004 22:22:38 -0700

Harry is a student at UC Santa Cruz and has talked to the professor
that works with me and 2 other graduate students on my foundation's
cluster project.

If any of you have ideas that he might work on that would be worth
the effort to develop for a cluster we could make the cluster available
to him for that work.  Speaking for the foundation, I am content to
have the copyright going to FSF as is normal, but I think it would be
up to UC in this case. Intellectual property rights are not a simple
thing at UC.


Cheers,
David


On Apr 20, 2004, at 6:53 AM, Arend Bayer wrote:


Daniel Bump wrote:

One thing that I think needs to get done is to implement persistent
caching of semeai results so we can increase the semeai node
limits. If you look in the function owl_attack() in owl.c you will
see a call to search_persistent_owl_cache().  There is no
corresponding call from the function owl_analyze_semeai().

Other people might have other projects to suggest.

A project of similar scope would be to reorganize the persistent reading
cache from a simple array to a heap sorted by lowest score. Then
store_persistent_reading_cache() would not have to go through the whole
array when trying to find the entry with lowest score (it does so when
the cache is full).

This would give an immediate speedup of about 1% and, more importantly,
allow us to increase the size of this cache with little performance cost
in the caching itself.

It would also be a good idea if you subscribe to the gnugo-devel mailing
list (see the link from the gnugo development home page).

Arend



_______________________________________________
gnugo-devel mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/gnugo-devel






reply via email to

[Prev in Thread] Current Thread [Next in Thread]