JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2018-08-28T23:08:27+02:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/279wall makes goal unreachable2018-08-28T23:08:27+02:00benjamin moehringwall makes goal unreachable## Summary
I produced a basic example of two almost similar geometries with subrooms on two levels. The only difference is that in geometry A, a wall is placed between an exit transition and the goal on a different level of the building...## Summary
I produced a basic example of two almost similar geometries with subrooms on two levels. The only difference is that in geometry A, a wall is placed between an exit transition and the goal on a different level of the building. In geometry B this wall was moved elsewhere.
It seems that because of this wall pedestrians can't reach their goal in geometry A, where as they do find a route in geometry B.
## Steps to reproduce
Run or visualize the provided examples.
## Expected behavior
Pedestrian leaves the building in both geometries.
## Actual behavior
pedestrian leaves the building in geometry B.
pedestrian doesn't find a route in geometry A.
> ERROR: ffRouter: unknown/unreachable goalID: 2 in FindExit(Ped)
> ERROR: VelocityModel::Init() cannot initialise route. ped 1 is deleted in Room 1 4.
## Inifile + Geometry + logs file to reproduce bug
Example A (not working):
[jps_traj.xml](/uploads/929d8acea156c9522a54b38b45bf0e7e/jps_traj.xml)
[jps_log.txt](/uploads/76bb932d56621b456a1825c876a6aad4/jps_log.txt)
[jps_ini.xml](/uploads/8f71afa7be16a5c0070c9999ab34bb86/jps_ini.xml)
[jps_geo.xml](/uploads/cb21d1b0ec28ed41f498e60008723f24/jps_geo.xml)
Example B (working)
[jps_log.txt](/uploads/2433af95a0047f7f786df0c3d9920346/jps_log.txt)
[jps_traj.xml](/uploads/5d2189b81a30f61671065e6eb8a33714/jps_traj.xml)
[jps_ini.xml](/uploads/e0005dcdc4484e778668ad3da49af928/jps_ini.xml)
[jps_geo.xml](/uploads/6cff9b78492d26d01689fe3631534a28/jps_geo.xml)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/280Clipping2018-09-18T14:21:21+02:00Mohcine Chraibim.chraibi@fz-juelich.deClippingClipping
(more later..)Clipping
(more later..)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/276CMAKE Flags2019-01-29T09:25:23+01:00Mohcine Chraibim.chraibi@fz-juelich.deCMAKE FlagsThe compiler flags are a mess.
The CMakeFileLists.txt needs some refactoring
- [ ] [For Visual Studio](https://stackoverflow.com/questions/45995784/how-to-set-compiler-options-with-cmake-in-visual-studio-2017)
- [ ] [using add_compile...The compiler flags are a mess.
The CMakeFileLists.txt needs some refactoring
- [ ] [For Visual Studio](https://stackoverflow.com/questions/45995784/how-to-set-compiler-options-with-cmake-in-visual-studio-2017)
- [ ] [using add_compiler_option](https://stackoverflow.com/questions/45955272/modern-way-to-set-compiler-flags-in-cross-platform-cmake-project)
- [ ] [VS_STARTUP_PROJECT](https://cmake.org/cmake/help/v3.6/prop_dir/VS_STARTUP_PROJECT.html)v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/227Global_Shortest router: Pedestrian not finding its way! [Hochhaus]2019-01-29T09:29:14+01:00Mohcine Chraibim.chraibi@fz-juelich.deGlobal_Shortest router: Pedestrian not finding its way! [Hochhaus]![router](/uploads/231dd348d3e499ec0db4953ce025b7f5/router.gif)
Files used to reproduce this behavior are here [issue_global_shortest.zip](/uploads/6825a7eb659a07d0ca23fe7710cf5390/issue_global_shortest.zip)
- Pedestrian has `i...![router](/uploads/231dd348d3e499ec0db4953ce025b7f5/router.gif)
Files used to reproduce this behavior are here [issue_global_shortest.zip](/uploads/6825a7eb659a07d0ca23fe7710cf5390/issue_global_shortest.zip)
- Pedestrian has `id=69` lives in `Subroom=39` `Room=12`
- Branch: DevelopArne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/206Reduce execution time of tests2019-03-23T05:00:38+01:00Mohcine Chraibim.chraibi@fz-juelich.deReduce execution time of tests- juelich 11 (136.13 s)
- juelich 13 (1321.74 s)
- juelich_14 (1493 s)
- juelich 6 (372 s)
- juelich 8 (147 s)
- Rimea 9 (192 s)
- Rimea 13 (1570 s)- juelich 11 (136.13 s)
- juelich 13 (1321.74 s)
- juelich_14 (1493 s)
- juelich 6 (372 s)
- juelich 8 (147 s)
- Rimea 9 (192 s)
- Rimea 13 (1570 s)guido bastenguido basten2016-12-24https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/291Add demos to CI2019-03-25T02:31:09+01:00Mohcine Chraibim.chraibi@fz-juelich.deAdd demos to CIFiles in demos show some important functionalities that need to be conserved during development.
For example, sources, events or stairs
- Unify the naming of the files in every directory: `inifile.xml`, `geometry.xml`
- Run demos with...Files in demos show some important functionalities that need to be conserved during development.
For example, sources, events or stairs
- Unify the naming of the files in every directory: `inifile.xml`, `geometry.xml`
- Run demos with every CIv0.8.4guido bastenguido bastenhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/296Groups2019-04-12T13:14:43+02:00Ghost UserGroupsGroups = People/Agents who want to stay together and therefore move only in the group, e.g families.Groups = People/Agents who want to stay together and therefore move only in the group, e.g families.0.8.5https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/301Restarting a simulation2019-04-12T13:14:52+02:00Ghost UserRestarting a simulationIt could be necessary to restart/continue a simulation after it has been finished or canceled.
Here is a idea which parameters are needed to restart the simulation:
* group id
* agent id
* location x, y, z
* velocity vx, vy
* fre...It could be necessary to restart/continue a simulation after it has been finished or canceled.
Here is a idea which parameters are needed to restart the simulation:
* group id
* agent id
* location x, y, z
* velocity vx, vy
* frequency (source)
* last frame = start frame
There can be a new trajectory file or the old one can be continued (maybe better).0.8.5https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/271Wiki and website have different content2019-04-12T13:17:19+02:00Mohcine Chraibim.chraibi@fz-juelich.deWiki and website have different contentsynchronize..synchronize..0.8.5Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/313Waiting behaviour2019-04-12T15:24:56+02:00tobias schroedterWaiting behaviourAdd model to display simple waiting behaviour of petsAdd model to display simple waiting behaviour of pets0.8.5tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/312Restructure routing and direction strategy2019-04-12T15:25:28+02:00tobias schroedterRestructure routing and direction strategyRestructure routing and direction strategy:
* [ ] Allow each router with each direction strategy
* [ ] Add waiting behaviour (see #313 )Restructure routing and direction strategy:
* [ ] Allow each router with each direction strategy
* [ ] Add waiting behaviour (see #313 )0.8.6tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/305Segmentation fault when using overlapping sources2019-04-15T15:11:32+02:00tobias schroedterSegmentation fault when using overlapping sources## Summary
When using overlapping sources in larger geometries the program fails with a Segmentation fault in the VelocityModel when accessing the position of the neighbors.
## Inifile + Geometry file to reproduce bug
[Personen_ini.xml...## Summary
When using overlapping sources in larger geometries the program fails with a Segmentation fault in the VelocityModel when accessing the position of the neighbors.
## Inifile + Geometry file to reproduce bug
[Personen_ini.xml](/uploads/a92b2f4f9efcd5e5af081dd82a0ba96f/Personen_ini.xml)
[Bahnsteige.xml](/uploads/8a9c8bfc24ae68bf3d264379216a6129/Bahnsteige.xml)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/317Logger2019-05-10T15:35:32+02:00tobias schroedterLoggerIssue for collecting ideas for logging librariesIssue for collecting ideas for logging librarieshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/283Stair in the middle of a (sub)room -> hole for stairs2019-05-10T20:11:52+02:00Ghost UserStair in the middle of a (sub)room -> hole for stairsDefining a (sub)room or a hole in the middle of an other (sub)room for a stair, without subdividing the second (sub)room in more (sub)rooms.
![Grundriss+Treppe](/uploads/58e4fa02fb331410c991954851531040/Grundriss+Treppe.png)
![Schnitt_...Defining a (sub)room or a hole in the middle of an other (sub)room for a stair, without subdividing the second (sub)room in more (sub)rooms.
![Grundriss+Treppe](/uploads/58e4fa02fb331410c991954851531040/Grundriss+Treppe.png)
![Schnitt_Treppe](/uploads/54fccbe897a47b57bee9cd46613ad004/Schnitt_Treppe.png)0.8.5Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/315Separation of pedestrian flows2019-05-11T00:40:21+02:00Ghost UserSeparation of pedestrian flowsFor our lecture "Evakuierungssimulation" we have an exercise to investigate the separation of pedestrian flows.
The result should be: evacuation-time variation a > evacuation-time variation b.
In the last lectures (SoSe 2018) the resu...For our lecture "Evakuierungssimulation" we have an exercise to investigate the separation of pedestrian flows.
The result should be: evacuation-time variation a > evacuation-time variation b.
In the last lectures (SoSe 2018) the results were as expected. When I rerunned the simulations for the current lectures (SoSe 2019) the result was totally different (with the same ini-file)! See the attached plots.
[Raum_2_a.xml](/uploads/165c5c314ffd73724dc32cbeb75a8f2f/Raum_2_a.xml)
[Raum_2_b.xml](/uploads/e26e39a7e2a69ccf4592c7cc597a4d4a/Raum_2_b.xml)
[Aufgabe4a_ini.xml](/uploads/e9b1edc57fbaee75fa1874429a0fc0eb/Aufgabe4a_ini.xml)
[Aufgabe4b_ini.xml](/uploads/47e8d7612162be80331d42389a69dd61/Aufgabe4b_ini.xml)
![Plot_Aufgabe4-alt](/uploads/fd276025b018d54994c98969223ab336/Plot_Aufgabe4-alt.png)
![Plot_Aufgabe4-neu](/uploads/52a615a20b75eaf14f5c4085cb70b7fc/Plot_Aufgabe4-neu.png)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/319malloc_error_break2019-05-11T18:02:05+02:00Ghost Usermalloc_error_breakThe error of issue #316 is gone, but there is another error, now...
![Bildschirmfoto_2019-05-11_um_17.39.04](/uploads/a715b6ac39de47efd527de0aaef42db4/Bildschirmfoto_2019-05-11_um_17.39.04.png)
[correct_Bahnsteige.xml](/uploads/bfb68e5...The error of issue #316 is gone, but there is another error, now...
![Bildschirmfoto_2019-05-11_um_17.39.04](/uploads/a715b6ac39de47efd527de0aaef42db4/Bildschirmfoto_2019-05-11_um_17.39.04.png)
[correct_Bahnsteige.xml](/uploads/bfb68e52ecd861ba2ea16efd02a2e33b/correct_Bahnsteige.xml)
[log-goal.txt](/uploads/2e71bfd86980ea60c03f89cda3d96d45/log-goal.txt)
[Personen_ini.xml](/uploads/26c7559ed1e1b4e2695fcad5685ec12b/Personen_ini.xml)
I do another simulation to see if the error occurs again.
For the small setup (Aufgabe6 - #316) there is no problem anymore.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/310New trajectory formats (TXT)2019-05-12T22:11:08+02:00Mohcine Chraibim.chraibi@fz-juelich.deNew trajectory formats (TXT)`jpscore` can produce two formats:
- txt: `#ID FR X Y Z `
- [xml](http://www.jupedsim.org/jpscore/2016-11-03-trajectory.html#xml)
I would try to change the txt format to
`
#ID FR X Y Z ...`jpscore` can produce two formats:
- txt: `#ID FR X Y Z `
- [xml](http://www.jupedsim.org/jpscore/2016-11-03-trajectory.html#xml)
I would try to change the txt format to
`
#ID FR X Y Z a b angle color
`
This could lead to slightly bigger files.
Alternatively, we should think about implementing a binary format like [HDF5](https://support.hdfgroup.org/HDF5/)
Any other suggestions are welcome.v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/314Different groups for one source2019-05-16T14:02:16+02:00Ghost UserDifferent groups for one sourceAs we want to model a population distribution, but don't want to use overlapping Sources (see #305) it could be very useful to use only one source to create new agents of different groups.As we want to model a population distribution, but don't want to use overlapping Sources (see #305) it could be very useful to use only one source to create new agents of different groups.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/320One-sided closed doors2019-05-19T10:50:03+02:00tobias schroedterOne-sided closed doorsAllows to pedestrian to go through in one direction but is (temp) closed from the other direction.Allows to pedestrian to go through in one direction but is (temp) closed from the other direction.tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/321Elevators2019-05-20T12:14:10+02:00Ghost UserElevatorsWe have stairs and escalators, but we should also have elevators.We have stairs and escalators, but we should also have elevators.