ctakes-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CTAKES-101) Term spotting pipelines returning 'unknown' classifications
Date Thu, 06 Dec 2012 20:55:11 GMT

    [ https://issues.apache.org/jira/browse/CTAKES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13512107#comment-13512107

Sean commented on CTAKES-101:

    Due to the ctakes-smoking-status using annotator as resources I'm having difficulty checking
in the annotators related to this fix.  For instance, the desc/analysis_engine/ClassifiableEntriesAnnotator.xml'
accesses desc/analysis_engine/ProductionPostSentenceAggregate_step1.xml via:


This requires that I copy the files into the src/main/resources.  Additionally, a unique relative
path needs to exist to make sure it is deployable both inside and out of eclipse.

However, I'm seeing problems when I attempt to commit:
'Unresolved Conflict 
svn: Commit failed (details follow):
svn: File or directory 'SmokingStatusDictionaryLookupAnnotator.xml' is out of date; try updating
svn: CHECKOUT of ...

Any suggestions?

> Term spotting pipelines returning 'unknown' classifications
> -----------------------------------------------------------
>                 Key: CTAKES-101
>                 URL: https://issues.apache.org/jira/browse/CTAKES-101
>             Project: cTAKES
>          Issue Type: Bug
>          Components: ctakes-drug-ner, ctakes-pad-term-spotter, ctakes-smoking-status
>    Affects Versions: 2.6-incubating, 3.0-incubating
>         Environment: Linux and Windows OS
>            Reporter: Sean
>              Labels: patch
>             Fix For: 2.6-incubating, 3.0-incubating
>   Original Estimate: 168h
>  Remaining Estimate: 168h
> The problem seems to have stemmed from the reorganization of the path structures with
the latest cTAKES  release.  Due to time and resource constraints we were not able to test
each project independently.   This will be fixed in current and future releases.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message