HermitCrab synthesis: 98% of Mbugwe synthesis work goes to candidates whose root lookup hits but never match the surface

Ouverte
  • Quelque chose ne va pas ?
#607 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
52/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
csharp
Domaine
backend

Piste de recherche

Start with docs/hermitcrab-2026-10-21-search-cost-round.md, lines 319–330, then review the failure-reason trace from #534 and the related discussion in #560. Identify where synthesis failures are traced and determine how to classify candidates whose lexical lookup hits but whose surface does not match. Done means the failures are classified by rejecting rule in work steps; do not add pruning.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Claude-drafted.

98% of Mbugwe's synthesis work goes to candidates whose lexical lookup hits but whose synthesis never matches the surface form. It is the largest unaddressed bucket on Mbugwe, and no sound prune is known. The same share was 86% on the private deletion variant, but that figure was measured before a port fix (fix B) that cut the variant's total work by 94.7%, so it does not describe the current port or hc.dll.

Status: open research lead, not started.

What we know (HC-Rust port, synthesis work in work steps):

  • 98% on Mbugwe; the record does not give the sample or the fix state for that figure.
  • 86% on the private deletion variant, before fix B (303,966,311 work steps then, 16,220,190 after).
  • A lexical oracle cannot prune these candidates: the root is reachable, so lexical-reachability pruning (ledger rows 10 and 11) cannot reach them.
  • The 2026-10-27 census on hc.dll attributes steps by failure reason (SurfaceFormMismatch is 27.2% of Mbugwe synthesis steps) but does not split root-reachable failures.

Not known: which rules reject these candidates, and whether a sound condition exists.

Proposed change: classify these failures by the rule that rejects them, in work steps. Do not add a prune until a sound condition is found.

Related: #534 (PR, closed, not merged), #560 (open). The failure-reason trace that would do the classification is #534's; the census harness (branch research/failure-reason-stats at af97348b) is test-only. PanGloss: sillsdev/PanGloss#109 (pointer, open), which depends on sillsdev/PanGloss#34 (open, ports #534).

Next: revive the #534 failure-reason trace, or extend the census harness, and report work steps per rejecting rule on Mbugwe.

Evidence -- what the record states
  • Open lead 4: 86% (deletion variant, before fix B) and 98% (Mbugwe) of synthesis work goes to candidates whose lookup hits but whose synthesis never matches the surface (L338-L341); the same sentence appears in the C1 verdict (L160-L162).
  • Fix B: a re-inserted segment-class node keeps its members on a featureless grammar. It was a bug in the Rust port; C# was already exact. Deletion variant, held list: 303,966,311 to 16,220,190 work steps, 94.7% less (L51).
  • Before fix B, a two-word profile of the deletion variant put synthesis at about 90% of parser work (L101-L103).
Sources -- pinned to 2eba2f50 (closed PR #490 record)
What would reopen this

A sound condition that rejects a root-reachable failure class before it is synthesised, with a work-step ceiling worth its cost.

Langage dominant
C#
Étoiles
29
Forks
16
Merge moyen
6 j 7 h
PR mergées (30 j)
14

Préparer son environnement

  • Aucun Dockerfile ni fichier Docker Compose
  • Propose un modèle de pull request
  • Aucun guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de sillsdev/machine

Toutes les issues de sillsdev/machine

Issues similaires

Plus d'issues C#

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.