gmane.comp.apache.uima.general

Re: Ruta - Optional First Token Problem

Peter Klügl — 2013-05-23T14:04:55

Hi,

the semantics of the match in the implementation is not as
straightforward as I thought. The fix will take some time.

I would advise that you use two rules for optional leading rule elements
for now:
"a" "b" "c"; // equal to "a"? "b" "c";
"b" "c"; // maybe with a -PARTOF()

Additionally, you could use dynamic anchoring in order to change the
matching direction. Here, the rules do not start with the first element,
but choose the optimal element by a simple heuristic.

Best,

Peter


On 23.05.2013 13:30, Peter Klügl wrote:

Re: AW: Ruta - MARKFAST

Marshall Schor — 2013-05-23T13:32:20

On 5/23/2013 9:03 AM, Armin.Wegner-w0Tf80GBFXAb1SvskN2V4Q< at >public.gmane.org wrote:

Sometimes, noobies make better contributions, because they write for other
noobies :-).  I would encourage you to contribute, anyways.  You can mark up
your contribution with little tags like <?> etc. to indicate you're not sure an
whoever integrates your patch in should pay more attention.

-Marshall

Re: Adding features to TokenAnnotation and DictTerm in Concept Mapper

Renaud Richardet — 2013-05-23T08:48:30

Hi Manisha,

Did you try the configuration params "AttributeList" and "FeatureList"?

(see the docs
http://uima.apache.org/downloads/sandbox/ConceptMapperAnnotatorUserGuide/ConceptMapperAnnotatorUserGuide.html#configParams
)

AW: Ruta - MARKFAST

2013-05-23T13:03:40

Hello Jörn,

absolutely right. But for now I'm still a nooby. That's why I'm asking so much.

Cheers,
Armin



-----Ursprüngliche Nachricht-----
Von: Jörn Kottmann [mailto:kottmann-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org] 
Gesendet: Donnerstag, 23. Mai 2013 14:24
An: user-HHKbSdsD6WQPKjDvHGQMeg< at >public.gmane.org
Betreff: Re: Ruta - MARKFAST

On 05/23/2013 01:19 PM, Peter Klügl wrote:

Another way to improve the documentation is to contribute patches for it, if you use a specific feature of Ruta and know it well enough, just take 10 minutes, write some documentation, open a jira issue and attach the patch to it.

Jörn

Re: Ruta - MARKFAST

Jörn Kottmann — 2013-05-23T12:23:36

Another way to improve the documentation is to contribute patches for it,
if you use a specific feature of Ruta and know it well enough, just take 
10 minutes,
write some documentation, open a jira issue and attach the patch to it.

Jörn

Re: Ruta 2.0.2 Textruler problems

Sondes Bannour — 2013-05-23T12:12:05

That's fine for me. I will continue working with the old version till the
new one is ready.

Cheers,
Sondes

Re: Ruta 2.0.2 Textruler problems

Peter Klügl — 2013-05-23T12:02:12

Hi,

On 23.05.2013 13:49, Sondes Bannour wrote:

Yes, unfortunately I did not yet find the time to adapt the TextRuler
framework to all changes in the last year. There was a lot of renaming
and reimplementation of the inference. It is on my todo list and I will
also provide an exemplary project with documentation in order to
facilitate the usage.

However, I fear that it will take a few weeks (end of June at the
latest) until I will be able to perform the necessary changes. I am
really sorry about that.

Best,

Peter

Ruta 2.0.2 Textruler problems

Sondes Bannour — 2013-05-23T11:49:14

Hi,

I tried the textruler view (whisk (token) ) under Ruta 2.0.2 and i got
weard results like rules with p=0 and n=0 while i fixed the maximum error
threshold to 0.1. Whisk (generic) doesn't even work for me (it seems like
crashing on the first step and still waiting without any results) (i am
just trying the pre-build version). I intend to do some development on
textruler but still don't find the appropriate version: i was using the
textruler source code with textmarker 1.0 but now that textmarker has been
improved i would like to use the latest version, the problem is that
textruler source code isn't working fine with these new versions of
textmarker.

cheers
Sondes

Re: Ruta - Optional First Token Problem

Peter Klügl — 2013-05-23T11:35:52

Hi,

On 23.05.2013 13:30, Peter Klügl wrote:

I just wanted to mention that you can write this rule now also the
following way:

("a"? "b" "c"){-> Test};

which is somehow more appealing to some people ;-)

Peter

Re: Ruta - Optional First Token Problem

Peter Klügl — 2013-05-23T11:30:36

Hi,

On 23.05.2013 13:09, Armin.Wegner-w0Tf80GBFXAb1SvskN2V4Q< at >public.gmane.org wrote:

Yes, this is a bug. Thanks for reporting this and I will fix it ASAP.

In previous versions of the system, the optional part of leading rule
elements was completely ignored. I must have missed that situation in
the test cases since I rarely use string expressions myself because the
implementation is still inefficient (will change soon).

Best,

Peter

Re: Concept Mapper in code

Marshall Schor — 2013-05-23T11:20:53

I made a little test case.  To isolate things to just how array-valued
parameters are programmatically set and accessed, I used a dummy annotator from
the uimaj-examples project called the "RoomNumberAnnotator" - the version I used
has no "initialize" of its own (so it didn't do anything in its initialize method).

Then I did the following "driver" code, modelled after your code, except I only
did one parameter - the string array valued p1:

   public static void main(String[] args) throws ResourceInitializationException {

    AnalysisEngineDescription_impl primitiveDesc = new
AnalysisEngineDescription_impl();
 
    primitiveDesc.setPrimitive(true);
 
    primitiveDesc.getMetaData().setName("test of setting string array parameters");
 
   
primitiveDesc.setAnnotatorImplementationName("org.apache.uima.tutorial.ex1.RoomNumberAnnotator");
 
    ConfigurationParameter p1 = new ConfigurationParameter_impl();
   
    p1.setMultiValued(true);  // needed to have this parameter take an array of
values
 
    p1.setName("AttributeList");
 
    p1.setDescription("Attribute List");
 
    p1.setType(ConfigurationParameter.TYPE_STRING); // This specifies the type
of each element of the array
   
   
primitiveDesc.getMetaData().getConfigurationParameterDeclarations().setConfigurationParameters(
        new ConfigurationParameter[] { p1 });

    // This sets the configuration parameter to a value which is an array of
Strings, "v1" and "v2"
   
primitiveDesc.getMetaData().getConfigurationParameterSettings().setParameterSettings(
       new NameValuePair[] {
           new NameValuePair_impl("AttributeList", new String[] {"v1", "v2"})} );

    TypeSystemDescription typeSystem = new TypeSystemDescription_impl();

    primitiveDesc.getAnalysisEngineMetaData().setTypeSystem(typeSystem);
   
    // For testing - make an UIMA Analysis Engine from this specification
    AnalysisEngine ae = UIMAFramework.produceAnalysisEngine(primitiveDesc);
   
    // Get the UIMA Context from where we can try getting the configuration
parameter settings
    UimaContext context = ae.getUimaContext();
   
    // Get the configured value
    Object v = context.getConfigParameterValue("AttributeList");
   
    System.out.format("Type of object returned is %s, object is %s%n",
v.getClass(), v) ;
   
    // print out the individual strings in the array
    String[] av = (String[]) v;
   
    System.out.format("The two values are %s and %s%n", av[0], av[1]);
  }

I ran this and it printed out:

Type of object returned is class [Ljava.lang.String;, object is
[Ljava.lang.String;< at >45a36ab6
The two values are v1 and v2.

No errors were thrown.

Hope that example helps.

-Marshall

On 5/22/2013 11:08 AM, harshal patni wrote:

Re: AW: AW: Ruta - MARKFAST

Peter Klügl — 2013-05-23T11:19:56

Hi,

On 23.05.2013 13:06, Armin.Wegner-w0Tf80GBFXAb1SvskN2V4Q< at >public.gmane.org wrote:

That is the official documentation. An up-to-date version that describes
the new features since 2.0.0 can be found in the trunk.

I know that there are many passages and section that need to be added or
improved, but it is hard to find enough time for it.

There is ongoing work by others to improve the description of the java
integration for uses cases in part of speech tagging, and we are
planning to provide screencasts for the Ruta Workbench.

Are there any specific passages that should be improved or added? I also
easily forget to add important information (since I implemented it).


This wiki refers to the old version hosted at sourceforge and should not
be referred to.

Best,

Peter

Ruta - Optional First Token Problem

2013-05-23T11:09:16

Hi!

In Ruta 2.0.2-SNAPSHOT, rules with an optional first element do not work. The optional part seems to be mandatory. Using

DECLARE Test;
"a"? "b" "c"{->MARK(Test, 1, 3)};

on

a b c x b c

marks "a b c" (0, 5) but not "b c" (8, 11).

Cheers,
Armin

AW: AW: Ruta - MARKFAST

2013-05-23T11:06:07

Hello Peter,

Now that I understand it, it's a nice feature.

By the way, where can I find a good documentation of Ruta? I only know of http://people.apache.org/~pkluegl/site/textmarker-current/tools.textmarker.book.html and http://tmwiki.informatik.uni-wuerzburg.de/. A more detailed description would be appreciated.

Thanks,
Armin

-----Ursprüngliche Nachricht-----
Von: Peter Klügl [mailto:pkluegl-Gq2KvKmhYTk8VN8EhmRbyw< at >public.gmane.org] 
Gesendet: Mittwoch, 22. Mai 2013 15:09
An: user-HHKbSdsD6WQPKjDvHGQMeg< at >public.gmane.org
Betreff: Re: AW: Ruta - MARKFAST

Hi,

yes this example won't work without changes, because the word list is sensitive to white spaces, e.g., you distinguish between "n.C." and "n.
C.". I know this sound like a bug, but it is rather a feature.

In order to solve your problem you could either remove all spaces in your word list, you could add "n.Chr." and "v.Chr." (without space) to your word list, or you could retain the spaces before calling MARKFAST (Document{-> RETAINTYPE(SPACE)};)

The short explanation for this is that the action and the word list won't see any spaces with the default filtering settings, thus they check on a candidate like "n.Chr". However, in the trie, there is no "h"
in that path without space before the "C".

Best,

Peter

On 22.05.2013 10:52, Armin.Wegner-w0Tf80GBFXAb1SvskN2V4Q< at >public.gmane.org wrote:

Adding features to TokenAnnotation and DictTerm in Concept Mapper

Mansi verma — 2013-05-23T07:36:39

Hi

I am using UIMA for annotating some documents using Concept Mapper. I have
built the dictionaries and configured it to our requirements. However, I
wanted to add
 features to TokenAnnotation and DictTerm.

For Example existing TokenAnnotation annotation supports the following
features :
text, tokenType, tokenClass and uima.tt.tokenAnnotation. Now if I want to
add more features such as POS or group etc.

Is there a neat way of doing it without touching the conceptMapper.jar and
changing our typesystem to extend the two types ?


Thanks
Manisha

Re: managing resources for UIMA?

Richard Eckart de Castilho — 2013-05-22T16:45:14

For some additional half-decent documentation on how and why we do the model packaging as we do it, see:

http://code.google.com/p/dkpro-core-asl/wiki/ResourceProviderAPI
http://code.google.com/p/dkpro-core-asl/wiki/PackagingResources

Re: managing resources for UIMA?

Richard Eckart de Castilho — 2013-05-22T16:43:04

Hi Jens,

for DKPro Core [1], we have packaged a large number of models as Maven artifacts and host them in our public Maven repository [1]. We have made good experiences with this approach. Please do feel free to make use of these packages.

To package models, we use a set of ant-macros [2] which we use in different Ant scripts that download the original models from their original sites and wrap them up in a standard layout and naming scheme, for example [4].

Cheers,

managing resources for UIMA?

Jens Grivolla — 2013-05-22T16:31:45

Hi, while not strictly a UIMA issue, we have a problem that seems very 
relevant in the context of UIMA analysis engines: how to manage large 
binary resources such as trained models used by an AE, etc.

So far, we have managed to achieve a good separation between code 
development and the actual AEs, using Maven (and git for version 
control). An AE thus consists only of a POM referencing the code, the AE 
descriptor, and the resources used for the AE. The AE poms are 
configured to generate PEAR archives that include all dependencies and 
resources.

At this point we have the code in git, and the AEs' pom and descriptor 
also, while we manually copy the resources to the directory before 
running `mvn package` (and exclude those resources from git). We're 
missing a way to manage those resources, including versioning etc.

I'm guessing that this is a rather typical problem, so what solutions do 
you use? We're thinking of having all resources also in Maven (e.g. 
Artifactory) so we can reference them with a unique identifier and 
version. This would also help us when moving to more complex pipeline 
assemblies using uimafit instead of generating individual PEARS for each 
component in order to create complete packages.

Btw, we are just very few core developers, with most of the team made up 
of linguists, so we want to make it easy for them to save versions of 
resources they create and assemble AEs by just referencing the algorithm 
and resource (e.g. "create a new OpenNLP POStagger using 
spanish-pos-model.bin, version 1.2.3").

Thanks for sharing your experiences with this...

Jens

Re: Concept Mapper in code

Richard Eckart de Castilho — 2013-05-22T15:30:48

A stack-trace would be helpful.

Re: Concept Mapper in code

harshal patni — 2013-05-22T15:08:26

Yes I did! When I do that it throws the following error -
It throws a cast error stating Type String cannot be converted to String
array.

Harshal


On Wed, May 22, 2013 at 8:03 PM, Marshall Schor <msa-DzKsKX1/Fv4AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: Concept Mapper in code

Marshall Schor — 2013-05-22T14:33:52

did you have the multi-values setting turned on in the parameter specification?


On 5/22/2013 10:15 AM, harshal patni wrote: