GitLab

# Conflicts:
#	VadereSimulator/src/org/vadere/simulator/entrypoints/Version.java
#	VadereSimulator/src/org/vadere/simulator/models/osm/updateScheme/UpdateSchemeSequential.java

Implemented "EventFactory" and use it in "TrajectoryReader" and use new output processors in "TestSalientBehavior" scenarios.

Added two new output processors ("PedestrianMostImportantEventProcessor" and "PedestrianEventProcessor") and use them in "TrajectoryReader".

Group models

Closes #217

See merge request !58

- Initialize group already configured in given pedestrians

Merge branch '234-add-default-migration-task-that-only-increases-the-version-number-if-no-version-specific-migration-is-given' into 'master'

Resolve "Add default Migration Task that only increases the Version number if no version specific migration is given."

Closes #234

See merge request !57

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

In "OSMBehaviorController.swapPedestrians()", improved bug fix to avoid "AssertionError" in "VTrajectory".

We have to do a code review here with Bene if event-driven update scheme is used properly.

In "OSMBehaviorController.swapPedestrians()", fixed bug ("pedestrian1.setTimeOfNextStep()" was not called).

Added print statements in "OSMBehaviorController" to debug why salient behavior causes an "AssertionError" when using event-driven update scheme.

In "DefaultModeAdapter", made resizing of scenario elements a two-step process: first, select element, then use resize handles at object edges.

Since commit c91dad12, a scenario element was selected when hovering over it.
This caused problems in the postvisualization. It was very tricky to track one
specific agent because when you moved the mouse cursor over the canvas different
agents were selected immediately. Therefore, I have reverted this behavior and
resizing a scenario is a two-step process now.

Added test scenarios for salient behavior: "03-UnidirectionalFlow-OSMSequential.scenario" and "04-CounterFlow-OSMSequential.scenario".

Added "angleCalculationType" and "targetOrientationAngleThreshold" to "AttributesAgent" and use it in "OSMBehaviorController".