| |||||||
| From | Message | ||||||
|---|---|---|---|---|---|---|---|
|
stalhandske 07-May-18, 22:37 |
engine analysis |
||||||
|
Also, depending on how many post-game analyses are pending at the time, we have to reduce the per-move thinking time for the engine in order to accommodate everyone in a reasonable time. There is a minimum depth limit to maintain quality -- i.e. the minimum number of moves that will be analyzed ahead, but if there is time, the engine will continue analyzing. If there are only a few pending requests, your analysis will be allowed to run much longer. Which generally means that the strength of the analysis might vary somewhat from game to game. We haven't officially tested the strength of our engine vs commercial chess engines head-to-head, but in game analysis tests, it was returning practically identical results to Stockfish on several hundreds of random games we used in our test. |
||||||
|
stalhandske 08-May-18, 09:29 |
|
||||||
|
penelope80 19-May-18, 11:02 |
|
||||||
|
tugger 19-May-18, 14:39 |
I say this because I find myself an an interesting stage of my chess here at gameknot... I'm starting to "beat" the engine. I have had my doubts for a while, but this game is what confirmed it for me... game 13. Bxf7+! - engine flags it as a mistake, my score goes from -0.66 to -2.61 13... Kxf7 (forced, Kh8 mates in six) 14. Qh5+ Kg8 (forced) - now my score is =0 This is a winning attack for white, I'm near certain that black cannot refute this. Of course, the engine found checkmates that I didn't, one of which I really should be seeing (34. Qd6), but I was on auto-pilot by this point, I knew Bf4 was winning too. But the key tactical move that won me this game, the GK engine failed to recognise it as a winning move, so sadly I think it's time for me to find an alternative for post-game analysis. |
||||||
|
tugger 19-May-18, 14:46 |
So yeah, I'm definitely hitting it's limit. |
||||||
|
stalhandske 20-May-18, 04:09 |
I am not at all sure of this, but I spontaneously feel that if tugger is right and the rating of the GK computer is around 2000 in practise (which I think is quite a reasonable estimate), it might as well be removed altogether, because then it is doing more harm than good. |
||||||
|
tugger 20-May-18, 04:31 |
I've been happy with the engine here up to my current rating, and only now am I finding that I need an alternative engine for post-game analysis. I consider it a good thing... it shows I'm still improving. I think it's a fine tool for sub-2000 players, but it shouldn't be considered as 100% reliable. For the 2000+, perhaps investing in something more accurate is necessary for post-game analysis. |
||||||
|
Along similar lines to Penelope, I’d be happy to wait a few more days for a better analysis. I guess GK has these sort of tricky dilemmas all the time, how quickly, how strong etc. |
||||||
|
tugger 20-May-18, 08:32 |
|
||||||
|
It's not as simple as allowing more analysis time, "and if it takes a day or more longer, so be it". We optimize the analysis time per game to make sure we can process the daily queue within a day. That means the analysis queue is not growing. But if you increase the analysis time by just 10%, that means you can only process 90% of the daily queue, and the next day you need to process 110%. And the next day it's 121%, and the next day it's 133% (the percentage compounds each day). Obviously, it's not sustainable. And due to the way the move tree grows, you need to double your analysis time to look just another move ahead once you get deep enough. Which means after a certain rating, to improve your analysis by a modest amount, you need to double your analysis time, which means to halve the number of games processed. There is a very fine balance between processing all games within a day, and never processing any new games for years. If you require the absolute top-notch analysis, by all means, do acquire a multi-core computer with gobs of RAM, and purchase the best commercial chess engine, and let it run for a couple of hours to analyse each game. Regretfully, we cannot compete with that, as we have to accommodate thousands of players simultaneously. |
||||||
|
stalhandske 20-May-18, 20:56 |
|
||||||
|
tugger 21-May-18, 01:22 |
I understand the problem you guys have with this. I'm certainly not complaining, just sharing my experience. I'll continue to use the GK engine, just with a sense of awareness that it's not perfect. |
||||||
|
|
||||||
|
|
||||||
|
penelope80 21-May-18, 09:37 |
|
||||||
|
tugger 21-May-18, 10:10 |
|
||||||
|
stalhandske 21-May-18, 20:34 |
|
||||||
|
|
||||||
|
ludus_puerorum 14-Jun-18, 05:49 |
|
||||||
|
penelope80 14-Jun-18, 05:56 |
you will read: -mistake/and the sequence of moves -best/that says the best move with the continuation I hope it helps |
||||||
|
ludus_puerorum 14-Jun-18, 06:08 |
|
||||||
|
I like the amendment...It was really in the matter of middlegame tactics that the GK engine was at its best, but also where its horizon effect weakness was most apparent. Nevertheless, I found it generally reliable tactically. I still use it to check out my games, and found with some recent games, my performance wasn't as strong as I thought at the time! |
||||||
|
If the analysis is useful for someone rated at 1400, should it be eliminated because a 2400 player doesn't get that much out of it? I think there are lots more 1400 rated players on GK than 2400 rated players. But I like GK's rating/depth solution--it is a clever idea that should work well enough. |
||||||
|
stalhandske 10-Jul-18, 20:41 |
My wording was imprecise. But a 1400 rated player will equally be served much better by a better engine. My aim was to point out some truly embarrassing positional judgements that the older version did, and which it did - of course - equally irrespective of the player's rating. It was great that GK was able to improve the engine usage in a difficult situation. I had not realised that the issue limiting its use was the large number of users. |
||||||
|
|
||||||
|
Strong Engine Analysis |
||||||
|
yon_cassius 26-Jul-18, 10:50 |
Nick |
||||||
|
thanks |
||||||
|
tugger 16-Dec-18, 04:19 |
game Here's another sub-2000 performance from the engine. Black has just played 51... Kf6, and I duly resigned. GK's engine suggests 51... Kf6 is a mistake, scoring just +0.56. My calculation (and that of my opponent) was that black queens and I'm lost. GK engine recommends 51... Bxd5, which I was hoping black plays, and which I calculated as drawn. GK scores it +1.68. So I took a look a Stockfish, and the results are that me myself and bookie are correct in our calculations, and that the GK engine is wrong. SF scores the following... 51... Kf6 +9.66 51... Kf7 +7.40 51... Bxd5 +0.41 How is the GK engine able to fail at endgame so badly? I can understand engines struggling for accuracy in middlegame, but I shouldn't be able to touch an engine when it comes to endgame, and for sure I can't touch Stockfish. For clarity, it was bookie who requested the analysis, he is a premium subscriber. I currently am not. Does that affect bookie's quality of analysis? |
||||||
| |||||||