My apologies. I missed this:
http://www.schachfeld.de/threads/26593-illegale-rochade
It seems polyglot is doing the right thing after all. When I went over
the game I too (like the players) forgot that black had already moved
the king. Many PGN viewers don't seem to be catching this bug. Sorry for
the false alarm.
However the game is technically official as neither player caught this
transgression. Perhaps polyglot could use an option to allow for these
rare occurences, i.e. allow castling even if the king already moved.
Thanks.
On Mon, 19 Jan 2015 14:00:04 -0600 [email protected] wrote:
> Package: polyglot 1.4.67b-1
> Hello,
>
> It seems polyglot still has the "castling long" bug, i.e. O-O-O is
> incorrectly considered illegal. I thought this was fixed a long time
> ago. Here's an example from a compendium of TWIC1-1053:
>
> /usr/games/polyglot make-book -pgn TWIC1-1053.pgn -bin TWIC1-1053.bin
> PolyGlot 1.4.67b by Fabien Letouzey.
> inserting games ...
> allocating 1.25MB ...
> allocating 2.5MB ...
> allocating 5MB ...
> allocating 10MB ...
> allocating 20MB ...
> allocating 40MB ...
> 10000 games ...
> tellusererror POLYGLOT: book_insert(): illegal move "O-O-O" at line
> 272130, column 50,game 12600
>
> but going over this PGN
>
> [Event "Ordix Open"]
> [Site "Frankfurt GER"]
> [Date "1999.07.03"]
> [Round "2"]
> [White "Adams, Mi"]
> [Black "Stelzer, H"]
> [Result "1-0"]
> [WhiteElo "2716"]
> [BlackElo "2250"]
> [ECO "B30"]
>
> 1.e4 c5 2.Nf3 Nc6 3.Bb5 Qc7 4.O-O d6 5.d4 cxd4 6.c3 dxc3 7.Nxc3 e6 8.Bd2
> Ke7 9.Be3 Ke8 10.Bf4 Nf6 11.e5 dxe5 12.Bxe5 Qb6 13.Bd4 Qc7 14.Bxf6 gxf6
> 15.Re1 Be7 16.Qd2 Bd7 17.Rac1 h5 18.Qe3 a6 19.Ba4 O-O-O 20.a3 Kb8
21.b4 b5
> 22.Bb3 Bd6 23.Qe2 Qb7 24.Ne4 Be7 25.Qe3 Ne5 26.Nxe5 fxe5 27.Nc5 Bxc5 28.
> Qxe5+ Ka8 29.Rxc5 Rhg8 30.g3 Bc6 31.Bc2 Rd5 32.Rxd5 Bxd5 33.Be4 Bxe4 34.
> Rxe4 Rd8 35.Re1 Qf3 36.h4 Rd3 37.Rc1 Rd1+ 38.Rxd1 Qxd1+ 39.Kg2 Kb7 40.Qc5
> Qd7 41.Qxh5 f5 42.Qf3+ Kc7 43.h5 e5 44.Qc3+ 1-0
>
> reveals that castling long is perfectly legal. What's the problem?
>
> Vielen Dank.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
