- 24 Apr, 2019 11 commits
-
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
Benedikt Kleinmeier authored
-
- 23 Apr, 2019 2 commits
-
-
Benedikt Kleinmeier authored
-
Benedikt Kleinmeier authored
-
- 15 Apr, 2019 3 commits
-
-
Benedikt Kleinmeier authored
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.
-
Benedikt Kleinmeier authored
-
Benedikt Kleinmeier authored
-
- 12 Apr, 2019 2 commits
-
-
Benedikt Kleinmeier authored
Make shapes resizable See merge request !56
-
-
- 10 Apr, 2019 1 commit
-
-
Benedikt Kleinmeier authored
-
- 08 Apr, 2019 1 commit
-
-
Stefan Schuhbaeck authored
Measurement area refactor processors rebased See merge request !55
-
- 04 Apr, 2019 4 commits
-
-
Benedikt Kleinmeier authored
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
Signed-off-by:
hm-schuhba1 <stefan.schuhbaeck@hm.edu>
-
Stefan Schuhbaeck authored
Signed-off-by:
hm-schuhba1 <stefan.schuhbaeck@hm.edu>
-
- 02 Apr, 2019 7 commits
-
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
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.
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
MigrationAssistant | +-- IncidentMigrationAssistant (Deprecated) | +-- JsonMigrationAssistant | +--using JsonTransformation Interface The JsonTransformation interface is implemented by in two different ways: AbstractJsonTransformation | implements JsonTransformation, JsonNodeExplorer | +-- JoltTransformation --> relying on Jolt [1] | +-- SimpleJsonTransformation --> relying on Jackson JsonNode The JsonTransformation interface provides a three step process of to transform a given scenario File were each consumes a JsonNode and returns the changed JsonNode. 1) preHooks 2) transformation 3) postHooks The MigrationAssistant selects the correct implementation by using the JsonTransformationFactory which map a given Version to the corresponding implementation of some JsonTransformation. 1. Subclass either JoltTransformation or SimpeJsonTransformation. (a) If JoltTransformation is used, a specialized transformation syntax must be used. See [1] for Doc. (b) If SimpleJsonTransformation is used no additional input is needed. The transformation is done by manually manipulating the Jackson JsonNode-Tree 2. add annotation where X.X resembles the Version label i.e. "0.8" @MigrationTransformation(targetVersionLabel = "X.X") 3. add the default constructor with no arguments and the call super constructor passing the Version 4. Implement initDefaultHooks() and add the pre- and postHook LinkedList with JsonTransformationHooks (a) use add[Post|Pre][First|Last] methods. (b) add addPostHookLast(AbstractJsonTransformation::sort) to ensure the right sorting order within the scenario file. 5. (optional) overwrite any of applyPreHooks, applyTransformation, applyPostHooks if needed. 6. (optional) add generic JsonNode manipulations to JsonNodeExplorer This interface contains useful default implementation to navigate a JsonNode-Tree such as: path(jsonNode, "some/path/within/the/json") <-- will return empty nodes with path das not exist pathMustExist(jsonNode, "some/path/within/the/json") <-- will throw MigrationException renameField(node, "release", "version") <-- rename keys iteratorProcessorsByType(jsonRoot, "org...PedestrianVelocityProcessor ) <-- returns an iterator of JsonNodes representing a PedestrianVelocityProcessor [1]: https://github.com/bazaarvoice/joltSigned-off-by: hm-schuhba1's avatarhm-schuhba1 <stefan.schuhbaeck@hm.edu>
-
Stefan Schuhbaeck authored
fix #222. allow renaming and setting of log level programmatically Closes #222 See merge request !54
-
Stefan Schuhbaeck authored
-
- 26 Mar, 2019 4 commits
-
-
Stefan Schuhbaeck authored
fix #225. Keep dialog open after csv export. Closes #225 See merge request !53
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
178 measurement area See merge request !52
-
Stefan Schuhbaeck authored
-
- 20 Mar, 2019 3 commits
-
-
-
Benedikt Zoennchen authored
-
Marion Goedel authored
Issue #138 : Update only if there are still pedestrians in the scenario and /or still pedestrians to be spawned.
-
- 19 Mar, 2019 2 commits
-
-
Stefan Schuhbaeck authored
generated sources see issue #227
-
Marion Goedel authored
-