Parsimony: an environment or rule context that spells one host word is not flagged

Open
  • Is something wrong?
#153 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
53/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp
Domain
backend

Research direction

Start by reading the schema v9 pattern_node facts and existing Grammar-group Measures to see how environments and rule contexts are represented and findings name their users. Build the proposed P-env-literal-host measure and compare a seeded-defect fixture with a clean control; use one real grammar to assess false positives from two-segment boundary-anchored sides. Done when the measure reports the specified literal-only sides and runs in under 1 second at 25,000 entries.

Written by the indexing model from the issue text.

Description

An environment or rule context that spells out one host word gets no Parsimony finding. / # w o r d _ restricts an allomorph to a single word: lexical listing written as phonology. A 25,000-entry grammar had four such environments and two rule contexts of this shape, and Parsimony was silent.

What we know:

  • pattern_node in the facts (schema v9) gives each side's nodes: phonemes, literal segments, natural classes and boundaries, for allomorph environments and rule contexts alike.
  • Context made only of literal segments, three or more long or anchored to a boundary, is the shape a reviewer flags (Black 3.1.3, 6.1.2.2).

Proposed change: a Grammar-group Measure P-env-literal-host, one finding per environment or rule context side made only of literal segments (at least three, or at least two next to a word or morpheme boundary), naming the users. Static; under 1 s at 25,000 entries.

Not known: whether two-segment boundary-anchored sides give false positives on real grammars; the fixture and one real grammar decide the threshold.

Next: build it with a seeded-defect fixture and a clean control.

Dominant language
C#
Stars
1
Forks
0
Avg merge
3h 55m
Merged PRs (30d)
36

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sillsdev/motif

All issues in sillsdev/motif

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.