>> > {{{{{{{
>> > $ ./freecell-solver-fc-pro-range-solve 30857 30857 1 --method a-star -to
>> > 01246 -asw 1,0,0,0,0
>> > Started at 1244313537.430385
>> > [[Num FCS Moves]]=108
>> > [[Num FCPro Moves]]=60
>> > [[Start]]
>> > 7a 7b 7c 7d 75 67 a5 27 6a 67
>> > 6h d5 b6 74 31 3d 37 3h 8b a8
>> > b7 3a 3b 34 84 83 81 8h b1 d3
>> > 64 2b 26 72 25 82 17v4 17 18 1d
>> > 14 14 27 46 4a 41 42 47 7h c1
>> > d1 a1 21 4c b4 81 52v7 5h 2h 5d
>> >
>> > [[End]]
>>
>> Following this solution, I have some questions & comments.
>> 1. It sometimes does and sometimes does not show an automove.
>
> It should never show an automove. the FCS Moves are incompatible with MS-
> Freecell/FC-Pro and I'm using a post-processor to process them and convert
> them to FC-Pro's moves.
>
Then there's a bug. Move 11 (for example) is 6h (a Horne automove).
>> 2. Also it sometimes does and sometimes does not indicate "vn"
>> after a multi-card move. Why to both?
>
> Well, the v$N is an extension to the standard notation that in case of a
> column-to-column move indicates the number of cards moved if-and-only-if they
> differ from what FC-Pro expects. If not, it must be omitted.
>
I would (and I think I've heard others say so too) consider that a bug in FC-Pro
(I think you ought to omit the suffix).
Received on Sat Jun 06 2009 - 15:55:47 IDT