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

Enter Your Reply

The Comment You're Replying To
Hans Aberg wrote on Wed, Apr 23, 2008 07:59 AM UTC:
I think one needs defining the context of the piece values: the traditional orthodox piece values are mostly used by humans to predict the end-game relative strength, excepting certain types end-games: if there are pawns left that may promoted, one pawn value down will normally draw, two may loose, three is a more certain defeat, but if there is no pawn to be promoted, at least five pawns ahead (rook plus king against king) are needed for a win. In middle game, one can add empirical reasoning, like 'knights strengthen (resp. weaken) in closed (resp. open positions)'.

So here there are usage several factors that need to be indicated: empiric for use by human reasoning, end game prediction, excluding certain types of end games, whether pawns can be promoted or not. The last factor does not traditionally alter the piece values, but their interpretation. 

For piece values used by computers, these can be more exact, but under what circumstances should the values apply? - To determine a local middle game fight, or determine overall material pressure, determine open development, or predict potential end-game capabilities? Perhaps different values should be given for different chess strategic positions. With that in hand, a computer might do more human like decisions, like 'in this situation, the sacrifice of this pawn is well compensated in the long term by position, but not the short one, so the best strategy here is to take it and give it back later'.

In Capa chess variations, one idea is to add material as to make end games less likely (though this may a change if the variation is learned thoroughly). Therefore, if position values are based upon games that rarely result in end games, perhaps that should considered 'middle game piece values'. And so on.

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.