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 Fri, 14 Dec 2012 20:58:13 GMT

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

Sean commented on CTAKES-101:
-----------------------------

I was finally able to get around to trying this fix.   By placing these resources in the src/main/resources/org/apache/ctakes/smokingstatus/analysis_engine/
the relative path needed to be shortened by one directory to correctly accessing at run time.
 However, using the CPE to edit these files with this relatative import path will cause problems
(The system cannot find the path specified).   Having it run correct is the primary issue,
so I'm okay with this compromise.  I thought I'd mention it in case there was another workaround
I hadn't considered.
                
> 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

Mime
View raw message