JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2019-04-12T13:30:30+02:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/294Events2019-04-12T13:30:30+02:00Ghost UserEventsSimulation does not work when using events (router: global_shortest)
The agents should not be rerouted. We want them to walk to the door (goal), even if it is closed and "wait" in front of it until it opens.
Maybe we should give the ff-...Simulation does not work when using events (router: global_shortest)
The agents should not be rerouted. We want them to walk to the door (goal), even if it is closed and "wait" in front of it until it opens.
Maybe we should give the ff-router an attribute to differentiate between two modes:
- `evacuation mode`: agents are rerouted if doors are closed
- `train mode`: pedestrians wait in front of *their* doors even if they are temporarily closed.
[log-c.txt.txt](/uploads/61a2fdf5bad0461a8b161b598804d2b6/log-c.txt.txt)
[events_list.xml](/uploads/c2157666f0aeb00496ac857153c940b0/events_list.xml)
[Raum_1_ini.xml](/uploads/0e3e58df2cf370810da7bcdefe151f99/Raum_1_ini.xml)
[Raum_1_traj-c.xml](/uploads/ff4861dad02f48fe08837066295c955f/Raum_1_traj-c.xml)
[Raum_1.xml](/uploads/b91f133cacb2df514e7c2f31993d57cb/Raum_1.xml)tobias schroedtertobias schroedterhttps://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/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/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/285FloorField Router: Open a door after a certain time2019-03-21T11:32:47+01:00Ghost UserFloorField Router: Open a door after a certain timeIf doors are closed they can not be used for the entire time. But sometimes there is a need to open a door again after a certain time.If doors are closed they can not be used for the entire time. But sometimes there is a need to open a door again after a certain time.tobias schroedtertobias schroedterhttps://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/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/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/277Error when set the source (containing the time and location)2019-03-15T16:51:55+01:00hongliu liError when set the source (containing the time and location)INFO: Source 171 generating 1 agents (0 remaining)
ERROR: In getDirectionToUID (3 args)
0.000000 0.000000
ERROR: desired_direction in VelocityModel::e0 is too small.
INFO: Source 172 generating 1 agents (0 remaining)INFO: Source 171 generating 1 agents (0 remaining)
ERROR: In getDirectionToUID (3 args)
0.000000 0.000000
ERROR: desired_direction in VelocityModel::e0 is too small.
INFO: Source 172 generating 1 agents (0 remaining)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/275AI Router not found / seg fault2018-06-01T10:13:08+02:00Ben HeinAI Router not found / seg faultWhen using the smoke sensor demo files (Directory: jpsfire/demos/A_smoke_sensor/JuPedSim), jpscore yields a seg fault. The log gives the following error:
ERROR: Could not Find any router with ID: [7].
Was there something changed wit...When using the smoke sensor demo files (Directory: jpsfire/demos/A_smoke_sensor/JuPedSim), jpscore yields a seg fault. The log gives the following error:
ERROR: Could not Find any router with ID: [7].
Was there something changed with the AI router?https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/273peds removed2018-05-09T12:20:18+02:00benjamin moehringpeds removedHi all,
a lot of peds in my obviously quite large simulation are removed directly after being inserted (4.500 out of 10.000). They do not show up in the trajectories.
This happens from second 30 on. If an agent is removed, all followin...Hi all,
a lot of peds in my obviously quite large simulation are removed directly after being inserted (4.500 out of 10.000). They do not show up in the trajectories.
This happens from second 30 on. If an agent is removed, all following agents, who were supposed to be inserted at the same time, are removed too. See the log:
> INFO: Source 159 generating 1 agents (0 remaining)
> INFO: Source 160 generating 1 agents (0 remaining)
> INFO: Source 161 generating 1 agents (0 remaining)
> INFO: Source 162 generating 1 agents (0 remaining)
> INFO: Source 163 generating 1 agents (0 remaining)
> INFO: Source 164 generating 1 agents (0 remaining)
> INFO: Source 165 generating 1 agents (0 remaining)
> WARNING: ped 160 with vmean 0.000000 has been deleted in room [39]/[3] after time 30.041667 s (current=30.083333
> WARNING: ped 161 with vmean 0.000000 has been deleted in room [39]/[2] after time 30.041667 s (current=30.083333
> WARNING: ped 162 with vmean 0.000000 has been deleted in room [1]/[12] after time 30.041667 s (current=30.083333
> WARNING: ped 163 with vmean 0.000000 has been deleted in room [29]/[14] after time 30.041667 s (current=30.083333
> WARNING: ped 164 with vmean 0.000000 has been deleted in room [2]/[11] after time 30.041667 s (current=30.083333
> WARNING: ped 165 with vmean 0.000000 has been deleted in room [53]/[6] after time 30.041667 s (current=30.083333
> INFO: Source 166 generating 1 agents (0 remaining)
> INFO: Source 167 generating 1 agents (0 remaining)
> INFO: Source 168 generating 1 agents (0 remaining)
> INFO: Source 169 generating 1 agents (0 remaining)
> INFO: Source 170 generating 1 agents (0 remaining)
> INFO: Source 171 generating 1 agents (0 remaining)
> INFO: Source 172 generating 1 agents (0 remaining)
> WARNING: ped 170 with vmean 0.000000 has been deleted in room [17]/[2] after time 31.083333 s (current=31.125000
> WARNING: ped 171 with vmean 0.000000 has been deleted in room [29]/[10] after time 31.083333 s (current=31.125000
> WARNING: ped 172 with vmean 0.000000 has been deleted in room [53]/[6] after time 31.083333 s (current=31.125000
In VelocityModel.cpp I found the relevant code:
` // stuck peds get removed. Warning is thrown. low speed due to jam is omitted.
if(ped->GetGlobalTime() > 30 + ped->GetPremovementTime() &&
std::max(ped->GetMeanVelOverRecTime(), ped->GetV().Norm()) < 0.01 &&
size == 0 ) // size length of peds neighbour vector
{
Log->Write("WARNING:\tped %d with vmean %f has been deleted in room [%i]/[%i] after time %f s (current=%f\n", ped->GetID(), ped->GetMeanVelOverRecTime(), ped->GetRoomID(), ped->GetSubRoomID(), ped->GetGlobalTime(), current);
#pragma omp critical(VelocityModel_ComputeNextTimeStep_pedsToRemove)
pedsToRemove.push_back(ped);
}`
What is the meaning of ped->GetPremovementTime() and is it possible that it should be set to a high value when agents are inserted from sources?
As I see it a ped, which is inserted after second 30, easily meets these demands.
How can we guarantee that these agents aren't immediately removed?
Thank you for your help.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/272Installation failed2018-05-01T08:16:29+02:00Ghost UserInstallation failedCmake Problem with commit a3ec1420
```
$ cmake ..
-- JPSCORE_VERSION: 0.8.2
-- BUILD_TESTING: OFF
-- BUILD_CPPUNIT_TEST: OFF
-- CMAKE_BUILD_TYPE: Debug
-- CMAKE_BINARY_DIR: /Users/anna/JuPedSim/jpscore/build
-- CMAKE_SOURCE_DIR: /User...Cmake Problem with commit a3ec1420
```
$ cmake ..
-- JPSCORE_VERSION: 0.8.2
-- BUILD_TESTING: OFF
-- BUILD_CPPUNIT_TEST: OFF
-- CMAKE_BUILD_TYPE: Debug
-- CMAKE_BINARY_DIR: /Users/anna/JuPedSim/jpscore/build
-- CMAKE_SOURCE_DIR: /Users/anna/JuPedSim/jpscore
-- CMAKE_TEST_DIR: /Users/anna/JuPedSim/jpscore/Utest
--
-- Platform:
-- Host: Darwin17.5.0x86_64
-- CMake: 3.10.2
-- CMake generator: Unix Makefiles
-- CMake build tool: /usr/bin/make
-- Configuration: Debug
--
-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE)
-- Brew detected: /usr/local
-- Could NOT find OpenMP_C (missing: OpenMP_C_FLAGS OpenMP_C_LIB_NAMES)
-- Could NOT find OpenMP_CXX (missing: OpenMP_CXX_FLAGS OpenMP_CXX_LIB_NAMES)
-- Could NOT find OpenMP (missing: OpenMP_C_FOUND OpenMP_CXX_FOUND)
CMake Warning at /usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:801 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:907 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
CMakeLists.txt:199 (find_package)
CMake Warning at /usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:801 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:907 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
CMakeLists.txt:199 (find_package)
CMake Warning at /usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:801 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:907 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
CMakeLists.txt:199 (find_package)
CMake Warning at /usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:801 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:907 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
CMakeLists.txt:199 (find_package)
CMake Warning at /usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:801 (message):
New Boost version may have incorrect or missing dependencies and imported
targets
Call Stack (most recent call first):
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:907 (_Boost_COMPONENT_DEPENDENCIES)
/usr/local/Cellar/cmake/3.10.2/share/cmake/Modules/FindBoost.cmake:1542 (_Boost_MISSING_DEPENDENCIES)
CMakeLists.txt:199 (find_package)
-- Boost version: 1.66.0
-- Found the following Boost libraries:
-- timer
-- chrono
-- system
-- filesystem
-- unit_test_framework
CMake Error at CMakeLists.txt:202 (find_package):
By not providing "FindCGAL.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "CGAL", but
CMake did not find one.
Could not find a package configuration file provided by "CGAL" with any of
the following names:
CGALConfig.cmake
cgal-config.cmake
Add the installation prefix of "CGAL" to CMAKE_PREFIX_PATH or set
"CGAL_DIR" to a directory containing one of the above files. If "CGAL"
provides a separate development package or SDK, be sure it has been
installed.
-- Configuring incomplete, errors occurred!
See also "/Users/anna/JuPedSim/jpscore/build/CMakeFiles/CMakeOutput.log".
```https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/270Statistics about deleted agents2018-05-18T19:04:12+02:00benjamin moehringStatistics about deleted agents## Short description of suggestion
To me stuck agents are a major indicator to the performance and reliability of a scenario. However, when agents are deleted from the simulation, they do not appear as stuck at the end of the simulation....## Short description of suggestion
To me stuck agents are a major indicator to the performance and reliability of a scenario. However, when agents are deleted from the simulation, they do not appear as stuck at the end of the simulation. This means that while trying to improve a simulation possibly more agents can be deleted, causing supposedly better results.
A number about the amount of deleted agents or a warning in the logfile whenever an agent is deleted would be useful.
Best, Bennihttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/268Make escalators direction-dependent2018-05-16T09:02:08+02:00benjamin moehringMake escalators direction-dependent## Short description of suggestion
JuPedSim allows us to define subrooms as "stairs" or "escalators". So far the escalator only influences an agent's speed, defined by the parameters
* v0_escalator_upstairs mu="0.5" sigma="0.0"/
* v0_e...## Short description of suggestion
JuPedSim allows us to define subrooms as "stairs" or "escalators". So far the escalator only influences an agent's speed, defined by the parameters
* v0_escalator_upstairs mu="0.5" sigma="0.0"/
* v0_escalator_downstairs mu="0.5" sigma="0.0"/
However, the direction of an escalator isn't considered in the routing. This mean that agents can take escalators in the wrong direction.
## How to change this:
Talking to Arne and Mohcine, we figured out a way that could possibly work.
* class="escalator"
has to be further specified by:
* class="escalator_up"
* class="escalator_down"
After initializing the distance_matrix the distance value in the forbidden direction has to be changed to a very large value for each escalator. The subroom is then unlikely to be chosen.
Best, Bennitobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/266Floorfield in large geometries2018-06-13T16:41:33+02:00benjamin moehringFloorfield in large geometries## Description
I created a first geometry version of Berlin Alexandeprlatz, which obviously became quite large.
I got a basic example of agent pairs between each platform running when simulating only the inside rooms. The DirectionLoca...## Description
I created a first geometry version of Berlin Alexandeprlatz, which obviously became quite large.
I got a basic example of agent pairs between each platform running when simulating only the inside rooms. The DirectionLocalFloorfield already takes quite some time though. (Please neglect the other simulation problems you can see in the log-file for the moment)
However when using the whole geometry, jpscore is being killed on my machine and debugging is aborted.
## Question
* Is there a solution to make the process less vulnerable? Smaller and more subrooms, convex subrooms, rectangular shapes, more rooms with less subrooms...
* Do you think using the current ff makes sense for such large geometries at all? Is it worth it to change to a conventional router and provide a routing.xml-file?
## Files
[alexanderplatz_all.7z](/uploads/659e88ab7227bce97b1ecbfc75a6ff81/alexanderplatz_all.7z)
[alexanderplatz_inside.7z](/uploads/3bd89564f684f181833238576a603971/alexanderplatz_inside.7z)
Best, BenniArne GrafArne Grafhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/264Rooms as goals2018-01-25T17:26:16+01:00benjamin moehringRooms as goals## Question
Can I also define rooms as goals? The documentation says I can't place goals inside rooms. How can I otherwise have sources and goals within the same area?
[documentation](http://www.jupedsim.org/jpscore/2016-11-01-inifile....## Question
Can I also define rooms as goals? The documentation says I can't place goals inside rooms. How can I otherwise have sources and goals within the same area?
[documentation](http://www.jupedsim.org/jpscore/2016-11-01-inifile.html#goals)
*Additional goals might be defined outside the geometry. They should NOT overlap with any walls or be inside rooms. It is recommended to position them near the exits.*
Thank you, Bennihttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/263Can't compile on linux! Wrong boost version?2018-01-24T10:34:58+01:00Ghost UserCan't compile on linux! Wrong boost version?`PedDistributor.cpp`
In member function ‘const std::vector<Point> PedDistributor::GetPositionsFromFile(std::string, int, std::string) const’:
pedestrian/PedDistributor.cpp:456:61:
error: no matching function for call to
`combine(std...`PedDistributor.cpp`
In member function ‘const std::vector<Point> PedDistributor::GetPositionsFromFile(std::string, int, std::string) const’:
pedestrian/PedDistributor.cpp:456:61:
error: no matching function for call to
`combine(std::vector<int>&, std::vector<int>&, std::vector<double>&, std::vector<double>&)`
`for (auto tup : boost::combine(ids, frames, xpos, ypos))` https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/262validating geometry files2018-01-18T16:39:18+01:00benjamin moehringvalidating geometry files## Question
As mentioned in my last issue i am writting a code to create jps-geometries. To validate my output i am using jpsvis. Usually file errors are well documented in the log file. I'm having problems with an example network, that...## Question
As mentioned in my last issue i am writting a code to create jps-geometries. To validate my output i am using jpsvis. Usually file errors are well documented in the log file. I'm having problems with an example network, that I created for my home village Meckesheim though.
jpsvis opens the file without errors and visualizes the content, including the transitions. When viewing the geometry structure it crashes though. No logfile iswritten.
Do you know possible reasons for the crash? Are there other ways to validate my geometry file before opening it in JPS?
Thank you, Benni
## File
[MeckesheimJPSOut.xml](/uploads/0e753401e32b7485081a29bbd739991c/MeckesheimJPSOut.xml)
## Screenshots
![image](/uploads/dd52b4a79822bbda8d4c0289fd0c9879/image.png)
![image](/uploads/3b0410c89dd401f90d40a71fdaa0e7e2/image.png)
https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/260Walking speed is not activated when specifying in JPSfire section of ini file2017-12-25T02:44:10+01:00Ben HeinWalking speed is not activated when specifying in JPSfire section of ini file## Summary
This if statement, which should activate the walking speed reduction, is not executed when Walking Speed is specified in the ini file.
` if(_WalkingSpeed && _WalkingSpeed->ReduceWalkingSpeed()) {
std::cout << "...## Summary
This if statement, which should activate the walking speed reduction, is not executed when Walking Speed is specified in the ini file.
` if(_WalkingSpeed && _WalkingSpeed->ReduceWalkingSpeed()) {
std::cout << "JPSfire?" << std::endl;
walking_speed = _WalkingSpeed->WalkingInSmoke(this, walking_speed);`
## Steps to reproduce
Activate in any ini file to see that WalkingSpeed is not executed.
## Expected behavior
Walking speed reduction of agents.
## Actual behavior
no behaviour at allMohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/255Simulation outcome not different when using jpsfire2017-12-28T11:16:09+01:00Ben HeinSimulation outcome not different when using jpsfireSpecifying jpsfire in the inifile like this for example:
`<JPSfire>
<A_smoke_sensor smoke_factor_grids="../FDS/3_sfgrids/" update_time="20" final_time="100" />
</JPSfire>`
with specific risk tolerances (`risk_tolerance_alpha="3.0" ris...Specifying jpsfire in the inifile like this for example:
`<JPSfire>
<A_smoke_sensor smoke_factor_grids="../FDS/3_sfgrids/" update_time="20" final_time="100" />
</JPSfire>`
with specific risk tolerances (`risk_tolerance_alpha="3.0" risk_tolerance_beta="12.0"`)
will not yield different simulation outcomes (the agents behave as if there were no sensor and take the shortest path).
However, I remember it working when the file input took place under the sensor section. Maybe they are not probably incorporated now...