- More time (180 s) for Rimea 9 and 11 tests (since they have more pedestrians)
- No output if a simulation is successful -> in the email we will hopefully see only the ones that failed now
- Excludes files from directories "output" and "legacy" for the location application

realTimeSimTimeRatio: 0.0
useFreeSpaceOnly = true
spawnAtRandomPositions = true

Reduced number of pedestrian in queueing_dynamic_floorfield_visual_check.scenario so that the test runs in less than 60 seconds.

# Conflicts:
#	VadereModelTests/TestOSM/scenarios/corner_waiting_time_processor_test.scenario
#	VadereModelTests/TestOSM/scenarios/narrow_passage_discrete_CA_fail.scenario

# Conflicts:
#	VadereModelTests/TestOSM/scenarios/corner_waiting_time_processor_test.scenario
#	VadereModelTests/TestOSM/scenarios/narrow_passage_discrete_CA_fail.scenario

Renamed four TestSFM RIMEA scenarios which includes too many persons to run in a reasonable time. Files are renamed to *.backup instead of *.scenario.

update PSO such that it uses more iteration to improve accuracy. Update OSM-ModelTests: add TestProcessors, update attributes of the tests. add additional scenarios.

- PedestrianOverlapDistProcessor
  Saves for each pedestrian in each timestep the size of the overlap. That is the difference between the radii of the pedestrians and the distance between their centers. The processors works only if all pedestrians in the simulation have the same radius!
- MaxOverlapProcessor
  Saves the maximum overlap for one simulation. As explained above, the overlap is 2*pedRadius - norm(ped_pos_i - ped_pos_j). Again, this processor only works if all pedestrians in the simulation have the same radius.

Both processors are especially useful for analyzing the number and sizes of overlaps occuring in the simulation. Both processors were tested with a Matlab script but there are no JUnit tests yet.

implementation of some TestProcessors, update of OSMTests e.g. add the TestProcessors to the scenarios.

Tests SFM: Activated useFreeSpaceOnly for spawning the pedestrian in the sources. Added necessary output processor for rimea_06_corner_sfm1.scenario (due to dependency pedestrianStartTimeProcessor was needed). Reduced the number of agents in basic_1_chicken_sfm*.scenario from 200 to 50 to reduce the computation time.

increase size of spwan grid in SourceController to ensure peds don't overlap

Changes:

* add new seed handling: By default new scenario files will be created
  with a random seed, which is written in the attribute fixedSeed.
  If the Boolean switch useFixedSeed  is set, this defined seed will
  be used within one simulation. At the start of each simulation this
  seed, or if useFixedSeed is false a newly generated one, will be used
  and persisted in the attribute simulationSeed. All generated data
  of this simulation will be written to the defined output directory
  with a copy of the current scenario file. All data generated in this
  simulation run can be reproduced with specified simulationSeed.

* new features for VaderConsole(migrate): The migrate subcommand will
  now accept a list of files or Directories (or a mix of them) to
  perform a migration or a revert. If a path is specified the
  default behavior will only migrate the selected directory without
  traversing to the directory tree. If the --recursive or -r flag is
  set, the hole sub tree of all given directories will be converted.
  Directories or directory trees will be ignored if the directory
  contains one of the following marker files:
  - DO_NOT_MIGRATE_TREE or .DO_NOT_MIGRATE_TREE
  - DO_NOT_MIGRATE or .DO_NOT_MIGRATE

* remove hard coded sc  enario files encoded as strings to allow
  testResource migration with the VadereConsole

* ignore scenario.legacy files within testResources

* add test for MigrationAssistant v0.3 to v0.4

[BugFix] in NumberOverlapsProcessor. Before, the occurrences of overlaps were counted and divided by two (since in at least two pedestrians were part of each overlap). Now the number of overlaps is counted for each pedestrian and the result is divided by two. Also, the number displayed in the infoBox (if uncommented) was corrected.