A complete 2000 lines of code engine

Discussion of anything and everything relating to chess playing software and machines.

Moderators: hgm, Harvey Williamson, bob

Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Fri May 03, 2019 1:50 pm

Ok thanks, I'll fix that !

But I'm not sure what wouldn't work following protocol 1 spec ?

User avatar
Werner Taelemans
Posts: 102
Joined: Mon Feb 03, 2014 10:57 am
Location: Belgium
Contact:

Re: A complete 2000 lines of code engine

Post by Werner Taelemans » Fri May 03, 2019 2:38 pm

xr_a_y wrote:
Fri May 03, 2019 1:50 pm
But I'm not sure what wouldn't work following protocol 1 spec ?
Probably:

version 1:
MOVE

version 2:
usermove MOVE

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Fri May 03, 2019 3:03 pm

ok indeed ....

I pushed a dirty patch ... https://github.com/tryingsomestuff/Mini ... 67fa10245c

I'll have to clean it up better some day.

Thanks again.

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Sat May 11, 2019 11:22 am

Recent (too small) progress

Code: Select all

Rank Name                          Elo     +/-   Games   Score   Draws
   1 minic_0.55_linux_x64_avx2_bmi2      53      13    1546   57.5%   41.7%
   2 minic_0.53_linux_x64_avx2_bmi2      39      13    1547   55.7%   40.9%
   3 minic_0.50_linux_x64_avx2_bmi2      27      13    1547   53.9%   40.7%
   4 minic_0.47_linux_x64_avx2_bmi2      -7      14    1547   49.0%   37.8%
   5 minic_0.43_linux_x64_see4.2    -116      14    1547   33.9%   36.5%

3867 of 10000 games finished.

Raphexon
Posts: 83
Joined: Sun Mar 17, 2019 11:00 am
Full name: Henk Drost

Re: A complete 2000 lines of code engine

Post by Raphexon » Sat May 11, 2019 2:23 pm

Still awesome that even with so few lines, it still would have been the strongest engine back in the late 90s/early 2000s.

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Sat May 11, 2019 2:59 pm

Well, I must admit this is just developing for fun (re)using what pioneers already tested back then and what is already working well on top engines. The real great part in the process is learning about chess, chess programming, re-discovering things by myself and sharing with the great chess programming community. I am still amazed about how kind everybody is here, spending time sharing, testing, searching and teaching.

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Thu May 23, 2019 6:21 pm

Minic 0.60 will be released tonight with +50elo thanks to TT use inside qsearch :lol:
Attachments
Capture.PNG
Capture.PNG (3.28 KiB) Viewed 2359 times

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Fri May 24, 2019 4:39 am

Minic is now better than fruit2.1 :D

Code: Select all

Score of fruit_21 vs Minic: 33 - 65 - 34 [0.379]
Elo difference: -85.94 +/- 52.46

User avatar
silentshark
Posts: 231
Joined: Sat Mar 27, 2010 6:15 pm
Contact:

Re: A complete 2000 lines of code engine

Post by silentshark » Fri May 24, 2019 7:18 am

xr_a_y wrote:
Thu May 23, 2019 6:21 pm
Minic 0.60 will be released tonight with +50elo thanks to TT use inside qsearch :lol:
A +50 elo tweak is always nice, well done.

For my engine, probing the TT table in qsearch (but not storing in TT in qsearch) was the best. How about for you?

User avatar
xr_a_y
Posts: 704
Joined: Sat Nov 25, 2017 1:28 pm
Location: France

Re: A complete 2000 lines of code engine

Post by xr_a_y » Fri May 24, 2019 7:51 am

Using TT in qsearch was useless in Minic with a very simple eval. It became good to store and probe in qsearch when eval started to be the bottleneck.

Just probing TT in qsearch seems strange to me, this will only be good when in check I guess... I store things in qsearch with depth=-1. I guess the important thing is to get eval score for free, I don't expect a lot from TT cut-off.

Post Reply