Apache UIMA Ruta Guide and Reference - Apache UIMA - The ...

More documents

Recommendations

Info

seeders Ruta Engine This list of string values refers to implementations of the interface "org.apache.uima.ruta.seed.RutaAnnotationSeeder", which can be used to automatically add annotations to the CAS. The default value of the parameter is a single seeder, namely "org.apache.uima.ruta.seed.DefaultSeeder" that adds annotations for token classes like CW, MARKUP or SEMICOLON. Remember that additional annotations can also be added with an additional engine that is executed by a UIMA Ruta rule. defaultFilteredTypes This parameter specifies a list of types, which are filtered by default when executing a script file. Using the default values of this parameter, whitespaces, line breaks and markup elements are not visible to Ruta rules. The visibility of annotations and, therefore, the covered text can be changed using the actions FILTERTYPE and RETAINTYPE. removeBasics This parameter specifies whether the inference annotations created by the analysis engine should be removed after processing the CAS. The default value is set to false. dynamicAnchoring If this parameter is set to true, then the Ruta rules are not forced to start to match with the first rule element. Rather, the rule element referring to the most rare type is chosen. This option can be utilized to optimize the performance. Please mind that the matching result can vary in some cases when greedy rule elements are applied. The default value is set to false. lowMemoryProfile This parameter specifies whether the memory consumption should be reduced. This parameter should be set to true for very large CAS documents (e.g., > 500k tokens), but it also reduces the performance. The default value is set to false. simpleGreedyForComposed debug This parameter specifies whether a different inference strategy for composed rule elements should be applied. This option is only necessary when the composed rule element is expected to match very often, e.g., a rule element like (ANY ANY). The default value of this parameter is set to false. If this parameter is set to true, then additional information about the execution of a rule script is added to the CAS. The actual information is specified by the following parameters. The default value of this parameter is set to false. debugWithMatches This parameter specificies whether the match information (covered text) of the rules should be stored in the CAS. The default value of this parameter is set to false. debugOnlyFor This parameter specifies a list of rule-ids that enumerate the rule for which debug information should be created. No specific ids are given by default. 14 Apache UIMA Ruta Overview UIMA Ruta Version 2.0.1
profile Annotation Writer If this parameter is set to true, then additional information about the runtime of applied rules is added to the CAS. The default value of this parameter is set to false. statistics If this parameter is set to true, then additional information about the runtime of UIMA Ruta language elements like conditions and actions is added to the CAS. The default value of this parameter is set to false. createdBy If this parameter is set to true, then additional information about what annotation was created by which rule is added to the CAS. The default value of this parameter is set to false. 1.5.2. Annotation Writer This Analysis Engine can be utilized to write the covered text of annotations in a text file, whereas each covered text is put into a new line. If the Analyis engine, for example, is configured for the type “uima.example.Person”, then all covered texts of all Person annotations are stored in a text file, one person in each line. A descriptor file for this Analysis Engine is located in the folder “descriptor/utils” of a UIMA Ruta project. 1.5.2.1. Configuration Parameters Output This string parameter specifies the absolute path of the resulting file named “output.txt”. However, if an annotation of the type “org.apache.uima.examples.SourceDocumentInformation” is given, then the value of this parameter is interpreted to be relative to the URI stored in the annotation and the name of the file will be adapted to the name of the source file. The UIMA Ruta Workbench automatically adds the SourceDocumentInformation annotation when the user launches a script file. The default value of this parameter is “/../output/”. Encoding Type This string parameter specifies the encoding of the resulting file. The default value of this parameter is “UTF-8”. Only the covered texts of annotations of the type specified with this parameter are stored in the resulting file. The default value of this parameter is “uima.tcas.DocumentAnnotation”, which will store the complete document in a new file. 1.5.3. Plain Text Annotator This Analysis Engines adds annotations for lines and paragraphs. A descriptor file for this Analysis Engine is located in the folder “descriptor/utils” of a UIMA Ruta project. There are no configuration parameters. UIMA Ruta Version 2.0.1 Apache UIMA Ruta Overview 15
Page 1 and 2: Apache UIMA Ruta Guide and Referenc
Page 3 and 4: Table of Contents 1. Apache UIMA Ru
Page 5: Apache UIMA Ruta Guide and Referenc
Page 8 and 9: Core Concepts then the actions of t
Page 10 and 11: Learning by Example There is also a
Page 12 and 13: Learning by Example matches on numb
Page 14 and 15: Learning by Example BLOCK(German) D
Page 16 and 17: Ruta Engine File specFile = new Fil
Page 18 and 19: Ruta Engine Name Short description
Page 22 and 23: 1.5.4. Modifier Modifier The Modifi
Page 24 and 25: Style Map Creator pattern. Per defa
Page 26 and 27: Basic annotations and tokens | ("BO
Page 28 and 29: Quantifiers Annotation Parent Descr
Page 30 and 31: Rule: SW CW[1,2] SW Matched: small
Page 32 and 33: Components //package "my.package" D
Page 34 and 35: 2.5.3.2. Example: Boolean Expressio
Page 36 and 37: 2.6.2.1. Definition: AND(Condition1
Page 38 and 39: 2.6.6.2. Example: CURRENTCOUNT Para
Page 40 and 41: 2.6.12. IS IS The IS condition eval
Page 42 and 43: 2.6.18. PARSE PARSE The PARSE condi
Page 44 and 45: 2.6.23.1. Definition: SIZE SCORE(Nu
Page 46 and 47: 2.7.2. ADDFILTERTYPE ADDFILTERTYPE
Page 48 and 49: CONFIGURE This rule colors all Head
Page 50 and 51: 2.7.13.2. Example: FILTERTYPE Headl
Page 52 and 53: 2.7.18. GETLIST GETLIST This action
Page 54 and 55: MARKONCE This rule annotates the la
Page 56 and 57: 2.7.27.2. Example: REMOVE Document{
Page 58 and 59: 2.7.33.2. Example: Document{->RETAI
Page 60 and 61: 2.7.38.2. Example: Keyword{-> TRIM(
Page 62 and 63: Blocks You will see that this match
Page 64 and 65: } Heuristic extraction using scorin
Page 66 and 67: WORDTABLEs WORDLIST FirstNameList =
Page 69 and 70: Chapter 3. Apache UIMA Ruta Workben
Page 71 and 72:
UIMA Ruta Workbench Overview 2. The
Page 73 and 74:
UIMA Ruta create project wizard Fig
Page 75 and 76:
UIMA Ruta Perspective 3.4. UIMA Rut
Page 77 and 78:
Explain Perspective Figure 3.7. Sel
Page 79 and 80:
Matched Rules and Failed Rules 3.5.
Page 81 and 82:
Statistics The following image show
Page 83 and 84:
Usage script. As a product of the t
Page 85 and 86:
Usage collected result data can be
Page 87 and 88:
Usage The testing environment also
Page 89 and 90:
3.7.2. Evaluators Evaluators When t
Page 91 and 92:
Available Learners • Status: The
Page 93 and 94:
Martin Apply a UIMA Ruta script to
show all

Apache UIMA Ruta Guide and Reference - Apache UIMA - The ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?