Changes between Version 1 and Version 2 of PTVS_Res

Timestamp:

Dec 27, 2009, 9:44:29 AM (14 years ago)

Author:

mihaela.teler

Comment:

--

PTVS_Res

@@ -1 @@
-Results
-We have tested our implementation with a map with 16 intersections. For each intersection there is an event processing thread assigned to handle the events coming from the surrounding area. 
-[[Image()]]
-When an event is extracted from the queue, if and only if it is a send or receive event, the list of all intersections is iterated, the closest one in determined and the proper thread in instantiated and started. The intersection must be on the same road with the source or destination point of the event. 
-We have tested using a scenario with one very short route near the intersection [Energetica Derdelus]. The results show that the closest intersection is computed and the proper thread started. In this particular example it is the thread 6 from the intersection [Energetica Derdelus].
 
-Example of points around the interest intersection:
-Intersection 6:  name: [Energetica Derdelus] (26.046 809934238127, 44.437 560887805944)
+== Results ==[[BR]]
+
+
+We have tested our implementation with a map with 16 intersections. For each intersection there is an event processing thread assigned to handle the events coming from the surrounding area. [[BR]]
+
+[[Image()]][[BR]]
+
+When an event is extracted from the queue, if and only if it is a send or receive event, the list of all intersections is iterated, the closest one in determined and the proper thread in instantiated and started. The intersection must be on the same road with the source or destination point of the event. [[BR]]
+
+We have tested using a scenario with one very short route near the intersection [Energetica Derdelus]. The results show that the closest intersection is computed and the proper thread started. In this particular example it is the thread 6 from the intersection [Energetica Derdelus].[[BR]]
+
+
+Example of points around the interest intersection:[[BR]]
+
+Intersection 6:  name: [Energetica Derdelus] (26.046 809934238127, 44.437 560887805944)[[BR]]
+
 p:(26.045079934242494, 44.435809887810365)
 p:(26.05040893422904, 44.43794988780496)
@@ -16 +25 @@
 
 What the thread does is to get the event from the queue and to call playEvent method. This method determines the processing of the event depending on its type, creation and planning of new events. 
-Some piece of output:
+Some piece of output:[[BR]]
+
 --- no of events in the queue:28
 Processing thread 6 from intersection [ Energetica Derdelus ]