HermitCrab synthesis: 25.6% of synthesis steps end in SurfaceFormMismatch; early-reject check not built (research lead)

オープン
  • 何か問題がありますか？
#603 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
45/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp
領域
performance

調査の方向性

Start with docs/hermitcrab-2026-10-27-synthesis-to-analysis-round.md, especially lines 96 onward and the cited lines 496 and 679; the issue points to branch docs/hc-optimization-ledger at 2eba2f50. Measure work steps per grammar for synthesis candidates that end in SurfaceFormMismatch, and compare their share with the existing census. Done means reporting whether the share is material enough to justify building the proposed count-only check.

索引モデルが issue の本文から書いたものです。

説明

Claude-drafted.

25.6% of synthesis steps on the five real-grammar samples end in SurfaceFormMismatch, after the whole rule stack has run. Whether an intermediate-shape check could reject those candidates earlier is not measured.

Status: research lead, not built. There is no soundness argument yet.

What we know (C# hc.dll, traced samples, unit: synthesis steps and analysis events):

  • SurfaceFormMismatch is 25.6% of synthesis steps pooled (279,872 steps); 37.9% on Indonesian, 27.2% on Mbugwe, 16.9% on Amharic.
  • Synthesis is a small part of total work (synthesis steps plus analysis events): 1.0% Aweti, 1.8% Sena, 9.0% Mbugwe, 9.4% Indonesian, 14.7% Amharic. A perfect check would therefore remove well under 25.6% of total work (inferred).
  • A check at each stratum boundary has no soundness argument: analysis shapes over-approximate (optional and underspecified nodes), and the earlier synthesis-side length bound (ledger row 8) lost valid parses.

Not known: how many SurfaceFormMismatch steps a sound check would cut, and whether any successful candidate would fail it.

Proposed change: count, do not prune. At each stratum boundary, record whether the check would fire and whether any successful candidate fails it, in steps per grammar. Build the check only if the share is material. Kill it if any success fails it on any corpus.

Related: #560 (E1, open). Retired record: PR #490 (closed). PanGloss: sillsdev/PanGloss#105 (pointer, open).

Next: run the boundary census on hc.dll and post steps cut per grammar plus any success that fails the check.

Evidence -- where the numbers come from

The census harness is test-only (branch research/failure-reason-stats at af97348b, master c2454760 with PR #480 merged; whether the branch still exists was not checked). A step is one rule-level synthesis trace event. Counts come from traced parses, which turn analysis merging off, so more analyses are explored than in an untraced run. 22.1% of steps have no terminal event and are unattributed.

Corpus (sample) SurfaceFormMismatch, % of synthesis steps Synthesis, % of total work
Pooled real grammars 25.6%
Aweti, every 2nd word 1.0%
Sena, every 100th 1.8%
Mbugwe, every 40th 27.2% 9.0%
Indonesian, all 70 37.9% 9.4%
Amharic, first 28 16.9% 14.7%

Blank cells were not given in the record. Conformance suite: 6.9% of its steps, 22.9% synthesis share.

Sources -- pinned to 2eba2f50 (closed PR #490 record)
What would reopen this

A soundness argument for a stratum-boundary check, or a census where no success fails it and the cut share is material.

主要言語
C#
スター
29
フォーク
16
平均マージ
5日 20時間
マージ済み PR（30日）
11

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

sillsdev/machine のほかの issue

sillsdev/machine の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。