Bihasa v3.0 is released

[Ferdy]

From the readme.

Code: Select all

Bihasa v3.0
Capablanca/gothic chess variants
Readme
January 22, 2012


A. Introdcution
Bihasa is an engine that can play capablanca and gothic chess variants that is
played on board size (10x8), 10 columns by 8 rows. The creation is inspired by
H.G.Muller who actively developed the winboard/xboard GUI and he is also the 
author of Joker80 and Fairy-Max engines that are able to play some variants 
including capablanca. You need to use the winboard GUI as an interface so engine 
thinking and piece movements can be visualized well.

Changes.

Code: Select all

Bihasa v3.0 (22-Jan-2012)
1. Fixed time control handling when playing in ponder mode.
2. Fixed comment output from engine that may exit winboard gui.
3. Modify default material values. 
4. Added specific ending eval on 1 rook + 1 minor vs 1 rook, 
1 rook + 1 minor vs 1 rook + 1 pawn, 1 rook + 1 pawn vs 1 rook, 
1 rook vs 1 minor, and 1 minor vs 1 or more pawns.

There is a slight improvement based from test games at tc 40 moves in / 5 sec repeating, at 1000 games.

Code: Select all

Rank Name               Elo    +    - games score oppo. draws 
   1 Bihasa-v3.0         13   10   10  1000   53%   -13   13% 
   2 Bihasa-v2.1        -13   10   10  1000   47%    13   13% 

Code: Select all

   1 Bihasa-v3.0         13 1000.0 (534.0 : 466.0)
                            1000.0 (534.0 : 466.0) Bihasa-v2.1        -13
   2 Bihasa-v2.1        -13 1000.0 (466.0 : 534.0)
                            1000.0 (466.0 : 534.0) Bihasa-v3.0         13

Download.
https://sites.google.com/site/deuterium ... ownloads-1

[George Tsavdaris]

From the readme.

Code: Select all

Bihasa v3.0
Capablanca/gothic chess variants
Readme
January 22, 2012

[/quote]

Bihasa seems to have a serious flaw in analysis mode.
 When you setup a position and play from it and go to analysis mode, Bihasa analyses for some time, generally <10 seconds, and then stops.
I can reproduce it millions times.

Same happens when you paste a game and try to analyze it.
When you play a game(with analysis mode or with edit game mode and then press to analyze it) from the beginning, analysis mode works correctly.

This occurs in version 2 also.

[Ferdy]

From the readme.

Code: Select all

Bihasa v3.0
Capablanca/gothic chess variants
Readme
January 22, 2012

[/quote]

Bihasa seems to have a serious flaw in analysis mode.
 When you setup a position and play from it and go to analysis mode, Bihasa analyses for some time, generally <10 seconds, and then stops.
I can reproduce it millions times.

Same happens when you paste a game and try to analyze it.
When you play a game(with analysis mode or with edit game mode and then press to analyze it) from the beginning, analysis mode works correctly.

This occurs in version 2 also.[/quote]

[quote]Bihasa seems to have a serious flaw in analysis mode. 
When you setup a position and play from it and go to analysis mode, Bihasa analyses for some time, generally <10 seconds, and then stops. 
I can reproduce it millions times. [/quote]
This is what I tried in winboard.
1. run winboard selecting bihasa
2. paste a capablanca position, say white to move
3. make a move for white
4. select Machine Black
5. wait for engine to finish searching and make a move
6. select analysis mode.

I have no problem here, the engine continued searching after 10 sec.
May I know your setup?

[George Tsavdaris]

This is what I tried in winboard.
1. run winboard selecting bihasa
2. paste a capablanca position, say white to move
3. make a move for white
4. select Machine Black
5. wait for engine to finish searching and make a move
6. select analysis mode.

I have no problem here, the engine continued searching after 10 sec.
May I know your setup?

I'm using Winboard version 4.5.2012.118
Bihasa 3.0 with the command line in winboard.ini:
bihasa3.exe /fd="C:\Program Files\WinBoard-4.5.0\Bihasa3" /variant="gothic"

Default Bihasa.ini except from pondering which i turned it off.

And then after i load Bihasa on Winboard paste the following position(EDIT->PASTE position from clipboard):

r6b2/1p2kb1pp1/2pncNp2r/p2p1pP2p/1Q3B4/2P3P2P/PP2P1BPP1/R3K4R w - - 0 1

Try to analyze more than 10 seconds.

IMPORTANT note:
Only some specific positions have this behavior.
Many many positions do not make Bihasa to stop analyzing.
But the above, as also many others do. I couldn't manage to find a pattern about what might go wrong, so i can't help you more.

[Ferdy]

This is what I tried in winboard.
1. run winboard selecting bihasa
2. paste a capablanca position, say white to move
3. make a move for white
4. select Machine Black
5. wait for engine to finish searching and make a move
6. select analysis mode.

I have no problem here, the engine continued searching after 10 sec.
May I know your setup?

I'm using Winboard version 4.5.2012.118
Bihasa 3.0 with the command line in winboard.ini:
bihasa3.exe /fd="C:\Program Files\WinBoard-4.5.0\Bihasa3" /variant="gothic"

Default Bihasa.ini except from pondering which i turned it off.

And then after i load Bihasa on Winboard paste the following position(EDIT->PASTE position from clipboard):

r6b2/1p2kb1pp1/2pncNp2r/p2p1pP2p/1Q3B4/2P3P2P/PP2P1BPP1/R3K4R w - - 0 1

Try to analyze more than 10 seconds.

IMPORTANT note:
Only some specific positions have this behavior.
Many many positions do not make Bihasa to stop analyzing.
But the above, as also many others do. I couldn't manage to find a pattern about what might go wrong, so i can't help you more.

Indeed I can't analyze long on this position too. However this bug is fixed now and I am considering releasing a new version in a few days. Thanks.

[George Tsavdaris]

Indeed I can't analyze long on this position too. However this bug is fixed now and I am considering releasing a new version in a few days. Thanks.

Can i ask about the specifics of this bug? What had to do with? Because it seemed strange to analyze some positions and in others to stop.

Hope you will release it soon since i'm preparing some reviews with annotations about some 10x8 games and Bihasa is a very good partner.

[Ferdy]

There was a time check even if the mode is analyze , this is fixed by simply ignoring time check in this mode.
Probably released 1 or 2 days from now, I am implementing SEE, applied in move ordering and in qsearch bad SEE prunning,
it showed some elo improvement after initial test. I will verify this at slightly longer TC.

TC 40moves/5sec @1000 games

Code: Select all

   1 Bihasa-v3.1    73 1000.0 (623.0 : 377.0)
                       1000.0 (623.0 : 377.0) Bihasa-v3.0   -23
   2 Bihasa-v3.0   -23 2000.0 (911.0 : 1089.0)
                       1000.0 (377.0 : 623.0) Bihasa-v3.1    73
                       1000.0 (534.0 : 466.0) Bihasa-v2.1   -50
   3 Bihasa-v2.1   -50 1000.0 (466.0 : 534.0)
                       1000.0 (466.0 : 534.0) Bihasa-v3.0   -23

[Werner]

Hi Ferdinand,
did you get my mail about the question for
Deuterium v11.02.29.107 ?

[Ferdy]

Hi Ferdinand,
did you get my mail about the question for
Deuterium v11.02.29.107 ?

Just read today.

[George Tsavdaris]

Hi Ferdinand,
did you get my mail about the question for
Deuterium v11.02.29.107 ?

Just read today.

Any news about when the new release will be that has the bug fix?