I think it is not such an extreme case : One engine maybe is faster but it has a bad evaluation so it solves less positions but faster (in the positive cases) than the other. I think it is a possible scenery.Hart wrote:A better model might include the number or percentage of solved position. However, what I have consistently seen is markedly high correlations between rated time and positions solved. In other words, they are both measuring, to a large extent, the same thing: playing strength. In most of my analyses I get better rankings using rated time as well, go figure.Andres Valverde wrote:1) Imagine a slow but good engine that solves 1000 positions at 3'' averaqe per position. Total time :
1000 x 3" = 3000 s
2) A _fast_ but not so good engine, finds only 500 solutions out of 1000, but it does it at 2"/position : Total time :
500 x 2" + 500 x 4" = 3000 s
Both engines would have the same rating, but former solved double number of positions than latter!.
So, the number of positions solved have to be used somehow in your formula or I'm missing somthing..
As for your example, I am not quite sure I understand it. From what I can see it does not look like you account for the law of averages or you are using an extreme example where my model would of course fail. No engine will solve x positions in one discrete moment of time and then y at another discrete amount of time in these tests. They will actually be distributed unevenly throughout the time period t largely depending on their relative strength, in which case this distribution will be captured in rated time and will correlate with playing strength.
I ran a test with Buzz (slightly fast) and Dirty (a bit slower, same search a more elaborated eval), results are as folllow:
Buzz 0.08 (2300 CCRL) , Total time : 2237'' , Solved : 356/714
Dirty 099OW5 (+2450 CCRL) , Total time : 2245'', Solved : 367/714
In this case, results are clearly not correlated with ELO. It was a quick test with 17 ICCF games (2400 ELO +-, draw result), analyzed from move 20 to 40.
I dont want to say your idea is bad, I think it's very interesting, but still believe that number of positions solved must be taken in account at least.