This page provides (emerging) information on support in the LOGON tree for the Answer Constraint Engine (ACE). As of mid-2013, ACE binaries for parsing-generating and treebanking are included with the LOGON tree, albeit (currently) only for 64-bit environments. These binaries are maintained by the ACE developer, WoodleyPackard.
$LOGONROOT/parse --binary --terg+tnt/ace --protocol 2 --best 1 --limit 0 --count 8 cb
To invoke full-forest treebanking, in the [incr tsdb()] podium, select ‘Trees|Switches|External Treebanking Tool’. While this toggle is in effect, the ‘Trees|Annotate’ and ‘Trees|Update’ commands will invoke the external ACE Full-Forest Treebanker. To give an illusion of tight integration, the following [incr tsdb()] parameters will have an effect on the external treebanking tool: (a) selection of a ‘working set’ of items, through a condition on profile entries (e.g. as determined through ‘Options|TSQL Condition’ or ‘Options|New Condition’); (b) the selection of a ‘gold’ profile (by clicking the middle mouse button in the [incr tsdb()] podium), as the source for update information; and (c) the toggle for batch vs. interactive updates (‘Trees|Switches|Automatic Update’).
Furthermore, the invokation of the ACE treebanker application can be customized through ‘Trees|Variables|Treebanking Tool’ or setting the [incr tsdb()] variable *redwoods-treebanker-application* in the per-user ‘.tsdbrc’. The default value, for the time being, is "answer --annotate --terg".
In principle, it should work to follow the ‘common’ release procedure for treebank creation, i.e. first call for an automatic update immediately following the parsing, but adding the option ‘--update/external’ to the ‘parse’ command line. This functionality remains to be validated, though.
Edge identifiers in full ACE derivations (as reported to [incr tsdb()]) are not unique in the context of one input to the parser-generator; this means that ‘classic’ [incr tsdb()] treebanking tools (i.e. tree-based annotation, using syntactic or semantic discriminants) cannot be used on these profiles.
The exact interpretation of the ‘--best’ and ‘--limit’ parameters remains to be defined for forest-based parsing-generating (unlike in the classic setups, a ‘--limit’ of 0 should probably mean recording no derivations, rather than an unlimited number of them; arguably, this interpretation should also be applied retroactively to n-best parsing-generating).
Resource limit specifications through command-line options to the LOGON parse or generate scripts (i.e. --time, --memory, and --edges) are not communicated to the ACE parser-generator.