MATCH sanity

[Guenther]

Based from this,

Code: Select all

103. Kf1 {0.00/33 0.29s, Black disconnects} 1-0

It is the engine that disconnected in the first place.

Doubt that because it can't :wink: But I think the -draw option will solve the problem.

I wouldn't do that. You'll hide problems. It seems ProDeo '2.4 future' crashed...

[hgm]

I don't see how you can guarantee that. Any program can crash, even if it is just by bugs in the libraries you link to.

[Rebel]

I wouldn't do that. You'll hide problems. It seems ProDeo '2.4 future' crashed...

I don't see how you can guarantee that. Any program can crash, even if it is just by bugs in the libraries you link to.

You both got me think twice and indeed after a long search (a week ) I got the deeply hidden bastard in it's full gory glory making the engine crash in extreme circumstances.

Glory, because when I fixed the bug I expected at least a small improvement. The opposite was true, a regression of aprox. 10 elo. The world upside down, bugs that provide elo!

Now that I have insight what the bug is actually doing I further exploited it and got an extra 6 elo

So now I am on the crossroad fixing the bug losing 10 elo (no more crashes) or tune the bug and gain 6 elo with the risk of an exceptional crash.

Isn't CC life wonderful?

[hgm]

I don't know the details, but it seems to me it should always be possible to detect the conditions that would lead to a crash (like out-of-bound array accesses, or infinite recursion), and take appropriate action in that case. While leaving the unintended behavior that seems to produce Elo just do its thing when it would not produce a crash.

[Rebel]

In a nutshell, what happens is that the bug removes legal moves from the move list. I noticed these moves in general are extremely bad and thus play no role and it's where the elo comes from. new kind of pruning

Naturally sooner or later Murphy's Law shows up and things go wrong especially in the late endgame.

[hgm]

Removing moves can cause poor play in unfavorable situations, but it should not be able to cause crashing.

[Rebel]

Removing moves can cause poor play in unfavorable situations, but it should not be able to cause crashing.

You are lacking imagination.

Not every program setup the same.

[hgm]

Well, I say 'should not' and not 'cannot'. I imagine there is something horrebly wrong with the design if pruning moves makes it crash. Pruning moves is basically just playing a game with somewhat different rules that would make the pruned moves not pseudo-legal..

[Rebel]

I understood what you were saying the first time.

It's a typical human fallacy to reject | deny | judge things people can not imagine without having experienced those things themselves.

Heck, on the issue at hand I might have even agreed with you one week ago although my choice of words (with regard to the above) would have been more careful.

Assumptions (judging etc.) without testing is not very scientific, you of all forgot?

[hgm]

Not really. When someone says something that is inconsistent, no testing is needed at all to know it is wrong. That is logic, i.e. mathematics. Mathematics is not an empirical science. One doesn't prove mathematical theorems by testing them.