hgm wrote:'Annoying' would describe it better than 'clever'! If it really refuses it for this reason, it is just needlessly restricting its usefulness to the user. Nothing worse than pedantic software...
There is something worse: software that crashes. An engine should reject what it cannot handle, but not more than that. For instance, if an engine has a data structure that admits up to 16 pieces per side and no more, it should reject positions with 17 pieces, otherwise, it will sooner or later crash. On the other hand, there is no reason to reject a position based on a clever retrograde analysis. Most likely, the internal data structures could handle that position. I agree with you in the latter case. However, in many cases, it is not pedantry, it is an acknowledgment of the limitations.
Miguel
I agree with both positions. I think that Abillo positions are tons of fun, though many cannot be achieved in retrograde perspective and so it is a shame to not process them (some engines do refuse). On the other hand, we cannot expect a chess position with 31 white queens and 31 black queens together with one king each to be processed successfully by a chess engine.
Out of idle curiosity, is there any chess engine that will accept and attempt to process this 'chess position'?
[d]qqqqkqqq/qqqqqqqq/qqqqqqqq/qqqqqqqq/QQQQQQQQ/QQQQQQQQ/QQQQQQQQ/QQQQKQQQ w - -
Dann Corbit wrote:
Out of idle curiosity, is there any chess engine that will accept and attempt to process this 'chess position'?
[d]qqqqkqqq/qqqqqqqq/qqqqqqqq/qqqqqqqq/QQQQQQQQ/QQQQQQQQ/QQQQQQQQ/QQQQKQQQ w - -
Jazz will do it happily, although it takes ages unless I prune SEE-equal captures and even then it's slow.
I suspect the problem are the two black bishops on d2 and b8, one of which must be the result of a promotion, but black still has all its 8 pawns on the board.
Just a guess, since that condition does not need a sophisticated retro computation.