Check out Janggi (Korean Chess), our featured variant for December, 2024.

Enter Your Reply

The Comment You're Replying To
Reinhard Scharnagl wrote on Sun, Apr 20, 2008 07:57 AM UTC:
To Derek: we know how much work you have invested in your piece value theory, so I understand, that you are somehow enraged on H.G.M.'s interpretations of his attempts. But all individuals I know to be investigating in that matter are strong-minded people. Thus please do not misinterpret their persisting in their viewpoints as pure animosity. 

To all: I understand, that the clearness and consistence of a value defining model is not enough to convince doubters to the 'truth' of such models. That way generated values have to be verified in practise. The easy part of that is to compare such figures to those experienced from 8x8 chess through centuries. The difficult rest of verification is to apply claimed value scales e.g. in 10x8 and to check out if they are well-working.

But it is unsufficient, to simply optimize a bunch of values within a given variant, because that does not establish a neutral theory, which could be applied on other scenarios, to be falsified or verified therein. A valid theory's conclusions have to exceed their input by magnitudes.

Watching the results of H.G.M.'s very interesting 'Battle of the Goths' experiments, what does this induce for our value theory discussion? In my opinion, there hardly could be derived anything concerning this question. Of course, some games have to be reviewed intensively for to see, whether there would have been structural imbalances. But to me it seems impossible to separate those engines' positional abilities from their tactical power, which is obviously very depending from the maturity of their implementation.

My program SMIRF is - as repeatedly stated - my first self-written playing chessengine, also often repaired and modified, but still caught in its initial naive design with a lot of detected basic weaknesses. Its detail evaluation as an example is incredible slow. Mating phases of games lead to concurring incompatible evaluations in SMIRF, thus some games will be lost even though having a clear mating line in view. SMIRF has been programmed without using foreign sources. By all of that it is no ripe engine - and thus I plan to put my experiences into a follow-up engine Octopus, which nevertheless will need a lot of time.

Derek and I have experimented with having different models applied to equal engines, identical beside of those different value approaches. Though this seems to be the more relyable approach for to verify value models, it nevertheless has structural weaknesses too, as in the realization of such a program there will be a lot of parts, reflecting the ideas of its creator, making it not completely independent of the ideas of that programmer.

So what is the arriving conclusion from H.G.M.'s event? SMIRF has to be rewritten as Octopus to become more mature. And maybe H.G.M. might try to embed his value model within a verificatable abstract theory, if he would like to widen its acceptance.

Edit Form

Comment on the page Aberg variation of Capablanca's Chess

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.