ctakes-notifications mailing list archives

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

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

Pei Chen commented on CTAKES-101:

I wonder how did this work in the past.  It must have required users to add smoker-status/desc
to the classpath.  I'm looking at ClassifiableEntires.java and it looks like it's trying to
load .xml descriptor files dynamically so the paths will be relative to runtime or needs to
be absolute; it probably worked because it ended up loading it from the classpath.
If this is the case and if you want to preserve that mechanism, my best guess would be to
move *step1.xml and step2.xml into src/main/resources/org/apache/ctakes/smokingstatus/analysis_engine/
and reference it some like file:org/apache/ctakes/smokingstatus/aanalysis_engine/ProductionPostSentenceAggregate_step1.xml
> 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