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

Allow modules to report a strange query #18

Open
Ezibenroc opened this issue Nov 6, 2014 · 3 comments
Open

Allow modules to report a strange query #18

Ezibenroc opened this issue Nov 6, 2014 · 3 comments

Comments

@Ezibenroc
Copy link
Member

For instance, in the grammatical question parsing module, we have an experimental approach. We expect that some cases will never appear because we never seen them, but exceptions can always exist.
We need to know if such cases exists, to correct our module.
Right now, we have such line of code in our module: sys.exit('exit: %s dependency unexpected (please, report your sentence on http://goo.gl/EkgO5l)\n' % t).

I think that it would be nicer to allow responses of the modules to do this. For instance, add an attribute report, with a string which explain in English why the request is reported (empty string when no report).

Then, the core would add a special tag in its log, to highlight the reported requests. We would also need to allow modules developers to have access to requests reported by their modules.

@progval
Copy link
Member

progval commented Nov 6, 2014

👍

1 similar comment
@yhamoudi
Copy link
Member

yhamoudi commented Nov 6, 2014

+1

@yhamoudi
Copy link
Member

yhamoudi commented Nov 6, 2014

More precisions about why it would be great to have an access asap to questions that produce error messages:

The current algorithm we use has to analyse about 50 dependencies output by the stanford parser. The documentation provided by Stanford is not perfect: we don't know precisely what kinds of dependencies can occure (there is no full list of all possible dependencies). Since we cannot process efficiently dependencies that we don't know, it's important to detect them to correct our algo :)

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

No branches or pull requests

3 participants