GitLab

Used following commands:
- mvn -Dmaven.test.skip=true package
- java -jar VadereSimulator/target/vadere-console.jar migrate -r VadereModelTests/
- git clean -n
- git clean -f (to delete <scenario_file>.scenario.legacy which is created by migration assistant)

In "VTrajectory", added workaround to avoid "NullPointerException", but workaround leads to corrupt output file.

new robust computation of the target direction for the BHM which is enabled if a target potential is available. New TimeCostFunction to compute a target potential repulsive at obstacles.

Added "VadereModelTests/TestSalientBehavior/scenarios/09-OriginalExperimentSetup-OSMEventDriven.scenario".

In "PedestrianSpeedInAreaProcessor", replaced "PedestrianVelocityProcessor" by "PedestrianTrajectoryProcessor" to calculate speed.

In "PedestrianSpeedInAreaProcessor", use "PedestrianVelocityProcessor" instead of "pedestrian.getVelocity()".

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".

- Initialize group already configured in given pedestrians

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

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

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

Handle salient behavior in "UpdateSchemeSequential" and reduced "requiredFootSteps" from "5" to "2" in "SalientBehaviorCognition".

Renamed "CognitionLayer" to "EventCognition", added class "SalientBehaviorCognition" and added test scenario "01-ExperimentSetup.scenario".

The ProcessorFlag interface is a marker interface used anywehre a
specifc attribute of some DataProcessors are needed. For instnace
the UsesMeasurementArea Interface is implemented by all Processors
usinge one or more MeasurementAreas. In this example the interface
exposes an array of given MeasurementAreaIds which can be used
within the ScenarioChecker.

These interfaces are therefore aribtraty flags used to filter a
generic list of DataProcesors if needed.

In "run_seed_comparison_test.py" and "run_vadere_console_with_all_scenario_files.py", increased timeouts to avoid errors during CI pipeline.

Further changes:
- Renamed test directory "TESTOVM" to "TestOVM".
- Renamed test directory "TestOSM_Group" to "TestOSMGroup".

In "01_unsupported_event_exception_for_unsupported_models.scenario", changed from Reynolds' to OSM model to avoid failing tests in CI pipeline.

Grouped all event tests in directory "VadereModelTests/TestEvents" and lowercased all test files (to be consistent with existing model tests).

Renamed exception "NotSupportedEvent" to "UnsupportedEventException" to respect Java's naming convention.

In all locomotion classes, throw exception if an event is not supported by this model to inform the user.

Use new exception "NotSupportedEvent" or the static helper method "throwExceptionIfNotElapsedTimeEvent()".

VadereModelTests/TestBangEvent/scenarios/00-NotSupportedEventTest.scenario:
- Added this scenario to test if an exception pops up in GUI when combining a locomotion model and an unsupported event.

Extended "BangEvent" to hold a "Target" and use this new information in "UpdateSchemeEventDriven" and "UpdateSchemeSequential".

New scenario element "AbsorbingArea" is not handled in:
- AbsorbingAreaController (this class is missing completely at the moment).
- MigrationAssistant (must add node '"absorbingAreas" : [ ]' to topography tree).
- DefaultConfig (to be able to change color).
- TikzGenerator (must use "topography.getAbsorbingAreas()" to iterate over the new scenario element).

Added two additional test scenarios:
- wait_event_2_sources_2_targets_osm_event_driven.scenario
- wait_event_recurring_2_sources_2_targets_osm_sequential.scenario

VadereSimulator/tests/org/vadere/simulator/control/events/EventControllerTest.java:
- Adapted unit tests for this logical change.