Now set up the model's activation. swarmContext indicates where
we're being started in - typically, this model is run as a
subswarm of an observer swarm.
the min level of inter-visibility; below this level two units cannot
exchange products; this value is not used in assignment coming from
OrderGenerator
ActionGroup for holding an ordered sequence of action
(the numbers of the model action names are the same used in the full
jES model, so some are lacking in this version)
ActionGroup for holding an ordered sequence of action
(the numbers of the model action names are the same used in the full
jES model, so some are lacking in this version)
ActionGroup for holding an ordered sequence of action
(the numbers of the model action names are the same used in the full
jES model, so some are lacking in this version)
repetition in unit creation
if repeatUnitGeneration > 1 each type of unit (as in each row of
unitData/unitBasicData.txt) can be be created in multiple copies,
always applying unitGenerationInitialP; unit number are
unit*100+repetition factor (if repeatUnitGeneration > 99 we have
nonsense numbers)
the integer vector containing the unit of time spent for each step
in the recipe; il will determine the tranformation of the orderRecipe1
vector into the orderRecipe2 vector containing the repetitions
of the steps, to reproduce the length of each step in time
NB this formalism is internal to internal (in external formalism
we have 'step s/h/d time'
as an examples
orderRecipe1 contains 1 12 7 3
stepLengthInOrder contains 1 3 2 2
orderRecipe2 contains 1 12 12 12 7 7 3 3
The Unit class instances are micro unit in our virtual enterprise;
i.e. the units where the steps required to build a product (to fulfill
an order) are done
at the beginning of each time tick in the 'day', each unit looks for
the order(s) (if any) to be executed; the production
cycle is 'one unit of time'
in a step of the recipe of an order in a tick of a day;