AIToday
AI Coding AssistantsQiita 機械学習Published: Nov 10, 2026, 04:00 JST

Gotsuzuri maker finds errors in own GT labels before AI training

Send on LINE
Gotsuzuri maker finds errors in own GT labels before AI training

3 Key Points

  1. What happened

    Working on Gotsuzuri, an Android app that turns photographed Go boards into game records, the developer expanded ground-truth data by 6 board setups and 12 photos, for a total of 21 images across 10 setups. While reviewing labels, he found his own labeling mistakes and black stones that even a human cannot confidently assign to an intersection, and marked those ambiguous points as "undiscernible" rather than guessing.

  2. Why it matters

    He also tried an added manual-correction method for stone-to-intersection assignment, but it worsened the board overall even where it helped locally, so he did not replace the existing judgment.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The record picks up from an earlier prototype of Gotsuzuri, an Android app that turns photos of a real Go board into game records. Even with the four corners aligned, shadows, reflections, and the height of the stones remained obstacles to recognizing stones, and a later attempt to reduce misassignment of neighboring stones to the wrong intersection by jointly mapping stone candidates to intersections did not pan out: he reports that it improved some cases but made the board worse overall, so the existing judgment was kept.

The emphasis then shifted from recognition logic to the data itself. To compare methods across different stone layouts, he added 6 setups and 12 photos, classifying each intersection as empty, black, white, or undiscernible, and built tools to reuse shooting layout diagrams and already-checked ground truth as drafts. Reviewing all 21 images with a side-by-side photo and top-down GT diagram surfaced his own labeling slips, and on the upper edge some black stones could not be pinned to an intersection by a human eye. Rather than fill those in as empty to make the counts tidy, he left them as undiscernible, and he notes that the 21 images include multiple angles of the same setups and are not 21 independent boards, with the home board and room still a source of bias.

The next planned step is a small training experiment: classify empty, black, and white from images around each intersection, first with images alone and then with grid spacing and tilt added, using PyTorch and AWS SageMaker. This is preparation rather than a result, since no AI model has been trained yet.

FAQ
Why not just label every ambiguous stone?
For black stones on the upper edge where even a human cannot decide the intersection, he marked the two candidate points as "undiscernible" and excluded them from the normal empty/black/white training targets, preferring to keep the uncertainty rather than replace it with empty.
How will the 21 images be used?
They are split by board setup: 15 images across 7 setups for development and comparison, and 6 images across 3 setups for final confirmation. Photos of the same setup are grouped together so training and validation are separated at the setup level.
What is the next step?
He plans to try a model that classifies intersections as empty, black, or white from images around each point, first using images alone and then adding grid spacing and tilt derived from the four corners, using PyTorch on AWS SageMaker.
Qiita 機械学習Read Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleOpenAI: Astra hides safety-task underperformance, worsens with RL