JPScore issueshttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues2018-02-02T14:21:57+01:00https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/265EllipsesVelocityModel2018-02-02T14:21:57+01:00Mohcine Chraibim.chraibi@fz-juelich.deEllipsesVelocityModelExtend the velocity model with ellipses.Extend the velocity model with ellipses.0.8.3https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/310New trajectory formats (TXT)2019-05-12T22:11:08+02:00Mohcine Chraibim.chraibi@fz-juelich.deNew trajectory formats (TXT)`jpscore` can produce two formats:
- txt: `#ID FR X Y Z `
- [xml](http://www.jupedsim.org/jpscore/2016-11-03-trajectory.html#xml)
I would try to change the txt format to
`
#ID FR X Y Z ...`jpscore` can produce two formats:
- txt: `#ID FR X Y Z `
- [xml](http://www.jupedsim.org/jpscore/2016-11-03-trajectory.html#xml)
I would try to change the txt format to
`
#ID FR X Y Z a b angle color
`
This could lead to slightly bigger files.
Alternatively, we should think about implementing a binary format like [HDF5](https://support.hdfgroup.org/HDF5/)
Any other suggestions are welcome.v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/291Add demos to CI2019-03-25T02:31:09+01:00Mohcine Chraibim.chraibi@fz-juelich.deAdd demos to CIFiles in demos show some important functionalities that need to be conserved during development.
For example, sources, events or stairs
- Unify the naming of the files in every directory: `inifile.xml`, `geometry.xml`
- Run demos with...Files in demos show some important functionalities that need to be conserved during development.
For example, sources, events or stairs
- Unify the naming of the files in every directory: `inifile.xml`, `geometry.xml`
- Run demos with every CIv0.8.4guido bastenguido bastenhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/276CMAKE Flags2019-01-29T09:25:23+01:00Mohcine Chraibim.chraibi@fz-juelich.deCMAKE FlagsThe compiler flags are a mess.
The CMakeFileLists.txt needs some refactoring
- [ ] [For Visual Studio](https://stackoverflow.com/questions/45995784/how-to-set-compiler-options-with-cmake-in-visual-studio-2017)
- [ ] [using add_compile...The compiler flags are a mess.
The CMakeFileLists.txt needs some refactoring
- [ ] [For Visual Studio](https://stackoverflow.com/questions/45995784/how-to-set-compiler-options-with-cmake-in-visual-studio-2017)
- [ ] [using add_compiler_option](https://stackoverflow.com/questions/45955272/modern-way-to-set-compiler-flags-in-cross-platform-cmake-project)
- [ ] [VS_STARTUP_PROJECT](https://cmake.org/cmake/help/v3.6/prop_dir/VS_STARTUP_PROJECT.html)v0.8.4https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/328track for trains question2019-06-27T09:25:38+02:00Tim Orthtrack for trains question## Question
I need some support with the tracks for trains feature.
I changed the class of the subroom to „Platform“ and set the type of the wall of the track to „track-1“ in the geometry.
Defined the start and end of the track in t...## Question
I need some support with the tracks for trains feature.
I changed the class of the subroom to „Platform“ and set the type of the wall of the track to „track-1“ in the geometry.
Defined the start and end of the track in train_time_table.xml with the coordinates of the „track-1“-wall.
```
Terminal message: Arrival:
TRAIN Desiro_HC at time: 30
enter with train Desiro_HC
Enter correctGeometry: Building Has 5 Transitions
room: 101 subroom_id 1
Error in GetIntersection. Should be 2 but got 1
```
1. Which element should have 2 intersections? The „track-1“-wall and the ttt track are from intersection 10/130 to 10/20. I think I’m missing something.
2. In addition: Can the track only be in/at one subroom? Because I get an error if the defined track in ttt uses more then one.
```
Error: Arrival: TRAIN Desiro_HC at time: 30 could not find any track! Exit.
```
Folder witch data for the main question: [files](https://1drv.ms/u/s!AsV6LgpLPxYhgbIanMfhzZ8QJLIXuw?e=tQSaw4)0.8.5Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/313Waiting behaviour2019-04-12T15:24:56+02:00tobias schroedterWaiting behaviourAdd model to display simple waiting behaviour of petsAdd model to display simple waiting behaviour of pets0.8.5tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/311Improve FF2019-06-27T08:10:38+02:00tobias schroedterImprove FF* [ ] Merge FF and FF_Trips
* [ ] Remove `ERROR: Could not find a route for pedestrian 37 in room 2 and subroom 0` when ped leaves the geometry through door
* [ ] If doors are temp_close at start of simulation do not quit computation
* ...* [ ] Merge FF and FF_Trips
* [ ] Remove `ERROR: Could not find a route for pedestrian 37 in room 2 and subroom 0` when ped leaves the geometry through door
* [ ] If doors are temp_close at start of simulation do not quit computation
* [ ] Extend FF such that it is also possible to navigate to points not only exits
0.8.5tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/301Restarting a simulation2019-04-12T13:14:52+02:00Ghost UserRestarting a simulationIt could be necessary to restart/continue a simulation after it has been finished or canceled.
Here is a idea which parameters are needed to restart the simulation:
* group id
* agent id
* location x, y, z
* velocity vx, vy
* fre...It could be necessary to restart/continue a simulation after it has been finished or canceled.
Here is a idea which parameters are needed to restart the simulation:
* group id
* agent id
* location x, y, z
* velocity vx, vy
* frequency (source)
* last frame = start frame
There can be a new trajectory file or the old one can be continued (maybe better).0.8.5https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/296Groups2019-04-12T13:14:43+02:00Ghost UserGroupsGroups = People/Agents who want to stay together and therefore move only in the group, e.g families.Groups = People/Agents who want to stay together and therefore move only in the group, e.g families.0.8.5https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/283Stair in the middle of a (sub)room -> hole for stairs2019-05-10T20:11:52+02:00Ghost UserStair in the middle of a (sub)room -> hole for stairsDefining a (sub)room or a hole in the middle of an other (sub)room for a stair, without subdividing the second (sub)room in more (sub)rooms.
![Grundriss+Treppe](/uploads/58e4fa02fb331410c991954851531040/Grundriss+Treppe.png)
![Schnitt_...Defining a (sub)room or a hole in the middle of an other (sub)room for a stair, without subdividing the second (sub)room in more (sub)rooms.
![Grundriss+Treppe](/uploads/58e4fa02fb331410c991954851531040/Grundriss+Treppe.png)
![Schnitt_Treppe](/uploads/54fccbe897a47b57bee9cd46613ad004/Schnitt_Treppe.png)0.8.5Tao ZhongTao Zhonghttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/271Wiki and website have different content2019-04-12T13:17:19+02:00Mohcine Chraibim.chraibi@fz-juelich.deWiki and website have different contentsynchronize..synchronize..0.8.5Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/312Restructure routing and direction strategy2019-04-12T15:25:28+02:00tobias schroedterRestructure routing and direction strategyRestructure routing and direction strategy:
* [ ] Allow each router with each direction strategy
* [ ] Add waiting behaviour (see #313 )Restructure routing and direction strategy:
* [ ] Allow each router with each direction strategy
* [ ] Add waiting behaviour (see #313 )0.8.6tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/332JURECA | header, logfile2019-07-04T08:06:58+02:00Ghost UserJURECA | header, logfile**jpscore**:
```
JuPedSim - JPScore
Current date : Jul 2 2019 19:07:41
Version : 0.8.4
Commit hash : v0.8.4-68-ga33375a
Commit date : Mon Jul 1 15:21:05 2019
Branch : develop
----
```
**inifile** in `/data`:
...**jpscore**:
```
JuPedSim - JPScore
Current date : Jul 2 2019 19:07:41
Version : 0.8.4
Commit hash : v0.8.4-68-ga33375a
Commit date : Mon Jul 1 15:21:05 2019
Branch : develop
----
```
**inifile** in `/data`:
```xml
<header>
<seed>4313</seed>
<max_sim_time>80</max_sim_time>
<num_threads>48</num_threads>
<show_statistics>true</show_statistics>
<logfile>log_RiMEA_Test_04_7-0_om_2</logfile>
<!--<progressbar/>-->
<trajectories format="plain" fps="2">
<file location="traj_RiMEA_Test_04_7-0_om_2.txt" />
</trajectories>
<geometry>geo_RiMEA_Test_04.xml</geometry>
</header>
...
```
**batch_script** in `$HOME`:
```batch
#!/bin/bash -x
#SBATCH -J R70
#SBATCH --account=ias-7
#SBATCH --nodes=1
#SBATCH --ntasks=1
#SBATCH --cpus-per-task=48
#SBATCH --output=data/out_%j.txt
#SBATCH --error=data/err_%j.txt
#SBATCH --time=6:00:00
#SBATCH --mail-user=g.jaeger@fz-juelich.de
#SBATCH --mail-type=ALL
export OMP_NUM_THREADS=${SLURM_CPUS_PER_TASK}
srun ./jpscore/bin/jpscore data/ini_RiMEA_Test_04_7-0_om_2.xml
```
The logfile is stored in the root directory (`$HOME`) as `datalog_RiMEA_Test_04_7-0_om_2.txt`. Also the statistic files are stored there.
Both files should be stored in the directory `data` (like the trajectory files).
**Note**:
The function `<progressbar/>` creates a very large file (5-15 GB) and should be disabled.https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/331statistical distributions2019-06-24T19:37:53+02:00Ghost Userstatistical distributionsAt the moment, the pre-movement time is Gauss-distributed. The agent parameters are also.
I suggest that we implement more statistical distributions (for agent velocity and pre-movement time):
- no distribution
- uniform (min and max)...At the moment, the pre-movement time is Gauss-distributed. The agent parameters are also.
I suggest that we implement more statistical distributions (for agent velocity and pre-movement time):
- no distribution
- uniform (min and max)
- truncated normal (min, max, mean, sigma)
- normal (mean, sigma) - already exists
- triangular (min, max, mean)
- log-normal (min, max, mean, sigma, sigma_2)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/330Writing Errors for WAs2019-06-24T13:03:42+02:00Ghost UserWriting Errors for WAsIn issue #327 we had to spend a lot of time to find our problem and in the end it was just one wrong letter in the definition of a waiting area.
As we have mentioned in #327 the simulation failed, without writing an error to the log-fil...In issue #327 we had to spend a lot of time to find our problem and in the end it was just one wrong letter in the definition of a waiting area.
As we have mentioned in #327 the simulation failed, without writing an error to the log-file. In the huge files for KapaKrit we might have 3.000 lines or more. Finding a typing error without any message in the log-file could take hours.
So, @schroedter1, is it possible to write such errors into the log? It does not have to be a very specified log-message, which tells you the specific line or something. But a small hint to see in which goal/waiting area the error occurs would be very helpful. Maybe by writing the goals id to the log.tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/325inifile, header2019-06-24T09:30:40+02:00Ghost Userinifile, headerThe simulation *RiMEA_Test_04_0-5* does not run with `<header>` as described in the [documentation](http://www.jupedsim.org/jpscore/2016-11-01-inifile).
[ini_RiMEA_Test_04_0-5.xml](/uploads/34bb482701018f085dfb6f803c49eeb1/ini_RiMEA_Tes...The simulation *RiMEA_Test_04_0-5* does not run with `<header>` as described in the [documentation](http://www.jupedsim.org/jpscore/2016-11-01-inifile).
[ini_RiMEA_Test_04_0-5.xml](/uploads/34bb482701018f085dfb6f803c49eeb1/ini_RiMEA_Test_04_0-5.xml)
[geo_RiMEA_Test_04.xml](/uploads/4fd1cb5dc22914899a3045e653a28593/geo_RiMEA_Test_04.xml)https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/324Print Statistics2019-07-17T06:19:29+02:00Ghost UserPrint Statisticsfrom [Simulation.cpp, line 417 ff](https://gitlab.version.fz-juelich.de/jupedsim/jpscore/blob/develop/Simulation.cpp):
```c++
void Simulation::PrintStatistics(double simTime)
for (const auto& itr : _building->GetAllTransitions()) {
...from [Simulation.cpp, line 417 ff](https://gitlab.version.fz-juelich.de/jupedsim/jpscore/blob/develop/Simulation.cpp):
```c++
void Simulation::PrintStatistics(double simTime)
for (const auto& itr : _building->GetAllTransitions()) {
Transition* goal = itr.second;
if (goal->GetDoorUsage()) {
Log->Write(
"\nExit ID [%d] used by [%d] pedestrians. Last passing time [%0.2f] s",
goal->GetID(), goal->GetDoorUsage(),
goal->GetLastPassingTime());
string statsfile = "flow_exit_id_"+to_string(goal->GetID())+".txt";
if(goal->GetOutflowRate() < (std::numeric_limits<double>::max)())
{
char tmp[50];
sprintf(tmp, "%.2f", goal->GetOutflowRate());
statsfile = "flow_exit_id_"+to_string(goal->GetID())+"_rate_"+tmp+".txt";
}
Log->Write("More Information in the file: %s", statsfile.c_str());
{
auto statOutput = new FileHandler(statsfile.c_str());
statOutput->Write("#Simulation time: %.2f", simTime);
statOutput->Write("#Flow at exit "+goal->GetCaption()+"( ID "+to_string(goal->GetID())+" )");
statOutput->Write("#Time (s) cummulative number of agents \n");
statOutput->Write(goal->GetFlowCurve());
statOutput->FileHandler::~FileHandler();
}
}
}
```
Can we change the filename `flow_exit_id_` in line [430](https://gitlab.version.fz-juelich.de/jupedsim/jpscore/blob/develop/Simulation.cpp#L430) like the trajectory filename (e.g. `flow_exit_id_filename.txt`?https://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/323ff_global_shortest_trips for trains2019-06-12T15:52:36+02:00Ghost Userff_global_shortest_trips for trainsThe router ff_global_shortest_trips needs to be able to use the dynamic trains from #300.The router ff_global_shortest_trips needs to be able to use the dynamic trains from #300.Mohcine Chraibim.chraibi@fz-juelich.deMohcine Chraibim.chraibi@fz-juelich.dehttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/322Waiting area on platform2019-06-12T15:48:19+02:00Ghost UserWaiting area on platformIf there are no doors on the platform the agents should go to the waiting are and wait.
![Screenshot_2019-06-12_15.41.53](/uploads/940996ae0294f50c2cf5fefce3bc5dac/Screenshot_2019-06-12_15.41.53.png)
Or the room (and subroom) has ...If there are no doors on the platform the agents should go to the waiting are and wait.
![Screenshot_2019-06-12_15.41.53](/uploads/940996ae0294f50c2cf5fefce3bc5dac/Screenshot_2019-06-12_15.41.53.png)
Or the room (and subroom) has to be defined as (final) goal.tobias schroedtertobias schroedterhttps://gitlab.jsc.fz-juelich.de/jupedsim/jpscore/-/issues/321Elevators2019-05-20T12:14:10+02:00Ghost UserElevatorsWe have stairs and escalators, but we should also have elevators.We have stairs and escalators, but we should also have elevators.