1. Project JUTS – Urban Traffic Simulation System David Hartman www.juts.zcu.cz DSS 2004

2. Talk Overview Short introduction Overview of the project structure Project team Main activity areas Conclusions and future works

3. Short introduction Complex urban traffic simulation Programs and peoples Java, XML, swing, CAD, … Wide collaboration (Pilsen dpt.)

4. Overview of project structure Concepts and design – DSS2003 Main parts – Simulation part – Core – GUI New programs – Data processing – Map Editor – Generator editor

5. Basic simulation structure Simulation core Data GUI

6. What is Simulation Core? Modified Nagel-Schreckenberg model Spatial divided cellular automata (CA) with pseudo-agent behavior Leading Head Algorithm as modified CA rule Simulation core

7. Simulation map structure Simulation map Segments of map – Roads with traffic lanes – Crossroads, roundabouts – Generators, Terminators Connections – Accessplaces (discrete graph structure) Simulation core

8. What does it mean Data? XML based simulation structure JUTS project as defined data structure – Main project file – Static Simulation Map Segment Structure Graphic representation – Dynamic data Stochastic settings Simulation state Data

9. What does GUI do? Reading results of simulation and visual representation Access to simulation structure – Reading content of different segments – Change properties Control the simulation running GUI

10. Extended project structure Simulation core Data GUI Map Editor Generators editor Transformation programs Pilsen Data

11. Project Team Project grows = more people Separeted problem parts – Data Analysis – Map Editor – Simulation Core – GUI Need for good communication

12. Team members Pavel Herout – The Leader David Hartman – Project specification, Core, First version of GUI, Site Martin Šour – GUI Jana Hájková – Map Editor T. Potužák & Z.Kubovec – Generator Editor

13. Team communication Simulation core GUI Map Editor Generators editor HartmanŠour Hájková Herout Kubovec & Potužák

14. Web Site Versions on web site – Simulation Core – GUI – Maps Plans and formats convention Other information

15. Main activity areas Simulation core development GUI development Map editor and data works Generator creation from data Case study Cooperation with Pilsen

16. Simulation map Creation of segment simulation map Loaded fully from XML data – Static map – Dynamic data Structure and Graphic divided Controled loading and logging

17. Simulation running Connection of the segments into map Implementation of Leading Head Algorithm Moving vehicles through the segment structure Still bugging

18. Simulation features Implementation of the basic simulation characteristics collecting Including the path determination Enable cooperation with GUI Enable to run with offline output …

19. First version of GUI Swing Multilanguage enviroment GUI window structure Configuration file in XML

20. First version of GUI Enable loading projects – Using specific project structure – Offline and online Manage the loading – Loading threads – Connecting GUI with simulation – Logging process

21. First version of GUI Simulation running – Creation of active running parser – Enable jumping Manage the simulation map – Editing traffic lane content – Editing content of crossroad – Editing generator properties – Editing vehicle properties

22. GUI extensions Extension of configuration file New structure according to core and data analysis developlment Map painting Performance improvement

23. Original map painting Map structure in image Views at scrollpanel only parts of the image Main disadvantage is memory requirements

24. Map graphical rendering Each simulation segment has its painter – Draw the segment (e.g. road) – Draw the parts of segment (e.g. traffic lane) – Draw vehicles in segments Drawing Decision – Each part of segment – The whole map is not needed – Better for memory requirements

25. Map segment rendering Painters test presents in area of view – Test itself – Test its parts Performance and memory improvement Testing follows

26. Memory Tests Map SizeImageRendering 1663 x 177511 530 KB47 KB 3326 x 355046 122 KB47 KB 4989 x 5325103 775 KB47 KB 6652 x 7100184 489 KB47 KB

27. Performance tests Map Size Icon repaint Graphical Rendering Segment Rendering 25 x 270,024,0 103 x 1100,025,4 207 x 2210,028,08,2 415 x 4430,0213,213,4 831 x8870,029,38,1 3326 x 35500,023,51,7 4989 x 53250,73,51,7 6652 x 7100Exception3,51,7

28. GUI final

29. Map editor and data analysis Design of map editor – Design of GUI – Data parsers Working with data – creating standards with Pilsen city departement Working on Lochotin district – Case study

30. Generator editor Processing traffic detectors data for specific traffic lanes – Transformation to XML structure – Cooperation with the JUTS standards GUI for simulation map editor creation – Graphical setting of generator properties – Easy segment creation

31. Visualization of detector data

32. Changes with emulation

33. Case study – Lochotin district All data available – CAD road graph – Detectors data – Traffic lights data Static structure of the map – Already created – Testing and adapting

34. Cooperation with Pilsen Available data – Static CAD Data – Detectors data – Traffic ligths data Standardization efforts – Connect city data through the juts id – Convert data to more standard format

35. Cooperation with Pilsen DAT Std.description in XML Excel XML Generator Editor Map Editor JUTS simulation system

36. Data standards Segment data standards – Definition of ID – Definition of connections Generator data standard – Time organized XML structure for specific detector (i.e. traffic lane)

37. Conclusions Division of project still in progress, communication needed Project parts separation speed-up project development Good cooperation with Pilsen Data standardization

38. Future work Lochotin district simulation and simulator verification Characteristic visualization Map structure and generator data standardization Other features and performance