MATSim Code

Move org.matsim.signalsystems to org.matsim.contrib.signals

Users of the signals implementation have to add the following steps to their code:
- Add a dependency to contrib/signals
- Load the scenario data and attach it to the scenario, i.e. scenario.addScenarioElement(SignalsData.ELEMENT_NAME, new SignalsScenarioLoader(signalsConfig).loadData())
- controler.addOverwriteModule(new SignalsModule())

Except the interfaces all code is moved to contrib. According to the package name of the contrib (signals) all interfaces are moved to package org.matsim.signals .
Before the interfaces can be moved to contrib, two issues have to be considered:
1.) Provide a way to inform the inverted network router about turn restrictions set by traffic signals.
2.) Provide an option to use type safe events from contrib packages without reimplementation of the events reading infrastructure.

Move org.matsim.signalsystems to org.matsim.contrib.signals

Users of the signals implementation have to add the following steps to their code:
- Add a dependency to contrib/signals
- Load the scenario data and attach it to the scenario, i.e. scenario.addScenarioElement(SignalsData.ELEMENT_NAME, new SignalsScenarioLoader(signalsConfig).loadData())
- controler.addOverwriteModule(new SignalsModule())

Except the interfaces all code is moved to contrib. According to the package name of the contrib (signals) all interfaces are moved to package org.matsim.signals .
Before the interfaces can be moved to contrib, two issues have to be considered:
1.) Provide a way to inform the inverted network router about turn restrictions set by traffic signals.
2.) Provide an option to use type safe events from contrib packages without reimplementation of the events reading infrastructure.

Move org.matsim.signalsystems to org.matsim.contrib.signals

Users of the signals implementation have to add the following steps to their code:
- Add a dependency to contrib/signals
- Load the scenario data and attach it to the scenario, i.e. scenario.addScenarioElement(SignalsData.ELEMENT_NAME, new SignalsScenarioLoader(signalsConfig).loadData())
- controler.addOverwriteModule(new SignalsModule())

Except the interfaces all code is moved to contrib. According to the package name of the contrib (signals) all interfaces are moved to package org.matsim.signals .
Before the interfaces can be moved to contrib, two issues have to be considered:
1.) Provide a way to inform the inverted network router about turn restrictions set by traffic signals.
2.) Provide an option to use type safe events from contrib packages without reimplementation of the events reading infrastructure.

Initial commit for new contribs

not required any more

minor changes to have better computational performance (faster but 18 test fails)

adjusting seepage network factory for different queueWithBufferType.

Test is adopted to new SeepageNetworkFactory.

make amit's playground compile again

fixing pom.xml in contrib