Download LKB User Manual - Stanford University

LKB user interface / 169
Print chart / Print parser chart∗ Displays the chart (crudely) to
the standard Lisp output (e.g., the emacs buffer). This can be useful as
an alternative display to the parse chart window, especially with very
large charts.
Print generator chart∗ As above, but for the generator.
6.1.8 Advanced∗
Tidy up This command clears expanded lexical entries which are stored
in memory. If accessed again they will be read from file and expanded
again.
Expansion of a large number of word senses will tend to fill up memory with a large number of TFSs. Most commands which are likely
to do this to excess, such as the batch parser, actually clear the TFSs
themselves, but if a lot of sentences have been parsed interactively and
memory is becoming restricted this option may be useful.
Create quick check file The check path mechanism constructs a filter
which improves efficiency by processing a set of example sentences. It is
discussed in more detail in §8.3.1.
The command prompts for a file of test sentences and an output
file to which the resulting paths should be written. This file should
subsequently be read in by the script. Note that constructing the check
paths is fairly time-consuming, but it is not necessary to use a very large
set of sentences. The mechanism is mildly grammar-specific in that it
assumes the style of encoding where the daughters of a rule are given by
an args list — see §8.3.1 for details.
6.1.9 Options
Expand/Shrink menu Changes the LKB top menu so that the advanced commands are added/removed.
Set options Allows interactive setting of some system parameters.
Note that the values of the boolean parameters are specified in the standard way for Common Lisp: that is, t indicates true and nil indicates
false. I will not go through the parameters here: Chapter 9 gives full
details of all parameters, including those that cannot be altered interactively.
If a parameter file has been read in by the script (using the load
function load-lkb-preferences) the parameter settings are saved in
the same file. Otherwise the user is prompted for the name of a file to
save any preference changes to. This file would then have to be specified
in the script if the changes are to be reloaded in a subsequent session.
Usually the preferences file is loaded by the script so that any preferences which are set in one session will be automatically saved for a
Copyright © 2002 CSLI Publications. To purchase, click here.