-
Notifications
You must be signed in to change notification settings - Fork 38
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
Increasing range of terms parsable into MathExpr #289
Comments
|
|
|
|
If it was commented out it probably is unnecessary due to a change somewhere, either my code or the Stanford parser. |
Added new sub issue regarding conjunct adjectives. |
The sub-issue regarding verbs inside TeX expressions has been solved by replacing the specific TeX expression, for example, |
Nice. So every LaTeX expression is a noun.
We need rules for adding "is true", but these should be simple to some
extent, and amenable to machine learning
…On Mon, 15 Feb 2021 at 10:50, sundararajan-s ***@***.***> wrote:
The sub-issue regarding verbs inside TeX expressions has been solved by
replacing the specific TeX expression, for example, $a > b$ with "$a > b$
is true". The correct TeX expression is selected by iterating over all
possible swaps and checking which one parses.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#289 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA3K3JGURSBEXVX62FW65RDS7CVIXANCNFSM4QMUXKGA>
.
|
For now, I'm doing an exhaustive search, but I do think in the future we could speed it up with some NLP methods. |
The following is a list of issues which need to be fixed/improved on in the parser for
MathExpr
These result in the entire tree being wrongly parsed.
unapply
function or by reformatting input sentences. These raise aMatchException
atprovingground.translation.MathExpr$Determiner$.apply
The text was updated successfully, but these errors were encountered: