Actually, I got it to sorta-kinda solve game #1 already.
It says it solves MS#1 in 61 moves (only a few could be cut out due
to redundancy), but about 30-40 moves in, it goofs. I'm currently
trying to figure out what its problem is.
One of the program's huge weaknesses is that it doesn't recognize
dead cards very well. That's mainly because I don't understand too
well how they work.
"A card is unneeded when no lower-rank cards of the opposite color
remain in the playing area" (from the tutorial).
Why is it that 2C and 2S will be sent home before either AH or AD
are? I can see why FC doesn't send my 3S home when only 4D and AH are
home, but that's probably why I'm so darn confused...
Right after my program tosses out a "solution" it crashes. D'oh!
Geez, 61 moves seems like a lot.
--- In fc-solve-discuss_at_yahoogroups.com, WKRfresno_at_a... wrote:
> It would be a good idea to get your solver running with zero
freecells before
> adding ANYTHING to the code to handle freecells. The movement to
and from the
> freecells just adds too much complexity. One of my firm beliefs
is "get a
> simpler version running first."
> Bill R.
Received on Thu Nov 20 2003 - 21:04:22 IST