JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2018-12-04T17:55:32+01:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/293Show statistics of crossings2018-12-04T17:55:32+01:00Ghost UserShow statistics of crossingsWhen using "show statistics" only the statistics of transitions are shown.
It will be useful to show the statistics of the crossings, too.When using "show statistics" only the statistics of transitions are shown.
It will be useful to show the statistics of the crossings, too.v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/298Sources2018-12-04T17:34:59+01:00Ghost UserSourcesWe have sources which "inject" new agents in a subroom with a frequency (agents/second) or one agent at a defined time.
What we want to have are sources which generate agents within a box or on a line and which have some more properti...We have sources which "inject" new agents in a subroom with a frequency (agents/second) or one agent at a defined time.
What we want to have are sources which generate agents within a box or on a line and which have some more properties than the existing:
time_min = first time that agents appear
time_max = last time that agents appear ("injection" will end after this time or before if agents_max is reached first)
N_create = Number of agents that should appear at one frequency time step
freq_time = frequency time step (e.g. freq_time="10": x agents will be created every ten seconds)
conti = false -> the agents will be created simultaneously for one frequency time step, true -> the agents will be created continuously (1 agent/second)
x_min, x_max, y_min, y_max = coordinates for the box/line where the agents should be "injected".
Example:
source 1 (old) = 10 agents will appear in room_0/subroom_1 with the frequency 2 agents/second.
source 2 (old) = 1 agent with id=50 will appear in room_0/subroom_1 after 10 seconds.
source 3 (new) = after 20 seconds 10 agents will appear simultaneously in a box (2m x 3m) every 15 seconds until 300 agents are created or time has reached 200 seconds.
```
<agents_distribution>
<group group_id="1" agent_parameter_id="1" room_id="0" subroom_id="1" number="10" goal_id="-1" router_id="1" />
<group group_id="3" agent_parameter_id="1" number="0" goal_id="-1" router_id="1" source_id="3"/>
</agents_distribution>
<agents_sources>
<source id="1" caption="old-source" frequency="2" agents_max="10" group_id="1" greedy="false"/>
<source id="2" caption="old-source" time="10" agent_id="50" group_id="1" greedy="true"/>
<source id="3" caption="new-source" time_min="20" time_max="200" freq_time="15" N_create="10" agents_max="300"
group_id="3" conti="false" x_min="1" x_max="3" y_min="2" y_max="5" />
</agents_sources>
```v0.8.4Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/4XSD Validation files for all inputfiles2018-11-09T16:01:07+01:00Mohcine Chraibim.chraibi@fz-juelich.deXSD Validation files for all inputfilesXSD-file is missing. We need to validate all input files, since they are written manually.
The validation can be put directly in the root of the server.XSD-file is missing. We need to validate all input files, since they are written manually.
The validation can be put directly in the root of the server.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/292Crossing IDs2018-11-09T15:26:46+01:00Ghost UserCrossing IDsIn different rooms, subrooms can have the same id, crossings can't.
Now:
```
room 1, subrooms 1-4, crossings 1-3
room 2, subrooms 1-4, crossings 4-6
```
Better:
```
room 1, subrooms 1-4, crossings 1-3
room 2, subrooms 1-4, crossings ...In different rooms, subrooms can have the same id, crossings can't.
Now:
```
room 1, subrooms 1-4, crossings 1-3
room 2, subrooms 1-4, crossings 4-6
```
Better:
```
room 1, subrooms 1-4, crossings 1-3
room 2, subrooms 1-4, crossings 1-3
```
So you are more flexible in writing geometry files.v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/281Continuous walls2018-11-08T09:11:13+01:00Ghost UserContinuous wallsIn 3D- or 2D-plans e.g. exterior walls are continuous. To define (sub)rooms more easily these walls should be subdivided automatically.In 3D- or 2D-plans e.g. exterior walls are continuous. To define (sub)rooms more easily these walls should be subdivided automatically.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/282Holes for doors2018-10-28T19:57:12+01:00Ghost UserHoles for doorsThe future of architectural drawing are BIM-data. When exporting the 3D building-data (coordinates), walls are continious, without door openings. The openings should therfore be created automatically by the definition of the doors.The future of architectural drawing are BIM-data. When exporting the 3D building-data (coordinates), walls are continious, without door openings. The openings should therfore be created automatically by the definition of the doors.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/289JPSfire and ZLIB dependency2018-10-22T00:07:34+02:00Mohcine Chraibim.chraibi@fz-juelich.deJPSfire and ZLIB dependencyThis dependency is annoying, especially when JPSfire is not used at all.
Add option to switch it on/off.This dependency is annoying, especially when JPSfire is not used at all.
Add option to switch it on/off.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/290Source SegFault2018-10-21T18:21:42+02:00Mohcine Chraibim.chraibi@fz-juelich.deSource SegFaultAny inifile using sources leads to a SegFaultAny inifile using sources leads to a SegFaultv0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/288documentation | geometry2018-10-18T13:52:18+02:00Ghost Userdocumentation | geometry![Rooms](/uploads/4580a5ef6221ccde8e1842d9fab719c7/Rooms.png)
[source](http://www.jupedsim.org/jpscore/img/Rooms.png)
Is the connection between room 0 and 1 a `crossing` or a `transition`? I think it must be a `transition`? Who can ch...![Rooms](/uploads/4580a5ef6221ccde8e1842d9fab719c7/Rooms.png)
[source](http://www.jupedsim.org/jpscore/img/Rooms.png)
Is the connection between room 0 and 1 a `crossing` or a `transition`? I think it must be a `transition`? Who can change the drawing?https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/284JPSfire Windows compatibility2018-10-17T08:31:27+02:00Mohcine Chraibim.chraibi@fz-juelich.deJPSfire Windows compatibilitySeveral path concatenations in JPSfire are not windows compatible.Several path concatenations in JPSfire are not windows compatible.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/286Deleted agents due to closed doors2018-10-16T09:59:27+02:00Ghost UserDeleted agents due to closed doorsIf all the doors of a room are closed, the agents are deleted because the route can not be initialized.
The should stay in the room waiting until the door opens again.If all the doors of a room are closed, the agents are deleted because the route can not be initialized.
The should stay in the room waiting until the door opens again.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/143Source code ZIP is incomplete2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deSource code ZIP is incompleteThe download link for externals towards the Source code of v0.7 is incomplete.
https://github.com/JuPedSim/JuPedSim/archive/v0.7.zipThe download link for externals towards the Source code of v0.7 is incomplete.
https://github.com/JuPedSim/JuPedSim/archive/v0.7.ziphttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/145stairs: coordinate calculation2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.destairs: coordinate calculationMax has written a small script to determine the coordinates of stair subrooms.
In combination with a small sketch, I suggest to implement the procedure more detailed into the v0.8 manual.
[Ebenengleichung.py](https://cst.version.fz-jue...Max has written a small script to determine the coordinates of stair subrooms.
In combination with a small sketch, I suggest to implement the procedure more detailed into the v0.8 manual.
[Ebenengleichung.py](https://cst.version.fz-juelich.de/jupedsim/jpscore/uploads/b867b2c621c2260ed62b451f0a71589c/Ebenengleichung.py)
@M.Osterkamp Would you please prepare some input for the documentation?
- English phraseology
- sketchMohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/161Influence of Pedestrian's in different rooms2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deInfluence of Pedestrian's in different roomsPedestrians in 3D geometry are in different rooms (on top of each other), may still influence each other.
Problem related to model 3: *Tordeux2015*
![UBF_traj_travisto_snap_160120_13h_0](/uploads/e9897fb781ea99469fc23c8e8133bf85/UBF_...Pedestrians in 3D geometry are in different rooms (on top of each other), may still influence each other.
Problem related to model 3: *Tordeux2015*
![UBF_traj_travisto_snap_160120_13h_0](/uploads/e9897fb781ea99469fc23c8e8133bf85/UBF_traj_travisto_snap_160120_13h_0.png)
![UBF_traj_travisto_snap_160120_13h_1](/uploads/18dac6db1526bd8d1bbffe47529e6704/UBF_traj_travisto_snap_160120_13h_1.png)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/174Segmentation Fault2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deSegmentation FaultThe problem occurs since commit edf536a.
Simulation with these files:
-----
- [UBF_routing.xml](/uploads/b8f2d9d1b9393be6c8f58628f4afdc2c/UBF_routing.xml)
- [UBF_dummy_id_6_seed_3011.xml](/uploads/ef14991532a96316fb9cf9748600d25f/UBF...The problem occurs since commit edf536a.
Simulation with these files:
-----
- [UBF_routing.xml](/uploads/b8f2d9d1b9393be6c8f58628f4afdc2c/UBF_routing.xml)
- [UBF_dummy_id_6_seed_3011.xml](/uploads/ef14991532a96316fb9cf9748600d25f/UBF_dummy_id_6_seed_3011.xml)
- [UBF_geo_extra_rooms.xml](/uploads/93c7f6ff75960a8539a2d9dcf38ffd89/UBF_geo_extra_rooms.xml)
----
The simulation starts with this error:
```
ERROR: Cannot find valid destination for ped [16]
located in room [0] subroom [0] going to destination [-1]
```
I could trace the problem back to the call of `Pedestrian::GetV0Norm()`
```
const Point& target = _navLine->GetCentre()
```
target is invalid:
```
read memory from 0x28 failed (0 of 8 bytes read)
```
therefore the following call
```
double nav_elevation = sub->GetElevation(target);
```
leads to SegFault.
@Arne maybe you can fix this swiftly..
Changing the router from `quickest` to `global` solves the problem. But here the very first problem (ped 16 not finding his ways) does not occur.
Maybe, we delete a ped, and then try *later* to access his parameters?Arne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/168Stair::IsInSubRoom2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deStair::IsInSubRoom(related to #167 )
The function
```
subroom->IsInSubRoom(ped)
```
returns *false* for `ped=33` in room `2`
- **FRAME 278**
![UBF_traj_travisto_snap_160202_16h_0](/uploads/fe4c5d6af1af8ed9986eb1e4639e0cf2/UBF_traj_travisto_snap_1602...(related to #167 )
The function
```
subroom->IsInSubRoom(ped)
```
returns *false* for `ped=33` in room `2`
- **FRAME 278**
![UBF_traj_travisto_snap_160202_16h_0](/uploads/fe4c5d6af1af8ed9986eb1e4639e0cf2/UBF_traj_travisto_snap_160202_16h_0.png)
- **FRAME 179**
![UBF_traj_travisto_snap_160202_16h_1](/uploads/c8b5e77cf0ed641a39749850643ea05a/UBF_traj_travisto_snap_160202_16h_1.png)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/167Error: correcting the door statistics2018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deError: correcting the door statisticsThe simulation stops with Error: correcting the door statistics by using:
show_statistics>true</show_statistics
otherwise by using show_statistics>false</show_statistics the simulation finished successful.[UBF_statistics.rar](/uploads...The simulation stops with Error: correcting the door statistics by using:
show_statistics>true</show_statistics
otherwise by using show_statistics>false</show_statistics the simulation finished successful.[UBF_statistics.rar](/uploads/3596ca367caed8f4876aa16930e867b6/UBF_statistics.rar)
![statistic_false](/uploads/4845510a9c93a99c241ff680fa9cb638/statistic_false.jpg)
![statistic_true](/uploads/3df872f7299daf33c8585c97a4d505e1/statistic_true.jpg)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/166SegFault DirectionStrategy 62018-06-13T16:41:49+02:00Mohcine Chraibim.chraibi@fz-juelich.deSegFault DirectionStrategy 6If you use DirectionStrategy 6 but not the FloorField model as the operational model a SegFault emerges.
It seems that the floorField is not initiated then (nullptr) (see Fig.)
![segFault](/uploads/1fe59dd3a100d443f8e1304bf67bb5a5/segF...If you use DirectionStrategy 6 but not the FloorField model as the operational model a SegFault emerges.
It seems that the floorField is not initiated then (nullptr) (see Fig.)
![segFault](/uploads/1fe59dd3a100d443f8e1304bf67bb5a5/segFault.JPG)Arne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/122Oscillating at navigation lines2018-06-13T16:41:48+02:00Mohcine Chraibim.chraibi@fz-juelich.deOscillating at navigation linesI think we had this problem already! Peds oscillate around nav lines: They go in and immediately out and so on and so forth..
![Screen_Shot_2015-07-17_at_23.35.08](https://cst.version.fz-juelich.de/jupedsim/jpscore/uploads/92f0f92afc28a...I think we had this problem already! Peds oscillate around nav lines: They go in and immediately out and so on and so forth..
![Screen_Shot_2015-07-17_at_23.35.08](https://cst.version.fz-juelich.de/jupedsim/jpscore/uploads/92f0f92afc28a043f2fb210a1a0aa645/Screen_Shot_2015-07-17_at_23.35.08.png)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/165Overlapping between Walls and Hlines2018-06-13T16:41:48+02:00Mohcine Chraibim.chraibi@fz-juelich.deOverlapping between Walls and Hlines- Reference: closed Issue #158
- attached files: testing geo- and ini-file used with 4 different Router ID´s
[JPScore_Test_21012016.rar](/uploads/cab238ad8cb30d8f7054b41c0766ba3e/JPScore_Test_21012016.rar)- Reference: closed Issue #158
- attached files: testing geo- and ini-file used with 4 different Router ID´s
[JPScore_Test_21012016.rar](/uploads/cab238ad8cb30d8f7054b41c0766ba3e/JPScore_Test_21012016.rar)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.de