Parse sents2X.ocf by using the command

parse sents2X

and after reviewing the results in

sents2X.log

write an analysis of the results.

Where it applies, you could answer such questions as:

1. Is the sentence, as an English sentence, grammatically wellformed?
2. Was a parse obtained?
3. If a parse was obtained, was it the intended analysis? I.e. does the ASSERTION accord with the main assertion in the sentence as you understand it? Are the modifiers the ones that you identify in your reading of the sentence, and do they modify the right element? If the parse is not the intended analysis, draw a parse tree of the correct one.
4. If no, parse was obtained, what feature of the grammar prevented it?
5. If a new structure or constraint is needed, describe it.

Note that parse calls upon the file parse.inp for input directives. The directive *TRACE=T causes every step in the building (and rebuilding) of the parse tree to be printed, i.e. records every call on the BNF definitions of the grammar. To turn off the BNF trace, replace *TRACE=T by *TRACE=F.

In the file parse.inp the directive *TRACER=T causes every step in the execution of all restrictions to be printed. If only a particular restriction is of interest, e.g. WAGREE, the form is

*TRACER(WAGREE)=T.

A companion directive *TRACERTREE(WAGREE)=T provides a short version of the parse tree at the time WAGREE is executed. In the parse.inp file for this lesson, no *TRACER=T is supplied; instead we have

*TRACERTREE(WAGREE)=T

*TRACER(WAGREE)=T

*TRACERTREE(WVERBOBJ)=T

*TRACER(WVERBOBJ)=T

Other restrictions can be traced in the same manner.