Mailing-List: contact dev-help@ctakes.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ctakes.apache.org
Received-SPF: pass (nike.apache.org: domain of john.travis.green@gmail.com
 designates 209.85.216.179 as permitted sender)
Date: Wed, 16 Jul 2014 12:07:22 -0700 (PDT)
MIME-Version: 1.0
Message-Id: <1405537642311.52e0b316@Nodemailer>
In-Reply-To: <E084D8EFE2B03A408B324458C5212E942453AEAD@CHEXMBX3A.CHBOSTON.ORG>
References: <E084D8EFE2B03A408B324458C5212E942453AEAD@CHEXMBX3A.CHBOSTON.ORG>
From: "John Green" <john.travis.green@gmail.com>
To: dev@ctakes.apache.org
Cc: dev@ctakes.apache.org
Subject: Re: Procedure
Content-Type: multipart/alternative;
 boundary="----Nodemailer-0.5.0-?=_1-1405537642478"

------Nodemailer-0.5.0-?=_1-1405537642478
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

Sounds like a good starting place to me, thanks Tim.=E2=80=94
Sent from Mailbox for iPhone

On Wed, Jul 16, 2014 at 3:06 PM, Miller, Timothy
<Timothy.Miller@childrens.harvard.edu> wrote:

> Do you mean something like figuring out why a named entity wasn't
> detected or something=3F I don't think we have anything formalized, but =
my
> technique is something like, find the smallest text example that
> demonstrates the issue and then work backwards in the pipeline. So for
> something missed by the dictionary I first check whether the correct
> lookup window was found. If it was then I know it's something about the
> dictionary, if not then I go back to the chunker to figure out why the
> lookup window wasn't found, etc.
> Tim
> On 07/16/2014 03:01 PM, John Green wrote:
>> Is there a generally accepted procedure for identifying why an =
annotation
>> wasnt made=3F
>>
>> JG
>>
------Nodemailer-0.5.0-?=_1-1405537642478--