Re: General question about UimaFIT

Hi. Thanks for your answers. So it seems that programming-language independence is the primal reason to do things as they have done. Many thanks, Asher. 2016-09-09 18:49 GMT+03:00 Richard Eckart de Castilho : > On 09.09.2016, at 17:37, Asher Stern wrote: >

Re: CPE processors and analysis engines

At least put the AEs and the consumers into separate CAS processors. Otherwise you run into either of the two situations: 1) AEs are not parallelized - no performance gain 2) consumers are parallelized - depending on their implementation, you might be getting mangled data, missing data, etc.

Re: UIMA RUTA script with stringfunctions doesnt work when executing from UIMA-Fit

On 08.09.2016, at 19:46, Peter Klügl wrote: > > Sorry, that was the wrong extension... it should read: > > = AnalysisEngineFactory.createEngine(RutaEngine.class, > RutaEngine.PARAM_ADDITIONAL_EXTENSIONS, new > String[]{BooleanOperationsExtension.class.getName()}); >

Re: General question about UimaFIT

On 09.09.2016, at 17:37, Asher Stern wrote: > > You explanation really makes things clear, and also answers my question. > > I still wonder whether some automatic mechanism can be developed to > automatically generate TypeDescription and TypeSystemDescription directly > from

Re: General question about UimaFIT

And I guess you don't get JCAS classes for your type system without going through JCasGen, which is another disadvantage to generating the types on the fly. It also kind of goes against the fact that the type system should be something you can rely on for communication between components, so it

Re: initiating CpeComponentDescriptor from String or InputStream

Thanks, Richard! That's also the solution I can think of: getting the descriptor contents from the database and save them as temp files. Then use those temp files to initiate the cas processors. Best, Xiaobin On Fri, Sep 9, 2016 at 5:28 PM, Richard Eckart de Castilho wrote: >

Re: General question about UimaFIT

Hi Richard. Many thanks! You explanation really makes things clear, and also answers my question. I still wonder whether some automatic mechanism can be developed to automatically generate TypeDescription and TypeSystemDescription directly from a Java class (under some conditions). This can

Re: initiating CpeComponentDescriptor from String or InputStream

Can you just write out the component descriptor to a file and pass that to the factory? I think you need a path since the underlying code needs uima-style include which supports import by name or location. Perhaps CPE can do this for you with a new API you are suggesting but I the quickest path

Re: initiating CpeComponentDescriptor from String or InputStream

Afaik there is no such thing. That is why the uimaFIT CpeBuilder stores programmatically created engine descriptors in temporary files. Cheers, -- Richard > On 09.09.2016, at 17:15, Chen Xiaobin wrote: > > Hi, > I am wondering if there is a way to initiate a

initiating CpeComponentDescriptor from String or InputStream

Hi, I am wondering if there is a way to initiate a CpeComponentDescriptor from an InputStream or a String, instead of from a physical descriptor file. I am using the following code originally: CpeCasProcessor casProcessor = CpeDescriptorFactory. produceCasProcessor(ae.getName());

Re: General question about UimaFIT

On 09.09.2016, at 13:39, Asher Stern wrote: > > Hi Armin. > Thanks for your quick answer! > > While the workaround is indeed helpful, I am still curios why is there no > regular mechanism to define new types and create new descriptors > programmatically, much like all other

Re: General question about UimaFIT

Hi Armin. Thanks for your quick answer! While the workaround is indeed helpful, I am still curios why is there no regular mechanism to define new types and create new descriptors programmatically, much like all other UIMA components? I mean, what is the difference between type-system and all

AW: General question about UimaFIT

Hi Asher! As a work around, you can use an empty type system, TypeSystemDescription tsd = TypeSystemDescriptionFactory.createTypeSystemDescription("EmptyTypeSystem"); add types programmatically, tsd.addType(typeName, null, CAS.TYPE_NAME_ANNOTATION); and get them later with Type type =

General question about UimaFIT

Hi. I have a general question regarding UimaFIT. In UimaFIT there is no longer need to write and deal with XML files, thanks to new classes and annotations. This is the case for almost all UIMA components, like AE, AAE, CPE, etc. However, for type-system definition, XML files are still required.