There is a routing module provided that uses a Reservation based router.
** WARNING ** you MUST have configured in you config.xml, like in the additional geneva scenarios, and the modification to equil, only have one thread available for global and qsim groups!
Some excerpts of the original matsim-example-projet are kept down below for future reference.
There is a population generator tool for generating simulation agents: https://github.com/HubbleCommand/node-matsim-population-generator
There is also a visualisation tool, primarily to compare runs: https://github.com/HubbleCommand/matsim-py-vis
A small example of how to use MATSim as a library.
By default, this project uses the latest (pre-)release. In order to use a different version, edit pom.xml
.
A recommended directory structure is as follows:
src
for sourcesoriginal-input-data
for original input data (typically not in MATSim format)scenarios
for MATSim scenarios, i.e. MATSim input and output data. A good way is the following:- One subdirectory for each scenario, e.g.
scenarios/mySpecialScenario01
. - This minimally contains a config file, a network file, and a population file.
- Output goes one level down, e.g.
scenarios/mySpecialScenario01/output-from-a-good-run/...
.
- One subdirectory for each scenario, e.g.
File -> New -> Project from Version Control
paste the repository url and hit 'clone'. IntelliJ usually figures out
that the project is a maven project. If not: Right click on pom.xml -> import as maven project
.
(The following paragraphs need to be adjusted according to the specifications of your project.)
The MATSim program code in this repository is distributed under the terms of the GNU General Public License as published by the Free Software Foundation (version 2). The MATSim program code are files that reside in the src
directory hierarchy and typically end with *.java
.
The MATSim input files, output files, analysis data and visualizations are licensed under a Creative Commons Attribution 4.0 International License.
MATSim input files are those that are used as input to run MATSim. They often, but not always, have a header pointing to matsim.org. They typically reside in the scenarios
directory hierarchy. MATSim output files, analysis data, and visualizations are files generated by MATSim runs, or by postprocessing. They typically reside in a directory hierarchy starting with output
.
Other data files, in particular in original-input-data
, have their own individual licenses that need to be individually clarified with the copyright holders.