Re: [computer-go] MoGoRel3_3550pps
Sylvain Gelly wrote: 2008/1/10, [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Hi Sylvain, Have you finished your thesis? We are eager to read it:-) Hi, Yes I did! :).It is not on my website, but will (soon?). However, you should not be so eager to read it :) Cheers, Sylvain Google finds it: http://tao.lri.fr/Papers/thesesTAO/SylvainGellyThesis.pdf Rémi ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
Sylvain Gelly wrote: It looks like MoGo does respect the time_left commands from GTP, so I don't think the totalTime parameter is required in this case. What do you mean? If you don't put --totalTime, then MoGo indeed ignores time_left. If you put --totalTime, then it respect the time_left. The reason I said that was this behavior from mogo. If I start it without that switch and as for a move, it allocates 20 seconds. If I then issue a small time_left command and ask for another move, it allocates a much smaller amount of time. Here is the output: [EMAIL PROTECTED]:~/go$ ./mogo --19 initiateNodeUrgencyForShisho at root node! Load opening database openingValues_19 succeed (nbEntries=60629) (nbIllegalMoves removed 0) tried to open openingValues_19, success 1 genmove b time left: 12 secs time given for this move: 20.0 sec time shishoCheck is called. Now we have 0 shishoLocations: and 0 attackShishoLocation initiateNodeUrgencyForShisho at root node! Self train initiation time: 0.00 0.450253(81%) || 1186/ 1(12%)(72%)(54%/0.59) ||44 |12 || G4 E5 F5 E4 E6 D6 D7 E7 F6||SSP:G4 C2 H1 J9 J4 ||PSP:G4 C2 H1 J9 J4 0.436817(80%) || 4487/ 2(22%)(31%)(72%/0.59) ||89 |13 || F6 D5 E4 F5 G5 E6 F7 E7 E8 F8 ||SSP:F6 G4 C2 H1 J3 ||PSP:F6 G4 C2 H1 J3 0.476407(90%) || 5277/ 3(18%)(91%)(59%/0.54) || 190 |13 || E5 E4 F4 D4 E3 F5 D5 G4 F3 D3 ||SSP:E5 F6 D5 G4 C2 ||PSP:E5 F6 D5 G4 C2 0.454793(91%) || 11005/ 4(28%)(44%)(80%/0.56) || 275 |14 || E5 E4 D5 F4 D4 D3 C3 F5 F6 C2 ||SSP:E5 F6 D5 F5 E4 ||PSP:E5 F6 D5 F5 E4 0.47(94%) || 12436/ 5(25%)(88%)(93%/0.53) || 323 |15 || F5 H5 E2 D7 F7 G7 G6 H7 G8 H8 ||SSP:F5 E5 F6 D5 E4 ||PSP:F5 E5 F6 D5 E4 0.481018(97%) || 22284/ 6(37%)(49%)(94%/0.52) || 374 |15 || F5 H5 E2 F7 C6 D6 D5 D7 E6 C7 ||SSP:F5 E5 F6 D5 E4 ||PSP:F5 E5 F6 D5 E4 0.477984(94%) || 32022/ 7(46%)(34%)(75%/0.52) || 428 |17 || F5 H5 E2 F7 C6 D6 D5 D7 E6 C7 ||SSP:F5 E5 F6 D5 E4 ||PSP:F5 E5 F6 D5 E4 0.470916(86%) || 39111/ 8(49%)(28%)(61%/0.52) || 483 |17 || F5 H5 E2 F7 C6 D6 D5 D7 E6 C7 ||SSP:F5 E5 F6 D5 E4 ||PSP:F5 E5 F6 D5 E4 earlyCut : max1 42505; max2 11005; sum 84807 max1/sum 0.501191 ; max1/max2 3.861984 (hard 0) 0.467192(41%) || 42505/ 84807(50%)(26%)(56%/0.52) || 513 |17 || F5 H5 E2 F7 C6 D6 D5 D7 E6 C7 ||SSP:F5 E5 F6 D5 E4 ||PSP:F5 E5 F6 D5 E4 84807 simulations(average length:0) done, time used: 14.63 seconds.( 5796.8 games/sec) A B C D E F G H JABCD EFGHJ +---+ +-+ 9 | . . . . . . . . . | | 0.3568 0.4000 2.4650 0.4468 0.3739 0.2987 0.3438 0.3775 0.3531 | 8 | . . . . . . . . . | | 2.4638 0.4384 2.4519 2.4556 2.4667 2.4589 2.4645 0.3612 0.3939 | 7 | . . . . . . . . . | | 0.4314 0.5714 2.4512 2.4637 2.4521 0.4403 0.4340 0.4259 0.3842 | 6 | . . . . . . . . . | | 0.3411 2.4606 2.4569 2.4634 2.4618 0.4322 0.5333 2.4670 0.3783 | 5 | . . . . . . . . . | | 0.3688 0.4433 2.4625 0.4450 0.4548 0.4672 0.4218 0.3996 0.3436 | Black to play 4 | . . . . . . . . . | | 0.3558 0.4111 2.4648 0.0001 0.4474 2.4652 0.4343 0.4400 0.4055 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0.3318 0.4500 0.4452 0.4113 2.4602 0.4554 0.3784 0.4123 0.4050 | White eaten stone(s): 0 2 | . . . . . . . . . | | 0.3658 0.3900 0.4232 0.4286 0.3070 0.4504 0.4053 0.3831 0.3723 | 1 | . . . . . . . . . | | 0.3201 0.3807 0.3238 0.3694 0.3747 0.3673 0.4036 0.3938 0.3508 | +---+ +-+ A B C D E F G H J A B C D E F G H J +---+ +---+ 9 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 8 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 7 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 6 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Move 1: F5 5 | . . . . . (@) . . . | | 0 0 0 0 0 1 0 0 0 | White to play 4 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White eaten stone(s): 0 2 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 1 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 |time_left w 1 0 = genmove w time left: 1 secs time given for this move: 0.0 sec time fast end mode gives one move:D8 A B C D E
Re: [computer-go] MoGoRel3_3550pps
From: Rémi Coulom [EMAIL PROTECTED] Sylvain Gelly wrote: Yes I did! :).It is not on my website, but will (soon?). However, you should not be so eager to read it :) Cheers, Sylvain Google finds it: http://tao.lri.fr/Papers/thesesTAO/SylvainGellyThesis.pdf Thanks, Rémi! Now eagerly awaiting the English translation! Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
There is lots of English in it. Just scroll down. terry mcintyre wrote: From: Rémi Coulom [EMAIL PROTECTED] Sylvain Gelly wrote: Yes I did! :).It is not on my website, but will (soon?). However, you should not be so eager to read it :) Cheers, Sylvain Google finds it: http://tao.lri.fr/Papers/thesesTAO/SylvainGellyThesis.pdf Thanks, Rémi! Now eagerly awaiting the English translation! Never miss a thing. Make Yahoo your homepage. http://us.rd.yahoo.com/evt=51438/*http://www.yahoo.com/r/hs ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
The reason I said that was this behavior from mogo. If I start it without that switch and as for a move, it allocates 20 seconds. If I then issue a small time_left command and ask for another move, it allocates a much smaller amount of time. Here is the output: Because you give a time_left 20, so MoGo is in fast end mode, just playing randomly to avoid loosing by time. Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
Sylvain Gelly wrote: The reason I said that was this behavior from mogo. If I start it without that switch and as for a move, it allocates 20 seconds. If I then issue a small time_left command and ask for another move, it allocates a much smaller amount of time. Here is the output: Because you give a time_left 20, so MoGo is in fast end mode, just playing randomly to avoid loosing by time. OK, here it is with 60 seconds (still no command-line switch): [EMAIL PROTECTED]:~/go$ ./mogo --19 initiateNodeUrgencyForShisho at root node! Load opening database openingValues_19 succeed (nbEntries=60629) (nbIllegalMoves removed 0) tried to open openingValues_19, success 1 time_left b 60 0 = genmove b time left: 60 secs time given for this move: 1.0 sec time shishoCheck is called. Now we have 0 shishoLocations: and 0 attackShishoLocation initiateNodeUrgencyForShisho at root node! Self train initiation time: 0.00 0.443380(83%) || 1148/ 1(11%)(93%)(58%/0.60) ||47 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 J1 ||PSP:B2 C3 A1 H8 J1 earlyCut : max1 1364; max2 1120; sum 12061 max1/sum 0.113082 ; max1/max2 1.216771 (hard 0) 0.435484(16%) || 1364/ 12061(11%)(82%)(65%/0.60) ||53 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 A6 ||PSP:B2 C3 A1 H8 A6 12061 simulations(average length:0) done, time used: 0.96 seconds.(12563.5 games/sec) A B C D E F G H JABCD EFGHJ +---+ +-+ 9 | . . . . . . . . . | | 0.0001 2.4427 2.4315 0.0001 0.2353 0.3509 0.3750 0.3204 0.3867 | 8 | . . . . . . . . . | | 2.4245 0.4698 2.4267 0.0001 2.4426 0.5111 2.4430 0.4303 0.3468 | 7 | . . . . . . . . . | | 0.5000 2.4244 2.4167 2.4193 0.5317 2.4296 2.4360 0.4259 2.4463 | 6 | . . . . . . . . . | | 0.4343 2.4323 2.4267 0.5000 2.4398 2.4261 0.0001 0.3043 0.3857 | 5 | . . . . . . . . . | | 0.3961 2.4463 2.4310 2.4306 0.4898 0.5248 2.4324 0.4249 0.3109 | Black to play 4 | . . . . . . . . . | | 0.3663 0.0001 2.4404 2.4231 2.4280 2.4326 2.4394 0.4268 0.3033 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0.3582 0.3846 0.4429 0.5417 2.4329 2.4407 2.4381 2.4381 0.3387 | White eaten stone(s): 0 2 | . . . . . . . . . | | 0.2000 0.4355 0.5000 0.4000 0.3438 2.4395 2.4387 0.3760 0.3895 | 1 | . . . . . . . . . | | 0.4284 0.4000 0.3867 0.3780 0.4011 0.3805 0.3782 0.4040 0.4129 | +---+ +-+ A B C D E F G H J A B C D E F G H J +---+ +---+ 9 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 8 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 7 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 6 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Move 1: B2 5 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White to play 4 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White eaten stone(s): 0 2 | . (@) . . . . . . . | | 0 1 0 0 0 0 0 0 0 | 1 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | +---+ +---+ B2 = B2 ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
Hi, Nothing strange here. You tell MoGo to play 19x19 and you tell him that there is only 60 s left. It can be understood that it takes only 1s for this move... BTW, if you see him play in 9x9, it is because while you told him to set his parameters for a 19x19, by default the boardsize is 9x9 and MoGo expects a gtp command to override it. Cheers, Sylvain 2008/1/13, Michael Williams [EMAIL PROTECTED]: Sylvain Gelly wrote: The reason I said that was this behavior from mogo. If I start it without that switch and as for a move, it allocates 20 seconds. If I then issue a small time_left command and ask for another move, it allocates a much smaller amount of time. Here is the output: Because you give a time_left 20, so MoGo is in fast end mode, just playing randomly to avoid loosing by time. OK, here it is with 60 seconds (still no command-line switch): [EMAIL PROTECTED]:~/go$ ./mogo --19 initiateNodeUrgencyForShisho at root node! Load opening database openingValues_19 succeed (nbEntries=60629) (nbIllegalMoves removed 0) tried to open openingValues_19, success 1 time_left b 60 0 = genmove b time left: 60 secs time given for this move: 1.0 sec time shishoCheck is called. Now we have 0 shishoLocations: and 0 attackShishoLocation initiateNodeUrgencyForShisho at root node! Self train initiation time: 0.00 0.443380(83%) || 1148/ 1(11%)(93%)(58%/0.60) ||47 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 J1 ||PSP:B2 C3 A1 H8 J1 earlyCut : max1 1364; max2 1120; sum 12061 max1/sum 0.113082 ; max1/max2 1.216771 (hard 0) 0.435484(16%) || 1364/ 12061(11%)(82%)(65%/0.60) ||53 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 A6 ||PSP:B2 C3 A1 H8 A6 12061 simulations(average length:0) done, time used: 0.96 seconds.( 12563.5 games/sec) A B C D E F G H JABCD EFGHJ +---+ +-+ 9 | . . . . . . . . . | | 0.0001 2.4427 2.4315 0.0001 0.2353 0.3509 0.3750 0.3204 0.3867 | 8 | . . . . . . . . . | | 2.4245 0.4698 2.4267 0.0001 2.4426 0.5111 2.4430 0.4303 0.3468 | 7 | . . . . . . . . . | | 0.5000 2.4244 2.4167 2.4193 0.5317 2.4296 2.4360 0.4259 2.4463 | 6 | . . . . . . . . . | | 0.4343 2.4323 2.4267 0.5000 2.4398 2.4261 0.0001 0.3043 0.3857 | 5 | . . . . . . . . . | | 0.3961 2.4463 2.4310 2.4306 0.4898 0.5248 2.4324 0.4249 0.3109 | Black to play 4 | . . . . . . . . . | | 0.3663 0.0001 2.4404 2.4231 2.4280 2.4326 2.4394 0.4268 0.3033 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0.3582 0.3846 0.4429 0.5417 2.4329 2.4407 2.4381 2.4381 0.3387 | White eaten stone(s): 0 2 | . . . . . . . . . | | 0.2000 0.4355 0.5000 0.4000 0.3438 2.4395 2.4387 0.3760 0.3895 | 1 | . . . . . . . . . | | 0.4284 0.4000 0.3867 0.3780 0.4011 0.3805 0.3782 0.4040 0.4129 | +---+ +-+ A B C D E F G H J A B C D E F G H J +---+ +---+ 9 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 8 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 7 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 6 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Move 1: B2 5 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White to play 4 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White eaten stone(s): 0 2 | . (@) . . . . . . . | | 0 1 0 0 0 0 0 0 0 | 1 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | +---+ +---+ B2 = B2 ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
I'm not saying that it's anything strange. I was just pointing out that it does seem to heed the time_left number, even without specifying totalTime on the command line. Yes, I started mogo with the --19 switch so that it would have to think about the first move on 9x9 instead of using the opening book. It's easier to type than --useOpeningBook 0. Sylvain Gelly wrote: Hi, Nothing strange here. You tell MoGo to play 19x19 and you tell him that there is only 60 s left. It can be understood that it takes only 1s for this move... BTW, if you see him play in 9x9, it is because while you told him to set his parameters for a 19x19, by default the boardsize is 9x9 and MoGo expects a gtp command to override it. Cheers, Sylvain 2008/1/13, Michael Williams [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Sylvain Gelly wrote: The reason I said that was this behavior from mogo. If I start it without that switch and as for a move, it allocates 20 seconds. If I then issue a small time_left command and ask for another move, it allocates a much smaller amount of time. Here is the output: Because you give a time_left 20, so MoGo is in fast end mode, just playing randomly to avoid loosing by time. OK, here it is with 60 seconds (still no command-line switch): [EMAIL PROTECTED]:~/go$ ./mogo --19 initiateNodeUrgencyForShisho at root node! Load opening database openingValues_19 succeed (nbEntries=60629) (nbIllegalMoves removed 0) tried to open openingValues_19, success 1 time_left b 60 0 = genmove b time left: 60 secs time given for this move: 1.0 sec time shishoCheck is called. Now we have 0 shishoLocations: and 0 attackShishoLocation initiateNodeUrgencyForShisho at root node! Self train initiation time: 0.00 0.443380(83%) || 1148/ 1(11%)(93%)(58%/0.60) ||47 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 J1 ||PSP:B2 C3 A1 H8 J1 earlyCut : max1 1364; max2 1120; sum 12061 max1/sum 0.113082 ; max1/max2 1.216771 (hard 0) 0.435484(16%) || 1364/ 12061(11%)(82%)(65%/0.60) ||53 |12 || B2 C3 D3 D4 E4 E3 D2 F4 E5||SSP:B2 C3 A1 H8 A6 ||PSP:B2 C3 A1 H8 A6 12061 simulations(average length:0) done, time used: 0.96 seconds.(12563.5 games/sec) A B C D E F G H JABCD EFGHJ +---+ +-+ 9 | . . . . . . . . . | | 0.0001 2.4427 2.4315 0.0001 0.2353 0.35090.3750 0.3204 0.3867 | 8 | . . . . . . . . . | | 2.4245 0.4698 2.4267 0.0001 2.4426 0.5111 2.4430 0.4303 0.3468 | 7 | . . . . . . . . . | | 0.5000 2.4244 2.4167 2.4193 0.5317 2.4296 2.4360 0.4259 2.4463 | 6 | . . . . . . . . . | | 0.4343 2.4323 2.4267 0.5000 2.4398 2.4261 0.0001 0.3043 0.3857 | 5 | . . . . . . . . . | | 0.3961 2.4463 2.4310 2.4306 0.4898 0.5248 2.4324 0.4249 0.3109 | Black to play 4 | . . . . . . . . . | | 0.3663 0.0001 2.4404 2.4231 2.4280 2.4326 2.4394 0.4268 0.3033 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0.3582 0.3846 0.4429 0.5417 2.4329 2.4407 2.4381 2.4381 0.3387 | White eaten stone(s): 0 2 | . . . . . . . . . | | 0.2000 0.4355 0.5000 0.4000 0.3438 2.4395 2.4387 0.3760 0.3895 | 1 | . . . . . . . . . | | 0.4284 0.4000 0.3867 0.3780 0.4011 0.3805 0.3782 0.4040 0.4129 | +---+ +-+ A B C D E F G H J A B C D E F G H J +---+ +---+ 9 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 8 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 7 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | 6 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Move 1: B2 5 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White to play 4 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | Black eaten stone(s): 0 3 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | White eaten stone(s): 0 2 | . (@) . . . . . . . | | 0 1 0 0 0 0 0 0 0 | 1 | . . . . . . . . . | | 0 0 0 0 0 0 0 0 0 | +---+
Re: [computer-go] MoGoRel3_3550pps
It looks like MoGo does respect the time_left commands from GTP, so I don't think the totalTime parameter is required in this case. What do you mean? If you don't put --totalTime, then MoGo indeed ignores time_left. If you put --totalTime, then it respect the time_left. Cheers, Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
2008/1/10, [EMAIL PROTECTED] [EMAIL PROTECTED]: Hi Sylvain, Have you finished your thesis? We are eager to read it:-) Hi, Yes I did! :).It is not on my website, but will (soon?). However, you should not be so eager to read it :) Cheers, Sylvain On 1/10/08, Sylvain Gelly [EMAIL PROTECTED] wrote: Hi, I guess the public version of MoGo was designed with a focus on 9x9 and not 19x19. It was not more on 9x9 that 19x19, it was more or less the best settings of MoGo against gnugo at the moment I left the developpement (early september) for both 9x9 and 19x19. Or is there something else I should be including on the command line? As other said, but just to confirm: --playsAgainstHuman 0 Also you have to specify --totalTime 300 if 300 is the number of seconds of the games. If not, MoGo does not care about the time left, and will just play a constant time per move, loosing by time with no other worry :). The release is designed to play against human on a server/client which supports a scoring taking into account the dead stones. On cgos you have to capture all dead stones. As for the rating, I don't know all the changes that has been done on CGOS since then, but on the old 19x19 one, the rating should be more than 2100 or 2200. Hoping this helps, Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
Hi, I guess the public version of MoGo was designed with a focus on 9x9 and not 19x19. It was not more on 9x9 that 19x19, it was more or less the best settings of MoGo against gnugo at the moment I left the developpement (early september) for both 9x9 and 19x19. Or is there something else I should be including on the command line? As other said, but just to confirm: --playsAgainstHuman 0 Also you have to specify --totalTime 300 if 300 is the number of seconds of the games. If not, MoGo does not care about the time left, and will just play a constant time per move, loosing by time with no other worry :). The release is designed to play against human on a server/client which supports a scoring taking into account the dead stones. On cgos you have to capture all dead stones. As for the rating, I don't know all the changes that has been done on CGOS since then, but on the old 19x19 one, the rating should be more than 2100 or 2200. Hoping this helps, Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
Hi Sylvain, Have you finished your thesis? We are eager to read it:-) On 1/10/08, Sylvain Gelly [EMAIL PROTECTED] wrote: Hi, I guess the public version of MoGo was designed with a focus on 9x9 and not 19x19. It was not more on 9x9 that 19x19, it was more or less the best settings of MoGo against gnugo at the moment I left the developpement (early september) for both 9x9 and 19x19. Or is there something else I should be including on the command line? As other said, but just to confirm: --playsAgainstHuman 0 Also you have to specify --totalTime 300 if 300 is the number of seconds of the games. If not, MoGo does not care about the time left, and will just play a constant time per move, loosing by time with no other worry :). The release is designed to play against human on a server/client which supports a scoring taking into account the dead stones. On cgos you have to capture all dead stones. As for the rating, I don't know all the changes that has been done on CGOS since then, but on the old 19x19 one, the rating should be more than 2100 or 2200. Hoping this helps, Sylvain ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
Re: [computer-go] MoGoRel3_3550pps
MoGoRel3_3550pps lost its winning game for not removing dead stones. http://www.lri.fr/~teytaud/SGF/2008/01/10/8590.sgf Maybe Mogo will pass when opponent pass in 19x19. Is there no option to remove dead stones? Hiroshi Yamashita - Original Message - From: Michael Williams [EMAIL PROTECTED] To: computer-go computer-go@computer-go.org Sent: Thursday, January 10, 2008 12:35 PM Subject: [computer-go] MoGoRel3_3550pps MoGoRel3_3550pps is MoGo started like this: ./mogo --19 on a core2 duo, which is yielding about 3550 playouts per second from an empty 19x19 board. Does the current rating of 1143 seem lower than expected to anyone else? I guess the public version of MoGo was designed with a focus on 9x9 and not 19x19. Or is there something else I should be including on the command line? I know I could add pondering, but that is not going to matter much. I could add another thread, but I need that other core for other things :) ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/ ___ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
