Arena Time Forfeits

[brianr]

It has been some time since I have used Arena.
I am testing Tinker against a number of other engines at 1 min plus 2 sec increment, no pondering (on Q6600, Vistax64).

It looks like nearly 10% of the games are time forfeits.

Examination of the arena.debug file indicates an Arena issue.
The time/otime/move sequence shows Arena sending less than 2 seconds (time 200) to Winboard engines (but not UCI), and then flagging them.

Has this been fixed in the 199B5 (currently using B4)?

I can use another tool like SCID to filter the forfeits, but then it is hard to know if there is an actual engine time bug.

Any comments or suggestion welcome
(aside from use another tourney manager like PSWBTM).
Thanks,
Brian

[Tony Thomas]

May be you should use Arena 1.1 as it is the most stable version to date..

[hgm]

uggestion welcome
(aside from use another tourney manager like PSWBTM).

You know about that, and still want to use Arena?

[Matthias Gemuh]

Examination of the arena.debug file indicates an Arena issue.
The time/otime/move sequence shows Arena sending less than 2 seconds (time 200) to Winboard engines (but not UCI), and then flagging them.

WB time 200 is 2 seconds.
UCI time 2000 is 2 seconds.

Matthias.

[brianr]

Yes, I know.
With an inc of 2 seconds, Arena.debug input to WB engines should never be less than 200, but it is.
UCI engines get the correct 2,000.

Arena forum post indicates it may be fixed in the 1.99B5 beta version.

I was using B4.

[brianr]

FWIW, 199B5 has the problem, and another post at arena forum indicates that 1.1 (last stable version?) does as well.