JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2018-06-13T16:41:29+02:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/193shelloutput of jpscore and jpsvis return two different evacuation times2018-06-13T16:41:29+02:00Mohcine Chraibim.chraibi@fz-juelich.deshelloutput of jpscore and jpsvis return two different evacuation timesSame scenario - two different evacuation times. Which one is the correct one?
Can you please check if you get different time, too?
![output](/uploads/d156ab3a95877db9af5deca2a121e13d/output.JPG)
![outputjpsvis](/uploads/18cf888167e723...Same scenario - two different evacuation times. Which one is the correct one?
Can you please check if you get different time, too?
![output](/uploads/d156ab3a95877db9af5deca2a121e13d/output.JPG)
![outputjpsvis](/uploads/18cf888167e7235f1e9c95f3aff14ae0/outputjpsvis.JPG)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/192Boost linking with g++ under Mac OSX2018-06-13T16:41:31+02:00Mohcine Chraibim.chraibi@fz-juelich.deBoost linking with g++ under Mac OSXBoost is sometimes not linked properly.
```
cmake -DCMAKE_CXX_COMPILER=g++-5 -DCMAKE_C_COMPILER=gcc-5 ..
```
then
```
make
```
leads to link-errors related to Boost.Boost is sometimes not linked properly.
```
cmake -DCMAKE_CXX_COMPILER=g++-5 -DCMAKE_C_COMPILER=gcc-5 ..
```
then
```
make
```
leads to link-errors related to Boost.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/191routing with goals in complex geometries2018-03-16T15:01:03+01:00Mohcine Chraibim.chraibi@fz-juelich.derouting with goals in complex geometriesWhen using goals to direct peds to a specific transition to -1, the routing patterns may not be as expected.
[Osloer_geo_train_crossings_closed_mod.xml](/uploads/735db2e2f466ea81cc2079e97de74728/Osloer_geo_train_crossings_closed_mod.x...When using goals to direct peds to a specific transition to -1, the routing patterns may not be as expected.
[Osloer_geo_train_crossings_closed_mod.xml](/uploads/735db2e2f466ea81cc2079e97de74728/Osloer_geo_train_crossings_closed_mod.xml)
[Osloer_routing_manual_mod.xml](/uploads/f60b879a930491f272687bf51c293254/Osloer_routing_manual_mod.xml)
[U8_007.xml](/uploads/0b7cafd4b618b7b07f39bb7378cf78c9/U8_007.xml)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/190Exception when using cogmap router2018-06-13T16:41:31+02:00Mohcine Chraibim.chraibi@fz-juelich.deException when using cogmap routerterminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not validterminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct null not validhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/188version mismatch2018-03-16T15:01:03+01:00Mohcine Chraibim.chraibi@fz-juelich.deversion mismatchall tests fail due to old version number (0.5, should be 0.8)all tests fail due to old version number (0.5, should be 0.8)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/187GlobaleRouter terminates with: ERROR: GlobalRouter: There is no visibility p...2018-06-13T16:41:31+02:00Mohcine Chraibim.chraibi@fz-juelich.deGlobaleRouter terminates with: ERROR: GlobalRouter: There is no visibility path from [trans_0_room_9_subroom_13] to the outside 2# Problem
GlobalRouter terminates with the error message "There is no visibility path ..." for a scenario with a trivial geometry (long channel of 5 rooms, one side open other side closed), where it should work.
# Detailed error message...# Problem
GlobalRouter terminates with the error message "There is no visibility path ..." for a scenario with a trivial geometry (long channel of 5 rooms, one side open other side closed), where it should work.
# Detailed error message
INFO: Done with Initializing the grid
INFO: Init the Global Router Engine
INFO: Exit to outside found: 14 [trans_3_room_13_subroom_21]
ERROR: GlobalRouter: There is no visibility path from [trans_0_room_9_subroom_13] to the outside 2
You can solve this by enabling triangulation.
--------> Dumping AP <-----------
Friendly ID: trans_0_room_9_subroom_13 centre = [ 112.35, 110.85 ]
Real ID: 11
Length: 20.25
Is final exit to outside :0
Distance to final goals
[ -1, 0 m ]
transit to final goals:
connected to aps :
[ 15_trans_4_room_14_subroom_26 , 1.67705 m ]
queue [ ]
------------------------------
ERROR: could not initialize the routers!
# Steps to reproduce
1. download
[geo.xml](/uploads/6a99f4e8ba99872cde78e58996746690/geo.xml)
[ini.xml](/uploads/bfca097a52d76cdad9432c792a467c89/ini.xml)
2. run
jpscore ini.xml
# Hints
Only one AP is assigned to room:subroom 9:13. It is the AP that corresponds to transition 4.Nevertheless in geo.xml there is also a transition 0 that connects 9:13 with 8:12, but the corresponding AP is not created.Arne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/186Implement sink2019-03-25T02:12:19+01:00Mohcine Chraibim.chraibi@fz-juelich.deImplement sinkPeople should not leave the building automatically, but according to a predefined outflow rate (time-independent?).People should not leave the building automatically, but according to a predefined outflow rate (time-independent?).Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/181QuickestPath stops with AP Dump2018-06-13T16:41:31+02:00Mohcine Chraibim.chraibi@fz-juelich.deQuickestPath stops with AP DumpQuickest Path stops: We think, that it happens in special cases only. One of these special cases is described now:
A subroom consists of a closed door and an open door.
Pedestrians, that start in that subroom, manage to get out.
Pedest...Quickest Path stops: We think, that it happens in special cases only. One of these special cases is described now:
A subroom consists of a closed door and an open door.
Pedestrians, that start in that subroom, manage to get out.
Pedestrians, that get pushed in that subroom (via the closed door), will not find a way out.
Such a room is Room 9, Subroom 1
**Reproduction Steps:**
1. run with provided ini, geo and routing file
**Expected behavior:**
Even if a pedestrian is pushed into another (sub-)room, the router should find an exit
**Observed behavior:**
Dump AP gets called with msg:
~~~
ERROR: Cannot find valid destination for ped [1174] located in room [9] subroom [1] going to destination [-1]
ERROR: No route to destination [ -1 ]
ERROR: Check your configuration file
~~~
**Screenshots and GIFs**
~~~
Time: 54.30 s | Evacuated: 91 / 1660 ( 5% ) [==> ]
ERROR: Cannot find valid destination for ped [1174] located in room [9] subroom [1] going to destination [-1]
ERROR: No route to destination [ -1 ]
ERROR: Check your configuration file
--------> Dumping AP <-----------
Friendly ID: trans_26_room_9_subroom_1 centre = [ 16.6103, 81.6841 ]
Real ID: 1286
Length: 1.00012
Is final exit to outside :0
Distance to final goals
transit to final goals:
to UID ---> [ -1 ] ---> [ Nothing ]
connected to aps :
queue [ ]
------------------------------
~~~
![Screenshots and GIFs which follow reproduction steps to demonstrate the problem](url)
- **JuPedSim version:** v0.8
- **OS and version:** Mac/Linux
- **Compiler and version:** gcc 4.8 / clang 3.1
**Additional Info**
* Problem happens with the attached ini and geometry files: [Yes]
* Might be connected to my latest change of subroom ID to UID in some parts (plz be very careful)
* GetBestDefaultRandomExit
[aaaaQuickest_UBF_id_1_seed_1905.xml.zip](/uploads/d782a4683257707a9cae839b38567fc0/aaaaQuickest_UBF_id_1_seed_1905.xml.zip)Arne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/180Pedestrian stays at Door2018-06-13T16:41:31+02:00Mohcine Chraibim.chraibi@fz-juelich.dePedestrian stays at DoorOne pedestrian stays at a door while leaving the building.
**Reproduction Steps:**
1. Load input files [Kobes_geo.xml](/uploads/143d6fa3f4644f56baaa379778dc2905/Kobes_geo.xml)
[Kobes_ini.xml](/uploads/30ea5160eb450f9a6c8080694f005ad3/K...One pedestrian stays at a door while leaving the building.
**Reproduction Steps:**
1. Load input files [Kobes_geo.xml](/uploads/143d6fa3f4644f56baaa379778dc2905/Kobes_geo.xml)
[Kobes_ini.xml](/uploads/30ea5160eb450f9a6c8080694f005ad3/Kobes_ini.xml)
2. Use cogmap, velocity model and exit_crossing_strategy 9
3. Problem also occurs using other (GCFM) operational models
**Expected behavior:**
All pedestrians are leaving the building.
**Observed behavior:**
One pedestrian stays at a door.
**Screenshots and GIFs**
![smokesensortest](/uploads/58d84aacd6c2924f890515e9a201b229/smokesensortest.JPG)
**JuPedSim version:** 0.9 (actual develop branch)
**OS and version:** Windows MingGW?
**Compiler and version:** MingGW C++? All?
**Additional information:**
* Problem can be reliably reproduced, doesn't happen randomly: [Yes]
* Problem happens with the attached ini and geometry files: [Yes]
@andresen pls check if all information is correct.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/179Pedestrians get trapped in obstacels with Tordeux20152018-03-16T15:01:03+01:00Mohcine Chraibim.chraibi@fz-juelich.dePedestrians get trapped in obstacels with Tordeux2015Even with the Tordeux2015 model, we obviously have serious problems with agents getting trapped in obstacles:
![Untitled](/uploads/824590463e8fb406287f76cd7a2e229c/Untitled.png)
With the example attached it is possible to reproduce t...Even with the Tordeux2015 model, we obviously have serious problems with agents getting trapped in obstacles:
![Untitled](/uploads/824590463e8fb406287f76cd7a2e229c/Untitled.png)
With the example attached it is possible to reproduce that
[Osloer_ini.xml](/uploads/2c8820e2ed0dcfb72452e7801a24d7ba/Osloer_ini.xml)
[Osloer_geo.xml](/uploads/6980f607f4f207365276c8ee3b578884/Osloer_geo.xml)
[Osloer_routing.xml](/uploads/530408351b2fa74625a589780263f8cb/Osloer_routing.xml)Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/178feature request: import pre-calculated floorfield?2018-03-16T15:01:03+01:00Mohcine Chraibim.chraibi@fz-juelich.defeature request: import pre-calculated floorfield?Assuming a static geometry, might it be reasonable to have the opportunity to import a pre-calculated floor field e.g. for sensitivity studies?
Instead of we would have to compute multiple times...Assuming a static geometry, might it be reasonable to have the opportunity to import a pre-calculated floor field e.g. for sensitivity studies?
Instead of we would have to compute multiple times...Arne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/177Unexpected beahavior with different OS's2018-06-13T16:41:33+02:00Mohcine Chraibim.chraibi@fz-juelich.deUnexpected beahavior with different OS'sLets start with were i found it: In issue jupedsim/jpscore#174 @chraibi found a segfault occurring on OS X. The reason here was that a ped could not find a route in the velocity model. So
~~~.cpp
if (ped->FindRoute() == -1)
~~~
was true...Lets start with were i found it: In issue jupedsim/jpscore#174 @chraibi found a segfault occurring on OS X. The reason here was that a ped could not find a route in the velocity model. So
~~~.cpp
if (ped->FindRoute() == -1)
~~~
was true and the ped was removed of the simulation but indexes where not handled correctly. However this segfault did not occur on Linux. The question here is why? The answer quite simple:
On Linux all peds could find a route while on OSX one Ped (`id=16`) could not.
Reproduction Steps
===
1. Load input files from jupedsim/jpscore#174
2. Take Linux and run them
3. Take OS X and run them
Expected behavior
===
The same number of peds should be tried to evacuate on every OS
Observed behavior
===
You will see in the output that on OS X 174 peds were evacuated, while on Linux 175.
- **JuPedSim version:** 0.8
- **OS and version:** Linux and OSX
- **Compiler and version:** gcc 4.8 and apple-clang 7.0
Additional information:
====
Supposed search start: See what happens in `ped->FindRoute()` and why the result may differ for different OS's
* Problem can be reliably reproduced, doesn't happen randomly: [Yes]
* Problem happens with the attached ini and geometry files: see jupedsim/jpscore#174https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/176Simulation continues even if all peds are evacuated.2018-06-13T16:41:30+02:00Mohcine Chraibim.chraibi@fz-juelich.deSimulation continues even if all peds are evacuated.Description:
============
Simulation continues running till max evacutation time even if all peds are evacuated long time before.
**Reproduction Steps:**
1. Change to branch issue_175
1. Take all input files from #175
2. Change `<ag...Description:
============
Simulation continues running till max evacutation time even if all peds are evacuated long time before.
**Reproduction Steps:**
1. Change to branch issue_175
1. Take all input files from #175
2. Change `<agents operational_model_id="1">` to `<agents operational_model_id="4">` in Kobes_ini.xml
3. run `jpscore Kobes_ini.xml`
**Expected behavior:**
Simulation should finish after all 11 peds are evacuated around 70s
**Observed behavior:**
Simulation continues till max Exec Time = 200s is exceeded
**Console Output**
~~~.bash
INFO: Loading and parsing the project file <Kobes_ini.xml>
INFO: seed <6943>
INFO: Maximal simulation time <200.00> seconds
INFO: Using num_threads <0> threads
INFO: output file <Kobes_traj.xml>
INFO: in format <xml-plain> at <8.000000> frames per seconds
INFO: Using the Gradient model
INFO: Parsing the model parameters
INFO: pSolver <euler>
INFO: stepsize <0.010000>
INFO: exit_crossing_strategy < 6 >
INFO: floorfield <delta h=0.0625, wall avoid distance=0.40>
INFO: floorfield <use wall avoidance=true>
INFO: linked cells enabled with size <4.2>
INFO: frep_ped mu=15, a=1.00, b=0.25 c=3.00
INFO: frep_wall mu=0, a=1.00, b=0.70 c=3.00
INFO: Anti Clipping: SlowDown Distance=0.80
INFO: Parsing agents parameters
INFO: Parsing the group parameter id [1]
INFO: desired speed mu=1.200000 , sigma=0.000000
INFO: Bmax mu=0.150000 , sigma=0.001000
INFO: Bmin mu=0.150000 , sigma=0.001000
INFO: Amin mu=0.150000 , sigma=0.001000
INFO: Tau mu=0.500000 , sigma=0.001000
INFO: Atau mu=0.000000 , sigma=0.001000
INFO: Using CognitiveMapRouter
INFO: Sensor Room2Corridor added
INFO: Sensor LastDestination added
INFO: Sensor Jam added
INFO: All pedestrian starting with a(n) complete cognitive map
INFO: Parsing the project file completed
INFO: Loading and parsing the persons attributes
INFO: ...Done
INFO: Parsing the geometry file
INFO: geometry <Kobes_geo.xml>
INFO: Loading building file successful!!!
INFO: Loading extra routing information
INFO: done with loading extra routing information
INFO: Init Geometry
INFO: Init Geometry successful!!!
INFO: Triangulating the geometry
INFO: Done...
INFO: Loading the traffic info file
INFO: Done with loading traffic info file
INFO: Init Distribute
INFO: Distributing 1 Agents in Room/Subrom [0/2]! Maximum allowed: 180
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/3]! Maximum allowed: 180
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/4]! Maximum allowed: 210
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/5]! Maximum allowed: 260
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/6]! Maximum allowed: 210
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/7]! Maximum allowed: 210
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/8]! Maximum allowed: 210
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/9]! Maximum allowed: 260
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/10]! Maximum allowed: 260
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/11]! Maximum allowed: 260
...Done
INFO: Distributing 1 Agents in Room/Subrom [0/12]! Maximum allowed: 252
...Done
INFO: Initializing the grid with cell size: 4.200000
INFO: Done with Initializing the grid
INFO: Init the Global Router Engine
INFO: Loading extra routing information for the global/quickest path router
INFO: from the file Kobes_routing.xml
INFO: Done with loading extra routing information. Loaded <3> Hlines
INFO: Exit to outside found: 124 [trans_0_room_0_subroom_13]
INFO: Exit to outside found: 125 [trans_1_room_0_subroom_13]
INFO: Exit to outside found: 126 [trans_2_room_0_subroom_13]
INFO: Exit to outside found: 127 [trans_3_room_0_subroom_13]
INFO: Done with the Global Router Engine!
INFO: Init the Cognitive Map Router Engine
INFO: Initialized CognitiveMapStorage
INFO: Initialized SensorManager
INFO: Checking the geometry for artifacts
INFO: ...Done!!!
INFO: Init Operational Model starting ...
INFO: Init DirectionFloorfield starting ...
INFO: GeometryFilename <Kobes_geo.xml>
INFO: Calling Construtor of FloorfieldViaFM
INFO: Start Parsing: Building
INFO: Finished Parsing: Building
INFO: Grid initialized: Walls
INFO: Grid initialized: Walldistances
INFO: Grid initialized: Speed
INFO: Taken time: 12.217932
INFO: Init DirectionFloorfield done
INFO: Init Operational Model done
INFO: nPeds 11 received
INFO: Files 'events.txt' missing.
INFO: Adding a new routing Engine with the key:
INFO: Looking for pre-defined events in other files
INFO: No events found
INFO: Start runSimulation() with 11 pedestrians
Time: 200.00 s | Evacuated: 11 / 11 (100% ) [========================================>]
INFO: End runSimulation()
Exec Time [s] : 113.00
Evac Time [s] : 200
Realtime Factor : 1.77 X
Number of Threads : 0
Warnings : 0
Errors : 0
~~~
**JuPedSim version:** 0.8 branch issue_175
**Compiler and version:** g++ 4.8
Edit: proper report ;)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/175Oscillating agents and uncaught exception2018-06-13T16:41:30+02:00Mohcine Chraibim.chraibi@fz-juelich.deOscillating agents and uncaught exceptionWhen using the operational models gcfm, grompertz or tordeux, the agents will not evacuate but oscillate in a specific place (e.g. door).
When using gradnav, the following error occurs:
~~~.bash
libc++abi.dylib: terminating with uncaug...When using the operational models gcfm, grompertz or tordeux, the agents will not evacuate but oscillate in a specific place (e.g. door).
When using gradnav, the following error occurs:
~~~.bash
libc++abi.dylib: terminating with uncaught exception of type std::out_of_range: map::at: key not found
Abort trap: 6
~~~
This is happening since I updated jpscore.[jpsvis_video.mov](/uploads/2cc501993e15e1df103ef37234a147d1/jpsvis_video.mov)
[Kobes_geo.xml](/uploads/2c39c4fc83acba133acd990b88ea8c85/Kobes_geo.xml)
[Kobes_ini.xml](/uploads/043a6369ea3f8774078063b89ac134ec/Kobes_ini.xml)
[Kobes_routing.xml](/uploads/8c5c856f4cf148692a7316390d785251/Kobes_routing.xml)Arne GrafArne Grafhttps://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/171Navigation lines in non-convex geometries2018-03-16T15:01:03+01:00Mohcine Chraibim.chraibi@fz-juelich.deNavigation lines in non-convex geometriesWhen simulating in non-convex geometries using the cognitive map router, jpscore returns the error: could not initialize the routers. This is the case for every operational model, but the floorfield model shouldn't need hlines? Surprisin...When simulating in non-convex geometries using the cognitive map router, jpscore returns the error: could not initialize the routers. This is the case for every operational model, but the floorfield model shouldn't need hlines? Surprisingly, one can fix this by adding navigation lines under the global shortest router. How come?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/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