home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!gatech!news.byu.edu!news.mtholyoke.edu!nic.umass.edu!dime!barrett
- From: barrett@astro.cs.umass.edu (Daniel Barrett)
- Newsgroups: comp.sys.amiga.advocacy
- Subject: Re: UChess.lha Avail via ftp
- Message-ID: <57932@dime.cs.umass.edu>
- Date: 22 Dec 92 20:24:22 GMT
- References: <harry.03qb@elfuerte.fipnet.fi>
- Sender: news@dime.cs.umass.edu
- Reply-To: barrett@astro.cs.umass.edu (Daniel Barrett)
- Organization: BLAZEMONGER INCORPORATED
- Lines: 27
-
- >In article ??? barrett@scooby.cs.umass.edu (Daniel Barrett) writes:
- >>So let's look 5 moves ahead. To store all the possible
- >> chessboard configurations would require 25*25*25*25*25*25*25*25*25*25*25*
- >> 25*32 bits or 200 billion megabytes.
-
- In article <harry.03qb@elfuerte.fipnet.fi> harry@elfuerte.fipnet.fi (Harri P Pesonen) writes:
- >Another way of saving memory is only store the best moves in each level.
- >If every level has 25 moves then one level takes only 100 bytes of memory.
- >So thinking 5 moves ahead takes only 2*5*100 bytes or 1000 bytes.
-
- But there is no simple way to decide which are the 25 "best" moves.
- Suppose you search 1 level deep and pick the 25 moves that look best. Maybe
- when you search 2 levels deep, some of these 25 opening moves now look bad.
- Maybe at 3 levels deep, some look good again!
-
- There is a tradeoff between how many moves you save, and how well
- your chess program plays.
-
- There are definitely some ways to save memory, but for chess,
- the more memory the better. :-)
-
- Dan
-
- //////////////////////////////////////\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- | Dan Barrett -- Dept of Computer Science, Lederle Graduate Research Center |
- | University of Massachusetts, Amherst, MA 01003 -- barrett@cs.umass.edu |
- \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\/////////////////////////////////////
-