Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"repair" utterances #67

Open
nalbion opened this issue Apr 30, 2023 · 0 comments
Open

"repair" utterances #67

nalbion opened this issue Apr 30, 2023 · 0 comments

Comments

@nalbion
Copy link
Member

nalbion commented Apr 30, 2023

When utterance does not correspond to an actionable command, possibly due to stop words, verbal fillers or extraneous text which cannot be directly parsed.
In short, if a given phrase, e.g., ``open uh foo java'' is received, we attempt to repair the utterance.
At the user's discretion, or in case of ambiguity when the phrase has multiple plausible alternatives, we can either visually or verbally prompt the user to choose from a set of actionable phrases, e.g:

Did you mean (a) open file foo.java, (b) open folder foo/java, or (c) something else?'

To correct recognition errors, we apply Considine et al.'s~\cite{considine2022tidyparse} work on Tidyparse, which supports recognition and parsing of context-free and mildly context-sensitive grammars, and computing language edit distance. Tidyparse implements a novel approach to error correction based on the theory of context-free language reachability, conjunctive grammars and Levenshtein automata.
We use a SAT solver to find the smallest edit transforming a string outside the language to a string inside the language.
Only when the utterance is one or two tokens away from a known command do we attempt a repair.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant