Skip to content

A very old MATSim model for Seattle (more precisely: the PSRC = Puget Sound Regional Council area)

License

Notifications You must be signed in to change notification settings

matsim-scenarios/matsim-seattle

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

2 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

The MATSim Open Seattle scenario

ˆ

About this project

Licenses

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. Creative Commons 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.

Note

Handling of large files within git is not without problems (git lfs files are not included in the zip download; we have to pay; ...). In consequence, large files, both on the input and on the output side, reside at https://svn.vsp.tu-berlin.de/repos/public-svn/matsim/scenarios/countries/us/psrc .


Simple things (without installing/running MATSim)

Movies
  1. Go to https://svn.vsp.tu-berlin.de/repos/public-svn/matsim/scenarios/countries/us/psrc/
  2. Decide for a scenario that you find interesting and go into that directory.
  3. Inside there, look for an output-* directory that you find interesting and go into that directory.
  4. Inside there, look for movie-* files. You can't view them directly, but you there are various ways to download them, and you can view them then. Try that.
Run VIA on output files
  1. Get VIA from https://www.simunto.com/via/. (There is a free license for a small number of agents; that will probably work but only display a small number of vehicles/agents.)
  2. Go to https://svn.vsp.tu-berlin.de/repos/public-svn/matsim/scenarios/countries/us/psrc/ .
  3. Decide for a scenario that you find interesting and go into that directory.
  4. Inside there, look for an output-* directory that you find interesting and go into that directory.
  5. Download *.output_network.xml.gz and *.output_events.xml.gz. Best make sure that they do not uncompress, e.g. by "Download linked file as ...".
  6. Get these files into VIA. This can be achieved in various ways; one is to open VIA and then drag the files from a file browser into VIA.
  7. Run VIA and enjoy.

Downloading the repository - Alternative 1: Download ZIP

  1. Click on Clone or download and then on Download ZIP.
  2. Unzip the repository.
  3. Go to "Run the MATSim Seattle scenario" below.

Downloading the repository - Alternative 2: Clone the repository

Initial stuff (needs to be done once)
  1. Install git for the command line.
  2. Type git clone https://github.com/matsim-scenarios/matsim-seattle.git in the command line.

(Or use your IDE, e.g. Eclipse, IntelliJ, to clone the repository.)

This will result in a new matsim-seattle directory. Memorize where you have put it. You can move it, as a whole, to some other place.

Update your local clone of the repository.
  1. Go into the matsim-seattle directory.
  2. Type git pull

(Or use your IDE, e.g. Eclipse, IntelliJ, to update the repository.)

This will update your repository to the newest version.


Run the MATSim Seattle scenario

... using a runnable jar file

(Requires either cloning or downloading the repository.)

  1. There should be a file directly in the matsim-seattle directory with name approximately as matsim-seattle-5.x-jar-with-dependencies.jar.
  2. Double-click on that file (in a file system browser). A simple GUI should open.
  3. In the GUI, click on the "Choose" button for configuration file. Navigate to one of the scenario directories and load one of the configuration files.
  4. Increase memory in the GUI.
  5. Press the "Start MATSim" button. This should run MATSim. Note that MATSim accepts URLs as filenames in its config, so while the config files are part of the git repo, running them will pull additional material from our server.
  6. "Open" the output directory. You can drag files into VIA as was already done above.
  7. "Edit..." (in the GUI) the config file. Re-run MATSim.
... using an IDE, e.g. Eclipse, IntelliJ - Alternative 1: use cloned/downloaded matsim-seattle repository

(Requires either cloning or downloading the repository.)

  1. Set up the project in your IDE.
  2. Make sure the project is configured as maven project.
  3. Run the JAVA class src/main/java/org/matsim/run/RunSeattleScenario.java or src/main/java/org/matsim/gui/RunSeattleScenarioGUI.java.
  4. "Open" the output directory. You can drag files into VIA as was already done above.
  5. Edit the config file or adjust the run class. Re-run MATSim.
  1. Write your own run class and make sure to execute the required public methods in RunBerlinScenario:
Config config = RunBerlinScenario.prepareConfig( args ) ;
// possibly modify config here

Scenario scenario = RunBerlinScenario.prepareScenario( config ) ;
// possibly modify scenario here

Controler controler = RunBerlinScenario.prepareControler( scenario ) ;
// possibly modify controler here, e.g. add your own module

controler.run


More information

For more information about MATSim, see here: https://www.matsim.org/.

Internal Documentation

See GoogleDoc

About

A very old MATSim model for Seattle (more precisely: the PSRC = Puget Sound Regional Council area)

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages