Project JUTS – Urban Traffic Simulation System David Hartman DSS 2004

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

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

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

Basic simulation structure Simulation core Data GUI

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Memory Tests Map SizeImageRendering 1663 x KB47 KB 3326 x KB47 KB 4989 x KB47 KB 6652 x KB47 KB

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, x 35500,023,51, x 53250,73,51, x 7100Exception3,51,7

GUI final

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

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

Visualization of detector data

Changes with emulation

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

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

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

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)

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

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