To: uima-user@incubator.apache.org
Subject: Re: Type Priorities
I would guess that many users of the subiterator get tripped up by type
priorities at some stage ... I certainly have. It'd be nice if we had a
version that just used the bounds of the input annotation, e.g.
FSIterator subiterator
, type priorities were
introduced because of user requirements. They're certainly not
an implementation convenience. Quite the opposite, in fact :-)
Now if enough users speak up, maybe we can change something.
Perhaps by default, type priorities should not be used and
you'd need to do something
Hi,
I don't like the behavior, either. However, type priorities were
introduced because of user requirements. They're certainly not
an implementation convenience. Quite the opposite, in fact :-)
Now if enough users speak up, maybe we can change something.
Perhaps by default, type priorities
Philip Ogren wrote:
Katrin,
Yes. There is a penalty for iterating through all the annotations of a
given type. Imagine you have a token annotation and a document with 10K
tokens (not uncommon).
We wrote a method that doesn't have this performance penalty and
bypasses the type priorities
in the simplest way
possible: take all the annotations of a given type with begin offsets greater
than x and end offsets less than y and through them in. It isn't the type
priorities themselves that felt like they were an implementation convenience
but the unexpected behavior. Using the naïve algorithm
Hi,
is there a way to programmatically define type priorities?
Actually, I am using the subiterator functionality and I need to have
type priorities to be set. But I don't want the user of a component to
be able to alter the type priorities by modifying the descriptors where
type priorities
13, 2008 1:38 PM
To: uima-user@incubator.apache.org
Subject: Re: Type Priorities
Hi Thilo,
Actually, I am using the subiterator functionality and I need to have
type priorities to be set. But I don't want the user of a component
to
be able to alter the type priorities by modifying
()) {
abbrev.add(currAbbrev);
}
return abbrev;
}
-Original Message-
From: LeHouillier, Frank D. [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 2:47 PM
To: uima-user@incubator.apache.org
Subject: RE: Type Priorities
I can't see in your example why the using the subiterator doesn't work.
You
: Thursday, March 13, 2008 2:54 PM
To: uima-user@incubator.apache.org
Subject: RE: Type Priorities
Typos in my code example fixed:
public ArrayListAbbreviation getAbbreviations(Entity entity,
JFSIndexRepository index) {
AnnotationIndex annotationIndex =
index.getAnnotationIndex(Abbreviation.type
Katrin,
Yes. There is a penalty for iterating through all the annotations of a
given type. Imagine you have a token annotation and a document with 10K
tokens (not uncommon).
We wrote a method that doesn't have this performance penalty and
bypasses the type priorities.
Please see:
http
10 matches
Mail list logo
