Measurement

Whereas the movement manager functions as the input (INP) of the moving area will the measurement manager (MsMg) takes measurements of the moving area with different sensors. In the beginning we make the following simple assumptions:

Sensor Field: Every position in the moving area is connected to one sensor which can sens whether this position is occupied by an object or not.

Data Selection: Only those positions will be recorded which actually are occupied. There can be more than one position at one point of measurement.

Data Rate: The measurement frequency $ f_{Meas}$ to obtain data from the movment area is generally variable. This allows different kinds of measurement. The 'standard case' is assumed to have at most 1 movement per time unit (if there are n moving objects, then there can be at most n changes of positions per time unit). A proposal for a scheduling diagram is given in figure 8.7.

Figure 8.7: Scheduling of events in case study 1
\includegraphics[width=3.5in]{timing_cmd_area_agent.eps}

Data Format: At any time unit there can be an ASCII string of the format `` $ \langle X,Y \rangle, \cdots$'' transmitting the X-Y-coordinates of every position which is in the actual time unit occupied. In the case of multiple objects it is not clear which command belongs to which measured position, except in the case of the start command. Besides this kind of movement data we assume, that at every time unit there can occasionally occure an additional language information including the ID of the moving object as well as the move command. See figure 8.8.

Figure 8.8: Example of measured data from an area
\includegraphics[width=1.5in]{movements_measured_from_area.eps}

Gerd Doeben-Henisch 2012-03-31