amodeus.amod Build Status

This repository allows to run an autonomous mobility-on-demand scenario using the amodeus library.

Try it, orchestrate your own fleet of amod-taxis! Watch a visualization of a traffic simulation in San Francisco generated using this repository.

![p1t1](https://user-images.githubusercontent.com/4012178/38852194-23c0b602-4219-11e8-90af-ce5c589ddf47.png) ![p1t4](https://user-images.githubusercontent.com/4012178/38852209-30616834-4219-11e8-81db-41fe71f7599e.png) ![p1t3](https://user-images.githubusercontent.com/4012178/38852252-4f4d178e-4219-11e8-9634-434200922ed0.png) ![p1t2](https://user-images.githubusercontent.com/4012178/38852212-3200c8d8-4219-11e8-9dad-eb0aa33e1357.png)

Admins

AMoDeus is jointly maintained and further developed by the Admins and Code Owners Christian Fluri (ETH Zürich), Joel Gächter (ETH Zürich), Sebastian Hörl (ETH Zürich), Claudio Ruch, Jan Hakenberg, ChengQi Lu (TU Berlin), and Marc Albert (nuTonomy).

Please let us know if you'd like to contribute!

First steps in the amod repository

Prerequisites

The code format of the amod repository is specified in the amodeus profile that you can import from amodeus-code-style.xml.

Getting Started

Follow these step-by-step instructions or the video to set up, prepare, and run your first simulation. You can get a sample simulation scenario at https://www.amodeus.science/

  1. Clone amod
  2. Import to eclipse as existing maven project (Package Explorer->Import) using the pom.xml in the top folder of this repository.
  3. Set up Run Configurations for: (ScenarioPreparer; ScenarioServer; ScenarioViewer), chose the Working Directory to be the top Simulation Folder directory.
  4. Adjust the simulation settings in the 3 config files: av.xml for av fleet values (e.g. number vehicles), AmodeusOptions.properties for AMoDeus settings (e.g. max number of people) and config.xml for Matsim settings (e.g. output directory).
  5. Add JAVA VM arguments if necessary, e.g., -Xmx10000m to run with 10 GB of RAM and -Dmatsim.preferLocalDtds=true to prefer the local Dtds.
  6. Run the ScenarioPreparer as a Java application: wait until termination
  7. Run the ScenarioServer as a Java application: the simulation should run
  8. Run the ScenarioViewer as a Java application: the visualization of the scenario should open in a separate window

Gallery

![usecase_amodeus](https://user-images.githubusercontent.com/4012178/35968174-668b6e54-0cc3-11e8-9c1b-a3e011fa0600.png) Zurich ![p1t5](https://user-images.githubusercontent.com/4012178/38852351-ce176dc6-4219-11e8-93a5-7ad58247e82b.png) San Francisco ![San Francisco](https://user-images.githubusercontent.com/4012178/37365948-4ab45794-26ff-11e8-8e2d-ceb1b526e962.png) San Francisco

String Interface

TODO improve and adapt documentation, de-dockerize Run docker-compose up to run the San Fransisco simulation. This will run two services, aido-host and aido-guest, which will communicate over port 9382.

The protocol is specified here.


ethz300