Congratulations, the result suggest that you're doing something rightTonight I had a lucky stroke against crafty. (I should have played lotto;)
Crafty 17.10 vs. Yace 0.15 1.5-8.5 (3 Draws) Game/60
Hash: Crafty hash 6M, hashp 4M, Yace: 10M (I know, that for crafty 8M, 2M
would be better, but it's impossible). Crafty learn off, no endgame
tables (haven't installed them yet). Book: both programs used 2600.pgn
from Dann Corbit's site with maxply 20. AMD K6-2 300 MHz.
I don't have the expertise to judge the appended games. From looking at
the logs, round 3 was interesting. Crafty came out of the book with
+1.11 and saw the mate when it resigned.
I made a few changes to Yace, that may help for longer time controls.
I'll ask Dann to make the new version available soon.
Best wishes,
Dieter "proud" Buerssner
Yes.. I use exactly the same configurations for Blitz..when using 10 Mb..Congratulations, the result suggest that you're doing something rightTonight I had a lucky stroke against crafty. (I should have played lotto;)
Crafty 17.10 vs. Yace 0.15 1.5-8.5 (3 Draws) Game/60
Hash: Crafty hash 6M, hashp 4M, Yace: 10M (I know, that for crafty 8M, 2M
would be better, but it's impossible).).
Even though Crafty does perform better with its own book, it's a very >impressive nonetheless. There's not even any duplicate games. Looking forward >to a release of Yace 0.15 as soon as possible.
BTW, what do you plan to implement in the nearby future? That would be >interesting to hear if it's not to technical or top secret).
I'd suggest to implement resigning... although you may not need it in the future!!?BTW, what do you plan to implement in the nearby future? That would be interesting to hear if it's not to technical or top secret).
I would like to second that. It makes testing much more efficient.I'd suggest to implement resigning... although you may not need it in the future!!?BTW, what do you plan to implement in the nearby future? That would be interesting to hear if it's not to technical or top secret).
Experimental in 0.15. Put a lineI'd suggest to implement resigning
Nothing secret. After the first point, no particular order. EverythingBTW, what do you plan to implement in the nearby future? That would be
interesting to hear if it's not to technical or top secret).
When is Yace designed to resign?Experimental in 0.15. Put a lineI'd suggest to implement resigning
resign on
into yace.ini.
Sent it to Frank and Dann. I assume, it will be available soon.
Regards,
Dieter
And, because testing was only done against tactical test positions, thereBTW, what do you plan to implement in the nearby future? That would be
interesting to hear if it's not to technical or top secret).
should be many possibilities for tweaking it's strength for real games.
It is very primitive. When it found for 6 moves a score smaller -8.0.When is Yace designed to resign?
The Crafty approach is three times under -x, where x is determined by the user. I believe that is the best way to do it. Six moves under -8 is too much IMHO. Something like 3 moves with a score smaller than -6.0 is sufficient. The time factor is best suited against human players I think, but definately an interesting factor to include later on.It is very primitive. When it found for 6 moves a score smaller -8.0.When is Yace designed to resign?
Time on the clocks is not considered. Feel free to suggest a better approach.
Regards,
Dieter
Thanks, for your suggestion.The Crafty approach is three times under -x, where x is determined by the user. I believe that is the best way to do it. Six moves under -8 is too much IMHO. Something like 3 moves with a score smaller than -6.0 is sufficient. The time factor is best suited against human players I think, but definately an interesting factor to include later on.
I think the resignation mode stated is a good one for calibration runs, etc.Thanks, for your suggestion.The Crafty approach is three times under -x, where x is determined by the user. I believe that is the best way to do it. Six moves under -8 is too much IMHO. Something like 3 moves with a score smaller than -6.0 is sufficient. The time factor is best suited against human players I think, but definately an interesting factor to include later on.
I will make the score and the number of moves settable by the user. (It's only
a few lines of code). But right now, Yace is too stupid for "aggressive
resigning". You may have recognized, that it doesn't understand a draw
with the rook pawn and the wrong bishop. It's score is far off. Also,
it sometimes is very lucky, and finds an "infinete chess" (don't know
the correct English term) from a very low score.
Yes for swindling..I think the resignation mode stated is a good one for calibration runs, etc.The time factor is best suited against human players I think, but definately >>an interesting factor to include later on.The Crafty approach is three times under -x, where x is determined by the >>>user
Thanks, for your suggestion.
I will make the score and the number of moves settable by the user. (It's >>only a few lines of code). But right now, Yace is too stupid for "aggressive
resigning".
You may have recognized, that it doesn't understand a draw
with the rook pawn and the wrong bishop. It's score is far off. Also,
it sometimes is very lucky, and finds an "infinete chess" (don't know
the correct English term) from a very low score.
But in some contests, you will want to keep trying until you are dead. So it >should be configurable, ideally.
This is planned. And it would of course help in this situation.Yes,maybe you could plug in TBs? But that helps a little only..You may have recognized, that it doesn't understand a draw
with the rook pawn and the wrong bishop. It's score is far off. Also,
it sometimes is very lucky, and finds an "infinete chess" (don't know
the correct English term) from a very low score.
Perpertual check?
One question, though, I never see programs offer draws? Why?
Return to Archive (Old Parsimony Forum)
Users browsing this forum: No registered users and 22 guests