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

Jeff Headley commented on CTAKES-370:
-------------------------------------

In case it might help save someone else days of frustration, the advice 
mentioned in CTAKES-363 seems to have solved my problem. I extracted the files 
out of ctakes-smoking-status-res-3.2.2.jar and placed them in ctakes/desc and 
then edited the import lines as mentioned above and the errors went away.

> Include smoking status in clinical pipeline
> -------------------------------------------
>
>                 Key: CTAKES-370
>                 URL: https://issues.apache.org/jira/browse/CTAKES-370
>             Project: cTAKES
>          Issue Type: Improvement
>          Components: ctakes-clinical-pipeline, ctakes-smoking-status
>    Affects Versions: 3.2.2
>         Environment: Linux
>            Reporter: Tomasz Oliwa
>            Priority: Minor
>         Attachments: AggregatePlaintextFastUMLSProcessor.xml
>
>
> The smoking status detection can be included in the clinical pipeline. 
> Attached is a AggregatePlaintextFastUMLSProcessor.xml that has the clinical 
> pipeline + the smoking status detection integrated.
> Currently cTAKES has smoking status resources that need to have 
> their imports adjusted for any smoking status detection to work. As a 
> workaround, in:
> ProductionPostSentenceAggregate_step1.xml
> change:
> <import name="org.apache.ctakes.core.analysis_engine.TokenizerAnnotator"/>
> <import 
> name="org.apache.ctakes.core.analysis_engine.SentenceDetectorAnnotator"/>
> to the absolute or relative path (depends on the installed system, on my 
> machine it is) of these annotators:
> <import 
> location="../../../../../../desc/ctakes-core/desc/analysis_engine/TokenizerAnnotator.xml"/>
> <import 
> location="../../../../../../desc/ctakes-core/desc/analysis_engine/SentenceDetectorAnnotator.xml"/>



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to