PROBLEM SPACE: CONSTRAINTS

Superspace: generator

Result type: Operator Elaboration

Problem Space Overview:
Tests ordering and agreement on link operators under construction. If a test fails, rejects generate-operator operator in supergoal. If tests succeed, augments generate-operator operator with ^annotation constraints-passed and, possibly, ^return-agreements. The value of this latter attribute gets put on the representation of the link operator under construction. Eventually, it will be used to enforce the agreements between the words.

Problem Space Proposal:
Proposed whenever there is an operator no-change, rejected whenever the operator no-change is not a generate-operator. By not testing the name of the operator in the proposal, the system learns elaboration productions from the impasse that will reject failed operators in the top space.

Initial state:
Shares ^ordering-info and ^adjacency-info with superstate. Create attribute ^agreements, which is used as a medium attribute to pass back agreements to ^return-agreements.

Operators in Problem Space:

Search control:
Check operators are indifferent. Constraints-success is worst than any check operators.

Productions are in the file: constraints.soar (for u-constructors)

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