Re: [computer-go] Digital Mars

2009-04-22 Thread Łukasz Lew
Please download newest version, I made some ifdefWIN 32 ... to aid mingw porting. http://github.com/lukaszlew/libego/zipball/master Under linux I can cross compile to windows binary with a following command $ i586-mingw32msvc-g++ -o engine.exe ego/ego.cpp example/main.cpp -O3 -march=native -Iego

Re: [computer-go] Digital Mars

2009-04-22 Thread Ben Shoemaker
Success! I was able to build on WinXP using Scons and minGW (with gcc4.3.3). Here's what (finally) worked for me: 1. Install Python 2.6.2 http://www.python.org/ftp/python/2.6.2/python-2.6.2.msi 2. Install minGW (using TDM's installer on empty minGW directory)

Re: [computer-go] Digital Mars

2009-04-22 Thread Michael Williams
I do have a core2, but it complained about that switch: ego/ego.cpp:1: error: bad value (core2) for -march= switch ego/ego.cpp:1: error: bad value (core2) for -mtune= switch example/main.cpp:1: error: bad value (core2) for -march= switch example/main.cpp:1: error: bad value (core2) for -mtune=

Re: [computer-go] Digital Mars

2009-04-22 Thread Michael Williams
After I used a better MinGW build, with a newer gcc (the one Ben suggested), I get must better results with no compiler warnings: 40.0609 kpps/GHz Lukasz, the march options of native, i686 and core2 all worked and came out to similar results with i686 being slightly faster for me. Łukasz

Re: [computer-go] Digital Mars

2009-04-22 Thread Jason House
That seems like a good speed. On my Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz, using linux and the exact compiler libego was tuned for, I get 42 kpps/GHz. On my AMD Athlon(tm) 64 X2 Dual Core Processor 5000+, using the same compiler, I only get 37 kpps/GHz. On Wed, 2009-04-22 at 18:09

Re: [computer-go] Digital Mars

2009-04-22 Thread Jason House
There's a big difference between kpps and kpps/GHz! For your system, you need to divide by two (and on my core2, divide by 1.66). For raw kpps, I think I had 70 on my core2 and 100 on the AMD64. Do you consistently get garbage such as -154.124 for your kpps/GHz? Sent from my iPhone On Apr

Re: [computer-go] Roadmap 2020 - using analysis mode to improve programs

2009-04-22 Thread terry mcintyre
I haven't got a ladder example at the moment, but here's an instance where Leela does not realize it is in terrible trouble. I ( with my 8 kyu AGA rating) know with certainty by move 223 (T5) that Black has captured a large white group. A stronger player could read this out sooner than I. This

Re: [computer-go] Roadmap 2020 - using analysis mode to improve programs

2009-04-22 Thread Darren Cook
I ( with my 8 kyu AGA rating) know with certainty by move 223 (T5) that Black has captured a large white group. A stronger player could read this out sooner than I. This fight is too big to lose for either side; nothing else on the board matters. Yes! I use Many Faces and GoGui/Mogo for

Re: [computer-go] Roadmap 2020 - using analysis mode to improve programs

2009-04-22 Thread Jason House
I've only looked at the first game, but it does seem very interesting to analyze. The white group around H2 is near death as well and I think Leela's evaluation considered that group to be threatened. Once that is solidly alive, it does switch to the semeai on the right. I probably would not

[computer-go] Libego benchmarking

2009-04-22 Thread Michael Williams
Here is my full set of numbers. I wonder why the known kpps/GHz but unknown kpps. = Benchmarking, please wait ... = 20 playouts in 0 seconds 1.#INF kpps 40.0245 kpps/GHz (clock independent) 105316/94359 (black wins / white wins) = 20 playouts in 0 seconds 1.#INF kpps 40.0721

Re: [computer-go] Libego benchmarking

2009-04-22 Thread Petri Pitkanen
Because your time measurement has gone wrong. You get 0 seconds in time hence kpssa in infinity. Petri 2009/4/23 Michael Williams michaelwilliam...@gmail.com: Here is my full set of numbers.  I wonder why the known kpps/GHz but unknown kpps. = Benchmarking, please wait ... = 20

Re: [computer-go] Re: Analysis mode for human use

2009-04-22 Thread Darren Cook
translated to Ishi-go B 1 Q4 W 2 R16 B 3 C4 W 4 F3 ... *** modified Ishi-go 1. q4 2. r16 3. c4 4. f3 ... from the west - my modified Ishi-go-format should be even better. (The repetitive B W are a bit annoying in Ishi-go, and small letters are better to read than capital