tarek wrote:the ALS xz rule specifies an "x" and a "z" which is fine and understandable.
dfhwze mentioned something which also correct that the consensus was that for for an wxyz wing, the "w" is actually the candidate constrained to a sector with a wz cell which goes to say that in a vwxyz, the "v" is the candidate that should be constrained to a sector with a vz cell.
If bennys had followed that line of thinking, we might today have the insanity of an xz-rule, a wz-rule, a vz-rule, etc.
tarek wrote:so the example from an ALS xz rule point of view is as ronk mentioned...
- Code: Select all
. . . | . . .
wyz wyz . |wxyz * *
. . . | . xz .
however from the general consensus about wings, this should be:
- Code: Select all
. . . | . . .
xyz xyz . |wxyz * *
. . . | . wz .
I think most people quickly understand that the letters are just placeholders. Exchanging 'w' and 'x' in one of the above produces the other. If you have a classical wxyz and see 1234 in the "pilot cell", do you assume w=1?
tarek wrote:for a classic wing IMO:
1. ALS1 should have ONLY one cell containing all candidates of the ALS (& that cell is the only cell containing "x" according to ALS xz opinion, or the only cell containing a "w" according to the general consensus of understanding wxyz wings) - that should serve as the pilot cell.
I have no problem with that being a requirement of the "classical" wxyz-wing.
tarek wrote:2. ALS2 should be a bivalued cell which is EXACTLY xz according to the ALS xz rule or exactly wz according to the general consesus of understanding wxyz wings(or vz if VWXYZ or uz if UVWXYZ).
That is precisely where a re-description should occur IMO ... so that the candidate constrained to one unit (group, sector) is always 'x'.
As our base of knowledge expands, it becomes prudent to occasionally re-describe the old knowledge base in order to unify the entire knowledge base. This doesn't invalidate the old knowledge base.
Ron