-
Our current navigation is broken for geometries with many skinny triangles.
This is a severe issue with no workaround and we will not be able to provide a quick fix. @JetteSchumann / @chraibi / @sc…
Ozaq updated
4 months ago
-
Especially for the juPedSim coupling it would be great to have the possibility to define network areas which will be covered by a different pedestrian model. This maybe useful for nonInteracting vs st…
-
Influencing JuPedSim pedestrian flows via multiple waypoints in the form of rerouter definitions with 'viaProbReroute' to assign more than one intermediate waypoints fails. These (2nd, 3rd, 4th ...) w…
-
The Duesseldorf scenario got much slower. We need to find out whether it is a change on our side, a change in JuPedSim or a change in the scenario
-
Create/modify (with jpscore) simple simulations for all methods, where the outcome of the method should be straightforward and easy to follow and reproduce.
The trajectories of previous tests are bas…
-
For whatever reason the Duesseldorf network near Sportpark Nord has many multilane service roads which allow pedestrians everywhere. The Jupedsim importer only has the rightmost lane.
-
-
This is relevant for jupedsim where stops / waypoints could be anywhere in the plane. For cars / other models it should be mapped to the closest edge
-
When we consider the case of two consecutive edges, the junction shape is a line which gets buffered in the geometry generation code. The result is visually not satisfying and we need to handle manual…
-
the current debug code should be "upgraded" into two options, one defining the filename and one to specify whether geo-coordinates are wished.