Open mnvx opened 8 years ago
Hello, this image integrates the available scripts to make the parser running with minimal changes to them. Thus, due to the lack of time, additional patches are not included and the scripts are currently provided as is.
Regarding your questions: (1) yes, it is OK to use temporary files for intermediate operations, (2) no, it seems to be wrong due to the potential issues in the CSTLemma invocation, and (3) no, the usable result is written to the tmpmalttext.parse
file instead.
The corresponding article on NLPub in Russian demonstrates the “proper” way to use this software that works for me (I checked the approach just now).
$ docker pull nlpub/maltparser
$ docker run --rm -it nlpub/maltparser /bin/bash
root@2ac6d282032f:/malt# echo Данное программное обеспечение всё-таки работает | ./russian-malt.sh
root@2ac6d282032f:/malt# cat tmpmalttext.parse
1 Данное данный P P P--nsna 3 опред _ _
2 программное программный A A Afpnsnf 3 опред _ _
3 обеспечение обеспечение N N Ncnsnn 5 предик _ _
4 всё-таки всё-таки N N Ncmsgn 3 1-компл _ _
5 работает работать V V Vmip3s-a-e 0 ROOT _ _
I will be very grateful for the improvements proposed. Probably, @versusvoid might be interested in this discussion.
Thanks for reply.
I tryed that way and fixed install script.
Currently I have same problems with CSTLemma
reading parameters ...
Value of <HANDLE> construct can be "0"; test with defined() at ./treetagger/cmd/lemmatiser.pl line 168.
tagging ...
finished.
...
all words 0
unknown words 0 (100%%)
conflicting 0 (100%%)
Result in tmpmalttext.parse
seems correct:
1 Данное данный P P P--nsna 3 опред _ _
2 программное программный A A Afpnsnf 3 опред _ _
3 обеспечение обеспечение N N Ncnsnn 5 предик _ _
4 всё-таки всё-таки R R R 5 обст _ _
5 работает работать V V Vmip3s-a-e 0 ROOT _ _
Oh... You mean way with docker. With docker I have output as in first post . File tmpmalttext.parse
in container is empty.
root@65ee6596db87:/malt# cat tmpmalttext.parse
root@65ee6596db87:/malt#
Ubuntu 16.04 x64
Well, this is something to investigate. Have you built the image on your own machine or pulled the nlpub/docker
image from the Docker Registry? I used the latter option. If you have chosen the former, some external links might be broken resulting in malfunctioning configuration.
I try to run next command and have next output:
My questions are:
Guessing unknown lemmas in /tmp/kSP5Am64RF
- is it normal?Is it good?
Every line have number one. Is it properly?