whereagles wrote:well, indeed keeping it stable is part of the game...
The same thing will go for computing Elo on the CCRL and CEGT lists.
For me, one of the truly great lessons from Fabian was the effort spent in writing bug free code (see his lovely use of asserts, for instance).
The crash is actually an opportunity for the fire team. If they can collect the position of the game that caused failure and reproduce the problem, then they can increase the reliability of Fire.
whereagles wrote:well, indeed keeping it stable is part of the game...
The same thing will go for computing Elo on the CCRL and CEGT lists.
For me, one of the truly great lessons from Fabian was the effort spent in writing bug free code (see his lovely use of asserts, for instance).
The crash is actually an opportunity for the fire team. If they can collect the position of the game that caused failure and reproduce the problem, then they can increase the reliability of Fire.
I could be wrong, but I don't think CCRL would count a crash as a defeat if the engine that crashed had a winning position.
whereagles wrote:well, indeed keeping it stable is part of the game...
The same thing will go for computing Elo on the CCRL and CEGT lists.
For me, one of the truly great lessons from Fabian was the effort spent in writing bug free code (see his lovely use of asserts, for instance).
The crash is actually an opportunity for the fire team. If they can collect the position of the game that caused failure and reproduce the problem, then they can increase the reliability of Fire.
I could be wrong, but I don't think CCRL would count a crash as a defeat if the engine that crashed had a winning position.
Even if its flag fell? If so, it sounds broken to me.