MATSim Files

=========================================================================
MATSim

Multi-Agent Transport Simulation

http://matsim.org/

Release "Spring 2012"  (internal number: 0.4.0)
=========================================================================


MATSim provides a toolbox to run and implement large-scale agent-based 
transport simulations. The toolbox consists of severel modules which can be
combined or used stand-alone. Modules can be replaced by own implementations
to test single aspects of your own work. Currently, MATSim offers a toolbox
for demand-modeling, agent-based mobility-simulation (traffic flow simulation),
re-planning, a controller to iteratively run simulations as well as methods to
analyze the output generated by the modules.

-------------------------------------------------------------------------

USAGE:
- unzip the downloaded file
- java -jar matsim-0.4.0.jar
  this should show the release info
- java -cp matsim-0.4.0.jar org.matsim.run.Controler myconfig.xml
  this should run the simulation
- A Tutorial can be found online: http://matsim.org/docs/tutorials
  some example files are included in this release.
- If you want to develop code with MATSim, e.g. in Eclipse:
  add the libs-directory and the matsim-jar to an Eclipse-Project.
  in Eclipes 3.5 or newer, add *only* the matsim-jar to the build-path in Eclipse.
  in Eclipse 3.4 or older, also add all the libs to the build-path.
  you should now be able to use the classes from matsim in your project.


-------------------------------------------------------------------------


CHANGELOG:

Release Spring 2012 (version 0.4.0)
-------------------------------------------------------------------------------

Main focus of this release:
Maintenance Release


Changes:

- Configuration changes:
  - move the "snapshotFormat" entry which you may have in your "simulation" and/or in your "qsim" configuration group to the "controler" configuration group (mzilske, r16484)
	- In module "controler" one can set the parameters  "writeSnapshotsInterval", "writePlansInterval", "writeEventsInterval" in order to reduce time needed for IO during the iterations.
	- In module "controler" one should specify which mobility simulation shall be used via the "mobsim" parameter

- New features:
  - OTFVis can display OSM-maps as background. Set option "mapOverlayMode" to "true". Also set the coordinate system of your scenario in the "global" section of config. 

- Feature improvements:
  - Major memory improvements in OsmNetworkReader by using Long instead of String for osm-ids (r14944)
  - CompressedRoutes can now be enabled using config file (plans.networkRouteType = CompressedNetworkRoute) (r17328)
  - dump of configuration to logfile now uses os-specific line endings, making the dump reabable on Windows (r14945, #168)
  - transit router now exposes additional attributes for configuration to config-file (r14860)
  - improved OTFVis visualization of traffic signals and lanes (r18143, r18129, r18387, r18390)
  - improved traffic light implementation: added a data model for intergreen times and a default implementation that checks if the minimum intergreen time between two signal groups is not violated 

- Bug fixes:
  - The link to link routing feature could not be enabled via controler config module in xml config. Fixed (r15002)

- Changes for developers:
	- package org.matsim.lanes:
		- moved classes of package: The classes mapping the XML data structures are moved to org.matsim.lanes.data.* (r18160)
		- provided some additional factories for better extensibility of the packages
		- provided convenience method in LanesUtils
	- package org.matsim.signalsystems
		- provided some additional factories for better extensibility of the packages
		- provided convenience method in SignalUtils
	- all persons now generate PersonEntersVehicleEvent/PersonLeavesVehicleEvent. Before, only pt passengers did that. Some event handlers may need to adapt. (r17776)


  Non-API changes:
	- org.matsim.lanes.* was split into two subpackages, one for each model: 
		1. org.matsim.lanes.data.v11.*: A model written to simplify creation and modelling of lanes
		2. org.matsim.lanes.data.v20.*: A model that is used as input for the simulation. 
	- dtd/laneDefinitions_v2.0.xsd: added additional element to laneType in order to allow the user to calibrate the lanes model via the capacity of the lane. The capacity must be set explicitly in the xml otherwise the model will use some defaults with probably too high capacities. In order to avoid the usage of the defaults use LanesCapacityCalculator to preprocess the data using the same semantics that have been used on the fly in previous releases. The capacity calculation is done automaticall if the lane layout is modelled via the org.matsim.lanes.data.v11 package classes and then converted to with the LaneDefinitionsV11ToV20Conversion class into the 2.0 model. 
	- config module signalsystems: added to parameters to switch on and off ambertimes and intergreen usage
	- org.matsim.lanes & signalsystems can deal with not available turning moves


Please note that OTFVis may not be able to read mvi-files created with an older release of MATSim.
Please make sure your mvi-files work as expected in OTFVis before deleting any older release of
MATSim. In the case of problems, it might be useful to keep the old release around just for
looking at old mvi-files.