|
||||||||||||
AW: GK2000/2100 und Konsorten...
Hallo Paul,
kein Problem, da gibt es nichts zu Entschuldigen, Du hast es nur übersehen. Das kann passieren und Hauptsache ist doch das Du es schließlich gefunden hast ![]() Viele Grüße Otto
__________________
Schach ist das Spiel, das die Verrückten gesund hält. ![]() |
|
|||||||||||
AW: GK2000/2100 und Konsorten...
Ich erlaube mir Neulings-Fragen zum H8-Bug (https://www.schach-computer.info/wik...php?title=Bugs).
Bei meinem Saitek Expert Travel Chess-Gerät habe ich mit dem "H8 Bug - Beispiel 1" von obigem Link verifiziert, dass mein Gerät "buggy" ist. Was mache ich mit so einem Gerät? Aufbewahren wie eine teure Briefmarke mit Fehldruck? Oder in den Elektroschrott werfen? Ist das Ding zum Schach-Spielen verwendbar? Mit "workaround"? Geändert von Hans21 (17.10.2023 um 14:02 Uhr) |
Folgender Benutzer sagt Danke zu Hans21 für den nützlichen Beitrag: | ||
Tibono (17.10.2023) |
|
|||||||||||
Re: GK2000/2100 und Konsorten...
Hi Hans21,
time ago I shared elsewhere: Code:
I can remember facing the H8 bug 3 or 4 times at most with my Mephisto Chess Challenger, out of 130 games played up to now. So, roughly 3% of games encountered the bug. Now, how should this translate into Elo-strength? Let's assume a same level opponent: bug-free, the Morsch program should achieve 50% points. 3% of games where the H8 bug happened should have granted 1,5% points to the overall Morsch score; we can assume these are totally lost due to the bug (as the bug is an obvious blunder and has a really bad impact). So, the buggy Morsch program achieves only 48,5% points instead of 50%. This is a -10 Elo points performance... The impact on strength is rather light. So, it is essentially a matter of frustration for the proud owner! Of course, should you enter your computer in a single-elimination tournament, any occurrence of the bug would mean a sudden death... but the bug can as well not surface at all! To answer your question: the bug enables no additional value as a misprinted stamp would do; as a number of devices suffer from this common bug. On the other hand, according to the above quote, it does not deserve a throw into the bin trash. And finally: a workaround can be used, but honestly limited to analysis purpose as it is rather cumbersome and time consuming. The idea is the bug only surfaces on the fly, playing the blunder instantly or so; while if you run the program in analysis mode one half move before (thinking as the opponent, so) it won't (at least from my experience so far). Setup the position so that the opponent's move is either mandatory or obvious (such as a honey pot Queen to capture) and leads to the position where the H8 bug surfaced; let the program calculate the time you want (analysis level) and watch the PV2 display (PV1 should be the obvious or mandatory move you prepared). This is the workaround move. Next steps are easy: let the program make the obvious expected move, restore the playing level you want, play the workaround move, take back the answered move and play instead (you can also use referee mode to play the workaround move, to avoid the takeback step). Regards, Tibono |
![]() |
Themen-Optionen | |
Ansicht | |
|
|
![]() |
||||
Thema | Erstellt von | Forum | Antworten | Letzter Beitrag |
Turnier: Ein paar Spiele des GK2000 | Moregothic | Partien und Turniere / Games and Tournaments | 0 | 26.02.2008 21:11 |
Anleitung: Saitek GK2000 | Moregothic | Die ganze Welt der Schachcomputer / World of chess computers | 4 | 26.02.2008 17:36 |
Frage: Kasparov Olympiad = GK2000/GK2100? | Fluppio | Die ganze Welt der Schachcomputer / World of chess computers | 1 | 22.08.2006 16:46 |
Turnier: Match Milano-GK2000, 40Z/2H | ed209 | Partien und Turniere / Games and Tournaments | 7 | 26.12.2004 16:01 |
Turnier: Match GK2000 vs Super Constellation | Stefan | Partien und Turniere / Games and Tournaments | 0 | 18.08.2004 23:56 |