search

syntax-prosody-ot / main

A webapp for the syntax-prosody analyst working in Optimality Theory, with automated Gen, Con and Eval. Download build files from syntax-prosody-ot/build
https://spot.sites.ucsc.edu/
GNU General Public License v2.0
12 stars 2 forks source link

Match-any #544

Closed jbellik closed 3 years ago

jbellik commented 3 years ago

  1. Check if Match-any is broken due to the checking of the prosodic hierarchy. Error checking in makeTableau() probably needs to be made more nuanced to only check that the category is in pCat if it's not "any" or "". Two other possible ways to handle this are (1) to change the way we refer to the category in category-insensitive Match to just not specify a category at all, or (2) change the category-check to just create a warning rather than throwing an error.

  2. Add interface support for "Match-any" (Match that ignores syntactic categories) by adding a checkbox with value 'any'.

jbellik commented 3 years ago

Create Mocha tests for this too. If the syntactic tree (inputTree) only contains nodes of cat: 'xp' and cat: 'cp', then: matchSP(inputTree, ptree, any) = matchSP(inputTree, ptree, 'xp') + matchSP(inputTree, ptree, 'cp')

jbellik commented 3 years ago

On the interface, make MatchSP-any look visually consistent with StrongStart-global and StrongStart-local (under Markedness > Sisterhood).

jbellik commented 3 years ago

For (1), you need to adjust the conditions in lines 95-96 of tableauMaker.js. Also check how categories are handled for strongStart_Elfner.

jbellik commented 3 years ago

See test/manual_testing/matchOptions.html as an example of a file that is broken currently & should not be.

sz245 commented 3 years ago

matchSP(inputTree, ptree, any) = /= matchSP(inputTree, ptree, 'xp') + matchSP(inputTree, ptree, 'cp') when testing. matchSP(inputTree, ptree, any) also seems to be counting things categorized as "x0" or "c0" etc. Is that right or does it need to be corrected?