Sorry for the delay in replying. I missed the thread continuation.jesper_nielsen wrote:Hmmm.... that sounds wierd.... I haven't noticed it myself.mhalstern wrote:Congratulations.
I am using it with my Fritz 11 Interface. I'll report the elostat results in a few weeks.
I noticed one thing: When the engine first starts to analyze, something, the reported depth count is unusually low for a while. Then, when it move, the numbers jump up much higher.
I report depth in two situations:
1. Whenever the PV changes.
2. Whenever an iteration completes.
So you might see something like "depth 9 seldepth 14" along with a pv.
And then a bit later "depth 9 seldepth 16" sometimes later when the iteration completes, if searching alternative moves takes it to ply 16 using extentions.
Kind regards,
Jesper
Maybe something is wrong with the GUI. As a test, I am playing a 3 minute game now. I don't always (but sometimes do) see all iteration counts. I'll sometime see 1/1 and after a few seconds see 9/15 or 10/16. I am used to seeing all in between depth iterations reported.
Not a big deal - Thought you might want to know.
Regards