- 24 Aug, 2018 2 commits
-
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
If the do not match a new file is created if the project is saved.
-
- 23 Aug, 2018 3 commits
-
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
New Features: * Graphical simulation result is displayed in a table view to show run-time and overlap information if the corresponding processors are loaded. The Simulation result dialog can be deactivated in the preferences. * PedestrianOverlapProcessor returns two values "distance", "overlaps" for each overlap detected. If no overlap occurs the output is empty. "distance": The distance between the center of the two pedestrians "overlaps": The amount the two pedestrian overlap Changes: * New version for scenario.json (0.5): - remove scenario/attributesSimulation/needsBoundary as it is not used anymore. - remove attributes from processor PedestrianOverlapProcessor because the radius of a pedestrian can be retrieved from the topography at run-time. This would allow to detect overlaps of different sized pedestrian in the future. * Helper interfaces for testing: - The TestResourceHandler interface groups all methods needed to retrieve backup and reset test resources between single test runs. All methods, except getTestDir() have default implementation which rely rely on relative paths on getTestDir(). - The JsonNodeTest interface groups all methods needed to travers or search the Jackson JsonNode data structures. In contains methos for path finding and will fail the test if a path does not exist. * Added Test for PedestrianOverlapProcessor to check if a overlap of (2*r - 0.001) will always be treated as an overlap. Additional test are created to ensure (2*r + 0.001) with r:= pedestrian radius, will never create an overlap. Only between [2*r - 0.001 , 2*r + 0.001] different placements of pedestrian can produce overlaps. Example: --, /(45 degree) , | represent the distance (2*r) Case A: Case B: Case: C O--O O O | \ O O In the Case A and B no overlap is detected. In Case C an overlap is detected, because of rounding errors when calculating the distance \. This does not occure if the overlap is bigger than 0.001. Then in all three case a overlap is detected. If the distance between two pedestrian is 0.001 bigger than 2*r in none of the above cases an overlap is detected.
-
Stefan Schuhbaeck authored
-
- 22 Aug, 2018 5 commits
-
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
- 17 Aug, 2018 17 commits
-
-
Marion Goedel authored
-
Marion Goedel authored
-
Marion Goedel authored
-
Marion Goedel authored
-> Reduce number of outputs. -> Highlight OSM Tests that failed.
-
Marion Goedel authored
-
Marion Goedel authored
- More time (180 s) for Rimea 9 and 11 tests (since they have more pedestrians) - No output if a simulation is successful -> in the email we will hopefully see only the ones that failed now - Excludes files from directories "output" and "legacy" for the location application
-
Marion Goedel authored
realTimeSimTimeRatio: 0.0 useFreeSpaceOnly = true spawnAtRandomPositions = true
-
Marion Goedel authored
-
-
Marion Goedel authored
Reduced number of pedestrian in queueing_dynamic_floorfield_visual_check.scenario so that the test runs in less than 60 seconds.
-
Stefan Schuhbaeck authored
-
Marion Goedel authored
-
Stefan Schuhbaeck authored
# Conflicts: # VadereModelTests/TestOSM/scenarios/corner_waiting_time_processor_test.scenario # VadereModelTests/TestOSM/scenarios/narrow_passage_discrete_CA_fail.scenario
-
Stefan Schuhbaeck authored
# Conflicts: # VadereModelTests/TestOSM/scenarios/corner_waiting_time_processor_test.scenario # VadereModelTests/TestOSM/scenarios/narrow_passage_discrete_CA_fail.scenario
-
Marion Goedel authored
-
Marion Goedel authored
Renamed four TestSFM RIMEA scenarios which includes too many persons to run in a reasonable time. Files are renamed to *.backup instead of *.scenario.
-
Stefan Schuhbaeck authored
-
- 16 Aug, 2018 5 commits
-
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
update PSO such that it uses more iteration to improve accuracy. Update OSM-ModelTests: add TestProcessors, update attributes of the tests. add additional scenarios.
-
Stefan Schuhbaeck authored
-
Stefan Schuhbaeck authored
-
-
- 14 Aug, 2018 4 commits
-
-
Marion Goedel authored
- PedestrianOverlapDistProcessor Saves for each pedestrian in each timestep the size of the overlap. That is the difference between the radii of the pedestrians and the distance between their centers. The processors works only if all pedestrians in the simulation have the same radius! - MaxOverlapProcessor Saves the maximum overlap for one simulation. As explained above, the overlap is 2*pedRadius - norm(ped_pos_i - ped_pos_j). Again, this processor only works if all pedestrians in the simulation have the same radius. Both processors are especially useful for analyzing the number and sizes of overlaps occuring in the simulation. Both processors were tested with a Matlab script but there are no JUnit tests yet.
-
Benedikt Zoennchen authored
implementation of some TestProcessors, update of OSMTests e.g. add the TestProcessors to the scenarios.
-
-
Benedikt Zoennchen authored
-
- 13 Aug, 2018 4 commits
-
-
Benedikt Kleinmeier authored
-
Benedikt Zoennchen authored
-
Benedikt Zoennchen authored
-
-