[CHECK CONVERSION TO NNPSCM, add S-constructor information]

Superspace: u-construct s-construct

Result type: Operator Proposal

Problem Space Overview:

The actual implementation of an u/s-constructor might consist of one empty-op operator or a combination of link and/or snip operators. NL-Soar tries to find all the possible link operators in the generation space. Whenever a link operator is selected, an operator no-change impasse occurs and nl-soar drops into the constraints space . And if this operator passes all the constraints tests, it will be proposed in the superspace, the u/s-construct space. Whenever an empty operator is selected, an operator no-change impasse occurs again but NL-Soar drops into the unconstraints space instead. After beading, the empty operator gets proposed in the u-construct space. Thus, the generator space is also responsible for building the proposals for the link and empty operators in the u-construct space.

Problem Space Proposal:

Proposed in response to a state no-change impasse in the u/s-construct space.

Initial state:

Shares ^ordering-info, and ^adjacency-info and ^assigners, ^receivers, ^semassigners, ^semreceivers2 with u-construct initial state

Operators in Problem Space:

• generate-operator
• exhausted

Search control:

Search control among generate-operator operators mimics preferences on the operators as in the u/s-construct space. Exhausted worse than generate-operator.

Back to the problem-space hierarchy.

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

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