GitLab

In "pom.xml" files, added "failIfNoTests" to avoid that module is (wrongly) marked as error if no tests were executed.

Otherwise, a module is flagged as error if no unit tests were executed at all.

implementation and performance testing of the SFMM. Stride information in pedestrianOSM will now be cleared to avoid large linked lists.

add a faster exp-implementation approximating exp, and a benchmark library called Java Microbenchmark Harness.

implementation and performance testing of the SFMM. Stride information in pedestrianOSM will now be cleared to avoid large linked lists.

There is a 1:1 Relation ship between DataKeys and OutputFiles. This Mapping is introduced into the OutputFileClass Annotation to create the mapping wihtin the OutputFileBaseFactory.  

add a faster exp-implementation approximating exp, and a benchmark library called Java Microbenchmark Harness.

In "pom.xml" of "VadereGui", "VadereSimultor", "VadereState" and "VadereUtils", use version 2.19 of Surefire plugin to be able to skip tests via CLI.

Version 2.19 or higher of Surefire plugin allows to use following notation to skip tests:

  mvn test -Dtest=!LegacyTest

Note: maybe, use "mvn test -Dtest=\!LegacyTest" (with escape character) to avoid shell interpretation of exlemation mark.

It seems to be more efficient in a small test.
Time measured in nanoseconds in a loop (3x).

(postvis.trajectories)  readTextFile:   139179300
(postvis.trajectories)  readTextFile2:   52790478 <-- new
(test_postvis.scenario) readTextFile3:    4355102
(test_postvis.scenario) readTextFile4:    1037918 <-- new
---------------------------------------------------------
(postvis.trajectories)  readTextFile:    37730947
(postvis.trajectories)  readTextFile2:    7910077 <-- new
(test_postvis.scenario) readTextFile3:    6125829
(test_postvis.scenario) readTextFile4:     484034 <-- new
---------------------------------------------------------
(postvis.trajectories)  readTextFile:    22605907
(postvis.trajectories)  readTextFile2:    6541635 <-- new
(test_postvis.scenario) readTextFile3:     688422
(test_postvis.scenario) readTextFile4:     415274 <-- new
---------------------------------------------------------

improve the visualization of the target potential field (no more flickering), refector some of the classes implementing the potential field

add feature: it is now possible to display the target potential field of a specific agent if the main model is a potential field model.

Extended "pom.xml" to generate coverage reports in CSV, HTML and XML by using "jacoco-maven-plugin".

Generate reports by executing:

  mvn test

Generated reports are located in:

  <project_root>/target/site/coverage-reports

Now, this Maven config can be used to activate report generation in Gitlab.

Processor: Implementation of the TargetFloorFieldGridProcessor and the refactoring of the PostVis such that the new data format can be read