uima-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Garcia Narbona <david.garc...@barcelonamedia.org>
Subject Re: [UIMA AS] example descriptor UIMA AS aggregate
Date Fri, 23 Dec 2011 08:07:28 GMT
Yes, I had a look at the UIMA-AS Getting Started as wall as the UIMA 
Asynchronous Scaleout documentation, but I didn't quite understand the 
example explained for Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml and 
MeetingDetectorTAE.xml descriptors.

(As from Deploy_MeetingDetectorTAE_RemoteRoomNumber it is only used one 
annotator defined in MeetingDetectorTAE, I thought the 
Deploy_MeetingDetectorTAE_RemoteRoomNumber to be a sort of wrapper for 
the RoomNumberAnnotator annotator. From my humble opinion, I think that 
an AS analysis engine deployment descriptor using two or more -- in this 
case up to three -- annotators defined in MeetingDetectorTAE or in 
another descriptor it'd be clearer).

Anyway, as I pointed in the previous mail. I launch the broker, as weel 
as Deploy_MeetingDetectorTAE_RemoteRoomNumber analysis engine, but 
nothing seems to happen.
Although I get:

Service:TutorialDateTime Annotator Initialized. Ready To Process Messages From Queue:inQ_DateTime_1.2
Service:Meeting Annotator Initialized. Ready To Process Messages From Queue:inQ_Meeting_1.3

when I launch the analysis engine, execution seems to finish, as console 
prompt appears again.

If I launch the cpeGui with MeetingDetectorAsyncAE descriptor, I get the 
error I mentioned.


El 22/12/2011 18:46, Marshall Schor escribió:
> Hi,
> Did you read and understand the UIMA-AS Getting Started?  You can find a link to
> it on the Documentation page (scroll to the bottom), or just use this link
> http://uima.apache.org/doc-uimaas-what.html
> It describes the relationship of the two descriptors.  The basic idea: The
> descriptor you point to with topDescriptor is a **non-UIMA-AS** plain UIMA
> descriptor - it doesn't have any information about deploying in a "scaled-out"
> environment using UIMA-AS.
> The UIMA-AS descriptor is intended to re-use the plain UIMA descriptor, but add
> information to it that describes scale-out details (only).
> That's why there are two.
> -Marshall
> On 12/21/2011 11:51 AM, David Garcia Narbona wrote:
>> Hi,
>> I am having a look at
>> /apache-uima-as-2.3.1/examples/deploy/as/Deploy_MeetingDetectorTAE_RemoteRoomNumber.xml
>> descriptor.
>> I don't quite understand the descriptor.
>> A list of the AS components can be found into "<delegates>" tag. So, what it
>> is necessary to define a "topDescriptor"? Which descriptor should be imported?
>> If you specify a list ot the avilable UIMA AS componenents, I don't know which
>> topDescriptor I should provide additionally.
>> On the other hand, I neither understand the example provided by
>> Deploy_MeetingDetectorTAE_RemoteRoomNumber descriptor.
>> Why is it using RoomNumber remoteAnalysisEngine if this annotator is described
>> in the MeetingDetectorTAE descriptor imported in the topDescriptor tag?
>> Thanks,
>> David

View raw message