MATSim Code

made changes such that code should also work when sim-start-time has fractional parts.

removed configs
(-> cvs.ivt)

tutorial

correction of adaptation reformatChoiceSetsForStatistics

config file

Several features and bugfixes:

- Made MatsimFileTypeGuesser work with schema and dtd again
- Refactored some classes to work on the Network interface instead of the implementation NetworkLayer
- Changed functionality of ScenarioImpl (see below)

The former ScenarioImpl(or ScenarioData for a long time) was a class providing functionality for storing the top level containers of a MATSim scenario and for loading the appropriate files. This functionality now has been split:

1.) There is a implementation of the Scenario interface that is just holding and creating the top level containers
2.) There is a class ScenarioLoader that loads the scenario using an instance of Scenario or Config
3.) There is a config module "scenario" that is responsible to en- or disable optional scenario features like roadpricing, lanes or signal systems

Why we have done this?

- The new ScenarioImpl can be used as starting point for initial demand modelling. From there you are able to programm only with the core interfaces (at least in theory, there is need for further cleanups) and get always the correct container that provides you with an appropriate builder of factory. Using that builder you can create all objects to be placed in the container without further knowledge of the classes implementing the core interfaces. This will also be done for the basic interfaces however there is more work pending.

- The Controller will hold a single Scenario instance where all data of a MATSim scenario is stored. By doing so the scenario can be given conveniently to different modules without access to Gbl.getWorld().getLayer().

- The config module "scenario" is a central place for en- or disable scenario feature that are optional. This is useful as the Controler and other modules do not have to check if an input file is set or not before accessing the data. Especially in the use case where optional scenario elements are not read from a file but created directly in Java such a switch is useful to ensure the usage of those feature without setting a filename in the config for a file that doesn't exist.

- The ScenarioLoader works closely together with both, the scenario config module and the Scenario and provides methods to load a scenario or just single parts of it. Programmers that are willing to customize one loading procedure no longer have to overwrite the Controler to get their data into the scenario, they can just write their own ScenarioLoader. This should reduce the amount of inherited Controler instances providing more stability to this really central element of the MATSim.

zoom saving works again

adapt ReformatChoiceSetsForDescriptives to new output of the attribute calculation