chunk singleton on everywhere by default

[garfieldnate]

Most of the time users want chunk singleton on to generate better chunks.

Add chunk singleton any topstate any to the default config file.

[garfieldnate]

Relevant section of Mazin's thesis is 5.8, "Unnecessary Generality." The final quote from the section is what we'd like to solve now:

Practically speaking, this feature has proven to be powerful if not essential. In many agents, we find that we must define domain-specific singletons to achieve efficient matching of rules.

What will happen if we set everything to singleton by default and then chunking needs to summarize some WMEs that are not singletons, though? Won't the chunks be under-general? Or does chunk singleton make it impossible to create multiple values of the specified WME's?

[scijones]

This is not a systematic answer, just recollection of some of my experience. When I use "chunk singleton" to declare an attribute that I know is multi-valued as a singleton, the declaration is correctly ignored and the learned chunk tests multiple wmes.

[garfieldnate]

Note from scijones:

In the input, "chunk singleton any 1 any", the "1" is treated as a string. (We don't know how we would make it treat the integer attribute as a singleton.) However, if we change things to be singleton by default, this wouldn't be important to fix.