Softpedia >Mac >Math/Scientific >MATSim >  Changelog

MATSim Changelog

What's new in MATSim 0.6.0

Sep 16, 2014
  • Changes:
  • a lot of internal changes to make MATSim more modular and more easily configurable

New in MATSim 0.5.0 (Sep 16, 2014)

  • Configuration Changes:
  • Changed default population file format to v5 (r20926)
  • New Features:
  • VehicleType now has size in passenger car equivalents (pce), and QSim honors
  • this attribute as well as the maximum vehicle speed. This is important,
  • if you use transit, please check your vehicles.xml for possibly
  • incorrect default settings.
  • Feature Improvements:
  • Loading Plans is now faster thanks to multithreading (r18639)
  • Preprocessing for AStarLandmarks router is now faster thanks to multithreading (r18734)
  • OTFVis now uses OpenGL2
  • BugFix:
  • Fixed a bug during preprocessing for routing algorithms, removing the (wrong) warning "All incident nodes of X are dead ends" in the logfile. (mrieser, r20547)
  • Changes for developers:
  • Class hierarchy of events is now much simpler (r21016)
  • Improved router integration for newer types of routers (e.g. transit router) (r21034 and other commits)
  • config modules are no longer serializable (r21205)

New in MATSim 0.2.0 (Nov 30, 2010)

  • New features:
  • OTFVis (org.matsim.run.OTFVis) can now be started in Swing mode (-swing).
  • In Swing-Mode, no OpenGL is required, but only very limited capabilities
  • are available (Network-Viewing, simple visualization of vehicles)
  • NetVis was removed from MATSim, use OTFVis in Swing mode instead.
  • Simulation of public transport possible
  • Feature improvements:
  • improved stability of OsmNetworkReader to convert networks from OpenStreetMap
  • Swing-OTFVis can open mvi-files created by conversion from events
  • Other changes for developers:
  • API-Changes:
  • ScenarioImpl.getPopulation() returns Population instead of PopulationImpl (r11288)
  • A bunch of classes no longer implement or extend Serializable, mostly for Network and Population data structure (r11637, r11638, r11650 r11653, r11655)

New in MATSim 0.1.1 (May 14, 2010)

  • New features:
  • handling events in a separate thread for speed up of runs (http://matsim.org/node/238)
  • conversion of OpenStreetMap-data for networks (see org.matsim.core.utils.io.OsmNetworkReader)
  • events can be written in an XML format to better accomodate attributes from new events
  • Feature improvements:
  • improved visualizer OTFVis:
  • show middle line of a road, save configuration, save views, start without argument, change speed, etc.
  • improved speed of default QueueSimulation
  • Events can be configured to be written only every n-th iteration
  • (speed due to less file I/O) (see http://matsim.org/node/344)
  • routing algorithms (Dijkstra, A*Landmarks) run faster (commit r8399)
  • faster writing of events and plans-files (commit r8867)
  • Planomat can now also do mode choice (see http://matsim.org/node/381)
  • Other changes for users:
  • use Dijkstra as default routing algorithm instead of A*-Landmarks
  • improved travel time calculation (r6767)
  • lots of bug fixes, too many to list them here
  • Simulation can handle non-car legs by means of simple teleportation
  • Other changes for developers:
  • moved project structure and Build process to Maven
  • first steps towards stable API for programmers (see package org.matsim.api.*)
  • Developers which cannot commit to the MATSim repository should try to only use
  • classes/interfaces from this package. If you need additional functionality from
  • other classes, please speak to us, as we cannot guarantee for other classes to
  • remain stable to the next release!
  • code cleanup towards API
  • renamed several classes and packages
  • improved code quality based on static code analysis
  • made scoring function more modular (see http://matsim.org/node/263)
  • introduce Scenario-class as Super-Element containing pointers to other data containers
  • (see org.matsim.api.Scenario)
  • use Builders to create Population and Network
  • use (API-)Interfaces instead of Implementations in many playces
  • try domain driven design, ues Ids instead of object references between data containers

New in MATSim 0.1.0 (Apr 30, 2010)

  • New features:
  • handling events in a separate thread for speed up of runs (http://matsim.org/node/238)
  • conversion of OpenStreetMap-data for networks (see org.matsim.core.utils.io.OsmNetworkReader)
  • events can be written in an XML format to better accomodate attributes from new events
  • Feature improvements:
  • improved visualizer OTFVis:
  • show middle line of a road, save configuration, save views, start without argument, change speed, etc.
  • improved speed of default QueueSimulation
  • Events can be configured to be written only every n-th iteration
  • (speed due to less file I/O) (see http://matsim.org/node/344)
  • routing algorithms (Dijkstra, A*Landmarks) run faster (commit r8399)
  • faster writing of events and plans-files (commit r8867)
  • Planomat can now also do mode choice (see http://matsim.org/node/381)
  • Other changes for users:
  • use Dijkstra as default routing algorithm instead of A*-Landmarks
  • improved travel time calculation (r6767)
  • lots of bug fixes, too many to list them here
  • Simulation can handle non-car legs by means of simple teleportation
  • Other changes for developers:
  • moved project structure and Build process to Maven
  • first steps towards stable API for programmers (see package org.matsim.api.*)
  • Developers which cannot commit to the MATSim repository should try to only use
  • classes/interfaces from this package. If you need additional functionality from
  • other classes, please speak to us, as we cannot guarantee for other classes to
  • remain stable to the next release!
  • code cleanup towards API
  • renamed several classes and packages
  • improved code quality based on static code analysis
  • made scoring function more modular (see http://matsim.org/node/263)
  • introduce Scenario-class as Super-Element containing pointers to other data containers
  • (see org.matsim.api.Scenario)
  • use Builders to create Population and Network
  • use (API-)Interfaces instead of Implementations in many playces
  • try domain driven design, ues Ids instead of object references between data containers (like Network, Population, ...)
  • Bugfix: QuadTree.values().iterator() did not return all values (r8303, r8863)

New in MATSim 20090108 (May 7, 2009)

  • New Features:
  • Integrated comparison with counting stations, output as html, pdf, kml
  • New visualizer (see class org.matsim.run.OTFVis as well as documentation
  • of www.matsim.org)
  • Simulate roadpricing-scenarios (distance, area, cordon)
  • New replanning modules: Secondary Location Choice, Planomat
  • Regenerate snapshots from events-files (note: events do not contain the
  • complete internal state of a simulation. The plotted vehicle positions are
  • therefore not the real positions as calculated by a simulation, but
  • positions calculated from the available events). See class
  • org.matsim.run.Events2Snapshot
  • Feature Improvements:
  • Java Mobsim / Queue-Simulation: Major speedup of 30 to over 100%,
  • depending on scenario
  • Improved positioning of vehicles in snapshots
  • Faster router (A*-Landmarks) is now used by default.
  • Reduced memory-consumption
  • misc. speed-improvements in events-handling, most noteably when running
  • big scenarios
  • Improvements for users who write code based on MATSim:
  • improved handling of config-settings within the code
  • rewrote scoring functionality to allow custom scoring functions to be
  • used.
  • improved available API in many areas such to allow easier
  • overwriting/extending of functionality.