Looking for someone to test Zeta v099l on RTX 2080 TI, or similar, gpu

[pferd]

BTW is there a faster way to scroll through older/newer commits in github, it has bothered me forever to be unable to see them all at once
in a list and instead have to go through dozens of pages with max 34 entries.

You could clone the git repository and browse it with some sort of 3rd party software like qgit.

[smatovic]

Hello Srdja, I have finally added Zeta to the XB/UCI chronology. (Zeta Dva was always there ofc)
Note that it originally was designed for cpu only programs (gpu programs did not exist in the beginning anyway).
Finally I have added another column for 'H Type' (Hardware Type = CPU/GPU).

When was the first release of a Zeta version (binary) working on some ordinary GPU?

Heyho Guenther,

Zeta development started in 2010, the first official code release on GitHub was
version 0915 on July 13, 2011, v0915 was the first version able to play chess
on a GPU (Nvidia 8800 GT).

Not sure about binaries, I guess the first binary release was v097x on Jan 17, 2013.

I am asking because you have hidden/deleted all previous versions before 0.99k and it was probably during my long hiatus between 2011-2015.
(I can still find some of them with working downloads from the source commits directly though,
but I don't know if they would run or if you want them to be acknowledged in the chronology.
Edit: It seems even github starts just in 2016 with 0.98g?)

I deleted all the previous versions cos they were all buggy, even v098 has some
flaws. 099 ist the first line of versions that is somehow stable and tested
with different GUIs and GPUs on Windows and Linux OS.

In the Zeta changelog you will find a rough timeline of Zeta milestones:

https://github.com/smatovic/Zeta/blob/master/changelog

I am not sure if a complete chronology makes sense, cos Zeta is actual an
experimental chess engine project, before version 097 the engine played really
poor chess and the interface was buggy.

On CPW I mentioned some data about version 097, 098 and 099

https://www.chessprogramming.org/Zeta

If you like, I could figure out when I released which version with specific
features, but archive.org, who archived my original blog, zeta-chess.blogspot.com,
is currently down, so I can not look up atm.

BTW is there a faster way to scroll through older/newer commits in github, it has bothered me forever to be unable to see them all at once
in a list and instead have to go through dozens of pages with max 34 entries.

Thanks in advance.

A forum search for 'Zeta release' goes back until 2011:
search.php?st=0&sk=t&sd=d&sr=posts&keyw ... ta+release

You could download/clone the whole .git repo and view the log file directly,
I use command line tools, but there are some GUIs for sure.

--
Srdja

PS: my Firefox browser (Ubuntu 18.04 64 bit) is somehow not able to show your chronology sheet...

[Guenther]

PS: my Firefox browser (Ubuntu 18.04 64 bit) is somehow not able to show your chronology sheet...

Did you see two scrollbars at the right side? If yes, you need to scroll down both two get the tabs for all sheets.
(I implemented it as an iframe, because I wanted to have always the same link from my main page and planned to change the google link
regularily after major updates. Due to size of the tables it always needed two scroll bars at least even on my 24'' monitor)

It is also mentioned in the text above:

Code: Select all

This is the new RWBC XB/UCI chronology

For viewing all sheets, you might need to scroll down also the outer bar, depending on your screen size!

You can also use the current direct link (may change in the future...) and try if you can access this way:
https://docs.google.com/spreadsheets/d/ ... 9H2VGT1bLQ

If you have some other problem for viewing could you create a screenshot or describe the problem?

[Guenther]

Hello Srdja, I have finally added Zeta to the XB/UCI chronology. (Zeta Dva was always there ofc)
Note that it originally was designed for cpu only programs (gpu programs did not exist in the beginning anyway).
Finally I have added another column for 'H Type' (Hardware Type = CPU/GPU).

When was the first release of a Zeta version (binary) working on some ordinary GPU?

Heyho Guenther,

Zeta development started in 2010, the first official code release on GitHub was
version 0915 on July 13, 2011, v0915 was the first version able to play chess
on a GPU (Nvidia 8800 GT).

Not sure about binaries, I guess the first binary release was v097x on Jan 17, 2013.

I am asking because you have hidden/deleted all previous versions before 0.99k and it was probably during my long hiatus between 2011-2015.
(I can still find some of them with working downloads from the source commits directly though,
but I don't know if they would run or if you want them to be acknowledged in the chronology.
Edit: It seems even github starts just in 2016 with 0.98g?)

I deleted all the previous versions cos they were all buggy, even v098 has some
flaws. 099 ist the first line of versions that is somehow stable and tested
with different GUIs and GPUs on Windows and Linux OS.

In the Zeta changelog you will find a rough timeline of Zeta milestones:

https://github.com/smatovic/Zeta/blob/master/changelog

I am not sure if a complete chronology makes sense, cos Zeta is actual an
experimental chess engine project, before version 097 the engine played really
poor chess and the interface was buggy.

On CPW I mentioned some data about version 097, 098 and 099

https://www.chessprogramming.org/Zeta

If you like, I could figure out when I released which version with specific
features, but archive.org, who archived my original blog, zeta-chess.blogspot.com,
is currently down, so I can not look up atm.

...

Thanks for the detailed answer Srdja. From the above I guess I will set up 0.99a or 0.99b as the first more or less stable
working version and as starting point in the chronology? I will figure out the date then.
BTW will it run on my old Nvidia GT 710?

[Guenther]

BTW is there a faster way to scroll through older/newer commits in github, it has bothered me forever to be unable to see them all at once
in a list and instead have to go through dozens of pages with max 34 entries.

You could clone the git repository and browse it with some sort of 3rd party software like qgit.

Thanks for the hint!

[smatovic]

PS: my Firefox browser (Ubuntu 18.04 64 bit) is somehow not able to show your chronology sheet...

Did you see two scrollbars at the right side? If yes, you need to scroll down both two get the tabs for all sheets.
(I implemented it as an iframe, because I wanted to have always the same link from my main page and planned to change the google link
regularily after major updates. Due to size of the tables it always needed two scroll bars at least even on my 24'' monitor)

It is also mentioned in the text above:

Code: Select all

This is the new RWBC XB/UCI chronology

For viewing all sheets, you might need to scroll down also the outer bar, depending on your screen size!

You can also use the current direct link (may change in the future...) and try if you can access this way:
https://docs.google.com/spreadsheets/d/ ... 9H2VGT1bLQ

If you have some other problem for viewing could you create a screenshot or describe the problem?

Attached a screen shot. When I scroll both bars down, I still see no sheets to select.

The direct google link works fine.

A remark to my entry, though born and living in Germany, I am actual Montenegrin citizen.

--
Srdja

[smatovic]

Thanks for the detailed answer Srdja. From the above I guess I will set up 0.99a or 0.99b as the first more or less stable
working version and as starting point in the chronology? I will figure out the date then.

Version 099 is fine for me.

BTW will it run on my old Nvidia GT 710?

Yes, if you are running 64 bit Windows. It may reach 1700 CCRL Elo on your device.

Zeta should run on all OpenCL 1.x capable GPUs (>= 2008),
but you should consider to read the README file,
there may be some issues with gpu timeouts....

--
Srdja

[Guenther]

PS: my Firefox browser (Ubuntu 18.04 64 bit) is somehow not able to show your chronology sheet...

Did you see two scrollbars at the right side? If yes, you need to scroll down both two get the tabs for all sheets.
(I implemented it as an iframe, because I wanted to have always the same link from my main page and planned to change the google link
regularily after major updates. Due to size of the tables it always needed two scroll bars at least even on my 24'' monitor)

It is also mentioned in the text above:

Code: Select all

This is the new RWBC XB/UCI chronology

For viewing all sheets, you might need to scroll down also the outer bar, depending on your screen size!

You can also use the current direct link (may change in the future...) and try if you can access this way:
https://docs.google.com/spreadsheets/d/ ... 9H2VGT1bLQ

If you have some other problem for viewing could you create a screenshot or describe the problem?

Attached a screen shot. When I scroll both bars down, I still see no sheets to select.

The direct google link works fine.

This is not nice - at least the direct link works - I will add it as a workaround on the chronology page.

A remark to my entry, though born and living in Germany, I am actual Montenegrin citizen.

If you like me to change the country entry to Montenegro it is up to you - I think that flag is still missing :)

[smatovic]

If you like me to change the country entry to Montenegro it is up to you - I think that flag is still missing

Okay, then go for it

--
Srdja

[Dokterchen]

Hello Srdja,

I have a RTX 2070 and maybe I did someting wrong but Zeta crashed during the benchmark:

Code: Select all

[2019-06-25 12:54:10] zeta.exe -l --dl 
[2019-06-25 12:54:10] #> ### Query the OpenCL Devices on Host...
[2019-06-25 12:54:10] #>
[2019-06-25 12:54:10] #> Number of OpenCL Platforms found: 1 
[2019-06-25 12:54:10] #>
[2019-06-25 12:54:10] #> platform_id:0, device_id: 0, Vendor: NVIDIA Corporation, Device name: GeForce RTX 2070 
[2019-06-25 12:54:10] #>
[2019-06-25 12:54:32] zeta.exe -l -p 0 -d 0 --guessconfigx 
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> ### Query the OpenCL Platforms on Host...
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> Number of OpenCL Platforms found: 1 
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> Platform: 0,  Vendor:  NVIDIA Corporation 
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> ### Query the OpenCL Devices on Platform...
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> Number of OpenCL Devices found: 1 
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> ### Query and check the OpenCL Device...
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> Device: 0, Device name: GeForce RTX 2070 
[2019-06-25 12:54:32] #>
[2019-06-25 12:54:32] #> OK, Device Endianness is little
[2019-06-25 12:54:32] #> OK, CL_DEVICE_MAX_COMPUTE_UNITS: 36 
[2019-06-25 12:54:32] #> OK, CL_DEVICE_MAX_MEM_ALLOC_SIZE: 2048 MB >= 128 MB 
[2019-06-25 12:54:32] #> OK, CL_DEVICE_GLOBAL_MEM_SIZE: 8192 MB
[2019-06-25 12:54:32] #> OK, Device extension cl_khr_global_int32_base_atomics is supported.
[2019-06-25 12:54:32] #> OK, Device extension cl_khr_local_int32_base_atomics is supported.
[2019-06-25 12:54:32] #> OK: Device extension cl_khr_int64_extended_atomics not supported.
[2019-06-25 12:54:32] #> OK, CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024 >= 64
[2019-06-25 12:54:32] #> OK, CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3 >= 3
[2019-06-25 12:54:32] #> OK, CL_DEVICE_MAX_WORK_ITEM_SIZES [3]: 64 >= 64
[2019-06-25 12:54:32] #> OK, CL_DEVICE_AVAILABLE: CL_TRUE 
[2019-06-25 12:54:32] #
[2019-06-25 12:54:32] #> ### Running NPS-Benchmark for minimal config on device,
[2019-06-25 12:54:32] #> ### this can last about 4 seconds... 
[2019-06-25 12:54:32] #> ### threadsX: 1 
[2019-06-25 12:54:32] #> ### threadsY: 1 
[2019-06-25 12:54:32] #> ### total work-groups: 1 
[2019-06-25 12:54:32] #> ### total threads: 64 
[2019-06-25 12:54:32] #
[2019-06-25 12:54:33] #fen: rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
[2019-06-25 12:54:33] ###ABCDEFGH###
[2019-06-25 12:54:33] #8 rnbqkbnr
[2019-06-25 12:54:33] #7 pppppppp
[2019-06-25 12:54:33] #6 --------
[2019-06-25 12:54:33] #5 --------
[2019-06-25 12:54:33] #4 --------
[2019-06-25 12:54:33] #3 --------
[2019-06-25 12:54:33] #2 PPPPPPPP
[2019-06-25 12:54:33] #1 RNBQKBNR
[2019-06-25 12:54:33] ###ABCDEFGH###
[2019-06-25 12:54:34] depth: 1, nodes 20, nps: 34, time: 0.579000 sec, score: 60  move b1c3
[2019-06-25 12:54:34] depth: 2, nodes 59, nps: 3470, time: 0.017000 sec, score: 0  move b1c3
[2019-06-25 12:54:34] depth: 3, nodes 525, nps: 525000, time: 0.001000 sec, score: 60  move b1c3
[2019-06-25 12:54:34] depth: 4, nodes 618, nps: 36352, time: 0.017000 sec, score: 0  move b1c3
[2019-06-25 12:54:34] depth: 5, nodes 2430, nps: 75937, time: 0.032000 sec, score: 27  move b1c3
[2019-06-25 12:54:34] depth: 6, nodes 16392, nps: 86730, time: 0.189000 sec, score: 0  move b1c3
[2019-06-25 12:54:34] depth: 7, nodes 20778, nps: 94876, time: 0.219000 sec, score: 22  move b1c3
[2019-06-25 12:54:35] depth: 8, nodes 83106, nps: 90039, time: 0.923000 sec, score: 12  move b1c3
[2019-06-25 12:54:38] depth: 9, nodes 254151, nps: 92384, time: 2.751000 sec, score: 16  move b1c3
[2019-06-25 12:54:38] #
[2019-06-25 12:54:38] #> ### Running NPS-Benchmark for best config,
[2019-06-25 12:54:38] #> ### this can last about some minutes... 
[2019-06-25 12:54:38] #
[2019-06-25 12:54:38] #
[2019-06-25 12:54:38] #> ### Running NPS-Benchmark for threadsY on device,
[2019-06-25 12:54:38] #> ### this can last about 4 seconds... 
[2019-06-25 12:54:38] #> ### threadsX: 36 
[2019-06-25 12:54:38] #> ### threadsY: 1 
[2019-06-25 12:54:38] #> ### total work-groups: 36 
[2019-06-25 12:54:38] #> ### total threads: 2304 
[2019-06-25 12:54:38] #
[2019-06-25 12:54:39] #fen: rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
[2019-06-25 12:54:39] ###ABCDEFGH###
[2019-06-25 12:54:39] #8 rnbqkbnr
[2019-06-25 12:54:39] #7 pppppppp
[2019-06-25 12:54:39] #6 --------
[2019-06-25 12:54:39] #5 --------
[2019-06-25 12:54:39] #4 --------
[2019-06-25 12:54:39] #3 --------
[2019-06-25 12:54:39] #2 PPPPPPPP
[2019-06-25 12:54:39] #1 RNBQKBNR
[2019-06-25 12:54:39] ###ABCDEFGH###
[2019-06-25 12:54:40] depth: 1, nodes 720, nps: 1288, time: 0.559000 sec, score: 60  move b1c3
[2019-06-25 12:54:40] depth: 2, nodes 2076, nps: 230666, time: 0.009000 sec, score: 0  move b1c3
[2019-06-25 12:54:40] depth: 3, nodes 4220, nps: 4220000, time: 0.001000 sec, score: 60  move b1c3
[2019-06-25 12:54:40] depth: 4, nodes 6122, nps: 556545, time: 0.011000 sec, score: 0  move b1c3
[2019-06-25 12:54:40] depth: 5, nodes 11996, nps: 1332888, time: 0.009000 sec, score: 27  move b1c3
[2019-06-25 12:54:40] depth: 6, nodes 54418, nps: 6046444, time: 0.009000 sec, score: 0  move b1c3
[2019-06-25 12:54:40] depth: 7, nodes 70772, nps: 4423250, time: 0.016000 sec, score: 22  move b1c3
[2019-06-25 12:54:40] depth: 8, nodes 286950, nps: 3336627, time: 0.086000 sec, score: 12  move b1c3
[2019-06-25 12:54:40] depth: 9, nodes 917200, nps: 3698387, time: 0.248000 sec, score: 18  move b1c3
[2019-06-25 12:54:42] depth: 10, nodes 4350058, nps: 3730753, time: 1.166000 sec, score: 15  move b1c3
[2019-06-25 12:54:42] #
[2019-06-25 12:54:42] #> ### Running NPS-Benchmark for threadsY on device,
[2019-06-25 12:54:42] #> ### this can last about 4 seconds... 
[2019-06-25 12:54:42] #> ### threadsX: 36 
[2019-06-25 12:54:42] #> ### threadsY: 2 
[2019-06-25 12:54:42] #> ### total work-groups: 72 
[2019-06-25 12:54:42] #> ### total threads: 4608 
[2019-06-25 12:54:42] #
[2019-06-25 12:54:43] #fen: rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
[2019-06-25 12:54:43] ###ABCDEFGH###
[2019-06-25 12:54:43] #8 rnbqkbnr
[2019-06-25 12:54:43] #7 pppppppp
[2019-06-25 12:54:43] #6 --------
[2019-06-25 12:54:43] #5 --------
[2019-06-25 12:54:43] #4 --------
[2019-06-25 12:54:43] #3 --------
[2019-06-25 12:54:43] #2 PPPPPPPP
[2019-06-25 12:54:43] #1 RNBQKBNR
[2019-06-25 12:54:43] ###ABCDEFGH###
[2019-06-25 12:54:44] depth: 1, nodes 1440, nps: 2748, time: 0.524000 sec, score: 60  move b1c3
[2019-06-25 12:54:44] depth: 2, nodes 2999, nps: 2999000, time: 0.001000 sec, score: 0  move b1c3
[2019-06-25 12:54:44] depth: 3, nodes 7111, nps: 790111, time: 0.009000 sec, score: 60  move b1c3
[2019-06-25 12:54:44] depth: 4, nodes 10705, nps: 10705000, time: 0.001000 sec, score: 0  move b1c3
[2019-06-25 12:54:44] depth: 5, nodes 21665, nps: 7221666, time: 0.003000 sec, score: 27  move b1c3
[2019-06-25 12:54:44] depth: 6, nodes 89473, nps: 4260619, time: 0.021000 sec, score: 0  move b1c3
[2019-06-25 12:54:44] depth: 7, nodes 129241, nps: 5874590, time: 0.022000 sec, score: 22  move b1c3
[2019-06-25 12:54:44] depth: 8, nodes 381478, nps: 6253737, time: 0.061000 sec, score: 12  move b1c3
[2019-06-25 12:54:44] depth: 9, nodes 1209965, nps: 6611830, time: 0.183000 sec, score: 18  move b1c3
[2019-06-25 12:54:45] depth: 10, nodes 6583634, nps: 6643424, time: 0.991000 sec, score: 10  move g1f3
[2019-06-25 12:54:46] depth: 11, nodes 9686311, nps: 6689441, time: 1.448000 sec, score: 12  move b1c3
[2019-06-25 12:54:47] #
#
################################################################################
// Zeta OpenCL Chess config file for device: GeForce RTX 2070 
################################################################################
threadsX: 36;
threadsY: 1;
nodes_per_second: 3730753;
tt1_memory: 1024; // in MB
tt2_memory: 768; // in MB
opencl_platform_id: 0;
opencl_device_id: 0;
opencl_gpugen: 2;
################################################################################
[2019-06-25 12:54:47] ##### Above output was saved in file config_0_0_.txt 
[2019-06-25 12:54:47] ##### rename it to config.txt to let engine use it
[2019-06-25 12:54:47] #
[2019-06-25 12:55:27] zeta.exe -l 
[2019-06-25 12:55:27] #> Zeta 099l
[2019-06-25 12:55:27] #> Experimental chess engine written in OpenCL.
[2019-06-25 12:55:27] #> Copyright (C) 2011-2019 Srdja Matovic, Montenegro
[2019-06-25 12:55:27] #> This is free software, licensed under GPL >= v2
[2019-06-25 12:55:27] #> eninge is initialising...
[2019-06-25 12:55:27] feature done=0
[2019-06-25 12:55:29] #> ...finished basic inits.
[2019-06-25 12:55:36] >> new
[2019-06-25 12:55:38] #fen: rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1
[2019-06-25 12:55:38] ###ABCDEFGH###
[2019-06-25 12:55:38] #8 rnbqkbnr
[2019-06-25 12:55:38] #7 pppppppp
[2019-06-25 12:55:38] #6 --------
[2019-06-25 12:55:38] #5 --------
[2019-06-25 12:55:38] #4 --------
[2019-06-25 12:55:38] #3 --------
[2019-06-25 12:55:38] #2 PPPPPPPP
[2019-06-25 12:55:38] #1 RNBQKBNR
[2019-06-25 12:55:38] ###ABCDEFGH###
[2019-06-25 12:55:44] >> sd 12
[2019-06-25 12:55:51] >> st 2000
[2019-06-25 12:56:00] >> benchsmp
[2019-06-25 12:56:00] ### doing inits for benchsmp depth 12: ###
[2019-06-25 12:56:02] ### computing benchsmp depth 12: ###
[2019-06-25 12:56:02] ### work-groups: 1 ###
[2019-06-25 12:56:02] depth score time nodes pv 
[2019-06-25 12:56:02] 1 60 53 20 b1c3 
[2019-06-25 12:56:02] 2 0 53 79 b1c3 b8c6 
[2019-06-25 12:56:02] 3 60 53 604 b1c3 b8c6 g1f3 
[2019-06-25 12:56:02] 4 0 55 1222 b1c3 b8c6 g1f3 g8f6 
[2019-06-25 12:56:02] 5 27 58 3652 b1c3 b8c6 g1f3 g8f6 d2d3 
[2019-06-25 12:56:02] 6 0 78 20044 b1c3 b8c6 g1f3 g8f6 d2d3 d7d6 
[2019-06-25 12:56:03] 7 22 101 40822 b1c3 b8c6 g1f3 g8f6 d2d3 d7d6 b2b3 
[2019-06-25 12:56:04] 8 12 194 123932 b1c3 b8c6 d2d4 g8f6 d4d5 c6e5 g1f3 e5f3 
[2019-06-25 12:56:06] 9 16 470 378129 b1c3 g8f6 g1f3 g7g6 d2d4 d7d6 c1f4 b8c6 e2e3 
[2019-06-25 12:56:14] Error: Waiting for kernel run to finish. (clFinish)
[2019-06-25 12:56:14] status:-36

KR
Torsten