Nested swarms

[Sven Thommesen]

Manor,

I'm trying to "unpack" Heatbugs according to your suggestion. I have the 
BatchSwarm/ObserverSwarm own the ModelSwarm which owns several sub-Swarms, 
each of which contains a bugList. I puzzle over the following:

a) in heatbugBatchSwarm, in method activateIn, there is first a call to
   [super activateIn: swarmContext], and then 
   [heatbugModelSwarm activateIn: self].

With another level of swarm to be activated (call it HeatbugSwarm), how 
does the story go? Do they all get activated by the BatchSwarm, or each 
separately? If separately, is it optional whether the ModelSwarm gets 
activated in BatchSwarm or in itself?

b) in my ModelSwarm, in method buildActions, I would create actions to tell 
my attribute spaces to do stepRule and updateLattice, because these spaces 
are owned by the ModelSwarm. But what about the bugSwarms that are owned by 
the ModelSwarm? I could just call [heatbugSwarm buildActions], but how then 
do we specify that the actions of the bugs come inbetween the actions taken 
on the attribute spaces?

c) (some objc syntax:) module HeatSpace has a method defined thus:
-(HeatValue) findExtremeType: (HeatExtremeType) heat X: (int*)x Y: (int*)y;
Now assume that the caller wishes to pass along to HeatSpace a method to be 
used to evaluate the "value" of a particular square, call it UtilFunc. 
[Yes, I'm an economist!] How might the resulting message look?

Grateful for any pointers (however indirect),
Sven