I agree that checkers is probably the game which will be most interesting to see this AI play.

There's currently one technical problem that needs to be solved before a feasible checkers AI can be generated, however: we need to use less space in memory. The Connect 4 AI uses up about 100 MB of memory once it plays up to about 70,000 games; there is simply too much state information to keep it all resident in memory at once. My computer has 96 MB of memory, and crawls to a halt after the memory size blows up.

A side effect of the huge amount of memory taken by the program is that it's also about 100 MB to write out the state information to disk. I plan on using Storable to store the data onto disk, because it should take up less space, and maybe tying the state data to some sort of database such that we don't have to keep it all in memory at once. We could also decide to pack state info into a more concise form than strings; that should save on space, but I doubt that the small savings there (on the order of using roughly 5x less space) would be enough savings to make checkers (or even connect four) viable.

All this space doubles if you choose to use another AI player (as opposed to the Random player) for the second player.


In reply to Re: Re: A simple game AI that learns by Falkkin
in thread A simple game AI that learns by Falkkin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.