Clever Cliques

[johnwdubois]

Background

1. A clique should be clever enough to know what's in it. But cliques change fast, so it's necessary to regularly update what's in the clique (without slowing things down).
2. Some clique updates may be needed only to support analysis outside of Rezonator (e.g. in rezonateR). These could be updated at long intervals -- e.g. once per minute, or per hour, or even just when the file is saved.

What to do

1. A clique should know which of the following it contains (in whole or part):
   • Units
   • Rez chains
2. A clique should also know its size, which should be calculated and saved according to several different measures (see #820 ).
3. Secondarily, it may be useful for a clique to know which of the following it contains. These may be derived from the primary contents of the clique (Units and Rez chains). Some may be wholly included in (coextensive with) the clique, while others are added to the clique "family", even though their contents may appear only partly inside the clique, and partly outside it.
   • "Contents" of all included Units
   • "Contents" of all included Rez chains
   • Chunks
   • Tokens
   • Trees
4. It is debatable whether it is useful for a clique to know which of the following it contains (in whole or part):
   • Trails
   • Stacks
   • ?

[johnwdubois]

Added another point above:

2. A clique should also know its size, which should be calculated and saved according to several different measures (see #820 ).

[terrydubois]

When refreshing chain order lists within cliques, preform this operation only on the clique(s) that need to be refreshed.