Lake, Nakade, Eye, Eyespace and Related Terms

For lessons, as well as threads about specific moves, and anything else worth studying.
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

As a motivation, here is an example:

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | S X S S S X X X M O . . . . . . . . . |
$$ | X X X X X X S X M . . . . . . . . . . |
$$ | S X M M M M M M M O . . . . . . . . . |
$$ | M X M M M M M M M , . . . . . , . . . |
$$ | M M M M M M M M O . . . . . . . . . . |
$$ | . O O . O . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ +---------------------------------------+[/go]


If considered generously, the 'potential eyespace' of the black group consists of all marked intersections. The squares denote the group's four 'lakes', where each connected part of squared intersections is a lake.

- The upper left lake is one eye.
- The upper lake is worth 1.5 eyes.
- The left lake is worth 0.5 eyes.
- The lower right lake is worth 0.5 eyes.

The lakes are parts of the eyespace that, in a life and death situation, tend to be the parts with good potential for becoming eyes. If there is only one lake, the defender wants to partition it, while the attacker wants to convert it to (create) a nakade:

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | S S S X . . . . . . . . . . . . . . . |
$$ | X X X X . O . . . . . . . . . . . . . |
$$ | . . . . O . . . . . . . . . . . . . . |
$$ | O . O , . . . . . , . . . . . , . . . |
$$ | . O . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |[/go]


Black wants to partition the lake, White wants to create a nakade. The outside can be called 'potential eyespace', but usually Black cannot construct additional lakes there.

"A LAKE is a connected part of the potential eyespace of the defender's group that is, or can easily become, visually surrounded by his stones [...]"

John has mentioned 'futokoro', but I have never heard of this term; maybe it has always been translated to 'eyespace', 'eye' or something similar. Would you now say that it has about the same meaning as 'lake'?

An eyespace can, but need not, contain lakes.

Presumably, I use nakade with a somewhat different meaning from the one you use. This, however, does not make my use wrong. I have seen different uses in the English literature. Therefore, when I use nakade, I also explain the meaning that I use:

"Simply speaking, a NAKADE is a lake, so that
1. the defender can fill all but one of its intersections,
2. the defender cannot partition it and
3. there cannot be a seki or ko in it."

Unlike you have guessed, I do not use nakade as a shape term. As you can infer from the approximative definition, I define it as a lake, i.e., as a part of the board, or you might say: "a set of intersections" or "connected part of the potential eyespace".

Furthermore, I use the term "create a nakade" for a play that, surprise, does create a nakade. I.e., I would describe the part of the board just before the move as "a part of the board that a play of the kind 'creating a nakade' can transform into a nakade". The previous example is such a part of the board.

The clarity of restricting the meaning of 'nakade' to a part after the interesting play allows us to perceive well the kind of play 'creating a nakade'. This is what the attacker wants: to make a play that creates a nakade. With this clear understanding of a move meaning, solving life and death situations is eased.

Other uses of 'nakade' exist, but I have found none else similarly useful when thinking about how to solve an LD problem.

Whichever use of nakade somebody (or a particular text) uses, it is bound to be in conflict with other uses of the word. This is a bit unfortunate, but it cannot be avoided, because we are in the age of transition from ambiguous terms to terms with clear meanings. During the transition phase, different people might prefer different uses. Well, this is not ideal, but it is much better when everybody, who uses a term regularly, declares the meaning of his use than continue ambiguous use of undefined terms in a text.

The meanings of 'eye', 'nakade' etc. are not well established in the go world yet. Also 'eye' has a (great) variety of meanings from "potential eye" (during the middle game) to "final eye" (as in scoring positions after completely finished yose). A potential eye can, but need not, become a final eye. Similarly, there are potential versus final eyespace of a group. Other varieties of meanings exist.
User avatar
Cassandra
Lives in sente
Posts: 1326
Joined: Wed Apr 28, 2010 11:33 am
Rank: German 1 Kyu
GD Posts: 0
Has thanked: 14 times
Been thanked: 153 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Cassandra »

Dear Robert,

There are several issues in your "definitions" that do not fit "common understanding".

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | . X . . . X X X M O . . . . . . . . . |
$$ | X X X X X X . X M . . . . . . . . . . |
$$ | . X . . . . . . M O . . . . . . . . . |
$$ | . X . . . . . . M , . . . . . , . . . |
$$ | M M M M M M M M O . . . . . . . . . . |
$$ | . O O . O . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |[/go]

These points can NEVER become part of Black's "eyespace", just because they will not remain empty. At most, they can become part of the outside bordering line of Black's group.

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | S X S S S X X X . O . . . . . . . . . |
$$ | X X X X X X . X . . . . . . . . . . . |
$$ | . X . . . . . . . O . . . . . . . . . |
$$ | . X . . . . . . . , . . . . . , . . . |
$$ | . . . . . . . . O . . . . . . . . . . |
$$ | . O O . O . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |[/go]

These points are Black's "eyespace" for SURE, as long as Black does not fill-in these points. They are NO LONGER part of "potential" eyespace.

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | . X . . . X X X . O . . . . . . . . . |
$$ | X X X X X X S X . . . . . . . . . . . |
$$ | S X . . . . . . . O . . . . . . . . . |
$$ | . X . . . . . . . , . . . . . , . . . |
$$ | . . . . . . . . O . . . . . . . . . . |
$$ | . O O . O . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |[/go]

At least these two points are part of Black's "potential eyespace" (irrelevant here, because Black's group is already alive).


If we take
"A LAKE is a connected part of the potential eyespace of the defender's group that is, or can easily become, visually surrounded by his stones [...]"
as the definition of "lake", then
"An eyespace can, BUT NEED NOT, contain lakes."
cannot be true (assuming that "eyespace" also includes "potential eyespace").
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
Bill Spight
Honinbo
Posts: 10905
Joined: Wed Apr 21, 2010 1:24 pm
Has thanked: 3651 times
Been thanked: 3373 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Bill Spight »

RobertJasiek wrote:As a motivation, here is an example:

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | S X S S S X X X M O . . . . . . . . . |
$$ | X X X X X X S X M . . . . . . . . . . |
$$ | S X C M M M M M M O . . . . . . . . . |
$$ | M X M M M M M M M , . . . . . , . . . |
$$ | M M M M M M M M O . . . . . . . . . . |
$$ | . O O . O . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ +---------------------------------------+[/go]


If considered generously, the 'potential eyespace' of the black group consists of all marked intersections. The squares denote the group's four 'lakes', where each connected part of squared intersections is a lake.

- The upper left lake is one eye.
- The upper lake is worth 1.5 eyes.
- The left lake is worth 0.5 eyes.
- The lower right lake is worth 0.5 eyes.


I have altered the diagram above. I think that we have to count :ec: as 0.5 eye (at least). :)

RobertJasiek wrote:Whichever use of nakade somebody (or a particular text) uses, it is bound to be in conflict with other uses of the word. This is a bit unfortunate, but it cannot be avoided, because we are in the age of transition from ambiguous terms to terms with clear meanings.


I am afraid that, as always, language tends to become less precise over time. One reason that go terms are ambiguous (when they are) is that they have been around for long enough to acquire new meanings. For instance, the root meaning of nakade is clear. It is a play inside an opponent's eye (specifically, a region of connected empty points surrounded by stones of one color). But other meanings have accrued.

Click Here To Show Diagram Code
[go]$$Bc Nakade
$$ ---------------------------------------
$$ | . 3 O O . . . . . . . . . . O O X . . |
$$ | 2 4 O O X X . . . . . . . . O X X O O |
$$ | 5 . O O . . . . . . . . . O O X X O O |
$$ | 1 O O , X . . . . , . . . . . X X X X |
$$ | O X X X . . . . . . . . . O . X X O O |
$$ | O O O . . . . . . . . . . . . . . O . |
$$ | . . . X X . . . . . . . . . O . O . . |
$$ | . X . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . , . . . . . , . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . X . |
$$ | . . . . . . . . . . . . . . . . X . . |
$$ | . O . O . . . . . . . . . . . . . X O |
$$ | . . . . . . . . . . . . . . . X X O . |
$$ | X X . O . . . . . , . . . . . , O O O |
$$ | . X . . O . . O . . . . . . X . O X X |
$$ | 2 . X X O . O . . . . . . . X O O X X |
$$ | X 3 . 4 X X . . . . . . . . . X O . X |
$$ ---------------------------------------[/go]


This example comes from the Gokyo Shumyo. :b1: in the top left is called a 7 point nakade. :w2: in the bottom left is called a 6 point nakade. Both of these are examples of the root meaning. The position in the bottom right is called a 5 point nakade. The position in the top right is called a 4 point nakade. These are accrued meanings, OC. :)
Last edited by Bill Spight on Sat Nov 09, 2013 5:47 am, edited 1 time in total.
The Adkins Principle:
At some point, doesn't thinking have to go on?
— Winona Adkins

Visualize whirled peas.

Everything with love. Stay safe.
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

Cassandra, ko threats can let more intersections become eyes. Of course, I get your point that my markup was very generous. For eyespaces, I am pragmatic and use a visual approach as a first approximation. For lakes, I am stricter and (was not cited) exclude 'simple boundary defects', i.e., intersections where necessarily the defender needs to fill. With a similar idea, we can be less generous and exclude the border intersections of the wide eyespaces.

Ok, if you want to distinguish potential from final eyespace early, you can do so by mentally partitioning an eyespace into its already final parts and its still potential parts. I have perceived the union of all the parts as one eyespace of the group; as a union, it is still a potential eyespace; when the outside shapes will be settled, the upper parts will remain and belong to the final eyespace. IOW, both approaches work, and it is a matter of choice which one wants to use.

Here is an example of a black group with a potential eyespace without lakes:

Click Here To Show Diagram Code
[go]$$B
$$ +---------------------------------------+
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . O . . . . . . . . |
$$ | . . . , . . . . . , . . . O . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . O . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . O . . . . . . . . . O . . . |
$$ | . . . , . . . . . X . . . . . , . . . |
$$ | . . . O . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . O . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . O . . . . |
$$ | . . . , . . . . . O . . . . . , . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ | . . . . . . . . . . . . . . . . . . . |
$$ +---------------------------------------+[/go]
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

Bill, I have wanted to test who understands lakes. You do:)
Boidhre
Oza
Posts: 2356
Joined: Mon Mar 05, 2012 7:15 pm
GD Posts: 0
Universal go server handle: Boidhre
Location: Ireland
Has thanked: 661 times
Been thanked: 442 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Boidhre »

Robert, may I ask, why the word "lake?" It really doesn't seem like a natural fit for this concept to me and sounds very out of place.
User avatar
Cassandra
Lives in sente
Posts: 1326
Joined: Wed Apr 28, 2010 11:33 am
Rank: German 1 Kyu
GD Posts: 0
Has thanked: 14 times
Been thanked: 153 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Cassandra »

Dear Robert,

Again, and again, your terminology is far, far away from "common understanding".

Again, and again, you do not understand that it is.

Again, and again, you divert into minor side-aspects of what has been written, or open new fields for discussion, as well as presenting childish "counter-examples".
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
User avatar
Bonobo
Oza
Posts: 2225
Joined: Fri Dec 23, 2011 6:39 pm
Rank: OGS 13k
GD Posts: 0
OGS: trohde
Universal go server handle: trohde
Location: Lüneburg Heath, North Germany
Has thanked: 8263 times
Been thanked: 925 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Bonobo »

Boidhre wrote:[..] why the word "lake?" It really doesn't seem like a natural fit for this concept to me and sounds very out of place.

Well, to me it doesn’t seem more “out of place” than “eyes” or the “racoon’s belly”.

I could adapt this word … I’ll have to think more about it, but something in it appeals to me. For me a lake (not “lah-keh” :-P ) is a big wet place where I could drown if I’m not careful. A few islands would be helpful … guess I must read up RJ’s definition.

BTW I like it that you, RJ, are using a geo-/topographical Real Life word as metaphor in Go :-D I wouldn’t have expected this.

Greetz, Tom
“The only difference between me and a madman is that I’m not mad.” — Salvador Dali
Bill Spight
Honinbo
Posts: 10905
Joined: Wed Apr 21, 2010 1:24 pm
Has thanked: 3651 times
Been thanked: 3373 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Bill Spight »

Boidhre wrote:Robert, may I ask, why the word "lake?" It really doesn't seem like a natural fit for this concept to me and sounds very out of place.


Oh, it's not a bad metaphor. Who knows, it might catch on. :)
The Adkins Principle:
At some point, doesn't thinking have to go on?
— Winona Adkins

Visualize whirled peas.

Everything with love. Stay safe.
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

Why lake? When I needed a term for the object, it was the word immediately occurring to my mind. Since then, I have always liked it. It is descriptive and short. For go, lake was not used as a term for something else. For a term needed frequently, these are very useful features.

Cassandra, with terms of "common understanding" / traditional terms, thinking and written text is nasty, clumsy, ambiguous and inefficient. Being far away from this state is a great advantage! LD is a complex topic, and it is essential to start with efficient language already for the basics. Otherwise, the situation remains as it is: LD theory is very weak in comparison other fields of go theory. Bad terms lead to bad theory, such as the proverb "1. reduce, 2. occupy vital point". We must overcome the current state of ca. 2/3 of all teachers teaching little else about LD than things like this bad proverb. Without proper tools (such as efficient terms), things do not change fast enough.
John Fairbairn
Oza
Posts: 3724
Joined: Wed Apr 21, 2010 3:09 am
Has thanked: 20 times
Been thanked: 4672 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by John Fairbairn »

Simply speaking, a NAKADE is a lake, so that
1. the defender can fill all but one of its intersections,
2. the defender cannot partition it and
3. there cannot be a seki or ko in it."


Again, there are lots and lots of people in the western go world who know some Japanese, so why be so obtuse as to misuse nakade like this? But my main question is:

Where does Gold Jade 7 and its seki fit in with this?

..
...
..
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

With a seki possible or existing, the thing is not a nakade. When the seki already exists, call it a 'seki'. When the seki does not exist yet, I call it a 'lake with a possible seki'. (If one wants to be more precise, one can state the two cases Black / White starts.) Similarly for ko, except that for historical reasons it would be called 'lake with a hidden ko' (the alternative is '...possible ko').

EDIT:

Defining 'nakade' in a specific way is done for the sake of profiting from this definition during its application as well as possible. When nakade is defined as I suggest, application is by far the easiest and most powerful. This is so, because such a nakade has very nice stable properties, which differ from the properties in the position preceding a nakade. E.g., the attacker wants to create the nakade and wants to get rid of the unsettled position preceding it. E.g., one can speak of 'creating a nakade' and, earlier, 'threatening to create a nakade', and these kinds of creating / threatening to create move meanings correspond consistently to the same kinds of other techniques for moves. Using the same words for things that have the same behaviour is much more useful than using the same word for things with different behaviours.

(An alternative terminology could be imagined: 'stable nakade' versus 'unstable nakade'. Then, one would need two words for the stable state. I prefer one word: 'nakade'. Simpler!)
User avatar
Cassandra
Lives in sente
Posts: 1326
Joined: Wed Apr 28, 2010 11:33 am
Rank: German 1 Kyu
GD Posts: 0
Has thanked: 14 times
Been thanked: 153 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by Cassandra »

RobertJasiek wrote:Cassandra, with terms of "common understanding" / traditional terms, thinking and written text is nasty, clumsy, ambiguous and inefficient. Being far away from this state is a great advantage! LD is a complex topic, and it is essential to start with efficient language already for the basics. Otherwise, the situation remains as it is: LD theory is very weak in comparison other fields of go theory. Bad terms lead to bad theory, such as the proverb "1. reduce, 2. occupy vital point". We must overcome the current state of ca. 2/3 of all teachers teaching little else about LD than things like this bad proverb. Without proper tools (such as efficient terms), things do not change fast enough.

Dear Robert,

It is carrying coals to Newcastle to let me know that Tsume-Go is complex.

As usual, you did not really understand what I tried to tell you.

"Common understanding" has "potential eyespace" as a subset of "eyespace". And knows that two solidly surrounded eyes are "sure" eyespace, not "potential".

In "your world", "potential eyespace" is the collecting term for solidly surrounded eyes (= "sure eyespace") and potential eyes. And this will not fit the expectation of the "usual" reader.
The really most difficult Go problem ever: https://igohatsuyoron120.de/index.htm
Igo Hatsuyōron #120 (really solved by KataGo)
RobertJasiek
Judan
Posts: 6273
Joined: Tue Apr 27, 2010 8:54 pm
GD Posts: 0
Been thanked: 797 times
Contact:

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by RobertJasiek »

Ok, you might be right about this. Anyway, the problem occurs only if a group has already 2 safe eyes. When one has determined that much, all further discussion is l'art pour l'art:)
hyperpape
Tengen
Posts: 4382
Joined: Thu May 06, 2010 3:24 pm
Rank: AGA 3k
GD Posts: 65
OGS: Hyperpape 4k
Location: Caldas da Rainha, Portugal
Has thanked: 499 times
Been thanked: 727 times

Re: Lake, Nakade, Eye, Eyespace and Related Terms

Post by hyperpape »

I like the term "lake", but it seems rather imprecise for you, Robert: why "visually surrounded"? And why "can become"? Under what conditions?
Post Reply