Check out Glinski's Hexagonal Chess, our featured variant for May, 2024.

Enter Your Reply

The Comment You're Replying To
Greg Strong wrote on Mon, Sep 25, 2006 11:20 PM UTC:
Sam and Dan,

Thank you both for the time that you have spent looking into this and
typing in your findings.  I appreciate it, and, with research, it will
lead to a stronger program.

It is true that development by itself doesn't guarantee anything. 
However, computer chess programs consider as many moves as they have time
to, and each sequence of moves leads to a positon.  The computer must then
evaluate that position (or, if pieces are still hanging, it plays out
winning captures before it evaluates,) but eventually a position must be
quantified with a number - the more positive the number, the better the
position for white, the more negative, the better for black.  Experience
can tell a human player a lot about what is good and what is bad, but
trying to program in too many specific scenarios makes a program worse,
because it takes too much CPU time to evaluate, and the more CPU time you
spend on evaluation, the less moves you can consider.

Lots of things can help ChessV.  Obviously, a good opening book would
help.  I am working on an opening book for Janus Chess, but it takes time.
 Also, evaluation of position gives pieces a bonus or penalty based on the
square it occupies (a piece-square-table.)  Such tables can be different
for each type of piece, and they can be different in the opening vs.
midgame vs. endgame.  Clearly the piece-square-tables for Janus Chess (and
all other 10x8 variants for that matter) could be improved.  I'll look
into the current tables, and, based on the game Dan has posted, I'll try
some experimentation.  Finally, I think that there is probably a bug
buried somewhere deep in the move-search functions that is proving very
difficult to isolate ...

Thanks again to you both.  I'll study what you have posted and keep you
posted!

Edit Form

Comment on the page ChessV

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.
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.