After 16-, the position would be written as "16".
After 1(17)1[2-4] it would be"12L3".
After 5(18)5[6-11] it would be "6L5L3".
After 5(19)18[12-15] it would be "6+4P1L3".
After 16(20)19 it would be "6+4+3LPP1".
After 2(21)3 it would be "6+4+A3LPP1"
See attached diagram.
To denote whether a position is to be considered in normal or misere
play, I propose adding a "+" or "-" suffix, and enclosing the position
in parenthesis if it already contains a "+" symbol. For example:
16-
(3LPP1+4+6)+
Note that a chain of pivots and loops can be written in two ways
("forwards" and "backwards"). I propose starting with the end that has
the largest number. For example, "6L5L3" is to be preferred over
"3L5L6", and "A3LPP1" is to be preferred over "PP1LA3".
[1] Peltier, Jeff. (2008-06-08) "Playing Sprouts with Misere Grundy
Tables" <http://www.geocities.com/chessdp/SproutsMisereGrundy2007-4.htm>
Simply "16" can often be ambiguous. How about something that stands out as more specialized for those ambiguous situations. I mean "16" is great in contexts such as "16+3P2". But if someone says, "I am now going to discuss 16," the meaning is not so clear. I suggest we say, "I am now going to discuss 16NC" in the latter case and "16+3P2" in the former.
After 1(17)1[2-4] it would be"12L3".
After 5(18)5[6-11] it would be "6L5L3".
After 5(19)18[12-15] it would be "6+4P1L3".
After 16(20)19 it would be "6+4+3LPP1".
After 2(21)3 it would be "6+4+A3LPP1"
(I would guess, though, that at some point a fundamental redesign encompassing those preliminary, somewhat ad hoc conventions might be desireable. For instance, we are calling a circle with one pivot a "P" and a circle with two pivots an "L". What if there are more than two pivots? Similarly, line segments with multiple pier spots call for a more generalized approach.)
I know what you mean, but a fundamental redesign seems to me
unwarranted. Pivot/loop notation was never intended to be
all-encompassing -- that's for AJS notation and derivatives. I believe
the a large fraction of the positions in modern tournament sprouts can
be represented in an extended pivot/loop notation, perhaps with a few
slight modifications not yet discussed here. Pivot/loop notation has
proven its usefulness in analysis and communication, even without
these extensions. Rather than fundamentally re-design it when we need
to discuss positions that it cannot describe, I think we should
instead describe those positions with an AJS-like notation such as
Glop notation.
I'd suggest angle braces again (because they look cleaner to me, the
necessity of escaping them in HTML notwithstanding). So I'd say 3P4
means 3<1>4 and 3L4 means 3<2>4 and then we'd have 3<3>3, 3<4>3, etc.
It's all quite logical, but in practice I rarely see a position like
x<3>y in tournament play, and we already have BL ("big loop") for
X<4>Y.
I propose that this position be written as 1L3(L1)(L2).
> I don't like any sort of parenthesis which I can't read as I always need to
> check first for right nesting and closure.
When writing down positions like the one above, I don't know of a way
to remain elegant and compact way without the use of some kind of
nesting parenthesis.
> Another possibility once used by Yper was to use letters for English numbers
> : T for three pier Spots, F for Four, Fi for Five, S for Six, Se for Seven,
> E for Eight, N for Nine, Te for Ten...
Arguments about notation can be endless, but I can't resist speaking
out against this particular idea. To go beyond P and L, Danny's way is
better. I think Roman uses something similar to Danny's approach in
his own analysis, so it can't be all bad.
I'm not sure what you mean by numbers polluting the position. Your notation already has cardinal numbers. My proposal is just to use additional cardinal numbers (in curly brackets) to specify additional pivots or pier spots. If Josh is correct that these positions will be rare, then I think my suggestion is all the more compelling because it is very easy to remember, and rarely rehearsed expedients are better if easily remembered.
I agree with you about parentheses, except, it is arguably better to have an available method than to have no method at all. If the notation is to accomodate your example, then it suddenly becomes powerful enough to specify quite complex positions. But to my mind, that's a good thing. And, at least for the given example, Josh's suggested 1L3(L1)(L2) is elegant.
My second proposal was for an entirely different type of notation. I much admire your idea "it is a sort of canonization of a position". Yes, that is an important purpose, and I suggest that we might call your notation "canonization notation". The other notation that I am proposing is less needed, but it would be nice to have a simple way to specify starting positions, positions that we wish to analyze, without having to run through a sequence of moves. Instead of "10 1(11)1[2-9] 2(12)2[3] 4(13)4[5,6]" we can say "1{2,3}4-6({7,8}9)({10,11}12,13)", though now I am wondering if that is really any more convenient.
Sadly, it seems impossible to extend canonization notation enough for any possible position to be specified by it. But here is a sprouts variant that occurs to me. "Canonizable sprouts" is played just like ordinary sprouts except that moves creating positions not specifiable by canonization notation are prohibited.
Danny
I think Roman *already* plays his moves this way, except perhaps at
the very end of the game. Furthermore, his moves are such that the
only replies available to his opponent are also specifiable by the
canonization notation!
I expect this greatly simplifies analysis.