a reader of the first edition (via my publisher) wrote: I've bought the 1st edition. Is it worth buying the second?
the same reader of the first edition (via my publisher) wrote: In particular, is there anything new wrt Sudoku?
DB in PBCS2 wrote:two and a half years after the version of champagne’s meta-collection used in the above tables, its most recent update [2014/09] as of this writing [2015/07] – the result of an intense and systematic search since the first edition of this book – introduced one more puzzle with SER 11.9, nineteen more with SER 11.8 and 108 more with SER 11.7, but all of them can be solved in B6B or lower.
Name in HLS: Name in PBCS: Remarks:
xy5-chain biv-chain-rc[5]
hxy-uu5-chain biv-chain-uu[5] uu = rn, cn or bn
nrc5-chain biv-chain[5]
xyz6-chain z-chain-rc[6]
hxyz-uu6-chain z-chain-uu[6] uu = rn, cn or bn
nrcz6-chain z-chain[6]
xyt-rc6-chain t-whip-rc[6]
hxyt-uu6-chain t-whip-uu[6] uu = rn, cn or bn
nrct6-chain t-whip[6] t-whips are slightly more general than nrct-chains
xyzt-rc8-chain whip-rc[8] whips-rc are slightly more general than xyzt-chains
hxyzt-uu8-chain whip-uu[8] uu = rn, cn or bn; whips-uu are slightly more general than xyzt-uu-chains
nrczt8-chain whip[8] whips are slightly more general than nrczt-chains
a reader of PBCS wrote: In a single sentence, of all the ideas introduced in your books and implemented in CSP-Rules/SudoRules, which would you name as the most innovative
denis_berthier wrote:As HLS was Sudoku-specific but PBCS applies to any finite CSP, names of various types of chains had to be changed so as to generalise the Sudoku-specific ones.
At the request of readers of HLS, I also re-introduced in CSP-Rules various types of chains that were called 2D-chains in HLS and that I didn't reproduce in PBCS. As "2D-chain" is related to the grid structure of Sudoku, I replaced this name by "typed-chain". All the names in PBCS are thus simpler and can be applied to any CSP.
- Code: Select all
Name in HLS: Name in PBCS: Remarks:
xy5-chain biv-chain-rc[5]
hxy-uu5-chain biv-chain-uu[5] uu = rn, cn or bn
nrc5-chain biv-chain[5]
xyz6-chain z-chain-rc[6]
hxyz-uu6-chain z-chain-uu[6] uu = rn, cn or bn
nrcz6-chain z-chain[6]
xyt-rc6-chain t-whip-rc[6]
hxyt-uu6-chain t-whip-uu[6] uu = rn, cn or bn
nrct6-chain t-whip[6] t-whips are slightly more general than nrct-chains
xyzt-rc8-chain whip-rc[8] whips-rc are slightly more general than xyzt-chains
hxyzt-uu8-chain whip-uu[8] uu = rn, cn or bn; whips-uu are slightly more general than xyzt-uu-chains
nrczt8-chain whip[8] whips are slightly more general than nrczt-chains
In my book PBCS2, section 6.6, I wrote:In 10,000 puzzles tested, only 20 (0.2%) have different W and B ratings. Moreover, the maximum length of whips in a single resolution path using only loopless whips and obtained by the “simplest first” strategy is a good approximation of both the W and B ratings.
PBCS3 wrote:– section 1.5.2 adds a few remarks on our view of AI and constructive modelling; this is of course related to our original modelling approach of Sudoku and to the way we extended its basic xy-chains into generic whips, braids and other chain rules;
– section 4.6 is split from the previous section and it adds the notion of “blocked” behaviour (as a local micro-strategy) for resolution rules;
– section 5.12 [Appendix 5A, “Typed chains and the 2D-chains of HLS”] re-introduces in the general formalism of the present book the 2D-chains formerly introduced in HLS (in the restricted context of Sudoku); they were not repeated in PBCS1 or PBCS2 because we had no purpose of including all that was already published in HLS; but many readers wanted to know how they fitted in the general framework of PBCS; a table shows the correspondences between the Sudoku-specfic names in HLS and the generic names adopted here; notice that typed chains are also present in CSP-Rules V2.1.
– section 5.13 [Appendix 5B, “A symbolico-graphical representation of chain rules”] is an answer to some readers request of a less formal presentation of the main chain patterns; it is also present in the Basic User Manual; the reader should be aware that graphics can help understand but cannot replace a precise definition.
– section 5.14 [Appendix 5C, “How to start looking for a chain pattern”] is also an answer to some readers request; it shows that the starting point of a chain is always a very simple pattern; but it should remain clear that the present book is not intended as a tutorial on how to use in practice the chains it introduces.
– section 5.15 [Appendix 5D, “The most distinctive feature of all our chains”] is an important addition, intended to make still more explicit two essential points of our “philosophy” of chains as logical patterns: a chain is a continuous sequence of candidates (of course, with additional conditions specific to the type of chain) and it has an intrinsic length defined as the number of CSP-Variables involved in its definition; this is in strong contrast to the traditional view of a chain as a chain or network of inferences with complexity defined by the number of “nodes” (i.e. of inference steps) it involves; the difference is particularly noticeable in chains with z- and/or t- candidates; our definition of length is in perfect agreement with our view that such candidates are not part of the chains; it is also what allows to give a pure logic definition of chains.
– section 6.6 [“How well the W rating approximates the B (and many other) rating(s)”] is an extension of the corresponding short section in PBCS2, with the resolution power of many patterns compared to whips; it justifies why whips are given a central place in our approach.
– section 12.5 [“Requirements on the number of steps”] deals with several additional requirements one can put on the number of steps in a resolution path; such requirements have become familiar in the Sudoku community; they go much beyond the fundamental “pattern based” requirement adopted in this book; we show that there are ways to use resolution rules to deal with them; we also show that requirements on the number of steps can only be reasonable if they take into account the ratings obtained by the simplest-first strategy, i.e. if they put an a priori bound (not too much higher than the rating) on the length of chains; as this is more a matter of coding procedures using resolution rules in various T&E-ish ways than of defining and studying such rules, we leave most of this topic to the Basic User Manual for CSP-Rules-V2.1.
– section 17.10.2 [“Extended Quasi-Loops”] describes a useful generalisation of Quasi-Loops in Slitherlink.
Users browsing this forum: No registered users and 0 guests