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

Private methods disallow building a MATE wrapper #5

Open
GoogleCodeExporter opened this issue Mar 18, 2015 · 1 comment
Open

Private methods disallow building a MATE wrapper #5

GoogleCodeExporter opened this issue Mar 18, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Building a wrapper for the MATE pipeline for processing several documents and 
without loading each model for every document, one needs to call the out() 
methods of the respective tools (after initialising each tool once with a 
model).

However, the following methods are not set to public and thus disallow direct 
use of the is2.parser.Parser:

- is2.parser.Parser.out()
- is2.parser.Pipe.nextInstance() 

Also, using the morph tagger at is2.mtag.Tagger is not possible because of the 
non-public access to these fields:

- is2.mtag.Tagger.pipe
- is2.mtag.Tagger.params 

I do not believe this is intended as the respective fields/methods are public 
in the other processor classes, e.g. the lemmatizer or POS tagger.

The problem can easily be solved by setting these fields/methods to public.

For more details and links to the respective source code, also check 
http://korap.ids-mannheim.de/2013/07/issues-with-mate-pipeline/ 

Original issue reported on code.google.com by joa.bin...@gmail.com on 16 Jul 2013 at 12:56

@GoogleCodeExporter
Copy link
Author

The idea was to use the apply method. We can have those public as well. 
Bernd

Original comment by boh...@informatik.uni-stuttgart.de on 5 Sep 2013 at 3:01

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

1 participant