Traffic Simulation Intersection Controllers Video

Another week, time for another video.

This one shows changes that have been made to the intersection controllers within the Traffic Simulator.

The give-way controller makes all the cars give way to all the other roads connected into the intersection with a minimum of 2.5 seconds between vehicles.

The traffic lights controller makes all the cars on the green road go at 2 second intervals and makes the others queue with a minimum wait time of 16 seconds.

The round-a-bout controller makes each car give way to the right and then go with a minimum of 3.9 seconds between each car on a road, but multiple cars from multiple roads can cross the intersection at the same time… hence the chaos on the video.

Traffic Sim: Round-A-Bouts

traffic flowing freely

Traffic flowing freely with two roads connecting to each other.

traffic congested into round a bout

Traffic Congested as three roads merge and they have to give way to the road on the immediate right as they enter the intersection, notice how many cars are queued up as compared to those that are leaving.

Traffic Simulation Update: Multiple Cars, Multiple Lanes

Okay, the traffic simulator project has been slow going over the past few weeks, just not been very focussed and playing with DLA and other assignments too much.

This morning/arvo I changed some of the code and layout of how cars were being generated. Now instead of a car know what road it is on it has been reversed, so each road has its own collection of cars to manage. With some changes to how the graphics are produced this now means that cars are now rendered at the same time as each road. A that allows perfect placement of cars onto roads rather than having to do a mathematically approximation. Clear as mud?

carsonlanes

The Honours Project Outline.

This is the next 10 months of my life:

Traffic Simulation

Purpose:

To construct a real time three dimensional simulation of congested traffic flows in Java and to test various ideas surrounding the build up of congestion.

Such tests may include but are not limited to:

  • Testing various algorithms for effectively navigating already congested traffic in the shortest amount of time
  • Testing algorithms to determine the best approach to reduce the build up of congestion
  • Investigating the impact of various events such as an accident, construction of a new road or lane on the amount of congestion in the model.

Expected Outcomes:

  • Project constructed in object orientated and model-view-controller code in Java
  • Use of Open GL or other three dimensional rendering tools
  • Interactive GUI allowing end user to construct traffic model
  • Ability to import satellite images in standard JPEG format to be used as ground textures.
  • Road network data structure to be based on Graph Theory
  • Cars implemented as artificial intelligence agents with real world physical control models, collision detection and awareness, environmental awareness.
  • Ability to perform controlled tests on simulation, including testing of algorithms for avoiding congestion once built up, algorithms for avoiding congestion build up, and impacts on varying road network design and events on traffic flows.
  • Ability to extract data and results from the model.

Planned Project Timeline:

  • February
    • Project planning
    • Initial prototyping and skeleton of code class layouts.
    • Skelton of thesis written in Latex.
  • March
    • Research into existing traffic simulation, causes of congestion, real life techniques for reducing congestion, and other relevant topics.
    • Coding of basic 3D GUI controls and viewers.
    • Thesis introduction written
  • April
    • Research and design of various tests to be performed on traffic simulator.
    • Coding of road network design controls.
    • Results of research written into thesis.
  • May
    • Review of possible tests and design of artificial intelligence controls to implement tests.
    • Coding of simulator controls and agents/cars on network.
    • Testing ideas written into thesis.
  • June
    • Correct realistic implementation of cars and interactions with road network within simulator.
    • GUI ideas written into thesis.
  • July
    • Implementation of initial tests on simulator.
    • Simulation controls written into thesis.
  • August
    • Review of results of simulator with expected outcomes and possible real world examples for validity, recoding of artificial intelligence controls if mistakes are discovered.
    • Summary of initial tests written into thesis.
  • September
    • Second set of tests on simulator, either the corrected versions of the initial tests or new tests developed as a result of initial tests.
    • Summary of second round of tests written into thesis.
  • October
    • Conclusions and review of thesis made.
    • Review of final version of thesis.
  • November
    • Thesis due on 11th.