I just looked at all the nets I have and that one wasn't among them, so I'm downloading it now. I'll give it a spin and see how it does.drewdrew wrote: ↑Fri Mar 20, 2020 6:36 pmNot exactly sure, but the line given by SV-384x30-t60-3070 was in agreement with SF for more than 30 plies - when I checked them both a few moves ago -.Zenmastur wrote: ↑Fri Mar 20, 2020 6:24 pmOnce I got a graphics card that could run NN engines at a reasonable speed I thought this would "fix" many of Lc0 short comings. It hasn't. I ran Lc0 side-by-side with Stockfish for several hours last night while I was analyzing. When ever Lc0 would select a different line than SF I would save both and then analyze them to see which was "right" or "better" or which had errors in it. In every case I investigated Lc0 lines had errors in it. By "errors" I mean moves in the line that evaluated significantly different than the evaluation given to the line as a whole by Lc0. This wasn't a one-off per line of analysis, there were several moves like this in each of Lc0 prefered lines. I tried several different nets, including 62078 320x24 and segio's 512x40 test net. I figured the larger nets would do better since the analysis times, while they varied, were around 300 seconds per move. This didn't seem to help.drewdrew wrote: ↑Fri Mar 20, 2020 6:15 pmlc0-384x30-t60-3070, also unassisted, at -0.32, depth 45. So far - since my last comment - lc0 and SF-dev have been following the same line as the one played here.
So, anyone have any suggestions on a net that under longtime control doesn't have this issue?
How deep were the searches?
Regards,
Zenmastur