PROBLEM SPACE: COMPLETION

Superspace: top-space

Result type: Operator Elaboration

Problem Space Overview:

After the basic implementations of a constructor have been constructed in the u-construct space or s-construct space, we would still get an operator no-change impasse for the u/s-constructor because it has not been reconsiderd. The completion space is thus used to terminate the u/s-constructor and to mark u/s-model-succes flag on the current word NL-Soar is working on.

In checking for u/s-model-success, a chunk is built and it becomes part of the implementation of the u/s-constructor. Even if no knowledge allows for u/s-model-succes to be marked, a reconsider is still returned (and chunked). However, this will lead to another learn-language operator and the creation of an empty operator, which will always leads to a completion (i.e., a successful marking of the u/s-model-success flag).

Problem Space Proposal:

Proposed whenever there is an operator no-change impasse on a u/s-constructor that has the attribute-value pair (^annotation applied).

Initial state:

An empty initial state is created.

Operators in Problem Space:

• completed
• incomplete

Search control:

This problem space has the best preference to prevent u/s-construct space from being selected again.

The operator completed for empty op is better than other operators. In general,completed is prefered over incomplete operators.

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 Mark Smith