search

jonathanmcdermid / Clovis

MIT License
4 stars 2 forks source link

measuring speed #2

Closed SzotsGabor closed 2 years ago

SzotsGabor commented 2 years ago

I don't know how to do it. I tried go depth n but whatever number n is it seems to disregard it. No nps, no time output. There is hit% which I think is hash hit rate but what is mpn?

jonathanmcdermid commented 2 years ago

hit% was hashtable hitrate and mps was a metric I was using for seeing the average number of moves done at each node. I've removed them now. Release 1.2 has the depth command functionality and time.

SzotsGabor commented 2 years ago

Hi Jonathan,

It seems it still does not support 'go depth n', in fact does not support 'go infinite' either because the search is stopped at depth 11 or 12 (depending on which compile I use).

jonathanmcdermid commented 2 years ago

In 1.2 the default time is not infinite, so you would need to enter something like 'go depth n wtime 5000 btime 5000'.

SzotsGabor commented 2 years ago

To my knowledge, 'go depth n' should make the engine calculate until it reaches depth n (search n plies only). 'Go infinite' should make the engine calculate until the "stop" command.

Anyway, I tried your suggestion and after go depth 15 wtime 100000 btime 100000 it indeed searched up to 15 plies. However, all other engines I know will calculate until ply 15 even if I don't include the wtime btime parameters.

I tried Shredder, which we might consider as authentic. Go depth 30 made it search till ply 30, go depth 30 wtime 100 btime 100 made it stop after 8 plies.

jonathanmcdermid commented 2 years ago

Thanks for letting me know about this oversight. Ill make the change for the next release