-- FelixLoew - 03 Feb 2004

MarkerConfiguration

The MarkerLoader carries the global context and is the control component of the system. It is responsible for the configuration of the MarkerLoader and for starting and shutting down the StateMachine.

Needs & Abilities

As stated in the MarkerConfiguration.xml file, the service has the following Needs and Abilities.

• Need: name="PatternConsumer" type="PatternData"

This is needed to connect to the MarkerDetection and configure it with the current set of markers. Before a new configuartion the markers have to be unloaded first.

• Need: name="StateMachine" type="RoomInfo"

Here you enable the StateMachine to set a new context if a context change occurs. Please not here that a predicate is set in order to startup StateMachine with the right context.

• Need: name="MLConfig" type="Configuration"

This is necessary for a reference on the Configuration service that provides MarkerData^? for each context situation. This data is queried and the pushed to the MarkerDetection (via method call).

Interaction with other Services

MarkerData^? is queried from the Configuration database. This MarkerData^? is pushed to the MarkerDetection. The MarkerConfiguration requests a StateMachine with a specific configuration (due to the current context). The StateMachine is started (startOnDemand). The old StateMachine dies (stopOnNoUse).

More Documentation

• Detailed documentation:
• Doxygen:
• The source can be found in the cvs repository:
  http://cvsbruegge.informatik.tu-muenchen.de/cgi-bin/viewcvs.cgi/src/services/MarkerConfiguration/?cvsroot=dwarf#dirlist

How-To

Usage

Example: MarkerConfiguration

Testing

Set up the whole system. Or only test parts of the functionality(eg. configuration of the MarkerDetection, startup of the StateMachine).

Configuration

MarkerData^? has to be inserted into the Database (Configuration). If you start the system a intial state has to be specified in the need for a StateMachine (e.g. user starts in the kitchen).

-- FelixLoew - 11 Dec 2003