You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@opennlp.apache.org by "Jörn Kottmann (JIRA)" <ji...@apache.org> on 2011/03/04 12:11:41 UTC

[jira] Created: (OPENNLP-142) NameFinderTrainer: Invalid tag in training data error is hard to find

NameFinderTrainer: Invalid tag in training data error is hard to find
---------------------------------------------------------------------

                 Key: OPENNLP-142
                 URL: https://issues.apache.org/jira/browse/OPENNLP-142
             Project: OpenNLP
          Issue Type: Improvement
          Components: Name Finder
            Reporter: Jörn Kottmann
            Priority: Trivial


When the Name Finder is trained with a training file which has multiple <START> tags in a row or is missing an <END> tag the training fails with an error message like this:
"Found unexpected annotation <START:organization> while handling a name sequence."

Now it is difficult to figure out where in the training data the mistake actually is. To make that easier the error message should also contain tokens before and after the tag.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (OPENNLP-142) NameFinderTrainer: Invalid tag in training data error is hard to find

Posted by "Jörn Kottmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENNLP-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann updated OPENNLP-142:
----------------------------------

    Fix Version/s: tools-1.5.2-incubating

> NameFinderTrainer: Invalid tag in training data error is hard to find
> ---------------------------------------------------------------------
>
>                 Key: OPENNLP-142
>                 URL: https://issues.apache.org/jira/browse/OPENNLP-142
>             Project: OpenNLP
>          Issue Type: Improvement
>          Components: Name Finder
>            Reporter: Jörn Kottmann
>            Priority: Trivial
>             Fix For: tools-1.5.2-incubating
>
>
> When the Name Finder is trained with a training file which has multiple <START> tags in a row or is missing an <END> tag the training fails with an error message like this:
> "Found unexpected annotation <START:organization> while handling a name sequence."
> Now it is difficult to figure out where in the training data the mistake actually is. To make that easier the error message should also contain tokens before and after the tag.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Closed] (OPENNLP-142) NameFinderTrainer: Invalid tag in training data error is hard to find

Posted by "Jörn Kottmann (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/OPENNLP-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed OPENNLP-142.
---------------------------------

    Resolution: Fixed
      Assignee: Jörn Kottmann

> NameFinderTrainer: Invalid tag in training data error is hard to find
> ---------------------------------------------------------------------
>
>                 Key: OPENNLP-142
>                 URL: https://issues.apache.org/jira/browse/OPENNLP-142
>             Project: OpenNLP
>          Issue Type: Improvement
>          Components: Name Finder
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>            Priority: Trivial
>             Fix For: tools-1.5.2-incubating
>
>
> When the Name Finder is trained with a training file which has multiple <START> tags in a row or is missing an <END> tag the training fails with an error message like this:
> "Found unexpected annotation <START:organization> while handling a name sequence."
> Now it is difficult to figure out where in the training data the mistake actually is. To make that easier the error message should also contain tokens before and after the tag.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira