[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki

[ Back to the navigation ]

You are here: start » external » tectomt » tutorial

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
external:tectomt:tutorial [2009/01/19 13:24]
kravalova 		external:tectomt:tutorial [2009/01/20 16:55]
popel Blocks ARE parametrizable now
Line 2: Line 2:
  
 Welcome at TectoMT Tutorial. This tutorial should take about 2 hours. Welcome at TectoMT Tutorial. This tutorial should take about 2 hours.
 +
  
  
Line 7: Line 8:
  
 TectoMT is a highly modular NLP (Natural Language Processing) software system implemented in Perl programming language under Linux. It is primarily aimed at Machine Translation, making use of the ideas and technology created during the Prague Dependency Treebank project. At the same time, it is also hoped to significantly facilitate and accelerate development of software solutions of many other NLP tasks, especially due to re-usability of the numerous integrated processing modules (called blocks), which are equipped with uniform object-oriented interfaces.  TectoMT is a highly modular NLP (Natural Language Processing) software system implemented in Perl programming language under Linux. It is primarily aimed at Machine Translation, making use of the ideas and technology created during the Prague Dependency Treebank project. At the same time, it is also hoped to significantly facilitate and accelerate development of software solutions of many other NLP tasks, especially due to re-usability of the numerous integrated processing modules (called blocks), which are equipped with uniform object-oriented interfaces. 
 +
  
 ===== Prerequisities ===== ===== Prerequisities =====
 +
 +In this tutorial, we assume 
 +
 +  * Your system is Linux
 +  * Your shell is bash
 +  * You have basic experience bash and you can read Perl
 +
 +
 +
 +
 +
 +
  
  
Line 14: Line 28:
 ==== Installation and setup ==== ==== Installation and setup ====
  
-TODO popsat instalaci+  * Checkout SVN repository. If you are running this installation in a computer lab in Prague, you have to checkout the repository into directory ''/home/BIG'' (because data quotas don't apply here):
  
-Before running any experiments with TectoMT, you must set up your environment by running+<code bash> 
 +    cd ~/BIG 
 +    svn --username <username> co https://svn.ms.mff.cuni.cz/svn/tectomt_devel/trunk tectomt 
 +</code> 
 + 
 +  * In ''tectomt/install/'' run ./install.sh:
  
 <code bash> <code bash>
-source config/init_devel_environ.sh+    cd tectomt/install 
 +    ./install.sh
 </code> </code>
 +
 +  * In your ''.bashrc'' file, add line (or source this file every time before experimenting with TectoMT):
 +
 +<code bash>
 +    source ~/BIG/tectomt/config/init_devel_environ.sh
 +</code>
 +
 +
 +
 +
  
  
  
  
-==== Theoretical background ==== 
  
-TODO obrazek 
  
  
Line 34: Line 62:
  
  
-==== TrEd ==== 
  
-TODO malicko o TrEdu a obrazek 
  
  
Line 42: Line 68:
  
 ===== TectoMT Architecture ===== ===== TectoMT Architecture =====
 +
  
  
Line 49: Line 76:
 In TectoMT, there is the following hierarchy of processing units (software components that process data): In TectoMT, there is the following hierarchy of processing units (software components that process data):
  
-  * The basic units are blocks. They serve for some very limited, well defined, and often linguistically interpretable tasks (e.g., tokenization, tagging, parsing). Blocks are not parametrizable. Technically, blocks are Perl classes inherited from ''TectoMT::Block''. The blocks repository is in ''libs/blocks/''.+  * The basic units are blocks. They serve for some very limited, well defined, and often linguistically interpretable tasks (e.g., tokenization, tagging, parsing). Technically, blocks are Perl classes inherited from ''TectoMT::Block'', each saved in a separate file. The blocks repository is in ''libs/blocks/''.
   * To solve a more complex task, selected blocks can be chained into a block sequence, called also a scenario. Technically, scenarios are instances of ''TectoMT::Scenario'' class, but in some situations (e.g. on the command line) it is sufficient to specify the scenario simply by listing block names separated with spaces.   * To solve a more complex task, selected blocks can be chained into a block sequence, called also a scenario. Technically, scenarios are instances of ''TectoMT::Scenario'' class, but in some situations (e.g. on the command line) it is sufficient to specify the scenario simply by listing block names separated with spaces.
-  * The highest unit is called application. Applications correspond to end-to-end tasks, be they real end-user applications (such as machine translation), or 'only' NLP-related experiments. Technically, applications are often implemented as ''Makefiles'', which only glue the components existing in TectoMT. Some demo applications can be found in ''applications''+  * The highest unit is called application. Applications correspond to end-to-end tasks, be they real end-user applications (such as machine translation), or 'only' NLP-related experiments. Technically, applications are often implemented as ''Makefiles'', which only glue the components existing in TectoMT. Some demo applications can be found in ''applications''.
  
 This tutorial itself has its blocks in ''libs/blocks/Tutorial'' and the application in ''applications/tutorial''. This tutorial itself has its blocks in ''libs/blocks/Tutorial'' and the application in ''applications/tutorial''.
 +
  
  
Line 59: Line 87:
  
 ==== Layers of Linguistic Structures ==== ==== Layers of Linguistic Structures ====
 +
 +{{ external:tectomt:pyramid.gif?300x190|MT pyramid in terms of PDT layers}}
  
 TectoMT blocks repository is saved in ''libs/blocks/''. In correspondence with ..., the blocks are located in directories describing their purpose.  TectoMT blocks repository is saved in ''libs/blocks/''. In correspondence with ..., the blocks are located in directories describing their purpose. 
Line 156: Line 186:
 tmttred sample.tmt tmttred sample.tmt
 </code> </code>
 +
 +
 +
 +
  
  
Line 214: Line 248:
 <code bash> <code bash>
 print_info: print_info:
-        brunblocks -S -o Print::Print_node_info -- sample.tmt+        brunblocks -S -o Tutorial::Print_node_info -- sample.tmt
 </code>         </code>        
  
Line 223: Line 257:
 </code> </code>
  
-Try to change the block so that it prints out the information only for verbs. (You need to look at attribute ''tag'' at the ''m'' level). The tagset is Penn Treebank Tagset.+Try to change the block so that it prints out the information only for verbs. (You need to look at attribute ''tag'' at the ''m'' level). The tagset used is Penn Treebank Tagset.
  
  
Line 231: Line 265:
  
 ===== Advanced block: finite clauses ===== ===== Advanced block: finite clauses =====
 +
 +
 +
  
  
Line 236: Line 273:
 ==== Motivation ==== ==== Motivation ====
  
-TODO prelozit motivaci+It is assumed that finite clauses can be translated independently, which would reduce computational complexity or make parallel translation possible. We could even use hybrid translation - each finite clause could be translated by the most self-confident translation system. In this task, we are going to split the sentence into finite clauses. 
 + 
 + 
  
 ==== Task ==== ==== Task ====
-A block which, given an analytical tree (''SEnglishA''), fills each ''a-node'' with nummerical attribute ''<clause>'' so that nodes in the same finite clause are marked with the same number of clause.+A block which, given an analytical tree (''SEnglishA''), fills each ''a-node'' with boolean attribute ''is_head'' which is set to ''1'' if the ''a-node'' corresponds to a finite verb, and to ''0'' otherwise. 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
  
  
  
  
-==== Algorithm ==== 
  
-TODO obrazek a vysvetleni algoritmu 
  
  
Line 254: Line 306:
 ==== Instructions ==== ==== Instructions ====
  
-There is a block template with hints in ''libs/blocks/Tutorial/Tutorial_fill_finite_clauses.pm''. You should edit the block so that the ouput of this block is the same a-tree, in addition with nummerical value ''<clause>'' attached to each ''a-node''. There is also a printing block ''libs/blocks/Tutorial_print_finite_clauses.pm'' which will print out the ''a-nodes'' grouped by clauses:+There is a block template with hints in ''libs/blocks/Tutorial/Mark_heads.pm''. You should edit the block so that the ouput of this block is the same a-tree, in addition with attribute ''is_head'' attached to each ''a-node''. There is also a printing block ''libs/blocks/Print_finite_clauses.pm'' which will print out the ''a-nodes'' grouped by clauses:
  
 <code bash> <code bash>
 finite_clauses: finite_clauses:
         brunblocks -S -o \         brunblocks -S -o \
-                SEnglishA_to_SEnglishT::Tutorial_fill_finite_clauses \ +                Tutorial::Mark_heads \ 
-                Print::Tutorial_print_finite_clauses -- sample.tmt+                Tutorial::Print_finite_clauses -- sample.tmt
 </code> </code>
  
 You are going to need these methods: You are going to need these methods:
  
-  * ''$bundle->get_tree($tree_name)'' +  * ''my root = $bundle->get_tree('tree_name')'' 
-  * ''$node->get_attr($attr_name)''+  * ''my $attr = $node->get_attr('attr_name')''
   * ''$node->set_attr('attr_name',$attr_value)''   * ''$node->set_attr('attr_name',$attr_value)''
-  * ''$node->get_eff_children()'' +  * ''my @eff_children = $node->get_eff_children()''
-  * ''$node->get_children()''+
  
 +//Note//: ''get_children'' returns topological node children in a tree, while ''get_eff_children'' returns node children in a linguistic sense. Mostly, these do not differ.
  
-==== Is it perfect? ==== 
  
-The output of our block is not ideal - we don't solve coordination and subordinate conjunctions. But for the time being, we can move to other tasks.+ 
 +//Advanced version//: The output of our block might still be incorrect in special cases - we don't solve coordination and subordinate conjunctions.
  
  
Line 280: Line 332:
 ===== Your turn: more tasks ===== ===== Your turn: more tasks =====
  
-==== SVO typology ==== 
  
  
Line 286: Line 337:
  
  
-==== Coordination ==== 
  
-This time ...  
  
-You can use block template in ''devel/libs/blocks/BlockTemplate.pm''. To see the results, you can again use TrEd (''tmttred sample.tmt'')+==== SVO to SOV ==== 
 + 
 +**Motivation**: During translation from an SVO based language (English) to an SOV based language (Korean) we might need to change the word order from SVO to SOV.  
 + 
 +**Task**: Change the word order from SVO to SOV. 
 + 
 +**Instructions**:  
 + 
 +  * To find an object to a verb, look for objects among effective children of a verb (''$child->get_attr('afun') eq 'Obj' ''). That implies working on analytical layer. 
 +  * Once you have node ''$object'' and node ''$verb'', use method TODO  
 +  * For debugging, a method returning word order of a node is useful: ''$node->get_attr('ord')''. It can be used to print out nodes sorted by attribute ''ord''. 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 + 
 +==== Prepositions ==== 
 + 
 +**Motivation**: In dependency approach a question "where to hang prepositions" arises. In praguian style (PDT), prepositions are heads of the subtree and the noun/pronoun is dependent on the preposition. However, another ordering might be preferable: The noun/pronoun might be the head of subtree, while the preposition would take the role of a modifier. 
 + 
 +TODO obrazek 
 + 
 +**Task**: The task is to rehang all prepositions as indicated at the picture. You may assume that prepositions have at most 1 child. 
 + 
 +** Instructions**: 
 + 
 +You are going to need these new methods: 
 +  * ''my @children = $node->get_children'' 
 +  * ''my $parent = $node->get_parent'' 
 +  * ''$node->set_parent($parent)'' 
 + 
 +//Hint//:  
 +  * On analytical layer, you can use this test to recognize prepositions: ''$node->get_attr('afun') eq 'AuxP' ''  
 +  * You can use block template in ''libs/blocks/BlockTemplate.pm''. To see the results, you can again use TrEd (''tmttred sample.tmt'') 
 + 
 + 
 +//Advanced version//: What happens in case of multiword prepositions? For example, ''because of'', ''instead of''. Can you handle it? 
 + 
 + 
  
  
Line 298: Line 401:
   * [[http://ufallab2.ms.mff.cuni.cz/~bojar/cruise_control_tmt/last_doc/generated/guide/guidelines.html|TectoMT Developer's Guide]] - obsolete   * [[http://ufallab2.ms.mff.cuni.cz/~bojar/cruise_control_tmt/last_doc/generated/guide/guidelines.html|TectoMT Developer's Guide]] - obsolete
   * Questions? Ask ''kravalova'' at ''ufal.mff.cuni.cz''   * Questions? Ask ''kravalova'' at ''ufal.mff.cuni.cz''
-  * Solutions to +  * Solutions to this tutorial tasks are in ''libs/blocks/Tutorial/*solution.pm''. 
 +  * [[http://ufal.mff.cuni.cz/~pajas/tred/|TrEd]] - tree editor
  
  
  
  

[ Back to the navigation ] [ Back to the content ]