ZGen
0.2.0
a linearization system for natural language.
|
ZGen is a linearization system that constructs natural lnaguage sentences from bags of words, given optional input syntactic constraints. Depending on the amount of input constraints, ZGen can perform free ordering, partial tree linearization and full tree linearization.
ZGen is developed with boost and compiled by cmake, along with some C++ 0x features. To compile ZGen, the following software packages is required:
The compiling commands is
Run the following commands to compile on unix.
After successfully compiling, you will get 3 executable files under the bin folder. They are:
ZGen accept different mount of syntactic constrains. These constraints includes the Postagging and Dependency parse structure. Constrain are input in a 4 columns data format, which means forms, postag, head, deprel. If certain lot (postag, head, deprel) is filled in the input file, it will be used to constrain the decoding process. The following example give an illustration to the barely constrainted input.
And this example is an illustration for the half postag and half dependency constrainted input.
If you want to train your own linearizing model with zgen, you need to prepare your reference data. The reference data should be a well-formed 4 columns dependency tree, as shown below.
Before performing sentence linearization, you need to get the corresponding model. We have provide several pretrained model on English (PennTreebank). You can download it from here.
After preparing the data and model file (we suppose you put the model file in /path/to/your/model), you can run ZGen in following commands:
The option -t
is used to specify the constrain type during the decoding. If your input constrain don't contains dependency relations, please use none
; If your input contains part of but not full dependency relations, you need to use partial
; If your input constrains contains the full dependency relations, please use full
.
The option -p
is used to specify the postag dict. It's an optional resource to constrain the postag for each token, but it's highly recommanded because it will magnitudely reduce the searching space, thus speed up the decoding.
Please refer the LICENSES file.