Difference between revisions of "Peep"
(Changing the direction of the redirect, as the term "peep" seems more common in Hex than "nozoki") |
m (Capitalization) |
||
(6 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
− | A '''peep''' is a [[Forcing moves|forcing move]] | + | A '''peep''' is a move in a specific region such that |
+ | * looking just at that region, it would normally be a [[Forcing moves|forcing move]] (even if the global situation means the opponent should respond elsewhere), and | ||
+ | * if the opponent does respond in that region (rather than merely close to it), then the exchange does not help the opponent and may help the player who played the peep. | ||
− | + | This situation occurs if one threatens to cut a connection between major groups or key stones of the opponent, or to create a connection between one's own major groups or key stones. | |
− | + | Sometimes it's hard to tell if a move is sufficiently [[Forcing moves|forcing]], and whether the opponent can gain by resisting, rather than just responding in the obvious way. Playing correct peeps is one of the most sophisticated aspects of Hex strategy. | |
− | == | + | The term "peep" is borrowed from the game of Go. Another term for peep, also borrowed from Go but less frequently used, is '''nozoki'''. |
+ | |||
+ | == Examples == | ||
+ | |||
+ | === Bridge peep === | ||
+ | |||
+ | By far the most common form of peep is a "bridge peep". That is, playing the correct side of a [[bridge]] which is [[Bolstered template|bolstered]] on exactly one side. | ||
+ | <hexboard size="3x3" | ||
+ | visible="-(a1 c3)" | ||
+ | edges="none" | ||
+ | coords="none" | ||
+ | contents="R c1 b3 B E *:c2 a:b2 S red:(b1 a3) blue:a2" | ||
+ | /> | ||
+ | If at least one of the shaded hexes is occupied by a piece of the indicated color, then Blue playing "*" is a peep. This is because in such cases, Red playing "*" would [[Dead cell|kill]] ''a''. Therefore, if Red just defends the [[bridge]], then Blue can't do any better here than Blue playing "*" and Red responding at ''a''. | ||
+ | |||
+ | === Ziggurat peep === | ||
+ | |||
+ | Similarly to the bridge peep, there can also be peeps at other templates, with suitable surrounding conditions. For example, consider the following position, where Red is connected to the bottom edge by a [[ziggurat]]. | ||
+ | <hexboard size="4x5" | ||
+ | visible="-(d1 c1 b2 b1 a2 a1)" | ||
+ | edges="bottom right" | ||
+ | coords="bottom right" | ||
+ | contents="B a3 R c2 S area(d4,a4,c2,d2)" | ||
+ | /> | ||
+ | If Red just defends the ziggurat, then Blue can't do any better here than Blue getting the outside of the ziggurat and c2 connecting down. | ||
+ | <hexboard size="4x5" | ||
+ | visible="-(d1 c1 b2 b1 a2 a1)" | ||
+ | edges="bottom right" | ||
+ | coords="bottom right" | ||
+ | contents="B a3 R c2 S area(d4,a4,c2,d2) B d2--d4 R b4" | ||
+ | /> | ||
+ | Blue d2 [[captured cell|captures]] the entire corner, turning the corner into this: | ||
+ | <hexboard size="4x5" | ||
+ | visible="-(d1 c1 b2 b1 a2 a1)" | ||
+ | edges="bottom right" | ||
+ | coords="bottom right" | ||
+ | contents="B a3 R c2 S area(d4,a4,c2,d2) B area(d2,d4,e4,e1) 1:d2 E *:b4" | ||
+ | /> | ||
+ | So Blue d2 is a peep at Red's ziggurat. | ||
+ | |||
+ | Note that d2 [[dominated cell|dominates]] d3 by [[Dominated cell#Capture-domination|capture-domination]]. | ||
+ | Conversely, Blue d3 dominates d2, because d3 also [[captured cell|captures]] the entire corner: | ||
+ | <hexboard size="4x5" | ||
+ | visible="-(d1 c1 b2 b1 a2 a1)" | ||
+ | edges="bottom right" | ||
+ | coords="bottom right" | ||
+ | contents="B a3 R c2 S area(d4,a4,c2,d2) B area(d2,d4,e4,e1) 1:d3 E *:b4" | ||
+ | /> | ||
+ | Namely, d3 first captures e2 and e3, then d4 and e4, and finally d2 and e1 by this capture pattern: | ||
+ | <hexboard size="4x4" | ||
+ | coords="none" | ||
+ | edges="none" | ||
+ | visible="area(d1,a3,b4,d2)" | ||
+ | contents="B d1--d2--b4 R a3 S blue:(b3 c2)" | ||
+ | /> | ||
+ | Therefore, the moves d2 and d3 are [[Dominated_cell#Mutually_dominating_moves|equivalent]] for Blue, and both are peeps at Red's ziggurat. | ||
+ | == Automatic peep == | ||
+ | |||
+ | If Red just completed a bridge and Blue has a bridge peep such that cutting off the bridge would kill the stone Red just played, then Blue should play the bridge peep. This is called an ''automatic bridge peep''. More precisely, if Blue was winning before Red's move, then Blue will still be winning after playing the automatic bridge peep. | ||
+ | |||
+ | For example, consider the following situation, where Red just played at 1: | ||
<hexboard size="6x6" | <hexboard size="6x6" | ||
− | + | coords="none" | |
− | + | edges="bottom left" | |
− | + | contents="B d5 d4 f1 R f3 d2 1:e3 E a:d3 b:e2 S (e2,e3,d2,d3)" | |
+ | /> | ||
− | + | Because the shaded bridge is [[bolstered template|bolstered]] on the b-side, a is a peep. Moreover, if Blue had both a and b, the red stone at 1 would be [[dead cell|dead]]. Therefore, this is an automatic peep and Blue should play at a. (More precisely, if Blue was winning before Red played at 1, then Blue playing at a preserves the win. If Blue was in fact losing before Red played at 1, then Blue playing at a may be losing and Blue may potentially have a winning move elsewhere. In any case, the situation after Blue plays at a is no worse for Blue than before Red played at 1.) | |
+ | |||
+ | There is an analogous notion of automatic peep for ziggurat peeps. | ||
− | |||
== Crucial peep == | == Crucial peep == | ||
Line 38: | Line 102: | ||
/><br/> | /><br/> | ||
− | == | + | == Bad peeps == |
+ | |||
+ | There are several possible reasons a peep can be bad. Here are some of them: | ||
+ | |||
+ | * Due to circumstances outside of the region, the apparent cutting threat does not actually work, in which case the peep is close to a [[irrelevant move|wasted move]]. | ||
+ | * While the apparent threat does work, it's not a big enough threat for the opponent to respond by defending against it. | ||
+ | * The opponent benefits by resisting the peep. | ||
+ | * The opponent can [[Minimax|minimax]], rather than answering more locally. | ||
+ | |||
+ | For example, consider the following situation, with Blue to move: | ||
+ | <hexboard size="8x8" | ||
+ | coords="none" | ||
+ | contents="R a3 e4 e5 d7 g7 B e2 d3 d5 f6 E a:g1 b:f3 *:d6 c:e6 d:g4" | ||
+ | /> | ||
+ | Here, Blue can win fairly easily by playing at ''a'' or ''b''. But suppose that Blue instead decides to play the bridge peep at "*". If Red defends the bridge at ''c'' as Blue expects, then Blue still wins by playing ''a'' or ''b''. However, if Red instead responds to the peep with a [[Minimax|minimaxing]] move at ''d'', Red wins. | ||
+ | <hexboard size="8x8" | ||
+ | coords="none" | ||
+ | contents="R a3 e4 e5 d7 g7 2:g4 B e2 d3 d5 f6 1:d6" | ||
+ | /> | ||
+ | Thus, the bridge peep was a bad peep in this situation. | ||
+ | |||
+ | == Resisting a peep == | ||
+ | |||
+ | Rather than responding in the obvious way, the opponent can play a move that mitigates against the peep's threat, while also getting something else. The most common example of this is [[Foiling|foiling]]. | ||
+ | |||
+ | For example, in response to Red's peep 1 in the following diagram, Blue can play 2 instead of *: | ||
+ | |||
+ | <hexboard size="5x6" | ||
+ | visible="-area(a1,a4,d1)" | ||
+ | edges="bottom" | ||
+ | coords="none" | ||
+ | contents="R e1 d2 1:e3 B f2 d3 2:d4 E *:e2" | ||
+ | /> | ||
+ | |||
+ | Red could have gotten a 2nd row ladder towards the right, but after 1 and 2, a red ladder towards the right would be a 3rd row ladder. | ||
+ | |||
+ | Note that this does not necessarily mean the peep was bad. For example, Red could be fine with a 3rd row ladder, and Red can now get c2 before pushing the ladder: | ||
+ | <hexboard size="5x6" | ||
+ | edges="left bottom" | ||
+ | coords="left bottom" | ||
+ | contents="R e1 d2 1:e3 3:c2 5:e2 B f2 d3 b2 2:d4 4:b4" | ||
+ | /> | ||
+ | Whereas if Red had started with c2, then Blue would presumably just defend the bridges. | ||
+ | <hexboard size="5x6" | ||
+ | edges="left bottom" | ||
+ | coords="left bottom" | ||
+ | contents="R e1 d2 1:c2 3:e3 5:c4 B f2 d3 b2 2:b4 4:e2 6:c3" | ||
+ | /> | ||
− | * | + | The consequences of resisting a peep can also be much harder to assess. In the following example, Red chose to resist Blue's peep 1 by playing at 2, rather than just playing *. |
+ | <hexboard size="6x8" | ||
+ | visible="" | ||
+ | edges="left bottom" | ||
+ | coords="none" | ||
+ | contents="B e1 g3 1:g1 R arrow(12):h1 f2 2:d3 E *:g2" | ||
+ | /> | ||
− | |||
[[category: Definition]] | [[category: Definition]] | ||
+ | [[category: Advanced Strategy]] |
Latest revision as of 00:27, 16 August 2022
A peep is a move in a specific region such that
- looking just at that region, it would normally be a forcing move (even if the global situation means the opponent should respond elsewhere), and
- if the opponent does respond in that region (rather than merely close to it), then the exchange does not help the opponent and may help the player who played the peep.
This situation occurs if one threatens to cut a connection between major groups or key stones of the opponent, or to create a connection between one's own major groups or key stones.
Sometimes it's hard to tell if a move is sufficiently forcing, and whether the opponent can gain by resisting, rather than just responding in the obvious way. Playing correct peeps is one of the most sophisticated aspects of Hex strategy.
The term "peep" is borrowed from the game of Go. Another term for peep, also borrowed from Go but less frequently used, is nozoki.
Contents
Examples
Bridge peep
By far the most common form of peep is a "bridge peep". That is, playing the correct side of a bridge which is bolstered on exactly one side.
If at least one of the shaded hexes is occupied by a piece of the indicated color, then Blue playing "*" is a peep. This is because in such cases, Red playing "*" would kill a. Therefore, if Red just defends the bridge, then Blue can't do any better here than Blue playing "*" and Red responding at a.
Ziggurat peep
Similarly to the bridge peep, there can also be peeps at other templates, with suitable surrounding conditions. For example, consider the following position, where Red is connected to the bottom edge by a ziggurat.
If Red just defends the ziggurat, then Blue can't do any better here than Blue getting the outside of the ziggurat and c2 connecting down.
Blue d2 captures the entire corner, turning the corner into this:
So Blue d2 is a peep at Red's ziggurat.
Note that d2 dominates d3 by capture-domination. Conversely, Blue d3 dominates d2, because d3 also captures the entire corner:
Namely, d3 first captures e2 and e3, then d4 and e4, and finally d2 and e1 by this capture pattern:
Therefore, the moves d2 and d3 are equivalent for Blue, and both are peeps at Red's ziggurat.
Automatic peep
If Red just completed a bridge and Blue has a bridge peep such that cutting off the bridge would kill the stone Red just played, then Blue should play the bridge peep. This is called an automatic bridge peep. More precisely, if Blue was winning before Red's move, then Blue will still be winning after playing the automatic bridge peep.
For example, consider the following situation, where Red just played at 1:
Because the shaded bridge is bolstered on the b-side, a is a peep. Moreover, if Blue had both a and b, the red stone at 1 would be dead. Therefore, this is an automatic peep and Blue should play at a. (More precisely, if Blue was winning before Red played at 1, then Blue playing at a preserves the win. If Blue was in fact losing before Red played at 1, then Blue playing at a may be losing and Blue may potentially have a winning move elsewhere. In any case, the situation after Blue plays at a is no worse for Blue than before Red played at 1.)
There is an analogous notion of automatic peep for ziggurat peeps.
Crucial peep
Playing peeps can be very useful. In certain situations, playing a peep can make the difference between winning and losing. Consider the following example:
The only winning move for Red is the peep at d6. If Red misses it, the game proceeds as follows and Blue wins:
If Red starts by playing d6 instead, Red wins.
Bad peeps
There are several possible reasons a peep can be bad. Here are some of them:
- Due to circumstances outside of the region, the apparent cutting threat does not actually work, in which case the peep is close to a wasted move.
- While the apparent threat does work, it's not a big enough threat for the opponent to respond by defending against it.
- The opponent benefits by resisting the peep.
- The opponent can minimax, rather than answering more locally.
For example, consider the following situation, with Blue to move:
Here, Blue can win fairly easily by playing at a or b. But suppose that Blue instead decides to play the bridge peep at "*". If Red defends the bridge at c as Blue expects, then Blue still wins by playing a or b. However, if Red instead responds to the peep with a minimaxing move at d, Red wins.
Thus, the bridge peep was a bad peep in this situation.
Resisting a peep
Rather than responding in the obvious way, the opponent can play a move that mitigates against the peep's threat, while also getting something else. The most common example of this is foiling.
For example, in response to Red's peep 1 in the following diagram, Blue can play 2 instead of *:
Red could have gotten a 2nd row ladder towards the right, but after 1 and 2, a red ladder towards the right would be a 3rd row ladder.
Note that this does not necessarily mean the peep was bad. For example, Red could be fine with a 3rd row ladder, and Red can now get c2 before pushing the ladder:
Whereas if Red had started with c2, then Blue would presumably just defend the bridges.
The consequences of resisting a peep can also be much harder to assess. In the following example, Red chose to resist Blue's peep 1 by playing at 2, rather than just playing *.