Parsing/home

From Nordic Language Processing Laboratory
(Difference between revisions)
Jump to: navigation, search
(Contact)
(Parsing Systems)
 
(14 intermediate revisions by 4 users not shown)
Line 2: Line 2:
  
 
An experimentation environment for data-driven dependency parsing is maintained for NLPL under the coordination of Uppsala University (UU).
 
An experimentation environment for data-driven dependency parsing is maintained for NLPL under the coordination of Uppsala University (UU).
Initially, the software and data are commissioned on the Norwegian Abel supercluster.
+
The data is available on the Norwegian Saga cluster and on the Finnish Puhti cluster.
The Uppsala Parser is publicly available at https://github.com/UppsalaNLP/uuparser.
+
The software is available on the Norwegian Saga cluster
Note that the version installed here may exhibit some slight differences, designed to improve ease of use.
+
  
= Using the Uppsala Parser =
+
Initially, software and data were commissioned on the Norwegian Abel supercluster, see [http://wiki.nlpl.eu/index.php/Parsing/abel The Abel page] for legacy information.
  
* Log into Abel
+
= Preprocessing Tools =
* Activate the NLPL module repository:
+
module use -a /projects/nlpl/software/modulefiles/
+
* Load the most recent version of the uuparser module:
+
module load nlpl-uuparser
+
  
== Training a parsing model ==
+
* [http://wiki.nlpl.eu/index.php/Parsing/udpipe UDPipe]
  
To train a set of parsing models on treebanks from Universal Dependencies (v2.1):
+
Additionally, a variety of tools for sentence splitting, tokenization, lemmatization, et al.
 +
are available through the NLPL installations of the
 +
[http://nltk.org Natural Language Processing Toolkit (NLTK)] and the
 +
[https://spacy.io spaCy: Natural Language Processing in Python] tools.
  
uuparser --include [languages to include denoted by their ISO id] --outdir my-output-directory
+
= Parsing Systems =
  
If you want to quickly test the parser is correctly loaded and running without waiting for the full training procedure, add the <code>--mini</code> flag.
+
* [http://wiki.nlpl.eu/index.php/Parsing/uuparser The Uppsala Parser]
For example:
+
* [http://wiki.nlpl.eu/index.php/Parsing/udpipe UDPipe]
 +
* [http://wiki.nlpl.eu/index.php/Parsing/turboparser TurboParser]
  
uuparser --include "sv en ru" --outdir ~/experiments --mini
 
  
will train separate models for UD Swedish, English and Russian and store the results in the <code>experiments</code> folder in your home directory. The <code>--mini</code> flag tells the parser to train on just the first 150 sentences of each language, and evaluate on the first 100 sentences of development data. It also tells the parser to train for just 3 epochs, as opposed to the default 30 (see more below under "Options")
+
Additionallly, parsers are available in several toolkits installed by nlpl: [http://wiki.nlpl.eu/index.php/Parsing/stanfordnlp StanfordNLP], [https://www.nltk.org/ NLTK], [https://spacy.io/ spaCy].
  
Model selection is included in the training process by default; that is, at each epoch the current model is evaluated on the UD dev data, and at the end of training the best performing model for each language is selected.
+
= Training and Evaluation Data =
  
== Predicting with a pre-trained parsing model ==
+
* [http://wiki.nlpl.eu/index.php/Parsing/ud Universal Dependencies v2.0–2.5]
 
+
* [http://wiki.nlpl.eu/index.php/Parsing/sdp Semantic Dependency Parsing]
To predict on UD test data with the models trained above:
+
 
+
uuparser --include "sv en ru" --outdir ~/experiments --predict
+
 
+
You may again include the <code>--mini</code> flag if you prefer to test on a subset of 50 test sentences.
+
 
+
== Options ==
+
 
+
The parser has numerous options to allow you to fine-control its behaviour. For a full list, type
+
 
+
uuparser --help | less
+
 
+
We recommend you set the <code>--dynet-mem</code> option to a larger number when running the full training procedure on larger treebanks. Commonly used values are 5000 and 10000 (in MB). Dynet is the neural network library on which the parser is built.
+
 
+
Note that due to random initialization and other non-deterministic elements in the training process, you will not obtain the same results even when training twice under exactly the same circumstances (e.g. languages, number of epochs etc.). To ensure identical results between two runs, we recommend setting the <code>--dynet-seed</code> option to the same value both times (e.g. <code> --dynet-seed 123456789</code>) and adding the <code>--use-default-seed</code> flag. This ensures that Python's random number generator and Dynet both produce the same sequence of random numbers.
+
 
+
== Training a multilingual parsing model ==
+
 
+
Our parser supports multilingual parsing, that is a single parsing model for one or more languages. To train a ''multilingual'' model for the three languages in the examples above, we simply add the <code>--multilingual</code> flag when training
+
 
+
uuparser --include "sv en ru" --outdir ~/experiments --multiling --dynet-mem 5000
+
 
+
In this case, instead of creating three separate models in the language-specific subdirectories within ~/experiments, a single model will be created directly in this folder. Predicting on test data is then as easy as:
+
 
+
uuparser --include "sv en ru" --outdir ~/experiments --multiling --dynet-mem 5000 --predict
+
 
+
Note that if you want to have different output directories for training and predicting, the <code>--modeldir</code> option can be specified when predicting to tell the parser where the pre-trained model can be found.
+
 
+
== Segmentation ==
+
 
+
In the above examples, we assume pre-segmented input data already in the [http://universaldependencies.org/format.html CONLL-U] format. If your input is raw text, we recommend using UDPipe to segment first. The UDPipe module can be loaded using <code>module load nlpl-udpipe</code> and then run by typing <code>udpipe</code> at the command line, see below.
+
 
+
= Using UDPipe =
+
 
+
UDPipe is available as a module on Abel. It was installed as part of the OPUS activity.
+
 
+
How to use UDPipe:
+
* Log into Abel
+
* Activate the NLPL module repository:
+
module use -a /projects/nlpl/software/modulefiles/
+
* Load the most recent version of the uuparser module:
+
module load nlpl-udpipe
+
 
+
To learn more about using UDPipe, check the official [UDPipe User's Manual](http://ufal.mff.cuni.cz/udpipe/users-manual)
+
 
+
= Data =
+
 
+
For parsing experiments we provide data from the [http://universaldependencies.org/ Univeral Dependencies (UD) project] for a high number of languages. The data is provided in version 2.0, which was also used for the CoNLL shared task 2017, and version 2.1.
+
 
+
All data is available on Abel at <code>/projects/nlpl/data/parsing/universal_dependencies</code>
+
 
+
== UD version 2.0 ==
+
 
+
folders:<br>
+
<code>/projects/nlpl/data/parsing/universal_dependencies/ud-treebanks-v2.0-conll2017</code><br>
+
<code>/projects/nlpl/data/parsing/universal_dependencies/ud-test-v2.0-conll2017</code>
+
 
+
info:<br>
+
Version 2.0 treebanks, archived at http://hdl.handle.net/11234/1-1983. <br>
+
70 treebanks, 50 languages, released March 1, 2017.<br>
+
Test data 2.0 are archived at http://hdl.handle.net/11234/1-2184. <br>
+
81 treebanks, 49 languages, released May 18, 2017.
+
 
+
Release 2.0 has test data released separately from the test data,
+
which is reflected in our folder structure. This data was released for
+
the CoNLL 2017 shared task.
+
 
+
== UD version 2.1 ==
+
 
+
folders:<br>
+
<code>/projects/nlpl/data/parsing/universal_dependencies/ud-treebanks-v2.1</code>
+
 
+
info:<br>
+
Version 2.1 treebanks are available at http://hdl.handle.net/11234/1-2515. <br>
+
102 treebanks, 60 languages, released November 15, 2017.
+
 
+
= Contact =
+
Aaron Smith, Uppsala University<br/>
+
Sara Stymne, Uppsala University<br/>
+
firstname.lastname@lingfil.uu.se
+

Latest revision as of 09:18, 15 January 2020

Contents

[edit] Background

An experimentation environment for data-driven dependency parsing is maintained for NLPL under the coordination of Uppsala University (UU). The data is available on the Norwegian Saga cluster and on the Finnish Puhti cluster. The software is available on the Norwegian Saga cluster

Initially, software and data were commissioned on the Norwegian Abel supercluster, see The Abel page for legacy information.

[edit] Preprocessing Tools

Additionally, a variety of tools for sentence splitting, tokenization, lemmatization, et al. are available through the NLPL installations of the Natural Language Processing Toolkit (NLTK) and the spaCy: Natural Language Processing in Python tools.

[edit] Parsing Systems


Additionallly, parsers are available in several toolkits installed by nlpl: StanfordNLP, NLTK, spaCy.

[edit] Training and Evaluation Data

Personal tools
Namespaces

Variants
Actions
Navigation
Tools