gmane.comp.apache.uima.general

Re: .addToIndexes() on subtype while iterating over supertype

Александър Л. Димитров — 2008-10-10T02:03:48

Well, I thought it was quite hacky. I usually detest 'outsourcing' resource this way. OK, thanks very much. I did the removal, too, seems cleaner this way. Best, Aleks PS: very sorry for my second mail, but my university forbids outgoing mail to be relayed by outside SMTPs and the UIMA-list initially rejected my mail for address-forgery, so I resent it with my uni-account (but forgot that I did so), without noticing Thilo had already forwarded my question. Just ignore the second mail :-)

.addToIndexes() on subtype while iterating over supertype

Александър Л. Димитров — 2008-10-10T01:03:04

Hello, I have the following design issue with one of my AnalysisEngines. I searched the documentation, but not exhaustively, so pardon me if I'm doing something fundamentally wrong or there is an easy obvious solution. I have a type T1 and its subtype T2. They would both span the same text in the CAS, and while T1 represents a general data structure, T2 represents a more specific one. Say, T1 represents a sentence and T2 a sentence of a certain kind. In order to find out about all T2's in the text, I first have to find all T1's, then declare some T1's as T2's. Currently, I first mark up all T1's in an AE, then, in the next step and another AE, iterate over all T1's, look at their features and decide whether or not a T1 is a T2. In my particular example, I have to first do sentence boundary detection, then, after a few other AE's have done additional work, decide whether a particular sentence contains a trigger. So, I iterate over T1: final AnnotationIndex ai = cas.getAnnotationIndex(T1.class); for (fina

Re: .addToIndexes() on subtype while iterating over supertype

Thilo Goetz — 2008-10-09T16:22:02

Александър Л. Димитров wrote: Yes. No, that is the recommended solution to this issue. I don't see anything wrong with it. This is not specific to the CAS, btw. You always get into these kinds of issues when you try to modify a collection that you're currently iterating over. And you also may want to remove the old T1s from the index as well, since they'll be replaced by the new T2s. You also need to do this in a separate step... --Thilo

.addToIndexes() on subtype while iterating over supertype

Александър Л. Димитров — 2008-10-09T14:13:09

Re: UimaASProcessCasTimeout exception hangs application

Burn Lewis — 2008-10-07T21:36:01

I meant that if you used: runRemoteAsyncAE tcp://localhost:61616 RoomNumberAnnotatorQueue –c FileSystemCollectionReader.xml -p 1 -t 6 -i then CASes would be sent one at a time (-p 1) and the 6 sec timeout would never be reached since each CAS takes 5 secs to process. But with a larger CAS pool, say -p 3, the -t value would have to be > 3 x 5, say -p 16, to ensure that the 3rd CAS does not timeout while waiting for the 1st two to complete. All this just to avoid errors since as Jerry said there is a bug in the handling of errors when -i is specified. Yes, a crash in a service looks just the same as a slow service ... no result returned in the allotted time. Timeouts are usually used to prevent the application from hanging when a service dies, so are often set much larger than the expected processing time to avoid abandoning those CASes that take longer than the average. When your application is an asynchronous aggregate with multiple remote delegates, you can set queue-specific timeouts in the d

RE: UimaASProcessCasTimeout exception hangs application

Charles Proefrock — 2008-10-07T20:22:40

I don't have ready access to the test environment, so I'll have to go back and play with the -t value. It isn't clear if you are saying that a longer timeout "will succeed" in avoiding the hanging problem, or "will succeed" in repeating the problem we've observed. Clarification on that would help, especially if some min or max timeout avoids the problem. Yes, the queue name should match the name configured in the deploy descriptor. I think we had a more complex example running and then simplified it before posting, so the queue name documented here was probably just a mistype. To be a little more specific, we are testing both the natural timeout when a deployed process runs too long, and also the scenario where a deployed process crashes/exits with ^C. Both seem to generate the same exception when the client timeout occurs, so the nature of the remote failure does not seem to be in play. This makes sense since the remote is on the other side of a message queue, the client does not see a direct connect

Re: Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa

Aaron Kaplan — 2008-10-07T14:53:08

Baptiste, This issue has been fixed in SVN, and the fix will be in the next release. https://issues.apache.org/jira/browse/UIMA-1107 -Aaron Baptiste.GAILLARD-s/S/64wAxt+H1Tvi1vFFB9BPR1lH4CV8< at >public.gmane.org wrote:

Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa

Baptiste Gaillard — 2008-10-07T14:32:20

Hi, I have to integrate 2 annotators in an aggregate, the first creates a new Sofa and the second work on this created Sofa. My problem is that when I use the Annotators descriptors in the imports everything works, but when I specify the ‘_pear.xml’ descriptors the second annotator continue to work on the ‘DEFAULT’ Sofa. For example with this descriptor my second annotator (InfomagicXipFrench) annotates the Sofa ‘txt’ : org.apache.uima.java false <

Re: UimaASProcessCasTimeout exception hangs application

Burn Lewis — 2008-10-07T14:10:21

I also see that the -t process timeout value has to be > 10 for this to succeed ... I'd have assumed anything > 5 secs would be safe, but the default value of -p 2 means that the client's timeout must be 2x the service process time when 2 CASes are in play, since the 2nd is queued immediately behind the first. Perhaps the default should be -p 1 for simplicity. P.S. I assume you meant RoomNumberAnnotatorQueue as the 2nd arg in step 4. On Tue, Oct 7, 2008 at 9:34 AM, Jaroslaw Cwiklik public.gmane.org> wrote:

Imports with '_pear.xml' in aggregate prevent annotators to work on the right Sofa

2008-10-07T13:42:07

Hi, I have to integrate 2 annotators in an aggregate, the first creates a new Sofa and the second work on this created Sofa. My problem is that when I use the Annotators descriptors in the imports everything works, but when I specify the '_pear.xml' descriptors the second annotator continue to work on the 'DEFAULT' Sofa. For example with this descriptor my second annotator (InfomagicXipFrench) annotates the Sofa 'txt' : org.apache.uima.java false

Re: UimaASProcessCasTimeout exception hangs application

Jaroslaw Cwiklik — 2008-10-07T13:34:57

VNS Server with private IP

Nassim Jammal — 2008-10-07T09:02:26

Hi, I just came across an issue while setting up a VINCI Service on a server that doesn't have a public IP. The server that host the Vinci Service is accesible through a public IP, but doesn't actually know it. (Load Balancer) Here is the scheme of the process. The CPE call the VNS Host through a public IP CPE ---------- Internet ------- Load Balancer --------> VNS Server ( 192.168.0.1:9000) For now everything is ok. The VNS Server then send to the CPE the IP and Port of the service that the CPE wanted to call. CPE <---------- Internet ------- Load Balancer -------- VNS Server The the CPE try to call the service via 192.168.0.1:10000 but this IP is not reachable from internet. I tried to get around this by setting up the variable VNS_HOST to the domain that linked to the public IP, but it didn't worked. The VNS Server still convert the domain into an IP. I also tried to set the VNS_HOST to the public IP, but their is a security feature on Load balancers that you can not call yourself with the publ

UimaASProcessCasTimeout exception hangs application

Charles Proefrock — 2008-10-06T21:59:47

When experimenting with the UIMA-AS examples and how the error handling mechanisms work in terms of timeouts due to AS Aggregates taking too long or going offline, we came across a situation in which the RunRemoteAsyncAE hangs and never returns after receiving and processing a UimaASProcessCasTimeout exception. Ultimately, we simply want the system to recover and try the next CAS or return gracefully without having to call a hard System.exit(1). Our tests are based on the Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml example. All we did was the following: (1) added “Thread.sleep(5000);” to RoomNumberAnnotator.java process to simulate a longer process. (2) Executed: startBroker.bat (3) Executed: deployAsyncService \Deploy_RoomNumberAnnotator.xml (4) Executed: runRemoteAsyncAE tcp://localhost:61616 MeetingDetectorTaeQueue –c \FileSystemCollectionReader.xml -t 4 -i In summary: when setting and triggering the time outs on the RoomNumber remoteAnalysisEngine, the exception is thr

Re: Order of CASes after multiplier

Eddie Epstein — 2008-10-02T22:38:12

Hi Aaron, Yes, for a synchronous UIMA aggregate the parent CAS is released only after all its children are released. When deployed asynchronously in UIMA AS, the parent CAS is released from the CM when hasNext returns false, and is then available to be routed. If the parent CAS comes into an async aggregate on a process call (that it, it is not itself generated by a CM inside), it will not be returned until all of its children CAS have been released; this allows an error on a child CAS to [optionally] generate an error on its parent CAS. Eddie On Thu, Oct 2, 2008 at 3:48 PM, Aaron Kaplan public.gmane.org>wrote:

Order of CASes after multiplier

Aaron Kaplan — 2008-10-02T19:48:33

I can't find this documented anywhere, but I observe empirically that components downstream of a CAS multiplier receive all of the new CASes generated by that multiplier before receiving the original CAS that was the input to the multiplier. Can I rely on that order? -Aaron

Re: [UIMA] How to remove a feature structure from a CAS

Thilo Goetz — 2008-10-02T14:14:36

True. If you have a potentially long-running interactive application, you need to consider that issue. What you can do is once in a while copy your current content into a clean CAS, using the CasCopier. Kinda clumsy... You have to call addToIndexes(). After that, it's both on the annotation and the default bag index.

Re: [UIMA] How to remove a feature structure from a CAS

Manuel Fiorelli — 2008-10-02T13:11:59

Thanks again, if I understand well, the best we can do is to prevent the feature structure from being saved. I think I cannot use this strategy since it can leak memory (until one saves and reload). A little question again, after I create a FS, is it added to the default unnamed bag index? (or I have to add it manually) Manuel Fiorelli

Re: [UIMA] How to remove a feature structure from a CAS

Thilo Goetz — 2008-10-02T13:01:03

Sort of. You can remove the annotation from the index. The annotation will continue to exist for the lifetime of the CAS, but it will no longer be accessible. If you then save the CAS to disk, the deleted annotation will not be saved. If you use the JCas, you can do removeFromIndexes() on the annotation itself. If using the base CAS, you need to use cas.removeFsFromIndexes(annotation) -- of course this will work with the JCas as well. --Thilo

[UIMA] How to remove a feature structure from a CAS

Manuel Fiorelli — 2008-10-02T12:51:37

Hello, I am developing an interactive annotator, which should produce a corpus of annotated documents for AE training. Since a human annotator can decide to remove an annotation, I would like to know if there were an API for remove a feature structure from the CAS after it was created. Manuel Fiorelli

Re: [UIMA] Annotated corpus

Manuel Fiorelli — 2008-10-02T12:26:21

Thank you for the answer. Since I am new to UIMA, I wanted to verify that there isn't a better solution. Manuel Fiorelli

Re: [UIMA] Annotated corpus

Thilo Goetz — 2008-10-02T12:03:48

Hi Manuel, how about storing the individual documents in XCAS or XMI format? That's probably the simplest and best supported way, though not very compact. --Thilo Manuel Fiorelli wrote: