[Rock-dev] Discussion about fault response tables

Sylvain Joyeux sylvain.joyeux at dfki.de
Tue May 7 15:58:31 CEST 2013


The fault responses apply to *all* actions that are active in the 
system. To handle that with the state machine, you would need to do e.g.


   transition(state1, :fault1, response1)
   transition(state2, :fault1, response1)
   transition(state3, :fault1, response1)
   transition(state4, :fault1, response1)
   transition(state5, :fault1, response1)
   transition(state6, :fault1, response1)

for EVERY SINGLE FAULT response you want to have. Does not scale very 
well. And that is assuming that you report all errors as events *at the 
level of the action*, which will make the process of creating the tasks 
a lot harder.

This is actually why the error representation in Roby is orthogonal to 
the event system: faults and fault responses are global things while 
reaction to nominal situations are mostly local.

In other words, the events are for nominal things, the exceptions for 
errors. This starts to appear at this level as well: the state machine 
are for nominal things, the fault responses for errors.

-- 
Sylvain Joyeux (Dr.Ing.)
Space & Security Robotics

!!! Achtung, neue Telefonnummer!!!

Standort Bremen:
DFKI GmbH
Robotics Innovation Center
Robert-Hooke-Straße 5
28359 Bremen, Germany

Phone: +49 (0)421 178-454136
Fax:   +49 (0)421 218-454150
E-Mail: robotik at dfki.de

Weitere Informationen: http://www.dfki.de/robotik
-----------------------------------------------------------------------
Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH
Firmensitz: Trippstadter Straße 122, D-67663 Kaiserslautern
Geschaeftsfuehrung: Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster
(Vorsitzender) Dr. Walter Olthoff
Vorsitzender des Aufsichtsrats: Prof. Dr. h.c. Hans A. Aukes
Amtsgericht Kaiserslautern, HRB 2313
Sitz der Gesellschaft: Kaiserslautern (HRB 2313)
USt-Id.Nr.:    DE 148646973
Steuernummer:  19/673/0060/3
-----------------------------------------------------------------------



More information about the Rock-dev mailing list