opennlp-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Piliouras (Closed) (JIRA)" <>
Subject [jira] [Closed] (OPENNLP-466) TokenNameFinderCrossValidator hangs when passed a NameEvaluationErrorListener...
Date Tue, 13 Mar 2012 19:16:40 GMT


Jim Piliouras closed OPENNLP-466.

    Resolution: Fixed

This turned out to be an external issue and NOT and openNLP related one. It is already known
that when dealing with sdtin & sdtout from leiningen (Clojure project management command-line
tool) you have to trampoline your code so it doesn't get nested inside leiningen's VM...i
am not sure whether the issue has been resolved in lein2 which is still in a preview release...Thanks
for your patience and i do apologise if i wasted some...

> TokenNameFinderCrossValidator hangs when passed a NameEvaluationErrorListener... 
> ---------------------------------------------------------------------------------
>                 Key: OPENNLP-466
>                 URL:
>             Project: OpenNLP
>          Issue Type: Bug
>          Components: Name Finder
>    Affects Versions: tools-1.5.3
>         Environment: ubuntu 11.10 x64 Java 1.7 update 3
>            Reporter: Jim Piliouras
>            Assignee: William Colen
>              Labels: cross-validation
>             Fix For: tools-1.5.3
>   Original Estimate: 2h
>  Remaining Estimate: 2h
> TokenNameFinderCrossValidator works fine if passed null or any other listener except
a "NameEvaluationErrorListener", for  the l"listeners" parameter (last vararglist parameter
in the constructor)...I have tested it with DetailedFMeasureListener and null and it works
fine. When trying to pass an array with the 2 listeners i want (DetailedFMeasureListener,
NameEvaluationErrorListener) it just hangs after the processing the last partition of data,
rather than showing the F-score! It is not a show stopper because i can simply pass null and
get my F-score, but it would be nice if could see the misclassifications as well...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message