GitLab

- Initialize group already configured in given pedestrians

Signed-off-by: hm-schuhba1 <stefan.schuhbaeck@hm.edu>

Watch out: Agents run into obstacles at the moment (and I do not know why).

Also add two scenario files for testing purposes:
- VadereModelTests/TestOSM/scenarios/01_bang_test.scenario
- VadereModelTests/TestOSM/scenarios/02_bang_test_with_obstacle.scenario

ids in rimea_04***h.scenario

* add new fields to AttributeOSM
* correct typo in PedestrianDensityGaussianProcessor

- added PedestrianOverlapProcessor, MAxOverlapProcessor and NumberOverlapProcessor to all scenarios
- increased size of sources in cases where overlaps occurred in the source

Changes for v0.6:

Processors:
* remove PedestrianOverlapDistProcessor and add functionality in
  PedestrianOverlapProcessor.
* show overlap distance in PedestrianOverlapProcessor as a positive
  delta
* refactor NumberOverlapsProcessor to use PedestrianOverlapProcessor
  as dependency
* refactor MaxOverlapProcessor to use PedestrianOverlapProcessor
  as dependency

JsonTransform Tests:

To test transformation and manipulate Jackson's JsonNode representation
four new Interface are included.

* JsonNodeExplorer: Methods to travers, delete and add JsonNodes in an
  existing Json representation. Many methods will throw Exceptions if
  a path does not exist or the operation does not work. Included are
  helpers for eays path traversal (i.e. path(root, "path/to/node"))

* TestJsonNodeExplorer: This extends the JsonNodeExplorer and overwrites
  all Methods with exceptions and insted inclueds Assertions and
  Junit test to indicate an error. Thus for example the method
  pathMustExist contains an assertion test that the path exists. This
  can be used in UnitTest as assertions.

* TestJsonNodeHelper: Create JsonNode tree from text files

* TestResourceHandler: Allows to load file based resources for test
  and will create backups of test files so the test enviroment can be
  resotred if a test fails. This helps in the development process.

In "TestOSM/scenarios/thin_wall_pso_ok.scenario", assigned correct id to "pedestrianWaitingTimeProcessorId" to avoid "NullPointerException".

If the do not match a new file is created if the project is saved.

New Features:

* Graphical simulation result is displayed in a table view to show
  run-time and overlap information if the corresponding processors
  are loaded. The Simulation result dialog can be deactivated in
  the preferences.
* PedestrianOverlapProcessor returns two values "distance", "overlaps"
  for each overlap detected. If no overlap occurs the output is empty.
  "distance": The distance between the center of the two pedestrians
  "overlaps": The amount the two pedestrian overlap

Changes:

* New version for scenario.json (0.5):
  - remove scenario/attributesSimulation/needsBoundary as it is not
  used anymore.
  - remove attributes from processor PedestrianOverlapProcessor because
  the radius of a pedestrian can be retrieved from the topography at
  run-time. This would allow to detect overlaps of different sized
  pedestrian in the future.
* Helper interfaces for testing:
  - The TestResourceHandler interface groups all methods
  needed to retrieve backup and reset test resources between single test
  runs. All methods, except getTestDir() have default implementation
  which rely rely on relative paths on getTestDir().
  - The JsonNodeTest interface groups all methods needed to travers or
  search the Jackson JsonNode data structures. In contains methos for
  path finding and will fail the test if a path does not exist.
* Added Test for PedestrianOverlapProcessor to check if a overlap
  of (2*r - 0.001) will always be treated as an overlap. Additional
  test are  created to ensure (2*r + 0.001) with r:= pedestrian radius,
  will never create an overlap. Only between
  [2*r - 0.001 , 2*r + 0.001] different placements of pedestrian can
  produce overlaps. Example: --,  /(45 degree) , |  represent the
  distance (2*r)

  	Case A:		Case B: 	Case: C
	   O--O		  O 		  O
	   			  |			   \
	   			  O             O

  In the Case A and B no overlap is detected. In Case C an overlap
  is detected, because of rounding errors when calculating the
  distance \.
  This does not occure if the overlap is bigger than 0.001. Then in all
  three case a overlap is detected. If the distance between two
  pedestrian is 0.001 bigger than 2*r in none of the above cases an
  overlap is detected.

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