> Thanks for sharing your ideas,
> Sean
>
>
>
> ____________
> From: Peter Abramowitsch
> Sent: Tuesday, August 25, 2020 11:56 AM
> To: dev@ctakes.apache.org
> Subject: Re: Question about window size in term lookup [EXTERNAL]
>
> * Exter
..
Thanks for sharing your ideas,
Sean
From: Peter Abramowitsch
Sent: Tuesday, August 25, 2020 11:56 AM
To: dev@ctakes.apache.org
Subject: Re: Question about window size in term lookup [EXTERNAL]
* External Email - Caution *
Thanks Sean. A lot of good ideas. I hadn't even b
.filter( notCaps )
> .forEach( Annotation::removeFromIndexes );
>
> Or mix and modify. For instance, ignore character length but Tui = Gene
> and the text is not all caps.
>
> Sometimes I enjoy mocking up code ...
>
> Sean
>
> _
ui = Gene and
the text is not all caps.
Sometimes I enjoy mocking up code ...
Sean
From: Kean Kaufmann
Sent: Monday, August 24, 2020 9:35 PM
To: dev@ctakes.apache.org
Subject: Re: Question about window size in term lookup [EXTERNAL]
* External Email - Cau
>
> my question is whether there's a place where one can register specific two
> character terms, for example BP or PT which will be found even with a
> window size set to three.
My brute-force approach is pretty brutal: Change the window size to two,
annotate terms, then remove all two-letter an
Hello all
Is there a mechanism, a lookup file, etc which overrides the window size
set on the term annotator or the chunker. Changing the window size from
the default of 3 to 2 opens the floodgate to false acronym annotations. So
my question is whether there's a place where one can register spe
