JuPedSim issueshttps://gitlab.jsc.fz-juelich.de/groups/jupedsim/-/issues2019-07-17T06:19:29+02:00https://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/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/jpseditor/-/issues/513D visibility2019-06-27T19:50:16+02:00Mohcine Chraibim.chraibi@fz-juelich.de3D visibilityIt would be nice if JPSeditor can visualize 3D geometries.
For instance like in JPSvis. See this [movie](https://fz-juelich.sciebo.de/index.php/s/p0dhs5MtHmZXzGy)
Maybe having two modis: 2D and 3D is good.
![Screen_Shot_2017-07-15_at_...It would be nice if JPSeditor can visualize 3D geometries.
For instance like in JPSvis. See this [movie](https://fz-juelich.sciebo.de/index.php/s/p0dhs5MtHmZXzGy)
Maybe having two modis: 2D and 3D is good.
![Screen_Shot_2017-07-15_at_12.53.44](/uploads/947ce516f41e5645e07ae64bc9ed4a16/Screen_Shot_2017-07-15_at_12.53.44.png)Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/69run fds2019-06-27T19:50:16+02:00Tao Zhongrun fdsTao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/74Zoom Extents2019-06-27T19:50:15+02:00Mohcine Chraibim.chraibi@fz-juelich.deZoom ExtentsBefore drawing anything, clicking on `Zoom Extents` leads to SegFault.Before drawing anything, clicking on `Zoom Extents` leads to SegFault.v0.9 - DevTao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/43Run jpscore2019-06-27T19:50:15+02:00Mohcine Chraibim.chraibi@fz-juelich.deRun jpscoreAdd Button to run jpscore.Add Button to run jpscore.v0.9 - DevTao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/58XML Converter with custom Setting2019-06-27T19:50:15+02:00Tao ZhongXML Converter with custom SettingThis is the third phase of XML2FDS project.
Feature description:
1. User clicks a convertor icon on toolbar, JPSeditor pops up a window
2. User chooses a `.XML` file to load
3. User changes the elements and values for FDS testing as th...This is the third phase of XML2FDS project.
Feature description:
1. User clicks a convertor icon on toolbar, JPSeditor pops up a window
2. User chooses a `.XML` file to load
3. User changes the elements and values for FDS testing as they need
4. click `Convert to FDS`.v0.9 - DevTao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/102Line snap2019-06-27T19:50:15+02:00Ghost UserLine snapA tool like "object snap", but for snapping any point on a line (wall), to be more flexible in drawing.
For example, you have a room like this:
```
______________
| |
| |
| | <-- line A
|____________...A tool like "object snap", but for snapping any point on a line (wall), to be more flexible in drawing.
For example, you have a room like this:
```
______________
| |
| |
| | <-- line A
|_____________|
```
and you like to do something like this:
```
______________
| line A --> |
| |_____________ line B
| | |
|_____________|_____________|
```
To draw line B, it would be useful to snap line A at the point, where line B comes up against it.v0.8.7Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/83Easier way to define stairs2019-06-27T19:50:15+02:00Tao ZhongEasier way to define stairs* Version: 0.83* Version: 0.83v0.8.8Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/109Goals and Sources2019-06-27T19:50:15+02:00Ghost UserGoals and SourcesIt should be able to draw and define goals and sources with the editor and save it in external files like the h-lines.It should be able to draw and define goals and sources with the editor and save it in external files like the h-lines.v0.8.8Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/134Update ini file reader2019-06-27T19:50:15+02:00Tao ZhongUpdate ini file readerThe format of ini file is changed, the praser in JPSeditor must be updatedThe format of ini file is changed, the praser in JPSeditor must be updatedv0.8.8Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/129Format the name of xml files2019-06-27T19:50:15+02:00Tao ZhongFormat the name of xml filesv0.8.8Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/131Show/ hide options tab2019-06-27T19:50:15+02:00Mohcine Chraibim.chraibi@fz-juelich.deShow/ hide options tabHave a look at the video to get the idea :-)
![hide_show](/uploads/2ef7a75662409182d82b2cf15fff0d75/hide_show.mov)Have a look at the video to get the idea :-)
![hide_show](/uploads/2ef7a75662409182d82b2cf15fff0d75/hide_show.mov)v0.8.8Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/135Update ini file writer/reader for models2019-06-27T19:50:15+02:00Tao ZhongUpdate ini file writer/reader for modelsv0.8.9Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/143Double Transitions2019-06-27T19:50:15+02:00Ghost UserDouble TransitionsWhen creating a geometry with doors, the transitions are (always) saved twice in the geometry file.When creating a geometry with doors, the transitions are (always) saved twice in the geometry file.v0.8.9Tao ZhongTao Zhonghttps://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)https://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/110Shortcuts2019-06-18T16:40:23+02:00Ghost UserShortcutsIt should be possible to use the old shortcuts for wall ("w"), door ("d") etc. again.
And it would also good to be able to use the "esc"- and "del"-button again.It should be possible to use the old shortcuts for wall ("w"), door ("d") etc. again.
And it would also good to be able to use the "esc"- and "del"-button again.Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpseditor/-/issues/104Delete walls by using "Del"2019-06-18T16:40:23+02:00Ghost UserDelete walls by using "Del"If you want to delete single or multiple walls, you select them and use the tool "delete selected lines".
In previous versions of the editor you could also delete the selected walls by pressing "Del" on the keyboard. It would be nice to ...If you want to delete single or multiple walls, you select them and use the tool "delete selected lines".
In previous versions of the editor you could also delete the selected walls by pressing "Del" on the keyboard. It would be nice to have such a function again. Maybe "backspace" can be used instead of "Del".v0.8.6 - stableTao ZhongTao Zhong