I guess that I've got one question at this point:
Is the name being given to the -new- dictionary lookup module temporary or
permanent?
I was under the assumption that it was temporary and that with the switch to it
being default (and eventually only) the module would simply be named
"dictio
I guess I saw it as a short-term thing -- having default and -fast, and
then if/when we deprecate the older one the -fast will just change to
regular ctakes-dictionary-lookup. But that could maybe be confusing to
people too.
Tim
On 06/16/2014 11:24 AM, Masanz, James J. wrote:
> I'd rather somethin
VJ,
Just an fyi, I just ran the script to apply the standard ASF license header
files to the ytex source files (.sql, .xml, .java, .jsp, .bat, etc.) in
trunk
This will allow us to pass the Apache RAT checks...
(For those who are curious, our mvn license:check and license:format will
do it automat
I'd rather something else than "dictionary-lookup-fast". If we come up with
something even faster than this one, having an older one called "fast" could be
confusing.
-Original Message-
From: Dligach, Dmitriy [mailto:dmitriy.dlig...@childrens.harvard.edu]
Sent: Monday, June 16, 2014 9:5
As far as which is the default, I'm curious what the implementers of
dictionary-lookup2 think. If we have something faster that is equally as good,
and we know one complaint about cTAKES is its speed, then why not have the new
one be the default?
-Original Message-
From: Chen, Pei [mail
+1
Guergana
-Original Message-
From: Dligach, Dmitriy [mailto:dmitriy.dlig...@childrens.harvard.edu]
Sent: Monday, June 16, 2014 10:56 AM
To: cTAKES Developer list
Subject: Re: Preparing for an Apache cTAKES 3.2 Release?
+1
Dima
On Jun 16, 2014, at 9:42, Miller, Timothy
wrote:
>
+1
Dima
On Jun 16, 2014, at 9:42, Miller, Timothy
wrote:
> Sorry to weigh in so late on this -- just returned from vacation. If we
> want to have a one release delay before making dictionary2 default for
> testing/documentation/configuration purposes, and there isn't an obvious
> function-r
I'm making some significant updates to trunk that may cause some instability
for this release.
It should be mostly transparent, but let me know if you encounter any issues
with trunk.
Also, regarding the dictionary-lookup2. If there are no strong objections, we
can leave default to as-is (old
Sorry to weigh in so late on this -- just returned from vacation. If we
want to have a one release delay before making dictionary2 default for
testing/documentation/configuration purposes, and there isn't an obvious
function-related name, and the main difference is speed, maybe we could
call it dic
