swami wrote: I plan to release version418 today or tomorrow(
Thanks,Uri. Movei needs to the updated because it has to catch up with lot of engines in Division 1 and 2, Movei will do well.It's just that the current version doesn't play at its level in blitz 1/1.
Regards.
I think that the main advantage of the new version is at long time control thanks to pruning based on hash tables.
possible problem of movei at 1+1 is that it prints too much information and it may cause significant speed reduction under an interface that is not winboard.
Movei prints pv in the following cases:
1)when it find new score for the pv move
2)when it fails high(there may be wrong fail high that after research are rejected)
3)when it fails low
4)at the end of every iteration.
For comparison other engines do not print pv at the end of the iteration and do not print fail high that may be wrong.
I do not know if it is the reason for the bad result that I saw at 1+1 and there may be a different reason(note that 438 also showed bad results at 1+1 in jorge testing).
That problem was not corrected in 438 but was corrected in a future versions when there is a noise parameter that tell movei not to print pv unless it searched more than noise nodes so by telling movei that noise=1000000 you can tell it not to print the pv in 1+1 blitz conditions.
I think that printing pv is not an important problem in 40/4 ccrl or 40/40 ccrl conditions and my guess is that the demage at 40/4 is less than 10 elo but it can be more important problem in faster time control.
Uri