Author: KarinsDad
Date: 14:43:27 12/23/03
Go up one level in this thread
On December 23, 2003 at 16:53:44, Dann Corbit wrote: >On December 23, 2003 at 16:35:02, KarinsDad wrote: > >>Another point is that you only need 62 bits to indicate piece/pawn location (the >>position of the kings is already known). > >With these two changes, you need a maximum of 166-4 = 162 bits to store a chess >position. Is that about what you had achieved befire? I do not remember what I had come up with before. At the moment (just messing around with it today at work since it is the holidays), I am probably in the ballpark of about 162 bits or so, but that is not verified quite yet (most standard positions are currently maxing at about 156 bits or so). 20 bytes is the goal I think. Hopefully, I'll have my encoding schemes from before somewhere at home. I don't think I ever made it to 160 (161 or 162 sounds about right). Something to look at over my holiday vacation. >At any rate, it limits the maximum possible number of legal board permutations >to no more than: >2^162 = 5846006549323611672814739330865132078623730171904 possible positions. >(about 5.846e48) > >This does not (of course) take into account things like the half-move clock and >position repeat status. What is half-move clock??? I've never considered position repeat status to be critical to position information, but if you do consider it so, it is normally +2 bits (0 repeats, 1 repeat, 2 repeats). However, I have a way to hide this in the current sized data encoding as well. Thanks for mentioning it. ;)
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.