New toolbar button with modal dialog to change width and size of
topography from the topography creator window.
Todo: new icon for resize action
Todo: Scenario Pane is not marked as changed (asterisk on scenario name)
Todo: Message Dialog for wrong syntax
Todo: allow comma an decimal point

The ScenarioPanel recreates the TopograpyWindow (view) each time a new
selection on the left is triggered. Within the recreation a new thread
recreated the view but was not synchronized to accept a
ChangeViewPortEvent for resizing.

The PostvisualizationWindow had the same issue.

update VadereConsole: delete unused arguements and add an output-dir arguement, maven will now generate a vadere-console.jar which can be executed via console.

This must be set even if the output directory is not valid yet. If
a new VadereProject is created but not saved, there is no representation
of the project on the hard drive and thus no output directories to load
from. ProjectOutput did not handled this correctly.

Issue 46

See merge request !23

ProjectOutput holds a map of SimulationOutputs which were marked as
valid. Only the scenario file is kept in memory. The trajectory file
is only loaded once to see if it is valid but is not kept in memory.
SimulationOutputs can be marked as dirty. If so they will not be listed
and will be reloaded or removed with the next cleanup is done.

The OutputDirWatcher can watch all or a subset of directories within
the output directory of a VadereProject. If The filesystem
WatchEventHandler will trigger reload of simulation output directories.
TODO: implement reload.

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

SimulationOutput holds the scenario information of simulation runs.

If a new obstacle is created remove all obstacles which are completely
covered by the new one.

If a new selection starts (i.e. mousePressed) set the bound of the
default selectionShape based on the current gridResolution and not
on the scale factor. Smaller Shapes can still be created if the
mouse drag motion is used or if a bigger zoom value is used.

Fix #42: in "ScenarioPanel.java", group model names in GUI under menu "Insert model name" (in "Model" tab).

Note: no unit tests have been written for new methods in "ClassFinder.java".

If the Viewport is changed due to a zoom or scroll action the
calculation of the world coordinates can lead to negative x, y
coordinates of the viewport. The view port coordinates should not
be negative.

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

The Topography contains copies of attributes in a HashSet which will
create inconsistent string representation when serialized. Exclude this
HashSet from serialization.

add feature: it is now possible to display the target potential field of a…

See merge request !22

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.

Clear list of DataProcessors in OutputFile before init to prevent
duplicated DataProcessors after second run of scenario.

attributes for output processor should now be displayed (with default values) if they are newly created via the gui.

Added coverage generation to "pom.xml" of following projects: VadereGui, VadereSimulator and VadereState

Now, coverage report is generated (under "<project>/target/site/coverage-reports/") when using

  mvn test

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.