User:Hexanna - Revision history

Hexanna at 18:52, 29 March 2026

2026-03-29T18:52:37Z

Hexanna: remove old stuff

2026-03-29T18:51:25Z

remove old stuff

Hexanna: opening database

2026-03-29T18:42:36Z

opening database

Hexanna: joseki explorer

2026-03-24T02:30:28Z

joseki explorer

Hexanna: hex local pattern explorer

2026-03-18T00:11:33Z

hex local pattern explorer

Hexanna: Hexata has branching move history now

2026-03-13T22:35:21Z

Hexata has branching move history now

Hexanna: current projects

2026-03-01T00:50:37Z

current projects

Hexanna: update elo-based swap map

2026-01-31T16:05:07Z

update elo-based swap map

Hexanna: new lightweight GUI

2026-01-31T15:43:46Z

new lightweight GUI

Hexanna at 03:56, 20 December 2025

2025-12-20T03:56:57Z

@@ Line 169: / Line 169: @@
 ==katahex/general strategy (draft material)==
 * Acute corner joseki continuations. Red 7 is an inaccuracy but this is a common joseki: https://hexworld.org/board/#19nc1,e6e4d4e3d3d5c7f2b7c5b10i2. Study the "continuation" moves Red 11 and Blue 12, and study similar moves in related joseki.
 ** For example, gain intuition for why Red 13 is the best move in https://hexworld.org/board/#19nc1,d5d4c5c3b4b3e4f2c4d3g3:pb8 (a5/b5 are captured by Red; see [[Theorems_about_templates#The_shape_of_templates]]), why Red 17 is the best move in https://hexworld.org/board/#19nc1,e6e5d6d4c5c4f5g3d5e4h4i2b5b4j3:pc9, and why other moves are weak.

@@ Line 14: / Line 14: @@
 * [https://hexanna1.github.io/hex-study/openings.html Opening explorer] with opening lines on sizes 11&ndash;14 and 17
 * Of these tools, I put the most thought into the design of the local pattern explorer, and it's probably the most useful one for improving at Hex.
 ==draft of more strategy stuff==
@@ Line 176: / Line 169: @@
 ==katahex/general strategy (draft material)==
 * Acute corner joseki continuations. Red 7 is an inaccuracy but this is a common joseki: https://hexworld.org/board/#19nc1,e6e4d4e3d3d5c7f2b7c5b10i2. Study the "continuation" moves Red 11 and Blue 12, and study similar moves in related joseki.
 ** For example, gain intuition for why Red 13 is the best move in https://hexworld.org/board/#19nc1,d5d4c5c3b4b3e4f2c4d3g3:pb8 (a5/b5 are captured by Red; see [[Theorems_about_templates#The_shape_of_templates]]), why Red 17 is the best move in https://hexworld.org/board/#19nc1,e6e5d6d4c5c4f5g3d5e4h4i2b5b4j3:pc9, and why other moves are weak.

@@ Line 9: / Line 9: @@
 * The CLI is primarily intended for AI coding tools and scripts. For example, I have used it to proofread and validate some of the KataHex eval claims made in my articles.
-[https://hexanna1.github.io/hex-study/ Hex Study Tools] is a collection of interactive tools/mini-databases. There are pages for [https://hexanna1.github.io/hex-study/patterns.html local patterns] and [https://hexanna1.github.io/hex-study/joseki.html josekis].
+[https://hexanna1.github.io/hex-study/ Hex Study Tools] is a collection of interactive databases:
-* The local pattern explorer is the more refined tool, and probably the more useful one for improving at Hex.
+* [https://hexanna1.github.io/hex-study/patterns.html Local pattern explorer] with up to 5-stone local patterns
 ==current projects==

@@ Line 9: / Line 9: @@
 * The CLI is primarily intended for AI coding tools and scripts. For example, I have used it to proofread and validate some of the KataHex eval claims made in my articles.
-[https://hexanna1.github.io/hex-study/ Hex Local Pattern Explorer]
+[https://hexanna1.github.io/hex-study/ Hex Study Tools] is a collection of interactive tools/mini-databases. There are pages for [https://hexanna1.github.io/hex-study/patterns.html local patterns] and [https://hexanna1.github.io/hex-study/joseki.html josekis].
 ==current projects==

@@ Line 8: / Line 8: @@
 * One of the GUI's main advantages (and a primary reason I created it) is that it's fast and responsive. It's not as useful for "traditional" analysis as some other GUI's &mdash; it doesn't support adding comments to moves, for example.
 * The CLI is primarily intended for AI coding tools and scripts. For example, I have used it to proofread and validate some of the KataHex eval claims made in my articles.
 ==current projects==
@@ Line 14: / Line 16: @@
 * using Hexata CLI in vibe-coded scripts to understand Hex better
 ** this is harder than I anticipated; there are a lot of decisions to make and a lot of things that could go wrong
-** for example: I've been trying to understand the strength of stones relative to local patterns in a more systematic way (removing bias introduced by the board edges and other sources of noise). I have always preferred using larger boards like 25&times;25 because the center of the board is far away from the edges, and katahex evals are further away from unstable 0% or 100% regions. I checked whether my methodology gave a consistent result across board sizes. unfortunately, it didn't, even though "the strength of stones relative to local patterns" is a concept that's theoretically independent of board size. preliminary investigation of this inconsistency shows that &mdash; despite the application of appropriate noise-reduction methods &mdash; there appears to be a systematic bias to its evals (on katahex 20240812) that becomes visible around the size 22&rarr;23 boundary and gets progressively worse as board size increases. so, many of my 25&times;25 analyses on local patterns are slightly wrong (luckily, I didn't use a larger size like 31 where the bias is more severe); a smaller size like 20&ndash;22 may be optimal for this net. (usual caveat: this finding is specific to katahex 20240812 and does not generalize to other nets. it does not imply that size 25 is categorically worse than sizes 20&ndash;22 for other kinds of analyses.)
+** for example: I've been trying to understand the strength of stones relative to local patterns in a more systematic way (removing bias introduced by the board edges and other sources of noise). I have always preferred using larger boards like 25&times;25 because the center of the board is far away from the edges, and katahex evals are further away from unstable 0% or 100% regions. I checked whether my methodology gave a consistent result across board sizes. unfortunately, it didn't, even though "the strength of stones relative to local patterns" is a concept that's theoretically independent of board size. preliminary investigation of this inconsistency shows that &mdash; despite the application of appropriate noise-reduction methods &mdash; there appears to be a systematic bias to its evals (on katahex 20240812) that becomes visible around the size 22&rarr;23 boundary and gets progressively worse as board size increases, as illustrated in [https://github.com/hexanna1/hex-study/blob/main/results/board_size_vs_canonical_key_stone_fraction_d3.png this graph]. so, many of my 25&times;25 analyses on local patterns are slightly wrong (luckily, I didn't use a larger size like 31 where the bias is more severe); a smaller size like 20&ndash;22 may be optimal for this net. (usual caveat: this finding is specific to katahex 20240812 and does not generalize to other nets. it does not imply that size 25 is categorically worse than sizes 20&ndash;22 for other kinds of analyses.)
 ==draft of more strategy stuff==

@@ Line 6: / Line 6: @@
 [https://github.com/hexanna1/hexata Hexata] is a GUI and CLI for analyzing Hex that I vibe-coded. It's still under active development, but I already use it as my main GUI.
-* One of the GUI's main advantages (and a primary reason I created it) is that it's fast and responsive. It's not as useful for "traditional" analysis as some other GUI's &mdash; it doesn't support adding comments to moves, or branching move history.
+* One of the GUI's main advantages (and a primary reason I created it) is that it's fast and responsive. It's not as useful for "traditional" analysis as some other GUI's &mdash; it doesn't support adding comments to moves, for example.
 * The CLI is primarily intended for AI coding tools and scripts. For example, I have used it to proofread and validate some of the KataHex eval claims made in my articles.

@@ Line 5: / Line 5: @@
 I started learning Hex mid-July of 2021, about 2 weeks before I created my LittleGolem account.
-[https://github.com/hexanna1/hexata Hexata GUI]
+[https://github.com/hexanna1/hexata Hexata] is a GUI and CLI for analyzing Hex that I vibe-coded. It's still under active development, but I already use it as my main GUI.
-[https://github.com/hexanna1/hex-scripts Hex scripts]
+==current projects==
 ==draft of more strategy stuff==
 There's a fair amount of stuff for [[Strategic advice from KataHex]] that I've either been too lazy to write up / polish, or haven't thought of a good way to explain. I also haven't properly conveyed which things are important; some things come up rarely and should either be mentioned briefly or cut for the article. There's also a tradeoff in generality/specificity and concreteness/abstractness.
 * terminology: inaccuracy < mistake < blunder

@@ Line 239: / Line 239: @@
 # It's fun to try to trick players into swapping a weak move or not swapping a deceptively strong move. :)
-==Insights and tidbits from KataHex (hzy's bot)==
+==Insights and tidbits from [[KataHex]]==
-* Swap map for 19&times;19 generated with net 20220618, with around 15k visits for most moves. For the red hexes, the number corresponds to Blue's Elo advantage if she swaps Red's move; for the blue hexes, the number corresponds to Blue's Elo advantage if she does not swap Red's move. Smaller numbers correspond to fairer openings. Includes all fair openings as well as a few selected unfair openings, including the strongest move without swap (e10). I used more visits for the fairest moves: 1000k for e3 (49.5% win rate), 500k for n3 (49.2%), 100k for a15 (52.5%).
+* Swap map for 19&times;19 generated with KataHex net 20240812 using [https://github.com/hexanna1/hexata Hexata], with around 30k&ndash;40k visits for most moves. For the red hexes, the number corresponds to Blue's Elo advantage if she swaps Red's move; for the blue hexes, the number corresponds to Blue's Elo advantage if she does not swap Red's move. Smaller numbers correspond to fairer openings. Includes all fair openings as well as a few selected unfair openings, including the strongest move without swap (e10).
 : <hexboard size="19x19"
@@ Line 247: / Line 247: @@
    contents="S red:all blue:(a1--r1 a2--q2 a3 e3--n3 s3)
                blue:(a17 f17--o17 s17 c18--s18 b19--s19)
-             E 65:(d3 p17)
+             E 84:(d3 p17)
 :(e3 o17)
 :(f3 n17)
 :(g3 m17)
 :(h3 l17)
 :(i3 k17)
 :(j3 j17)
 :(k3 i17)
 :(l3 h17)
 :(m3 g17)
 :(n3 f17)
 :(o3 e17)
 :(p3 d17)
 :(h4 l16)
 :(i4 k16)
 :(j4 j16)
 :(k4 i16)
 :(l4 h16)
 :(m4 g16)
 :(i5 k15)
 :(j5 j15)
 :(k5 i15)
 :(q2 c18)
 :(p2 d18)
 :(b17 r3)
 :(b18 r2)
 :(a2 s18)
 :(b2 r18)
 :(c2 q18)
 :(d2 p18)
 :(a3 s17)
 :(b3 r17)
 :(c3 q17)
 :(a4 s16)
 :(b4 r16)
 :(a5 s15)
 :(a6 s14)
 :(a7 s13)
 :(a8 s12)
 :(a9 s11)
 :(a10 s10)
 :(a11 s9)
 :(a12 s8)
 :(a13 s7)
 :(a14 s6)
 :(a15 s5)
 :(a16 s4)
 :(a17 s3)
 :(a18 s2)
 :(a19 s1)
 :(e10 o10)"
    />

@@ Line 77: / Line 77: @@
 ** On the other hand, playing a bridge away from your own stone is frequently strong &mdash; such moves should generally be on your radar.
 ** If you play adjacent or a bridge away from an opponent stone, you should expect an increased chance that the next few moves are all in the vicinity. That helps with pruning and deciding which lines to analyze more deeply.
 <hexboard size="3x3" float="inline" edges="none" coords="none" contents="R b1 c1 B -:b2 a3 E *:c2" />
@@ Line 88: / Line 90: @@
 *: <hexboard size="5x5" float="inline" edges="bottom left" coords="none" contents="B 1:d2 R 2:c3 B 3:e1 R 4:c2 E *:d3"
 /> <hexboard size="6x6" float="inline" edges="bottom left" coords="none" contents="B 1:f1 R 2:d2 B 3:d3 R 4:e2 B 5:d4 R 6:c3" />
 ===Ladders===