Return-Path: X-Original-To: apmail-ctakes-user-archive@www.apache.org Delivered-To: apmail-ctakes-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id B458B1888C for ; Mon, 4 Jan 2016 11:27:40 +0000 (UTC) Received: (qmail 72795 invoked by uid 500); 4 Jan 2016 11:27:40 -0000 Delivered-To: apmail-ctakes-user-archive@ctakes.apache.org Received: (qmail 72772 invoked by uid 500); 4 Jan 2016 11:27:40 -0000 Mailing-List: contact user-help@ctakes.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ctakes.apache.org Delivered-To: mailing list user@ctakes.apache.org Received: (qmail 72539 invoked by uid 99); 4 Jan 2016 11:27:40 -0000 Received: from Unknown (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 Jan 2016 11:27:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id D87201A1190 for ; Mon, 4 Jan 2016 11:27:39 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.879 X-Spam-Level: ** X-Spam-Status: No, score=2.879 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-us-west.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JLDlOdBOXF2R for ; Mon, 4 Jan 2016 11:27:39 +0000 (UTC) Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by mx1-us-west.apache.org (ASF Mail Server at mx1-us-west.apache.org) with ESMTPS id 924C120265 for ; Mon, 4 Jan 2016 11:27:38 +0000 (UTC) Received: by mail-lf0-f49.google.com with SMTP id p203so275571300lfa.0 for ; Mon, 04 Jan 2016 03:27:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VCH+SQTdLQ/L15OWOqQj7+DbEMzssZxUIc8q4Y6KgKU=; b=dIyabXZN1UndNAuAPTJ3dvENFtXDyKhWMflvOMx4nmQERkJt3mrcAlBypQwVRG3IHR PikDBozRxC9FKiv+Xq+u4JD4EOuDgEiFnguh00p4eO2ifpBCHhx5284bPrZldx24oqf6 5LS48CJ6HXZBnzbM7HZNKm3/a198/eL+ytFuD9FiebDDZoWOGag0gp/dnVYQ35/EOSQM cYnYilj/9JqXAbZEESqXA4dncOrVHA+EvgJDkS4deUQKlBYfkfLBLudDe4moQKNuAcOi Sis2LzCpgIvKr0v1FM+LuOlghNWf1laS3Pv7R/Ix0bnx40/id56FF3KD1nwMfRJleJ/d WgYQ== MIME-Version: 1.0 X-Received: by 10.25.21.225 with SMTP id 94mr26887893lfv.159.1451906856936; Mon, 04 Jan 2016 03:27:36 -0800 (PST) Received: by 10.112.168.234 with HTTP; Mon, 4 Jan 2016 03:27:36 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Jan 2016 12:27:36 +0100 Message-ID: Subject: Re: Achieving YTEX negation in CuisOnlyPlaintextUMLSProcessor From: vijay garla To: "user@ctakes.apache.org" Content-Type: multipart/alternative; boundary=001a113f245e7470810528806853 --001a113f245e7470810528806853 Content-Type: text/plain; charset=UTF-8 CTAKES_HOME\desc\ctakes-ytex-uima\desc\analysis_engine\DictionaryLookupAnnotator.xml references CTAKES_HOME\resources\org\apache\ctakes\ytex\dictionary\lookup\LookupDesc_SNOMED.xml, which limits all dictionary lookups to org.apache.ctakes.typesystem.type.textspan.LookupWindowAnnotation spans, which are created by the LookupWindowAnnotator. You can either add the LookupWindowAnnotator (not sure about its dependencies), or you can change LookupDesc_SNOMED.xml to use a different annotation (e.g. Noun Phrase or Sentence). HTH, VJ On Thu, Dec 31, 2015 at 3:52 PM, Jessica Glover wrote: > I have noticed that using the AggregatePlaintextUMLSProcessor in > ctakes-ytex-uima results in improved negation detection over the one in > ctakes-clinical-pipeline on my test documents. > > I would like to get the same improvement in > CuisOnlyPlaintextUMLSProcessor. I have tried replacing the > DictionaryLookupAnnotator, which seemed to be the determining factor in > AggregatePlaintextUMLSProcessor, but when I run it, I find no > IdentifiedAnnotations. Does the YTEX DictionaryLookupAnnotator depend on an > analysis engine I've overlooked? Any other suggestions? > > Thank you, > Jessica G. > --001a113f245e7470810528806853 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
CTAKES_HOME\desc\ctakes-ytex-uima\desc\analysis_engin= e\DictionaryLookupAnnotator.xml references CTAKES_HOME\resources\org\apache= \ctakes\ytex\dictionary\lookup\LookupDesc_SNOMED.xml, which limits all dict= ionary lookups to=C2=A0org.apache.ctakes.typesystem.type.textspan.LookupWin= dowAnnotation spans, which are created by the=C2=A0LookupWindowAnnotator.

You can either add the LookupWindowAnnotator (not s= ure about its dependencies), or you can change LookupDesc_SNOMED.xml to use= a different annotation (e.g. Noun Phrase or Sentence).

HTH,

VJ

On Thu, Dec 31, 2015 at 3:52 PM, Jessica G= lover <glover.jessica.m@gmail.com> wrote:

I have noticed that using the Aggre= gatePlaintextUMLSProcessor in ctakes-ytex-uima results in improved negation= detection over the one in ctakes-clinical-pipeline on my test documents.

I would like to get the same improvement in CuisOnlyPlaintex= tUMLSProcessor. I have tried replacing the DictionaryLookupAnnotator, which= seemed to be the determining factor in AggregatePlaintextUMLSProcessor, bu= t when I run it, I find no IdentifiedAnnotations. Does the YTEX DictionaryL= ookupAnnotator depend on an analysis engine I've overlooked? Any other = suggestions?

Thank you,
Jessica G.


--001a113f245e7470810528806853--