Banksia GUI released

[Cornfed]

I don't understand the challenges on liches properly. Can someone explain to me, for example, how I can only play 3m + 2s (or another level) with Banksia GUI? I manually set the timer to 180s + 2s under Banksia GUI. In addition, under "challenging" also only 180s + 2s. Nevertheless, I am currently playing a game with 2m + 7s! How can that be?

Here is a live copy of the game info on Lichess:

2+7 • Gewertet • Blitz
Partie läuft

(2 + 7 • Ranked • Blitz Game runs)

I don't want to play 2m + 7s.

Quick question from someone who does not yet use Banksia:
On lichess...are you actually using the Banksia interface to play others...or using an engine via the Banksia interface to play others or other engines on lichess?
I ask because I've never liked the default lichess interface when I play there.

[AdminX]

I don't understand the challenges on liches properly. Can someone explain to me, for example, how I can only play 3m + 2s (or another level) with Banksia GUI? I manually set the timer to 180s + 2s under Banksia GUI. In addition, under "challenging" also only 180s + 2s. Nevertheless, I am currently playing a game with 2m + 7s! How can that be?

Here is a live copy of the game info on Lichess:

2+7 • Gewertet • Blitz
Partie läuft

(2 + 7 • Ranked • Blitz Game runs)

I don't want to play 2m + 7s.

Quick question from someone who does not yet use Banksia:
On lichess...are you actually using the Banksia interface to play others...or using an engine via the Banksia interface to play others or other engines on lichess?
I ask because I've never liked the default lichess interface when I play there.

Banksia GUI can only be used to play engine games online (lichess) only at the moment.

[AdminX]

I don't understand the challenges on liches properly. Can someone explain to me, for example, how I can only play 3m + 2s (or another level) with Banksia GUI? I manually set the timer to 180s + 2s under Banksia GUI. In addition, under "challenging" also only 180s + 2s. Nevertheless, I am currently playing a game with 2m + 7s! How can that be?

Here is a live copy of the game info on Lichess:

2+7 • Gewertet • Blitz
Partie läuft

(2 + 7 • Ranked • Blitz Game runs)

I don't want to play 2m + 7s.

Hello Eduard,

When you set the time in Banksia, it is only for your challenges. If someone challenges you however it will be at their time control.

[Eduard]

Thanks Ted!

Such time controls are absurd! 3 + 0, 3 + 2, 4 + 2, 5 + 0, 5 + 3 are OK. Time controls like 2 + 7 also have the disadvantage that with tablebase draws, another 50 and even 100 moves are senselessly drawn with +7 seconds / move! That's a lot of minutes. On PlayChess the GUI can automatically play endgames immediately, and on InfinityChess the server automatically agrees a draw with 5 and 6 pieces. You can't do that on Lichess. A regulation has to be found to avoid such pointless games.

Banksia GUI has another problem. I played against the account Lc0test several times today. This account has been set in such a way that Lc0 only has a few seconds on the clock at the end. Lc0 then moves very quickly, and almost always runs out of time.

Unfortunately, Banksia GUI recognizes a few tenths of a second too early when the opponent is about to run out of time. "Move Margin" doesn't help either! Banksia then stops its own engine too early!

On the Lichess homepage, however, the time continues and the opponent is waiting for my move. I helped myself today with a legal trick. I went to Lichess and continued to play by hand (as Human)! A few moves later the opponent exceeded the time and I was given the victory.
A few days ago I lost all such games. The GUI should keep its own engine running until Lichess ends the game with a sound, and not before! Banksia is currently making decisions based on its own GUI clock, and that is wrong!

[CMCanavessi]

Thanks for the report!

It is a bug when reading tournament games 960 from files and will be fixed for the next release.

Cool, glad to be able to help reporting things. Here's another one: you said that tournament info is saved whenever there's a change in it, but I still don't see it updating after games are played which would imply that if my banksia process that's currently running crashes, or the whole system crashes, I will lose all progress... look at the timestamp of the files and the current time (I left it running overnight, played around 20 games at TC 30m+5s, and still not saved)



I created the tournament at around 22:26, then because of an engine crash i stopped it, reset a game, and hit continue/resume at 22:43... hasn't saved progress since, and it's now noon of the next day.

Edit: I just hit stop, waited a bit, then checked the files and it updated. Then hit continue and it's all good, but still, that should be automatic.

[CMCanavessi]

Here is another issue regarding ponder:

Code: Select all

Monolith 2 > info depth 24 seldepth 26 currmove a7a6 currmovenumber 14
Houdini 6.03 Pro > info time 88001 nodes 143231320 nps 1627000 tbhits 0 hashfull 477
Monolith 2 > info depth 24 seldepth 26 currmove e7e5 currmovenumber 15
Houdini 6.03 Pro > info time 89002 nodes 144806163 nps 1626000 tbhits 0 hashfull 478
Monolith 2 > info depth 24 seldepth 26 currmove g7g6 currmovenumber 16
Monolith 2 > info depth 24 seldepth 26 currmove f7f5 currmovenumber 17
Houdini 6.03 Pro > info multipv 1 depth 25 seldepth 49 score cp 14 lowerbound time 89135 nodes 145021557 nps 1626000 tbhits 0 hashfull 479 pv e1f3
Houdini 6.03 Pro > info multipv 1 depth 25 seldepth 49 score cp 14 lowerbound time 89135 nodes 145021557 nps 1626000 tbhits 0 hashfull 479 pv e1f3
Houdini 6.03 Pro > info depth 26
Houdini 6.03 Pro > info currmove e1f3 currmovenumber 1
Monolith 2 > info depth 24 seldepth 26 currmove f7f6 currmovenumber 18
Monolith 2 > info depth 24 seldepth 26 currmove d8c6 currmovenumber 19
Monolith 2 > info depth 24 seldepth 26 currmove g7g5 currmovenumber 20
Monolith 2 > info depth 24 seldepth 26 score cp -14 time 89287 nodes 84739697 nps 949070 hashfull 73 tbhits 0 pv c7c5 b2b3 b7b6 e1f3 e8f6 h2h4 d8e6 d2d4 c5d4 f3d4 f8d8 d4f5 g8f8 g2g3 d7d5 c4d5 a8d5 d1e3 d5a5 c1b2 c8b7 f2f3 h7h5 b1c2 b8c7 f1c1
Monolith 2 > bestmove c7c5 ponder b2b3
Monolith 2 < position fen qbbnnrkr/pppppppp/8/8/8/8/PPPPPPPP/QBBNNRKR w HFhf - 0 1 moves c2c4 c7c5 b2b3
Monolith 2 < go ponder wtime 1680899 btime 1710710 winc 5000 binc 5000
Houdini 6.03 Pro < ponderhit
Houdini 6.03 Pro > info multipv 1 depth 25 seldepth 49 score cp 14 time 89290 nodes 145278205 nps 1627000 tbhits 0 hashfull 479 pv e1f3
Houdini 6.03 Pro > info multipv 1 depth 25 seldepth 49 score cp 14 time 89290 nodes 145278205 nps 1627000 tbhits 0 hashfull 479 pv e1f3
Houdini 6.03 Pro > bestmove e1f3 ponder b7b6
Houdini 6.03 Pro < position fen qbbnnrkr/pppppppp/8/8/8/8/PPPPPPPP/QBBNNRKR w HFhf - 0 1 moves c2c4 c7c5 e1f3 b7b6
Houdini 6.03 Pro < go ponder wtime 1680889 btime 1715710 winc 5000 binc 5000
Monolith 2 < stop
Monolith 2 > bestmove 0000
Houdini 6.03 Pro > info multipv 1 depth 16 seldepth 32 score cp 22 time 133 nodes 288387 nps 2168000 tbhits 0 pv b2b4 c5b4 a2a3 b8d6 d1e3 e7e6 a3b4 d6b4 h2h4 c8b7 d2d4 a7a5 c1b2 b7f3 e2f3 f7f5
Houdini 6.03 Pro > info multipv 1 depth 17 seldepth 34 score cp 24 time 243 nodes 506739 nps 2085000 tbhits 0 pv b2b4 c5b4 a2a3 b8d6 d1e3 e7e6 a3b4 d6b4 h2h4 c8b7 d2d4 f7f5 h4h5 a7a5 h5h6 b7f3 e2f3 f8f6 h6g7 e8g7 h1h3
Houdini 6.03 Pro > info multipv 1 depth 18 seldepth 37 score cp 25 time 852 nodes 1558139 nps 1828000 tbhits 0 pv b2b4 c5b4 a2a3 b4b3 a1c3 e7e6 c3b3 f7f5 d2d4 e8f6 d1c3 c8a6 c1d2 d8f7 b1d3 f8c8 f1c1 g8h8
Houdini 6.03 Pro > info time 1003 nodes 1801802 nps 1796000 tbhits 0 hashfull 479
Houdini 6.03 Pro > info multipv 1 depth 19 seldepth 37 score cp 21 time 1362 nodes 2400186 nps 1762000 tbhits 0 hashfull 480 pv b2b4 c5b4 a2a3 b4b3 a1c3 e7e6 c3b3 f7f5 h2h4 e8f6 h1h3 f8e8 d2d4 g8h8 d1c3 d8f7 c1g5 c8b7 g5f6
Houdini 6.03 Pro > info depth 20
Houdini 6.03 Pro > info time 2003 nodes 3558619 nps 1776000 tbhits 0 hashfull 483
Houdini 6.03 Pro > info time 3003 nodes 5168122 nps 1720000 tbhits 0 hashfull 484
Houdini 6.03 Pro > info multipv 1 depth 20 seldepth 40 score cp 18 time 3334 nodes 5736330 nps 1720000 tbhits 0 hashfull 485 pv b2b4 c5b4 a2a3 b4b3 a1c3 e7e6 c3b3 d8c6 d2d4 f7f5 c1d2 c8a6 d1e3 e8f6 d4d5 c6a5 d2a5 b6a5 d5e6 d7e6 c4c5 f6d5 e3d5
Houdini 6.03 Pro > info depth 21
Houdini 6.03 Pro > info time 4003 nodes 6866819 nps 1715000 tbhits 0 hashfull 487
Houdini 6.03 Pro > info multipv 1 depth 21 seldepth 40 score cp 18 upperbound time 4051 nodes 6949486 nps 1715000 tbhits 0 hashfull 487 pv b2b4 c5b4
Houdini 6.03 Pro > info currmove a2a3 currmovenumber 2
Houdini 6.03 Pro > info currmove b1f5 currmovenumber 3
Houdini 6.03 Pro > info currmove e2e4 currmovenumber 4
Houdini 6.03 Pro > info currmove d2d4 currmovenumber 5
Houdini 6.03 Pro > info currmove d1c3 currmovenumber 6
Houdini 6.03 Pro > info currmove d2d3 currmovenumber 7
Houdini 6.03 Pro > info currmove f1e1 currmovenumber 8
Houdini 6.03 Pro > info currmove f3e5 currmovenumber 9
Houdini 6.03 Pro > info currmove b1d3 currmovenumber 10
Houdini 6.03 Pro > info currmove g2g3 currmovenumber 11
Houdini 6.03 Pro > info currmove f3d4 currmovenumber 12
Houdini 6.03 Pro > info currmove h2h4 currmovenumber 13
Houdini 6.03 Pro > info currmove b1e4 currmovenumber 14
Houdini 6.03 Pro > info currmove b1c2 currmovenumber 15
Houdini 6.03 Pro > info currmove e2e3 currmovenumber 16
Houdini 6.03 Pro > info currmove d1e3 currmovenumber 17
Houdini 6.03 Pro > info currmove f3g5 currmovenumber 18
Houdini 6.03 Pro > info currmove h2h3 currmovenumber 19
Houdini 6.03 Pro > info currmove a2a4 currmovenumber 20
Houdini 6.03 Pro > info currmove b2b3 currmovenumber 21
Houdini 6.03 Pro > info currmove f3h4 currmovenumber 22
Houdini 6.03 Pro > info currmove f3e1 currmovenumber 23
Houdini 6.03 Pro > info currmove g2g4 currmovenumber 24
Houdini 6.03 Pro > info currmove b1g6 currmovenumber 25
Houdini 6.03 Pro > info currmove b1h7 currmovenumber 26
Houdini 6.03 Pro > info currmove b2b4 currmovenumber 1

You will see in the logs that it's Monolith's time to move, and it's thinking, while Houdini is pondering. Then Monolith stops thinking and plays a move
Monolith 2 > bestmove c7c5 ponder b2b3

So Banksia feeds it the new position and tells it to go ponder on that move b2b3
Monolith 2 < position fen qbbnnrkr/pppppppp/8/8/8/8/PPPPPPPP/QBBNNRKR w HFhf - 0 1 moves c2c4 c7c5 b2b3
Monolith 2 < go ponder wtime 1680899 btime 1710710 winc 5000 binc 5000

Then, as Houdini guessed Monolith's move, it's given the ponderhit command, so far so good
Houdini 6.03 Pro < ponderhit

Houdini quickly plays a move and Banksia gives it the new position and tells it to go ponder on a new move
Houdini 6.03 Pro > bestmove e1f3 ponder b7b6
Houdini 6.03 Pro < position fen qbbnnrkr/pppppppp/8/8/8/8/PPPPPPPP/QBBNNRKR w HFhf - 0 1 moves c2c4 c7c5 e1f3 b7b6
Houdini 6.03 Pro < go ponder wtime 1680889 btime 1715710 winc 5000 binc 5000

Then Banksia tells Monolith to stop, to which monolith answers with bestmove 0000, and then nothing else happens. Banksia never gives Monolith the correct move to search, and eventually Monolith loses on time, as it never starts thinking
Monolith 2 < stop
Monolith 2 > bestmove 0000


I've seen this happen with Ethereal and Minic also.

[CMCanavessi]

Here is another one, Banksia is playing moves that engines didn't yet send!!

Code: Select all

Ethereal 13.25 > info depth 25 currmove e1f3 currmovenumber 11
Ethereal 13.25 > info depth 25 currmove e2e3 currmovenumber 12
Ethereal 13.25 > info depth 25 currmove a2a3 currmovenumber 13
Ethereal 13.25 > info depth 25 currmove h2h4 currmovenumber 14
Ethereal 13.25 > info depth 25 currmove e1d3 currmovenumber 15
Ethereal 13.25 > info depth 25 currmove g2g4 currmovenumber 16
Ethereal 13.25 > info depth 25 currmove g2g3 currmovenumber 17
Ethereal 13.25 > info depth 25 currmove c2c3 currmovenumber 18
Ethereal 13.25 > info depth 25 currmove a2a4 currmovenumber 19
Ethereal 13.25 > info depth 25 currmove h2h3 currmovenumber 20
Ethereal 13.25 > info depth 25 seldepth 36 multipv 1 score cp 19 time 53672 nodes 41524100 nps 773000 tbhits 0 hashfull 47 pv f1g1 f8g8 h1g3 b7b6 c2c4 e7e6 b2b3 h8g6 e2e4 c8b7 d1c2 d8f6 c1b2 f6b2 a1b2 e8f6 e4e5 f6e4 c2e4 b7e4 g3e4 a8e4 d2d4 e4b7 b2e2 c7c5
Ethereal 13.25 > info depth 26 currmove f1g1 currmovenumber 1
RubiChess 2.2 < isready
RubiChess 2.2 > readyok
Ethereal 13.25 < isready
RubiChess 2.2 < isready
RubiChess 2.2 > readyok
banksia > Error: Ethereal 13.25 stalled too long or crashed. Stopped!
Ethereal 13.25 < position fen qrbbnkrn/pppppppp/8/8/8/8/PPPPPPPP/QRBBNKRN w GBgb - 0 1 moves f1g1 f8g8
Ethereal 13.25 < go ponder wtime 1686464 btime 1800000 winc 5000 binc 5000
RubiChess 2.2 < position fen qrbbnkrn/pppppppp/8/8/8/8/PPPPPPPP/QRBBNKRN w GBgb - 0 1 moves f1g1
RubiChess 2.2 < go wtime 1686464 btime 1800000 winc 5000 binc 5000
Ethereal 13.25 > readyok
Ethereal 13.25 > info depth 1 seldepth 1 multipv 1 score cp 13 time 0 nodes 5 nps 5000 tbhits 0 hashfull 0 pv h1g3
Ethereal 13.25 > info depth 2 seldepth 2 multipv 1 score cp 13 time 0 nodes 17 nps 17000 tbhits 0 hashfull 0 pv h1g3 h8g6
Ethereal 13.25 > info depth 3 seldepth 3 multipv 1 score cp 13 time 0 nodes 39 nps 39000 tbhits 0 hashfull 0 pv h1g3 h8g6 c2c4
Ethereal 13.25 > info depth 4 seldepth 5 multipv 1 score cp 21 time 0 nodes 164 nps 164000 tbhits 0 hashfull 0 pv b2b3 h8g6 e2e3 b7b6
Ethereal 13.25 > info depth 5 seldepth 6 multipv 1 score cp 12 time 0 nodes 500 nps 500000 tbhits 0 hashfull 0 pv b2b3 h8g6 c1b2 c7c5 h1g3
Ethereal 13.25 > info depth 6 seldepth 7 multipv 1 score cp 19 time 0 nodes 773 nps 773000 tbhits 0 hashfull 0 pv b2b3 h8g6 h1g3 e7e5 e2e4 d7d6
RubiChess 2.2 > info depth 1 seldepth 2 multipv 1 time 0 score cp -18 nodes 20 nps 0 tbhits 0 hashfull 0 pv f8g8
Ethereal 13.25 > info depth 7 seldepth 8 multipv 1 score cp 13 time 0 nodes 1152 nps 1152000 tbhits 0 hashfull 0 pv h1g3 h8g6 c2c4 b7b5 b2b3 b5c4 b3c4
RubiChess 2.2 > info depth 2 seldepth 3 multipv 1 time 0 score cp -14 nodes 44 nps 0 tbhits 0 hashfull 0 pv f8g8 h1g3
RubiChess 2.2 > info depth 3 seldepth 4 multipv 1 time 0 score cp 7 nodes 77 nps 0 tbhits 0 hashfull 0 pv f8g8 h1g3 h8g6
Ethereal 13.25 > info depth 8 seldepth 9 multipv 1 score cp 13 time 0 nodes 1606 nps 1606000 tbhits 0 hashfull 0 pv h1g3 h8g6 c2c4 b7b5 b2b3 b5c4 b3c4 b8b1
RubiChess 2.2 > info depth 4 seldepth 4 multipv 1 time 0 score cp 7 nodes 106 nps 0 tbhits 0 hashfull 0 pv f8g8 h1g3 h8g6
RubiChess 2.2 > info depth 5 seldepth 5 multipv 1 time 0 score cp 46 nodes 151 nps 0 tbhits 0 hashfull 0 pv f8g8 h1g3 h8g6 a2a3
RubiChess 2.2 > info depth 6 seldepth 6 multipv 1 time 1 score cp 36 nodes 395 nps 0 tbhits 0 hashfull 0 pv f8g8 h1g3 h8g6 b2b3

In this case, Banksia thought that Ethereal had crashed (it had NOT!!, just took some time while busy to answer the "isready" command) so it just took it's last move on the info string and played it, even when Ethereal was still thinking.

[AlexChess]

Banksiagui is much better in engines crashing. Arena 3.5.1 often suddenly restarts the same game again and again...

Regards, AlexChess

[AlexChess]

Hi dear phhnguyen!

Another feature request:

In the Windows version, could you make tournament crosstable cells size and backgroung color customizable like in the macOS version? There is room for 4 rounds in the default setting, but so the crosstable becomes very large and I don't find a way to resize cells, excepted importing the full Windows games.pgn on BanksiaGui for Mac (losing engines ELO column) .

Windows 10 version:



macOS version:



Thank you!
Best regards,
AlexChess
..

[phhnguyen]

A few days ago I lost all such games. The GUI should keep its own engine running until Lichess ends the game with a sound, and not before! Banksia is currently making decisions based on its own GUI clock, and that is wrong!

I have been working with Eduard on this issue, thanks Eduard!

Just inform that BSG doesn't rule the game nor running its own clocks when playing as Lichess bots. Instead, all game decisions, clocks, time left are from Lichess.