Challenges in Engineering Self-Organizing Systems

From Self-Organization Wiki
Revision as of 23:09, 12 July 2010 by Welmenre (talk | contribs)
Jump to: navigation, search
  • Design of emergence:
    • How to design local rules achieving the desired global properties?
    • Non-trivial but approaches exist (eg. evolutionary design).
    • Definition of fitness function (designer needs to provide intermediate goals first (eg. subgoals like ball handling in a soccer simulation), but overall system can later revise/remove those intermediate steps (only winning the game counts))
  • Simple versus chaotic behavior: Can we describe the system state?
    • The state of some self-organizing systems can be easily modeled (firefly sync)
    • The state of other self-organizing systems cannot be modeled, they exhibit chaotic behavior, which makes it impossible to predict future states.
  • Robustness issues
    • Malicious nodes, faults, defects
  • Testing:
    • It can be very difficult to test a proposed self-organizing system with respect to a given goal (many entities, large operational range, chaotic behavior)
    • Rare events may lead to major global effects.
    • Repeatability of results
    • even simple deterministic systems can bear an interesting, unexpected (unwanted?) behavior, cf. Langton's Ant.
  • User aspects
    • To what extend can today’s systems be replaced or complemented by self-organizing systems, taking into account
      • constraints and acceptance of the technology and
      • risks for users?
  • Reliability and trust (this point is somehow connected to the aboce two points on testing and user aspects)
    • "Hey, look, I have just evolved a complex control algorithm for the cooling system of the reactor."


Documents from group work

Examples of self-organizing behavior in technology