Superspace: create-operator

Result type: operator implementation

Problem Space Overview:

The u-construct space creates the implementation for new u-constructors (u-constructors build pieces of the utterance model ).

Problem Space Proposal:

The problem space is proposed in response to an operator no-change impasse on the u-constructor operator gensymed by the create-operator space.

Initial state:

Shares the same state as create-operator problem space.

Operators in Problem Space:

• empty operator
• link
• snip

Note that these operators are not initially proposed in this problem space. A state no-change impasse will occur first and this leads to the selection of the generator space . Each u-constructor can either be one empty-op or consist of one or more link and/or snip operators. When the spaces below this u-construct space terminate and return, the empty-op, link or snip operator gets proposed and executed in this space. Implementation chunks are thus built and these chunks would eventually fire in the top-space too because u-construct shares state with create-operator and the state in create-operator is a lean copy of the top space. If other link or snip operators are possible, nl-soar will keep dropping into the generator space until the generator space results in a exhaustion operator.

Search Control:

Empty operators are worse than any link or snip operators. Link operators are indifferent but are prefered to snip operators. Snip operators are indifferent. In addition, there are a large number of additional search control rules that help mediate among link operators based upon the pieces of structure they will build (see u-construct.search-ctrl.soar.)

Back to the problem-space hierarchy.

Updated by Julie Van Dyke (vandyke@cs.cmu.edu), August, 1997

This page written by Jill Fain Lehman (jef@cs.cmu.edu) and Han Ming Ong (hanming@cs.cmu.edu)