Difference between revisions of "Challenges in Engineering Self-Organizing Systems"

From Self-Organization Wiki
Jump to: navigation, search
(New page: * [Group 2])
 
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
−
* [Group 2]
+
* '''Design of emergence''':
 +
** How to design ''local rules'' achieving the desired ''global properties''?
 +
** How to couple local (unit) behaviors to global (system) behavior?
 +
** Non-trivial but approaches exist (eg. evolutionary design), Bio-inspired techniques  (stigmergy, social insects metaphors, immune systems, evolutionary algorithms), these approaches perform well in some specific domains (dynamic networks : routing, P2P, ..)
 +
** 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))
 +
 
 +
* '''Design of the representation / communication / interaction''':
 +
** Degrees of freedom and adaptability
 +
** How to represent/set up the problem (cartesian vs. polar spatial coordinates in the sensor protocol made a difference in evolving a control system: [http://wwwu.uni-klu.ac.at/welmenre/papers/fehervari-2010-Evolving_Neural_Network_Controllers_for_a_Team_of_Self-organizing_Robots.pdf I. Fehervari and W. Elmenreich. '''Evolving neural network controllers for a team of self-organizing robots'''. Journal of Robotics, 2010.])
 +
** The representation of a problem is very important (see [http://pespmc1.vub.ac.be/papers/Problem-Formulation.html Heylighen F. (1988): '''Formulating the Problem of Problem-Formulation''', in: Cybernetics and Systems '88, Trappl R. (ed.), (Kluwer Academic Publishers, Dordrecht), p. 949-957.])
 +
 
 +
* '''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. [http://en.wikipedia.org/wiki/Langton%27s_ant '''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."''
 +
 
 +
* '''(Unified?/complete) Theory of Self-organizing systems'''
 +
** Standards of System Theory? :  General Control Theory
 +
** Deterministic, non linear dynamic systems (Chaos Theory)
 +
** Cellular Automata?
 +
** Conceptual/philosophical : Autopeïsis  & Enaction Theory (Maturana & Varela) ⇒ Structural/ Behavioural Coupling
 +
** Complexity Theory and Complex Networks Theory
 +
 
 +
 
 +
==Documents from group work==
 +
* [[Group 2]]
 +
 
 +
==Examples of self-organizing behavior in technology==
 +
*

Latest revision as of 10:14, 14 July 2010

  • Design of emergence:
    • How to design local rules achieving the desired global properties?
    • How to couple local (unit) behaviors to global (system) behavior?
    • Non-trivial but approaches exist (eg. evolutionary design), Bio-inspired techniques (stigmergy, social insects metaphors, immune systems, evolutionary algorithms), these approaches perform well in some specific domains (dynamic networks : routing, P2P, ..)
    • 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."
  • (Unified?/complete) Theory of Self-organizing systems
    • Standards of System Theory? : General Control Theory
    • Deterministic, non linear dynamic systems (Chaos Theory)
    • Cellular Automata?
    • Conceptual/philosophical : Autopeïsis & Enaction Theory (Maturana & Varela) ⇒ Structural/ Behavioural Coupling
    • Complexity Theory and Complex Networks Theory


Documents from group work

Examples of self-organizing behavior in technology

Retrieved from "https://mobile.aau.at/selforganized-wiki/index.php?title=Challenges_in_Engineering_Self-Organizing_Systems&oldid=635"