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

Switch to ClearParser #17

Open
schmmd opened this issue Feb 14, 2013 · 3 comments
Open

Switch to ClearParser #17

schmmd opened this issue Feb 14, 2013 · 3 comments
Assignees

Comments

@schmmd
Copy link
Member

schmmd commented Feb 14, 2013

Switch to clear parser for superior parses with equal scalability. Some patterns will need to be changed because clear represents them differently (better). In particular, there are no cop edges.

@ghost ghost assigned schmmd Feb 14, 2013
@ReshuAgarwal
Copy link

When you will release the latest jar which uses clearParser and the latest updation???

@schmmd
Copy link
Member Author

schmmd commented May 30, 2013

This probably won't happen as we are moving to a new extractor based on
SRL. Expect a release sometime in the next two months.

On Thu, May 30, 2013 at 4:59 AM, ReshuAgarwal notifications@github.comwrote:

When you will release the latest jar which uses clearParser and the latest
updation???


Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-18675822
.

@schmmd
Copy link
Member Author

schmmd commented May 30, 2013

You could wire Ollie with ClearParser easily by looking at the example program included with the Ollie source and using the nlptools-parse-clear dependency instead of nlptools-parse-malt. However, while ClearParser has higher precision parses, the dependency language is somewhat different--causing Ollie to miss a different class of extractions.

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

2 participants