I just want to clarify something. Did the engine lost a total of 20 games, 10 of which from crashes and 10 from losses on time? Or just a total of 10 games that are just crashes and therefore it losses on time?
When it crashed, is it just searching indefinitely for a position or there is something that pops up like an error window?
I think that the engine has some array overflow, a stray pointer or a divide by zero something kind of error in the code.
Would you mind giving me the details of how it crashed? Like in what move number, what time is remaning, what kind of positions it is searching, what game phase, how many plies it has searched, etc..
Thanks very much for the testing. The UEL is always the first to publish the test results of every new engine version.
I just want to clarify something. Did the engine lost a total of 20 games, 10 of which from crashes and 10 from losses on time? Or just a total of 10 games that are just crashes and therefore it losses on time?
When it crashed, is it just searching indefinitely for a position or there is something that pops up like an error window?
I think that the engine has some array overflow, a stray pointer or a divide by zero something kind of error in the code.
Would you mind giving me the details of how it crashed? Like in what move number, what time is remaning, what kind of positions it is searching, what game phase, how many plies it has searched, etc..
Thanks very much for the testing. The UEL is always the first to publish the test results of every new engine version.
Edsel Apostol
Hi Edsel,
The engine losses on time only after a crash.
When I'll back home this evening, I will send you the position where it crashs.
The previous version (20070602) had the same problem.
I am not sure if I understand correctly the term that the engine "crashed". Please understand my somewhat naive questions.
When the engine crashed, does it stop thinking, no outputs, and the OS pops-up an error window? Or it simply losses on time while thinking indefinitely on a position while still producing outputs like the PV and the NPS?
I am not sure if I understand correctly the term that the engine "crashed". Please understand my somewhat naive questions.
When the engine crashed, does it stop thinking, no outputs, and the OS pops-up an error window? Or it simply losses on time while thinking indefinitely on a position while still producing outputs like the PV and the NPS?
Edsel Apostol
To be honest, I haven't always been at the computer to observe the actual losses.
I would assume that if see the popup box reporting an error, then that means that Twisted crashed before losing on time?
I am not sure if I understand correctly the term that the engine "crashed". Please understand my somewhat naive questions.
When the engine crashed, does it stop thinking, no outputs, and the OS pops-up an error window? Or it simply losses on time while thinking indefinitely on a position while still producing outputs like the PV and the NPS?
Edsel Apostol
To be honest, I haven't always been at the computer to observe the actual losses.
I would assume that if see the popup box reporting an error, then that means that Twisted crashed before losing on time?
Regards, Graham.
When TL crashes, the pop-up error box appears, and the task manager processes table shows that there is no thinking by TL.
Twisted Logic 20070706 first rating in the UEL: 2398.
