Release of XBoard 4.9.0 soon

[Guenther]

The reason I am a bit hesitant is that I consider the {score/depth time} comments as a kind of standard (although formally they are just comments). So it should not become amenable to mis-interpretation, because the meaning of the 'time' parameter is ambiguous. So if the item following score-depth is not the time for the move itself it must be somehow distinguishable from it. E.g. by preceding it with a + sign to indicate cumulative time.

Wouldn't it be better to print the time left on the clock, btw?

Yes probably the time left would be even better especially for all other time controls.

[bnemias]

On my Orange Pi+ (arm cortex A7), xboard 4.6.x thru xboard 4.9.0 hangs when I try to load a .pgn file.

I tracked this down some by backtracking older xboard version, and 4.5.3a worked. Checking the differences, it's in GameListBuild() where it hangs after encountering BlackWins (probably all gameend types) in Myylex() the next iteration looking for (ChessMove) 0.

Not wanting to debug Myylex(), I just deleted parser.c from 4.5.3a, regenerating it during make, and copied parser.c into 4.8.0 and it worked.

Obviously this means it is using an old parser.c, but it at least appears to work.

BTW, this happens if I install from debian repository, or if I build from source.

[hgm]

Can you try it with the latest snapshot at winboard.nl?

I suspect that on the Pi 'while((c = fgetc()) != EOF)' in the ReadLine() routine does not work because 'char c' means 'unsigned char c' there.

[bnemias]

That snapshot works.

[hgm]

Yes probably the time left would be even better especially for all other time controls.

OK, I added an option -pgnTimeLeft true|false. When set it causes the time printed in the {score/depth time} comments to be the time left on the clock of the player that just moved. It will always be printed as integer seconds, and always preceded by a sign.

That snapshot works.

OK, great.

[Guenther]

I have a few questions about the 'analyze game' function in WB,
which I never had used before.
(It took me some time to find how to set the analyzing time BTW - do you
have a link to a quite recent help/manual of WB?)

Is it possible to automatically save the analyzed game/file or do I always
have to save it manually before it starts a new game?
Is it possible to analyze a whole pgn file and let all of it save automatically?
What is the meaning of both zeros before and behind the kn/s number?
Would it be possible to add the name (and perhaps hash/threads setting)
and the used analyzing time per move as a last comment (or tag)?

Code: Select all

[Event "SC Windischeschenbach 1-Regensburger Turnerschaft 1"]
[Site "?"]
[Date "2016.01.17"]
[Round "5.6"]
[White "Unterkircher, Michael"]
[Black "Simon, Guenther"]
[Result "*"]
[Board "6"]
[WhiteTeam "SC Windischeschenbach 1"]
[BlackTeam "Regensburger Turnerschaft 1"]
[PlyCount "43"]
[Annotator "2. +0.24   1... -0.25"]

1. d4 Nf6 {-0.25/16}
(0 1144 0	d5 e3 Nf6 c4 c6 Nf3 g6 Bd3 dxc4 Bxc4 Bg7 O-O a5 Nc3 O-O h3 Bf5)
2. Nf3 {+0.24/17}
(0 1116 0	c4 c6 Bf4 d6 Nc3 h6 e3 Bf5 Bg3 Nbd7 Nf3 g5 Bd3 Bxd3 Qxd3 g4 Nd2 Bg7)
2... g6 {-0.19/17}
(0 1081 0	d5 e3 Bf5 c4 c6 Bd3 Bxd3 Qxd3 Nbd7 O-O e6 b3 Be7 Nc3 h6 h3 dxc4 Qxc4 Nb6)
3. Nc3 {+0.31/17}
(0 1017 0	c4 d5 cxd5 Bg7 h3 O-O e3 a6 Bd3 Nxd5 O-O Nc6 Nc3 Nxc3 bxc3 Be6 Ng5 Bd5)
3... Bg7 {-0.23/18}
(0 1041 0	d5 Bf4 Bg7 e3 Nh5 Bg5 c6 Bh4 O-O Bd3 b5 h3 b4 Ne2 c5 g4 c4 gxh5 cxd3 cxd3)
4. e4 {+0.29/17}
(0 1072 0	e4 d5 exd5 Nxd5 Nxd5 Qxd5 Be2 O-O O-O Rd8 c3 Qc6 a4 Be6 h3 Qb6 a5 Qc6 Ng5 Bf5)
4... d6 {-0.46/17}
(0 1071 0	d5 e5 Ne4 Nxe4 dxe4 Ng5 c5 c3 cxd4 cxd4 Nc6 Bc4 Qxd4 Bxf7+ Kf8 Qb3 Qb4+ Bd2 Qxb3 Bxb3 Bxe5 O-O Nd4 Bc4 b5)
5. Bc4 {+0.49/16}
(0 1067 0	h3 O-O Be3 e6 Bd3 b6 O-O Bb7 a4 a5 b3 c5 Qe2 Nbd7 dxc5 Nxc5 Ng5 Nxd3)
5... c6 {-0.20/17}
(0 1034 0	O-O Bb3 Nc6 h3 Na5 O-O Nxb3 axb3 b6 e5 Nd7 e6 fxe6 Ng5 Nb8 d5 e5 Be3)
6. Bg5 {+0.39/17}
(0 1001 0	O-O b5 Bb3 O-O a3 a5 h3 a4 Ba2 Qc7 Be3 Nbd7 Qd2 Ba6 Rfe1 h5 b4 e6)
6... Nxe4 {-0.02/15}
(0 1003 0	h6 Bxf6 exf6 Bd3 O-O O-O Re8 b4 d5 exd5 cxd5 Re1 Rxe1+ Qxe1 a6 a3 Nc6 h3 Be6)
7. Bxf7+ {+0.39/17}
(0 1068 0	Bxf7+ Kxf7 Nxe4 Rf8 O-O Kg8 h3 h6 Be3 Kh7 Re1 Nd7 Ng3 e5 c3 a6 Qc2 d5 Nh5 e4)
7... Kxf7 {-0.39/18}
(0 1113 0	Kxf7 Nxe4 Rf8 O-O Kg8 h3 h6 Be3 Kh7 Re1 Nd7 Ng3 e5 c3 a6 Qc2 d5 Nh5 e4)
8. Nxe4 {+0.47/18}
(0 1138 0	Nxe4 Rf8 O-O Kg8 c3 h6 Bh4 Be6 Re1 Qd7 h3 Na6 b3 d5 Ned2 g5 Bg3 Kh7)
8... Re8 {-0.47/17}
(0 1028 0	Rf8 O-O Kg8 c3 h6 Bh4 Be6 Re1 Qd7 h3 Na6 b3 d5 Ned2 g5 Bg3 Kh7)
9. Qd2 {+0.63/16}
(0 1077 0	O-O Kg8 h3 h6 Be3 Be6 Qd2 g5 c3 Bd5 Qc2 Bc4 Rfe1 Nd7 Ng3 Rf8)
9... Kg8 {-0.62/16}
(0 1163 0	Kg8 O-O-O Bg4 Bh6 d5 Bxg7 dxe4 Qh6 exf3 Be5?)
10. Bh6 {+0.56/16}
(0 1162 0	h3 Bf5 Ng3 Be6 O-O-O Bd5 h4 h5 Bh6 Bf6 Ng5 e5 dxe5 Bxe5 f4!)
10... Bh8 {-0.89/15}
(0 1228 0	Nd7 Bxg7 Kxg7 O-O d5 Ng3 e5 dxe5 Nxe5 Qf4 Nxf3+!)
11. O-O {+0.93/16}
(0 1148 0	O-O Nd7 Rfe1 d5 Ng3 e5 Bg5 Qb6 c4 e4 Bh6 Qd8 Ng5 Nf6 cxd5 cxd5 h3 Bg7 Bxg7 Kxg7)
11... Nd7 {-0.65/17}
(0 1174 0	Nd7 c4 Nf6 Nc3 e5 dxe5 dxe5 Qxd8 Rxd8 Bg5 Bf5 Nxe5 Bg7 Rfe1 Re8 Rad1 Ng4 Nxg4 Bxg4!)
12. Nfg5 {+0.94/17}
(0 1151 0	Rfe1 d5 Nc3 a5 Qf4 Bf6 a4 Nf8 Qd2 Nd7 h3 e5 Bg5 exd4 Rxe8+ Qxe8 Bxf6 Nxf6 Qxd4)
12... Nf6 {-0.65/17}
(0 1154 0	Nf6 f3 d5 Nf2 e5 dxe5 Rxe5 Rae1 Rxe1 Rxe1 Qd6 b4 Bd7 Nd3 Re8 Nc5 Nh5 Rxe8+ Bxe8 Nxb7 Qe5 g4)
13. Qf4 {+0.35/18}
(0 1098 0	f3 d5 Nf2 e5 dxe5 Rxe5 Rae1 Rxe1 Rxe1 Qd6 b4 Bd7 Nd3 Re8 Nc5 b6 Nxd7 Qxd7 Rxe8+ Nxe8 Qf4 Bf6?)
13... Qd7 {+0.00/16}
(0  974 0	Qb6 Nxf6+ Bxf6 c3 Qxb2 Ne4 Bh8 Ng5 Bf6)
14. f3 {+0.68/17}
(0 1093 0	Rfe1 Qf5 Qd2 Nxe4 Nxe4 Bd7 c3 Qd5 b3 Bf5 Ng3 Bd7 Ne2 e5 c4 Qf7 h3 Bf6)
14... Qf5 {-0.35/18}
(0 1103 0	d5 Nc5 Qd6 Qe3 e5 Rae1 e4 Qb3 b6 Ncxe4 Nxe4 fxe4 Bxd4+ Kh1 Ba6 Qa4 Bc4 b3 b5!)
15. Qe3 {+0.86/16}
(0 1113 0	Qd2 Qb5 c3 Nxe4 fxe4 Bf6 Rae1 Bxg5 Bxg5 Be6 b3 a5 e5 a4 exd6 exd6 Bf6 Qh5 c4 axb3 axb3 Ra3)
15... Bd7 {-0.44/15}
(0 1068 0	Qb5 b3 Nd5 Qf2 Nf4 c4 Qb6 c5 dxc5 dxc5 Qa6 Rad1 Bd4 Rxd4 Ne2+ Kh1 Nxd4 Rd1 Ne2 a4)
16. g4 {+0.57/14}
(0 1004 0	c4 Qa5 Qf2 b6 Nd2 Bg7 Nb3 Qa6 Bxg7 Kxg7 c5 bxc5 dxc5 d5 Rfe1 e5 Nd2 Bf5)
16... Qb5 {+0.00/15}
(0  865 0	Qb5 b3 Nxe4 Nxe4 b6 Rad1 Qa5 Ng5 Qxa2 Qf4 Bf6 Ne4 Bh8 Ng5)
17. Nc3 {-0.17/17}
(0  983 0	b3 Nxe4 fxe4 Bf6 h3 c5 Nf3 cxd4 Nxd4 Qa5 a4 a6 Rad1 Rec8 c4 b5?)
17... Qb6 {+0.51/17}
(0  939 0	Nd5 Nxd5 cxd5 c3 e5 Qd2 Bf6 Rf2 Bc6 f4 e4 Re1 Qd3 Qxd3 exd3 Rd1 Bd7 f5 gxf5 gxf5 Re2 Rxd3 Rxf2)
18. Ne6 {-0.19/15}
(0 1043 0	Ne6 c5 Rfd1 cxd4 Nxd4 Rec8 Nde2 Qxe3+ Bxe3 Bg7 a3 b6 Kg2 Rab8 g5 Nh5 Nd5 Rxc2 Nxe7+)
18... Rac8 {+0.00/16}
(0 1249 0	c5 dxc5 Qxb2 Nc7 Nxg4 fxg4 Qxc3 Rad1 Bxg4 Nxa8 Qxe3+ Bxe3 Rxa8 Rb1 b6 c6 Be5 Kg2 Bf5 c7 Be4+ Kh3 Bf5+ Kg2)
19. Rad1 {+0.05/16}
(0  922 0	Rad1 Qa5 Rfe1 Nd5 Nxd5 Qxd5 b3 Qxe6 Qxe6+ Bxe6 Rxe6 Kf7 Ree1 c5 d5 c4 b4 Bc3 Bd2 Bxd2 Rxd2 c3 Rd4)
19... Nd5 {+0.36/16}
(0 1183 0	c5 Rd3 cxd4 Nxd4 e5 Ndb5 Qxe3+ Rxe3 Bxb5 Nxb5 Rxc2 Rb3 d5 Rf2 Rxf2 Kxf2 Re7 Nxa7 Rf7 Ke2 e4 h3 Bg7 Bd2 Rc7 Nb5)
20. Qe4 {-0.20/17}
(0  928 0	Nxd5 cxd5 Rf2 Qxb2 c4 Qb4 cxd5 Qa4 Rd3 Qb5 Qe4 Qb1+ Rf1 Qxa2 Rd2 Qa5 Rdd1 Rc4 Ra1 Qb6 Rfd1 Be5 Rab1 Qa6)
20... Nf6 {+0.93/15}
(0  989 0	Nc7 Nxc7 Rxc7 Qd3 Qxb2 Kg2 e5 Rb1 Qa3 Rb3 Qa5 d5 cxd5 Nxd5 Rc5 Ra3 Qb5 c4 Qxc4 Qxc4)
21. Qe3 {-0.37/16}
(0 1075 0	Qe3 c5 Rd3 cxd4 Nxd4 e5 Ndb5 Qxe3+ Rxe3 Bxb5 Nxb5 Rxc2 Rb3)
21... Nd5 {+0.22/16}
(0 1056 0	c5 dxc5 Qxb2 Rd4 b5 Rfd1 b4 Ne2 Qxa2 N2f4 Bxe6 Nxe6 dxc5 R4d2?)
22. Qe4 {-0.13/19}
(0 1030 0	Nxd5 cxd5 Rf2 Qxb2 c4 Qb4 cxd5 Qa4 Rd3 Qb5 Qe4 Qb1+ Kg2 Rc2 Rxc2 Qxc2+ Rd2 Qxe4)
{final score +1.14/17}

*

I am fiddling around with a great tool integrated in Dabbaba, but it seems
he did not update it to his latest version (I saw a post with a version 1.7).
This tool takes above WB output and gives the analyzed file below.
In the given example it could parse everything but I have seen it missing
a few lines sometimes, but I don't know yet why...
The author Jens Baek Nielsen first mentioned it in this thread below.
http://talkchess.com/forum/viewtopic.ph ... w=&start=0
He released it later in his Dababba versions. When he introduced that tool
he and other people thought this should be integrated in a GUI, but obviously it never happened.
A pity because I think it has great potential when user settings could be applied to it.
AFAIK he did not post for over a year now.

Edit: Actually I found this explicit post when he mentioned that this function could be used in WB

Winboard is - to my knowledge - the ONLY interface that lets you analyze a pgn-file with a lot of games AND produces an output that is always correct and where all relevant information is included (fx score after the last move that is used to determine if the last move is an error).

I use that information for my Dabbaba-Blunderlist.
http://talkchess.com/forum/viewtopic.ph ... undergraph

Actually I have adjusted Dabbaba (this version is not released) so it ONLY can use the output from Winboard now. Better concentrate on something that is correct. Anything else is garbage-in, garbage-out.

When my team has played a match (8 games) a sunday, my teammates send me their games as pgn-files. I just collect them in one file and let Winboard analyze them all. So easy.
After that I let Dabbaba produce the Blunderlist for all the games - also in a single run, of course.
And a few minutes after that I can mail the pgn-games and Blundergraphs to my teammates. What a nice service to have a look at all the games and know where all the errors (and what the best moves instead) are!

Winboard has another nice feature made on my request:
If you right-click on the evaluation graph, you get the score through the game shown as a line, and the dark/light bars show how big an error the moves are!!
Very nice!

HGM; perhaps I should try to request that you produce a BlunderList.txt after Winboard has analyzed one or more games!

That would be wonderful!!

Code: Select all

(...pgn header removed...)
                ----- Error --------      Score IF This line was played
1. d4           ooooo.          0.45       0.20    e4.
.....Nf6             .          0.01      -0.25    0 1144 0	d5 e3 Nf6 c4 c6 Nf3 g6 Bd3 dxc4 Bxc4 Bg
2. Nf3               .          0.00      -0.24    0 1116 0	c4 c6 Bf4 d6 Nc3 h6 e3 Bf5 Bg3 Nbd7 Nf3
2... g6              .          0.00      -0.19    0 1081 0	d5 e3 Bf5 c4 c6 Bd3 Bxd3 Qxd3 Nbd7 O-O 
3. Nc3               .          0.00      -0.31    0 1017 0	c4 d5 cxd5 Bg7 h3 O-O e3 a6 Bd3 Nxd5 O-
3... Bg7             .          0.00      -0.23    0 1041 0	d5 Bf4 Bg7 e3 Nh5 Bg5 c6 Bh4 O-O Bd3 b5
4. e4           ooo  .          0.17      -0.29    0 1072 0	e4 d5 exd5 Nxd5 Nxd5 Qxd5 Be2 O-O O-O R
4... d6              .          0.00      -0.46    0 1071 0	d5 e5 Ne4 Nxe4 dxe4 Ng5 c5 c3 cxd4 cxd4
5. Bc4               .          0.00      -0.49    0 1067 0	h3 O-O Be3 e6 Bd3 b6 O-O Bb7 a4 a5 b3 c
5... c6              .          0.00      -0.20    0 1034 0	O-O Bb3 Nc6 h3 Na5 O-O Nxb3 axb3 b6 e5 
6. Bg5               .          0.00      -0.39    0 1001 0	O-O b5 Bb3 O-O a3 a5 h3 a4 Ba2 Qc7 Be3 
6... Nxe4            .          0.00      -0.02    0 1003 0	h6 Bxf6 exf6 Bd3 O-O O-O Re8 b4 d5 exd5
7. Bxf7+             .          0.00      -0.39    0 1068 0	Bxf7+ Kxf7 Nxe4 Rf8 O-O Kg8 h3 h6 Be3 K
7... Kxf7            .          0.00      -0.39    0 1113 0	Kxf7 Nxe4 Rf8 O-O Kg8 h3 h6 Be3 Kh7 Re1
8. Nxe4              .          0.00      -0.47    0 1138 0	Nxe4 Rf8 O-O Kg8 c3 h6 Bh4 Be6 Re1 Qd7 
8... Re8             .          0.00      -0.47    0 1028 0	Rf8 O-O Kg8 c3 h6 Bh4 Be6 Re1 Qd7 h3 Na
9. Qd2               .          0.00      -0.63    0 1077 0	O-O Kg8 h3 h6 Be3 Be6 Qd2 g5 c3 Bd5 Qc2
9... Kg8        x    .          0.06      -0.62    0 1163 0	Kg8 O-O-O Bg4 Bh6 d5 Bxg7 dxe4 Qh6 exf3
10. Bh6         oooo .          0.33      -0.56    0 1162 0	h3 Bf5 Ng3 Be6 O-O-O Bd5 h4 h5 Bh6 Bf6 
10... Bh8            .          0.00      -0.89    0 1228 0	Nd7 Bxg7 Kxg7 O-O d5 Ng3 e5 dxe5 Nxe5 Q
11. O-O              .          0.00      -0.93    0 1148 0	O-O Nd7 Rfe1 d5 Ng3 e5 Bg5 Qb6 c4 e4 Bh
11... Nd7            .          0.00      -0.65    0 1174 0	Nd7 c4 Nf6 Nc3 e5 dxe5 dxe5 Qxd8 Rxd8 B
12. Nfg5             .          0.00      -0.94    0 1151 0	Rfe1 d5 Nc3 a5 Qf4 Bf6 a4 Nf8 Qd2 Nd7 h
12... Nf6       xxxx .          0.30      -0.65    0 1154 0	Nf6 f3 d5 Nf2 e5 dxe5 Rxe5 Rae1 Rxe1 Rx
13. Qf4              .          0.00      -0.35    0 1098 0	f3 d5 Nf2 e5 dxe5 Rxe5 Rae1 Rxe1 Rxe1 Q
13... Qd7            .          0.00       0.00    0  974 0	Qb6 Nxf6+ Bxf6 c3 Qxb2 Ne4 Bh8 Ng5 Bf6
14. f3               .          0.00      -0.68    0 1093 0	Rfe1 Qf5 Qd2 Nxe4 Nxe4 Bd7 c3 Qd5 b3 Bf
14... Qf5            .          0.00      -0.35    0 1103 0	d5 Nc5 Qd6 Qe3 e5 Rae1 e4 Qb3 b6 Ncxe4 
15. Qe3              .          0.00      -0.86    0 1113 0	Qd2 Qb5 c3 Nxe4 fxe4 Bf6 Rae1 Bxg5 Bxg5
15... Bd7            .          0.00      -0.44    0 1068 0	Qb5 b3 Nd5 Qf2 Nf4 c4 Qb6 c5 dxc5 dxc5 
16. g4               .          0.00      -0.57    0 1004 0	c4 Qa5 Qf2 b6 Nd2 Bg7 Nb3 Qa6 Bxg7 Kxg7
16... Qb5       xxx  .          0.17       0.00    0  865 0	Qb5 b3 Nxe4 Nxe4 b6 Rad1 Qa5 Ng5 Qxa2 Q
17. Nc3              .          0.00       0.17    0  983 0	b3 Nxe4 fxe4 Bf6 h3 c5 Nf3 cxd4 Nxd4 Qa
17... Qb6            .          0.00       0.51    0  939 0	Nd5 Nxd5 cxd5 c3 e5 Qd2 Bf6 Rf2 Bc6 f4 
18. Ne6         ooo  .          0.19       0.19    0 1043 0	Ne6 c5 Rfd1 cxd4 Nxd4 Rec8 Nde2 Qxe3+ B
18... Rac8           .          0.00       0.00    0 1249 0	c5 dxc5 Qxb2 Nc7 Nxg4 fxg4 Qxc3 Rad1 Bx
19. Rad1             .          0.00      -0.05    0  922 0	Rad1 Qa5 Rfe1 Nd5 Nxd5 Qxd5 b3 Qxe6 Qxe
19... Nd5            .          0.00       0.36    0 1183 0	c5 Rd3 cxd4 Nxd4 e5 Ndb5 Qxe3+ Rxe3 Bxb
20. Qe4              .          0.00       0.20    0  928 0	Nxd5 cxd5 Rf2 Qxb2 c4 Qb4 cxd5 Qa4 Rd3 
20... Nf6            .          0.00       0.93    0  989 0	Nc7 Nxc7 Rxc7 Qd3 Qxb2 Kg2 e5 Rb1 Qa3 R
21. Qe3         oo   .          0.15       0.37    0 1075 0	Qe3 c5 Rd3 cxd4 Nxd4 e5 Ndb5 Qxe3+ Rxe3
21... Nd5            .          0.00       0.22    0 1056 0	c5 dxc5 Qxb2 Rd4 b5 Rfd1 b4 Ne2 Qxa2 N2
22. Qe4              .          0.00       0.13    0 1030 0	Nxd5 cxd5 Rf2 Qxb2 c4 Qb4 cxd5 Qa4 Rd3 
                                           -1.14

                               White      Black
Total error                     1.29       0.54
Evaluated moves                   22         21
Error/move                     0.059      0.026
Performancerating               3009       3228
 - positional (err<0.70)        3009       3228




                               DabbabaListPgnAnalyze 1.5 / Jens Bæk Nielsen

[Guenther]

I have to admit that I did not read/nor looked up the 'What's New' section more than sporadically the last years. My excuse is, that I wasn't really into computerchess for the last 4-5 years and I never used WB installation.
http://www.gnu.org/software/xboard/

Those pages and your work are awesome and I suggest everyone to go through those 'What's New' sections and finally download that damned manual.
http://www.gnu.org/software/xboard/manual/

My question about saving the analysis remains though.

Guenther

[hgm]

I have a few questions about the 'analyze game' function in WB,
which I never had used before.
(It took me some time to find how to set the analyzing time BTW - do you
have a link to a quite recent help/manual of WB?)

Is it possible to automatically save the analyzed game/file or do I always
have to save it manually before it starts a new game?
Is it possible to analyze a whole pgn file and let all of it save automatically?

This should be possible, although perhaps not in an obvious way: when you load a PGN file when Analyze Game mode is already switched on, it will analyze all games in the file. You would need to have auto-save on to save the results. When you switch Analyze Game on when a game is already loaded it just analyzes that game starting from the current position to its end, and there is no auto-save.

What is the meaning of both zeros before and behind the kn/s number?

You mean in the Engine-Output window with all columns open? These are tablebase hits and selective depth. They are zero for engines that do not report them in their Thinking Output. UCI engines should report them through Polyglot, if the Polyglot option ShowTbHits is switched on. If they report them in UCI, that is.

Would it be possible to add the name (and perhaps hash/threads setting)
and the used analyzing time per move as a last comment (or tag)?

I guess this would be the official function of the 'Annotator' tag. Winboard_x abused this tag to print the out-of-book score, however, and I never changed that. I will think about how to solve it, but I cannot promise it will be in 4.9.0.

Edit: Actually I found this explicit post when he mentioned that this function could be used in WB

...
HGM; perhaps I should try to request that you produce a BlunderList.txt after Winboard has analyzed one or more games!

That would be wonderful!!

I am not sure how to present such a result. E.g. should it be added as a (very long) comment to the auto-saved PGN? (And displayed in the Engine-Output window when analyzing a single game?) The code in Dababba might not be directly usable, as it was made to process external PGN files, while in WinBoard it must be created from data that is already saved in internal tables. I don't feel much like trying to figure out how other people's code works, to see how it can be adapted. Furthermore GNU is pretty strict that they own the copyright of all code that goes into the official WinBoard version, so I cannot just use other peoples code even if the license allows it. A copyright-transfer form would have to be signed.

[Guenther]

I have a few questions about the 'analyze game' function in WB,
which I never had used before.
(It took me some time to find how to set the analyzing time BTW - do you
have a link to a quite recent help/manual of WB?)

Is it possible to automatically save the analyzed game/file or do I always
have to save it manually before it starts a new game?
Is it possible to analyze a whole pgn file and let all of it save automatically?

This should be possible, although perhaps not in an obvious way: when you load a PGN file when Analyze Game mode is already switched on, it will analyze all games in the file. You would need to have auto-save on to save the results. When you switch Analyze Game on when a game is already loaded it just analyzes that game starting from the current position to its end, and there is no auto-save.

You are right I found the games I thought I 'lost', because I have always autosave on.

What is the meaning of both zeros before and behind the kn/s number?

You mean in the Engine-Output window with all columns open? These are tablebase hits and selective depth. They are zero for engines that do not report them in their Thinking Output. UCI engines should report them through Polyglot, if the Polyglot option ShowTbHits is switched on. If they report them in UCI, that is.

This rings a bell in me. I believe we talked about this already once or even twice ;) I have that option set to true, but I believe I still have Polyglot 2.02, but IIRC I needed 2.03? Is there a single download?

Would it be possible to add the name (and perhaps hash/threads setting)
and the used analyzing time per move as a last comment (or tag)?

I guess this would be the official function of the 'Annotator' tag. Winboard_x abused this tag to print the out-of-book score, however, and I never changed that. I will think about how to solve it, but I cannot promise it will be in 4.9.0.

No problem. This has no big priority and I believe the Annotator tag is very useful for book cookers. I have no idea which other tag should be used for this. Other UIs or tools abuse it for average ply depth BTW.

Edit: Actually I found this explicit post when he mentioned that this function could be used in WB

...
HGM; perhaps I should try to request that you produce a BlunderList.txt after Winboard has analyzed one or more games!

That would be wonderful!!

I am not sure how to present such a result. E.g. should it be added as a (very long) comment to the auto-saved PGN? (And displayed in the Engine-Output window when analyzing a single game?) The code in Dababba might not be directly usable, as it was made to process external PGN files, while in WinBoard it must be created from data that is already saved in internal tables. I don't feel much like trying to figure out how other people's code works, to see how it can be adapted. Furthermore GNU is pretty strict that they own the copyright of all code that goes into the official WinBoard version, so I cannot just use other peoples code even if the license allows it. A copyright-transfer form would have to be signed.

This was just an idea and I can always use the original tool. A pity though that I did not care more for it when it appeared. I hope he returns and we can improve it further... if someone has his email he could send me a PM, thanks.

Guenther

[hgm]

This rings a bell in me. I believe we talked about this already once or even twice I have that option set to true, but I believe I still have Polyglot 2.02, but IIRC I needed 2.03? Is there a single download?

I checked the development history, and Polyglot 2.02 should already do this. (Not 2.01, though.) Not every UCI engine might print selective dept, however. Fruit 2.1 does print knps and seldepth, but not tablebase hits.

Polyglot 2.03 is included in the WinBoard 4.8.0 download.