why use UIMA logging facility?

I am involved in a discussion about how to do logging in uima. We were looking at section 1.2.2 in the tutorial for some motivation as to why we would use the built-in UIMA logging rather than just using e.g. log4j directly - but there doesn't seem to be any. Could someone give us some

what is the difference between the base CAS view and _InitialView?

I have a component that takes text from the _InitialView view, creates a second view, and posts a modified version of the text to the second view. I had a unit test that was reading in a JCas from an XMI file and running the JCas through my annotator and testing that the text was correctly

Re: Dynamic Annotators

Ram, You might check out the uutuc project at: http://code.google.com/p/uutuc/ The main goal of this project is to make it easier to dynamically describe and instantiate uima components. The project started off as utility classes for unit testing - but has really become a dynamic

Re: Problem reconfiguring after setting a config parameter value

Girish, I have done exactly the same thing as you minus step 2 below without any problems. The only caveat being that this didn't seem (as I recall) to trigger my analysis engines initialize() method and so I had to reread the parameter in my analysis engine's process() method. I don't

Re: Get the path

One thing that you might consider doing is putting the path information into its own view. That is, create a new view and set its document path to be the path/uri. One advantage of this is that if you have a CollectionReader that is otherwise type system agnostic you don't have to pollute it

Re: model file problen in opennlp uima wrapper

It may be worth pointing out that there is a very nice set of uima wrappers for OpenNLP available from their sourceforge cvs repository. See http://opennlp.cvs.sourceforge.net/opennlp/. While this is still a work in progress - it is *much* nicer than the example wrappers that ship with UIMA.

uutuc - uima unit test utility code

We have posted a light-weight set of utility classes that ease the burden of unit testing UIMA components. The project is located at: http://uutuc.googlecode.com/ and is licensed under ASL 2.0. There is very little documentation for this library at the moment - just a bare-bones getting

proposal for UIMA unit test utility code

We have assembled some misc. utility methods that make unit testing easier to support our UIMA-based project ClearTK. I have come across several scenarios now where I wish that this code was available as a separate project so that I don't have to create a dependency on our entire ClearTK

abandoning Groovy

Marshall, This may be frustrating/annoying feedback. Last summer I sent a few emails to the list about unit testing uima components using groovy and probably said a few other positive things about groovy. We have since abandoned groovy for a variety of reasons. Here are a few: - unit

Re: Type Priorities

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:

Re: How to test a CollectionReader (in Groovy)

I didn't follow the thread closely so I may be wandering here - but I thought I would volunteer my working strategy for testing collection readers in Groovy even though it may be overly simplistic for many situations. My unit tests for our collection readers start off with one line: JCas

Re: ClassCastException thrown when using subiterator and moveTo()

: That's a bug. The underlying implementation of the two iterator types you mention is totally different, hence you see this only in one of them. Any chance you could provide a self-contained test case that exhibits this? --Thilo Philip Ogren wrote: I am having difficulty with using

Unit testing with Groovy

that, please check the box that says something like, ok to include in Apache code (so we can check it in and use it as regression test). Groovy, hm. Never used it before. If it doesn't take me more than 5 min to set up in Eclipse, and I can still debug, not a problem ;-) --Thilo Philip Ogren wrote

typeSystemInit() method in CasAnnotator_ImplBase but not JCasAnnotator_ImplBase

Thilo had pointed me towards the method typeSystemInit() in a recent posting as a way of getting type system information in an annotator. Is there a reason that this method exists in CasAnnotator_ImplBase but not JCasAnnotator_ImplBase? Or is this an omission? My intuition is that might

Re: subtyping uima.cas.String

Attached is a type system descriptor file that isolates the bug. I cannot create a subtype of TestType in the CDE. Philip Ogren wrote: I was just putting some unit tests together and was editing a type system and noticed that I can't seem to subtype a type that is a subtype

Re: subtyping uima.cas.String

Sorry for the noise! A little investigation reveals that this behavior is almost certainly by design. Changing the source by hand gives an error message that says don't do that and section 2.3.4 also of the UIMA References also documents this. Philip Ogren wrote: Attached is a type system

Re: Human annotation tool for UIMA

to the CasEditor to uima-user so we don't all have to go hunting for it? Thanks, Andrew Borthwick On 6/7/07, Philip Ogren [EMAIL PROTECTED] wrote: Also note that we have a contribution by Joern Kottmann in the sandbox called CAS editor. This is Eclipse based tooling that also allows you to manually

problem creating Index Collection Descriptor File

I have three related questions that I decided to split up into three messages. I composed them as one email initially and decided I could be spawning a hard-to-traverse thread. Advanced apologies for the inundation. I am trying to create an Index Collection Descriptor File so that I can

finding annotations relative to other annotations

Is there any simple way to ask for the token 3 to the left of my current token? I can't find anything that is built into the default annotation index, and so I have defined an index for this in the descriptor file. In order to do this I define a feature in my token type that keeps track of

Re: Human annotation tool for UIMA

My initial thought was to have a CasConsumer that loads annotations directly into Knowtator programmatically, and a CasInitializer that goes the other way. What remains is to have a way to translate/synchronize the Type System in UIMA with the class hierarchy / annotation schema in Knowtator

Re: Human annotation tool for UIMA

I'm glad I happened to browse the archive today! I just joined the list today because I have noticed a couple of bugs that I want to post somewhere. So, I developed and maintain Knowtator and am also steeped in UIMA technology - I have been using it for just over a year and a half now. I would

creating a type called 'Feature'

If you create a type with the name 'Feature' you get compile errors because of a namespace conflict with the Feature interface. I think this could be easily fixed by simply removing the import statement in the generated code and explicitly providing the fully qualified name for the Feature