Frequently found user model bugs, or How can I stick beans up my nose metaphorically in Soar?
There is intended to turn into a rogue’s gallery of frequently found bugs that are hard to diagnose on your own, but are not bugs in the architecture per se. • If something fishy happens where items drop out of memory and come back in again in a cycle, check I and O-support. If you have a production cycling (firing repeatedly on the same symbols, the rule does not have o-support like you think it does, and it is removing one of the values that matches its conditions, which forces it to retract and its results to retract. The rule now matches again and the loop continues. You need to rewrite the rule to give it o-support, either by fixing its clauses so that they get o-support, giving it o-support explicitly, or by breaking its results up into o-supported clauses and non-o-supported clauses. • If something fishy happens where items drop out of memory and don’t come back in, check for attribute value ties. If two values are both acceptable, but not indifferent and not parallel, they will
