JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2018-06-13T16:29:18+02:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/7GlobalRouter exits2018-06-13T16:29:18+02:00Mohcine Chraibim.chraibi@fz-juelich.deGlobalRouter exitsGlobalRouter should not quit when the final Exit is not visible.
Maybe a warning is enough.
Example: Corner - One Room - One Exit. Here the exit is not yet visible, but that is fine. The Router should not panik and quit the simulation.GlobalRouter should not quit when the final Exit is not visible.
Maybe a warning is enough.
Example: Corner - One Room - One Exit. Here the exit is not yet visible, but that is fine. The Router should not panik and quit the simulation.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/6Exit strategies2018-06-13T16:29:18+02:00Mohcine Chraibim.chraibi@fz-juelich.deExit strategiesAll exit strategies (choosing the direction of the desired velocity) should be combined in a unique usable strategy.
One approach can be to adapt the strategy to the length of the portal.All exit strategies (choosing the direction of the desired velocity) should be combined in a unique usable strategy.
One approach can be to adapt the strategy to the length of the portal.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/5Simulation report2018-06-13T16:41:22+02:00Mohcine Chraibim.chraibi@fz-juelich.deSimulation reportCreate an optional report at the end of the simulation.
It should contain:
1. Evacuation time
2. Simulation time
3. Exit usage statistic
4...Create an optional report at the end of the simulation.
It should contain:
1. Evacuation time
2. Simulation time
3. Exit usage statistic
4...https://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/3Closed boundary conditions2018-06-13T16:41:45+02:00Mohcine Chraibim.chraibi@fz-juelich.deClosed boundary conditionsClosed boundary conditions should be implemented. Important for FD in 1dim (e.g. Rotunde) and 2dim (UG Hermes)Closed boundary conditions should be implemented. Important for FD in 1dim (e.g. Rotunde) and 2dim (UG Hermes)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/2Unified unit in all input and output files. Choose SI, metre for distances an...2018-06-13T16:41:22+02:00Mohcine Chraibim.chraibi@fz-juelich.deUnified unit in all input and output files. Choose SI, metre for distances and second for timeInput files currently are in Metres
Trajectories are in CentimetersInput files currently are in Metres
Trajectories are in Centimetershttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/1documentation2018-06-13T16:41:23+02:00Mohcine Chraibim.chraibi@fz-juelich.dedocumentationDocumentation of all classes in doxygen style
Update the manual to reflect the changes in the input file formatDocumentation of all classes in doxygen style
Update the manual to reflect the changes in the input file formathttps://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/269Agents not passing a transition2018-04-16T16:18:34+02:00benjamin moehringAgents not passing a transition## Summary
In the provided minimal example an agent isn't able to pass one of the transitions, while another agent passes the same transition in a different direction.
## Steps to reproduce
Run the example
## Inifile + Geometry file t...## Summary
In the provided minimal example an agent isn't able to pass one of the transitions, while another agent passes the same transition in a different direction.
## Steps to reproduce
Run the example
## Inifile + Geometry file to reproduce bug
[jps_geo.xml](/uploads/97d9f1e34b592c8b0ef4f8e63ac24235/jps_geo.xml)
[jps_ini.xml](/uploads/d18d16318f8c452f5514c36693af3535/jps_ini.xml)
## Relevant logs, files (inifile and geometry) and/or screenshots
[jps_log.P0.dat](/uploads/c8439717a78562c34e585e5f9464ba54/jps_log.P0.dat)
[jps_traj.xml](/uploads/c8fe5766d4c02249763fd05b3d732100/jps_traj.xml)
![image](/uploads/a01781270b513a254afb0b7c441bc04d/image.png)0.8.3Arne GrafArne Grafhttps://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/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/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/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/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/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/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/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/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/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/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/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/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/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/299Door frequency2019-03-24T19:10:55+01:00Ghost UserDoor frequencyWhen doors are used as exits, e.g. to simulate boarding a train, a defined frequency is needed to regulate the "outflow".
E.g. only one person per 2 seconds may board the train, because of the distance between the track and the train,...When doors are used as exits, e.g. to simulate boarding a train, a defined frequency is needed to regulate the "outflow".
E.g. only one person per 2 seconds may board the train, because of the distance between the track and the train, some steps in the train, etc.
So the door needs a frequency, which allows only one person per 2 seconds to pass the door.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/295Close doors after a certain number of agents have entered2019-01-29T13:25:32+01:00Ghost UserClose doors after a certain number of agents have enteredFor the studies in KapaKrit it will be useful to close the doors after a certain number of agents have entered the room.For the studies in KapaKrit it will be useful to close the doors after a certain number of agents have entered the room.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/302External files2019-03-29T15:31:40+01:00Ghost UserExternal filesFor the ini-file we need external **files for**:
- [x] goals
- [x] waiting areas
- [x] sources
- [x] traffic_constraints
Then we also need an external file for the **geo-file**:
- [x] transitions For the ini-file we need external **files for**:
- [x] goals
- [x] waiting areas
- [x] sources
- [x] traffic_constraints
Then we also need an external file for the **geo-file**:
- [x] transitions v0.8.4tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/300Tracks for Trains2019-07-17T06:19:29+02:00Ghost UserTracks for TrainsTo simulate different trains in the same simulation we need a flexible geometry. The track edge need to be a big wall, if there is no train. When a train arrives it must contain doors to the train and be again a big wall when the train l...To simulate different trains in the same simulation we need a flexible geometry. The track edge need to be a big wall, if there is no train. When a train arrives it must contain doors to the train and be again a big wall when the train leaves. And this needs to be done for every arriving train.
Here is an example, how it might look like:
**ini-file:**
```
<train_time_tables>
<train id="1" type="RE" room_id="1" track_x-start="0" track_y-start="0" track_x-end="300" track_y-end="0" time="5" >
<train id="2" type="ICE" room_id=„1“ track_x-start="0" track_y-start="0" track_x-end="300" track_y-end="0" time="300">
<train id="3" type="RB" room_id="1" track_x-start="0" track_y-start="0" track_x-end="300" track_y-end="0" time="900">
<\train_time_tables>
```
* *RE, ICE etc.* links to the external file of the train_types (see below), which contains the door information.
* *track_x/y_start/end* defines the track edge.
* *time* means the time when the train arrives the station and opens its doors.
**train_types-file:**
The train_types need to be translated into transitions (see below -> geometry-file)
```
<train_type = "RE" agents_max="600" xa="20" xe="220">
<door_id="1" x1="3" x2="5.5" door_frequency="2">
<door_id="2" x1="13" x2="15.5" door_frequency="3">
<door_id="3" x1="23" x2="25.5" door_frequency="2">
...
<\train_type>
<train_type = "ICE" agents_max="750">
<door_id="1" x1="3" x2="5.5" door_frequency="2">
<door_id="2" x1="13" x2="15.5" door_frequency="3">
<door_id="3" x1="23" x2="25.5" door_frequency="2">
...
<\train_type>
```
* *agents_max* is the maximum capacity of the train. When this number is reached, all doors will be closed.
* *xa, xe* are the start- and endpoint of the train relatively to the start point of the track.
* *x1, x2* are the coordinates of the doors relatively to the start- and endpoints of the train.
* *door_frequency* [s] defines the time, which one agent needs to enter the train.
* *door_id* can be used to set transition_id.
**Geometry-file**
```
<transitions>
<transition id="101" caption="RE_1" type="train_door" room1_id="1" subroom1_id="1" room2_id="-1"
subroom2_id="-1" frequency"3">
<vertex px="90" py="87"/>
<vertex px="90" py="88.5"/>
</transition>
<\transitions>
```
* *caption* is a composition of "train_type" and "door_id".
* *type="train_door"* can be used to know that the agents exit the model with a train ans a frequency is needed for the doors.
* *room_id1* from train_type (see above), subroom_id automatically by checking the coordinates of the track doors an the subrooms.
* *frequency* ist the door_frequency from train_type-file (see above).0.8.5Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/297Agent deadlock when using different repulsion rates in Tordeux model2019-07-09T17:07:53+02:00Ben HeinAgent deadlock when using different repulsion rates in Tordeux modelPlease checkout branch `tordeux_extend` and use the ini and geo files provided.
Problem: Several agents won't move at all when modelling different repulsion rates a.
In this example, 20 agents are modelled with a=0 and 30 agents with a=...Please checkout branch `tordeux_extend` and use the ini and geo files provided.
Problem: Several agents won't move at all when modelling different repulsion rates a.
In this example, 20 agents are modelled with a=0 and 30 agents with a=10.
[0_geo.xml](/uploads/2dc8e12983616b6c28d0bf92429766ea/0_geo.xml)
[1_ini.xml](/uploads/ffacdace584aacf3251a1a33f2c38533/1_ini.xml)
![output](/uploads/22e4e76bae29e4a768a2fb1abef8f7d7/output.mp4)Ben HeinBen Heinhttps://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/303Wrong parameter id2019-02-11T08:54:45+01:00guido bastenWrong parameter idIf you insert the wrong parameter id jpscore shows you an error, but still starts the simulation until it crashes.![issue](/uploads/3ef51b862f0e22858fee38b3644b0dab/issue.png)If you insert the wrong parameter id jpscore shows you an error, but still starts the simulation until it crashes.![issue](/uploads/3ef51b862f0e22858fee38b3644b0dab/issue.png)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/304Windows Problems2019-02-21T17:18:12+01:00Ghost UserWindows ProblemsWe tried to do a simulation on a Windows pc, but it crashes after some seconds. I tried it with my Mac and it works. So, it seems to be a Windows problem again.
[correct_Bahnsteige_geo.xml](/uploads/e7691e6c97ca1b57ff65a76958f83faa/corr...We tried to do a simulation on a Windows pc, but it crashes after some seconds. I tried it with my Mac and it works. So, it seems to be a Windows problem again.
[correct_Bahnsteige_geo.xml](/uploads/e7691e6c97ca1b57ff65a76958f83faa/correct_Bahnsteige_geo.xml)
[correct_Bahnsteige_ini.xml](/uploads/b479536d6c2886a6747c8fcf0898f13b/correct_Bahnsteige_ini.xml)
[log-Windows.txt.P0.dat](/uploads/7c40371a5a140bd4d3308937d676a784/log-Windows.txt.P0.dat)
[log-Mac.txt](/uploads/b5b5e485b9b76d7165ae0390bb794f99/log-Mac.txt)
Is there any quick solution for this problem?tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/307New type for doors2019-03-22T15:14:02+01:00Ghost UserNew type for doorsWe need a new door type:
>**temp_close**We need a new door type:
>**temp_close**tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/308Divide trajectory files2019-03-29T15:25:13+01:00Ghost UserDivide trajectory filesBecause we have very huge trajectory files, it could be good to divide the file into smaller ones when simulating. Maybe by writing a new file every 250 MB.Because we have very huge trajectory files, it could be good to divide the file into smaller ones when simulating. Maybe by writing a new file every 250 MB.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/309Dynamic door-statistic2019-03-22T15:14:02+01:00Ghost UserDynamic door-statisticThe door-statistics (crossings and transitions) are written at the end of a simulation. If the simulation fails at an advanced point of time you do not have any results. Hence it could be better to write and update the door statistics dy...The door-statistics (crossings and transitions) are written at the end of a simulation. If the simulation fails at an advanced point of time you do not have any results. Hence it could be better to write and update the door statistics dynamically, like we do it for the trajectories.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/318Building jpscore on windows102019-06-02T14:35:00+02:00Ghost UserBuilding jpscore on windows10## Summary
Build of jpscore not possible.
## Steps to reproduce
http://www.jupedsim.org/jpscore/2018-10-21-windows
## Expected behavior
Build
## Actual behavior
Errors during build in Simulation.cpp and Makros.h
## Relevant logs,...## Summary
Build of jpscore not possible.
## Steps to reproduce
http://www.jupedsim.org/jpscore/2018-10-21-windows
## Expected behavior
Build
## Actual behavior
Errors during build in Simulation.cpp and Makros.h
## Relevant logs, files (inifile and geometry) and/or screenshots
Platform:
- Host: Windows10.0.17763AMD64
- CMake: 3.14.2
- CMake generator: Visual Studio 16 2019
- CMake build tool: C:/Program Files (x86)/Microsoft Visual Studio/2019/Enterprise/MSBuild/Current/Bin/MSBuild.exe
- MSVC: 1920https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/326inifile, header, location for trajectory files2019-07-17T06:19:29+02:00Ghost Userinifile, header, location for trajectory filesThe file location definition (see [header](http://www.jupedsim.org/jpscore/2016-11-01-inifile.html#header)) is only considered for the first trajectory file.
```xml
<trajectories format="xml-plain" fps="8" color_mode="velocity">
<fi...The file location definition (see [header](http://www.jupedsim.org/jpscore/2016-11-01-inifile.html#header)) is only considered for the first trajectory file.
```xml
<trajectories format="xml-plain" fps="8" color_mode="velocity">
<file location="trajectories.xml" /> </trajectories>
```
The other files are stored in the folder of the ini-file.
(example: [geo_RiMEA_Test_04.xml](/uploads/e8d626b8cbbfb2359fc060cf6f531fc7/geo_RiMEA_Test_04.xml), [ini_RiMEA_Test_04_0-5.xml](/uploads/b6b8bcff88e241078336dbf60e9673f8/ini_RiMEA_Test_04_0-5.xml))https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/327Wating area testing 32019-06-24T13:03:43+02:00guido bastenWating area testing 3In this test 100 pedestrians are created with an `agents_source`.
After 50 distributed peds the simulation stops and doesn't show any Errors in the console.
In the Log file is also no explanation why the simulation stops at this point....In this test 100 pedestrians are created with an `agents_source`.
After 50 distributed peds the simulation stops and doesn't show any Errors in the console.
In the Log file is also no explanation why the simulation stops at this point.
![WA_console](/uploads/d2c97e4e79af62f7bc357d8a9a70ed90/WA_console.png)tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/329JPSreport: Err: The trajectory of ped with ID <1> is not continuous. Please m...2019-06-19T13:21:35+02:00Ghost UserJPSreport: Err: The trajectory of ped with ID <1> is not continuous. Please modify the trajectory file!## Summary
JPSreport does not finish its analyzis because "The trajectory of ped with ID <1> is not continuous.". The same error occurs for all IDs.
With a trajectory file from the JuPedSim demo folder this error does not occur. Traject...## Summary
JPSreport does not finish its analyzis because "The trajectory of ped with ID <1> is not continuous.". The same error occurs for all IDs.
With a trajectory file from the JuPedSim demo folder this error does not occur. Trajectories in trajectory file seem to be ok.
## Steps to reproduce
Windows 10, PowerShell
. ..\..\bin\jpsreport.exe ini_corridor_december.xml
## Inifile + Geometry file to reproduce bug
[ini_corridor_december.xml](/uploads/d4caed6c299041a2554e2f14a12188f8/ini_corridor_december.xml)
[geo_test2.xml](/uploads/991d5e7f7bb397764b22d488c368c448/geo_test2.xml)
[traj_100_N25_h0_R2.txt](/uploads/54c49306d5cd857d1ea824af67f1ed48/traj_100_N25_h0_R2.txt)
## Relevant logs, files (inifile and geometry) and/or screenshots
![PowerShell_JPSreport_DecemberExp](/uploads/cb6ce7a583354549b154de30c3ee46df/PowerShell_JPSreport_DecemberExp.jpg)