What does using a ^problem-space.name flag buys you apart from providing a conventional label within which to enable operator proposition?
From Randy Jones: My opinion is that the ^problem-space flag is an anachronism that should be discarded, especially for non-trivial Soar programs. The flag originally arose from Newell and Simon’s problem-space hypothesis, and the notion that people tend to employ specific sets of methods and goals for specific types of problems. What this “flag-based” representation neglects, however, is the potential for sharing methods and goals across types of problems that we might normally view as being in distinct problem spaces. In TacAir-Soar, for example, we have *many* operators that can apply in a variety of different states, independent of the problem-space flag on that state. In general (and again in my opinion), operators should be sensitive to patterns of data represented on the “current state”, rather than being a slave to a single, discrete, problem-space flag. This allows the use of operators to transfer across problem spaces in useful, and sometimes surprising, ways. Under this view
Related Questions
- Why will we hear on the radio or television that there is a Red Flag condition yet the 311 Operator indicates that the City of Los Angeles is not enforcing the Towing Policy?
- What does using a ^problem-space.name flag buys you apart from providing a conventional label within which to enable operator proposition?
- Can I apply for other games such as for lottery winnings refunds apart from conventional casino gambling activities?
