[computer-go] Clean Orego code up

[Peter Drake <drake@xxxxxxxxxx>]

We're done with research for the summer, so we've cleaned up our code 
and posted it:

http://www.lclark.edu/~drake/go/

This summer, we learned:

- Extracting patterns from recorded games helps, and it's even better 
if they're professional games.  (We've submitted a paper to ICGA on 
this.)

- Most optimizations don't seem worth it, although we did get a 
significant speedup by improving a commonly-used hash function.

- Our elaborate revertible data structures were not worth the effort, 
so we removed them.

- eXtreme Programming (sic) techniques, especially the "test first" 
approach, are helpful.

Of course, we also had further impressed on us the things everyone here 
already knows:

- Go is hard!

- Life and death is almost everything.


Enjoy, and please let us know if you find any bugs.

Peter Drake
Assistant Professor of Computer Science
Lewis & Clark College
http://www.lclark.edu/~drake/

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