Simple fortress detection, engines fail

Discussion of anything and everything relating to chess playing software and machines.

Moderator: Ras

lech
Posts: 1175
Joined: Sun Feb 14, 2010 10:02 pm

Re: Simple fortress detection, engines fail

Post by lech »

bob wrote:
kgburcham wrote:
bob wrote:
Houdini wrote:If you say "fortress" I reply "FiftyMoveDistance=12" and get the following result with Houdini 2.0c:

Code: Select all

8/8/8/5Bp1/7k/7P/4pPK1/8 b - -
Engine: Houdini 2.0c x64 (2048 MB)
17/38  0:01   -4.52    1...g4 2.Bxg4 e1Q 3.Bf3 Kg5 4.Bg4 Kf4 
                       5.Bf3 Qe7 6.Bg4 Ke5 7.Kg3 Kd4 8.Kf3 Kc3 
                       9.Bf5 Kd2 10.Kg4 Ke1 11.f4 Kf2 
                       12.Bg6 Qe2+ 13.Kh4 Kg2 14.f5 Qe4+ (8.330.990) 8175
The obvious question, why not run with that set to 12 all the time? Tuning a parameter to a specific position is not exactly solving the position as one would generally do. Setting the counter to 12 would be quite harmful overall, which makes it useless here as well.
Robert Hyatt
If you decide to go commercial with Crafty and I have to pay $125 for the mp version, would you please include this same option that Robert Houdart has included? It offers some variety and fun to the program. With the fifty move option in Houdini, I can use it to solve test positions and then switch right back to the #1 world default settings.
thanks in advance
kgburcham
Why stop there? No mates longer than 10? No captures deeper than 20 plies? Pawn push every 16 plies or draw?

The game DOES have real rules...
Robert's Houdini is without rules. Hi is dodger, juggler and Lucky. :lol:
Maybe, I can't be friendly, but let me be useful.