Page 1 of 1

Bihasa 4.3.3

Posted: Tue Dec 27, 2016 8:13 am
by Ferdy
An engine that can play capablanca and gothic chess variants.

* Fixed time per move
* Modify pruning
* Modify evaluation
* Remove dependency on ini file
* Added some eval options that can be set by the user

https://sites.google.com/view/capablanca/engines/bihasa

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 12:45 pm
by George Tsavdaris
Ferdy wrote:An engine that can play capablanca and gothic chess variants.

* Fixed time per move
* Modify pruning
* Modify evaluation
* Remove dependency on ini file
* Added some eval options that can be set by the user

https://sites.google.com/view/capablanca/engines/bihasa
But without and *.ini and without a README, how to set different parameters/personalities? :?

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 1:22 pm
by hgm
I think the idea is that you use the Engine Settings dialog to set the parameters, and then have the GUI save them, so that each time the engine is loaded it will automatically run with the modified settings.

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 1:27 pm
by Guenther
George Tsavdaris wrote:
Ferdy wrote:An engine that can play capablanca and gothic chess variants.

* Fixed time per move
* Modify pruning
* Modify evaluation
* Remove dependency on ini file
* Added some eval options that can be set by the user

https://sites.google.com/view/capablanca/engines/bihasa
But without and *.ini and without a README, how to set different parameters/personalities? :?
George, I thought Ferdinand already had answered this in the original thread about your problems?

http://talkchess.com/forum/viewtopic.php?t=62611

Ok, I think I understand now, you miss more or less a readme file for knowing what settings can be changed at all?
Ferdinand described how you can see them by starting from console and feeding a few commands to get them.

You can also load it in WB and just look at the settings.
There is a menu for this, since ... I don't know when - several years at least.

Image

For CuteChess Ferdinand has already described how you change the engines.json file with the desired settings...

Edit: I forgot that you also directly can see and change the engine options in CuteChess under Engines/Advanced options or similar...

Image

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 1:44 pm
by Ferdy
George Tsavdaris wrote:
Ferdy wrote:An engine that can play capablanca and gothic chess variants.

* Fixed time per move
* Modify pruning
* Modify evaluation
* Remove dependency on ini file
* Added some eval options that can be set by the user

https://sites.google.com/view/capablanca/engines/bihasa
But without and *.ini and without a README, how to set different parameters/personalities? :?
Run in console and type xboard then protover to see its features.

Code: Select all

xboard
feature done=0

protover
feature ping=1 time=1 setboard=1 name=1 colors=1 debug=1
feature draw=0 sigint=0 sigterm=0 reuse=0 analyze=1 ics=1
feature variants="capablanca,gothic"
feature option="MultiPV -spin 1 1 300"
feature memory=1
feature myname="Bihasa v4.3.3"
feature option="Resign -check 0"
feature option="ResignScore -spin -1200 -30000 30000"
feature option="Ponder -check 1"
feature option="Book -check 0"
feature option="ContemptValue -spin 0 -1000 1000"
feature option="PawnValueOp -spin 75 0 1000"
feature option="PawnValueEn -spin 100 0 1000"
feature option="KnightValueOp -spin 310 0 1000"
feature option="KnightValueEn -spin 310 0 1000"
feature option="BishopValueOp -spin 350 0 1000"
feature option="BishopValueEn -spin 350 0 1000"
feature option="RookValueOp -spin 530 0 1000"
feature option="RookValueEn -spin 530 0 1000"
feature option="ArchBishopValueOp -spin 870 0 1500"
feature option="ArchBishopValueEn -spin 870 0 1500"
feature option="ChancellorValueOp -spin 990 0 1500"
feature option="ChancellorValueEn -spin 990 0 1500"
feature option="QueenValueOp -spin 1040 0 1500"
feature option="QueenValueEn -spin 1040 0 1500"
feature option="MobilityWeight -spin 100 0 1000"
feature option="ArchBishopNearOppKingWeight -spin 100 0 1000"
feature option="ChancellorNearOppKingWeight -spin 100 0 1000"
feature option="QueenNearOppKingWeight -spin 100 0 1000"
feature done=1
In WB 4.8 you can modify the winboard.ini file and the command line for this engine, for example, to change the value of pawn in op and en.

Code: Select all

-firstOptions "PawnValueOp=90,PawnValueEn=120"
In WB 4.9.xxxxxx, options can be saved permanently by going to the engine settings, modify its values and press make persistent button.

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 1:49 pm
by Ferdy
George Tsavdaris wrote:
Ferdy wrote:An engine that can play capablanca and gothic chess variants.

* Fixed time per move
* Modify pruning
* Modify evaluation
* Remove dependency on ini file
* Added some eval options that can be set by the user

https://sites.google.com/view/capablanca/engines/bihasa
But without and *.ini and without a README, how to set different parameters/personalities? :?
Run in console and type xboard then protover to see its features.

Code: Select all

xboard
feature done=0

protover
feature ping=1 time=1 setboard=1 name=1 colors=1 debug=1
feature draw=0 sigint=0 sigterm=0 reuse=0 analyze=1 ics=1
feature variants="capablanca,gothic"
feature option="MultiPV -spin 1 1 300"
feature memory=1
feature myname="Bihasa v4.3.3"
feature option="Resign -check 0"
feature option="ResignScore -spin -1200 -30000 30000"
feature option="Ponder -check 1"
feature option="Book -check 0"
feature option="ContemptValue -spin 0 -1000 1000"
feature option="PawnValueOp -spin 75 0 1000"
feature option="PawnValueEn -spin 100 0 1000"
feature option="KnightValueOp -spin 310 0 1000"
feature option="KnightValueEn -spin 310 0 1000"
feature option="BishopValueOp -spin 350 0 1000"
feature option="BishopValueEn -spin 350 0 1000"
feature option="RookValueOp -spin 530 0 1000"
feature option="RookValueEn -spin 530 0 1000"
feature option="ArchBishopValueOp -spin 870 0 1500"
feature option="ArchBishopValueEn -spin 870 0 1500"
feature option="ChancellorValueOp -spin 990 0 1500"
feature option="ChancellorValueEn -spin 990 0 1500"
feature option="QueenValueOp -spin 1040 0 1500"
feature option="QueenValueEn -spin 1040 0 1500"
feature option="MobilityWeight -spin 100 0 1000"
feature option="ArchBishopNearOppKingWeight -spin 100 0 1000"
feature option="ChancellorNearOppKingWeight -spin 100 0 1000"
feature option="QueenNearOppKingWeight -spin 100 0 1000"
feature done=1
In WB 4.8 you can modify the winboard.ini file and the command line for this engine, for example, to change the value of pawn in op and en.

Code: Select all

-firstOptions "PawnValueOp=90,PawnValueEn=120"
In WB 4.9.xxxxxx, options can be saved permanently by going to the engine settings, modify its values and press make persistent button.

Re: Bihasa 4.3.3

Posted: Wed Dec 28, 2016 3:37 pm
by George Tsavdaris
Guenther wrote: George, I thought Ferdinand already had answered this in the original thread about your problems?
I missed that, but in the general case anyone doesn't read this forum how could he set the parameters in cutechess-cli for example? :D

Ok, I think I understand now, you miss more or less a readme file for knowing what settings can be changed at all?
Well i see the settings inside Cutechess or Winboard and i was too dumb/fast to ask anyway. :D
With an *.ini file it was more convenient but anyway this works too so....
Ferdinand described how you can see them by starting from console and feeding a few commands to get them.

For CuteChess Ferdinand has already described how you change the engines.json file with the desired settings...
Thank god there is not need to do that manually. :D

Re: Bihasa 4.3.3

Posted: Fri Jan 13, 2017 12:30 pm
by defrag71
Thanks for keeping this engine updated, still the best playing 10x8 with much new parameters.
In my tests though, previous version 3.2 remains the strongest.

Re: Bihasa 4.3.3

Posted: Sun Jan 15, 2017 12:48 pm
by Ferdy
defrag71 wrote:Thanks for keeping this engine updated, still the best playing 10x8 with much new parameters.
In my tests though, previous version 3.2 remains the strongest.
Thanks for the info, I have not seriously tested it vs 3.2 before the release but tested it vs other engines. There was a bug that I unfortunately introduced in my pruning/reduction modification. I will fix this once I get the time.