-[Generalized Centrifugal Force Model with lateral swaying](#generalized-centrifugal-force-model-with-lateral-swaying)
### Example 1
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
If the text between $$ contains newlines it will rendered in display mode:
Several operational models are implemented in `jpscore`.
An operational model defines how pedestrians moves from one time step to the next.
In the definition of agent's properties it is mandatory to precise the number of the model to be used e.g.:
```xml
<agentsoperational_model_id="n">
```
$$
f(x) = \int_{-\infty}^\infty\hat f(\xi)\,e^{2 \pi i \xi x}\,d\xi
$$
where `n` is 1, 2, 3, 4 or 5.
### General model parameters (for all models)
The definition of any model parameter is composed of two different
sections:
-**model_parameters**: Model specific parameter. See below in the different model sections.
-**agent_parameters**: These parameter are mainly specific for the shape of pedestrians
or other pedestrian properties like desired speed, reaction time etc.
### Model_parameters
-`<solver>euler</solver>`
- The solver for the ODE. Only *Euler*. No other options.
-`<stepsize>0.001</stepsize>`:
- The time step for the solver. This should be choosed with care. For force-based model it is recommended to take a value between $`10^{-2} `$ and $`10^{-3}`$ s.
For first-order models, a value of 0.05 s should be OK.
A larger time step leads to faster simulations, however it is too risky and can lead to
numerical instability, collisions and overlapping among pedestrians.
- Unit: s
-`<periodic>0</periodic>`
- Set to 1 if a system with closed boundary conditions should be simulated. Default setting is 0.
- This option is only implemented in *Tordeux2015* and is very geometry-specific (only for corridors) with predefined settings. See Utest/Validation/1test_1D/ for a use case.
[Collision-free speed model][#Tordeux2015] is a velocity-based model. See also this [talk](https://fz-juelich.sciebo.de/index.php/s/1pYFETbvJdJDusE) for more details about the model.
Besides the options defined in [Mode_parameters](#model_parameters) the following options are necessary for this model:
-`<force_ped a="5" D="0.2"/>`
- The influence of other pedestrians is triggered by $`a`$ and $`D`$ where $`a`$ is the strength if the interaction and $`D`$ gives its range. The naming may be misleading, since the model is **not** force-based, but velocity-based.
- Unit: m
-`<force_wall a="5" D="0.02"/>`:
- The influence of walls is triggered by $`a`$ and $`D`$ where $`a`$ is the strength if the interaction and $`D`$ gives its range. A larger value of $`D`$ may lead to blockades, especially when passing narrow bottlenecks.
- Unit: m
The names of the aforementioned parameters might be misleading, since the model is *not* force-based. The naming will be changed in the future.
#### Agent parameters (recommendations)
Actually, this model assumes circular pedestrian's shape, therefore the parameter for the semi-axes [Agent_parameters](#agent_parameters) should be chosen, such that circles with constant radius can be obtained.
[Wall-avoidance model][#ModelGraf2015] is a velocity-based model. The Wall-Avoidance Model focuses on valid pedestrian positions. The interaction of agents with walls takes precedence over the agent-to-agent interaction. There are two key aspects:
* In the vicinity to walls, agents take on a different behaviour, slowing them down (parameter: slowdowndistance)
* Agents follow special floorfields, directing them to the targets/goals, which will have them avoid walls if possible (free space)
Valid exit strategies are {6, 8, 9}. Please see details below.
The strategies 6, 8 and 9 differ only in the way the floorfield is created:
- 6: one floorfield over all geometry (building); only in 2D geometries; directing every agent to the closest exit
- 8: multiple floorfield-objects (one for every __room__); each object can create a floor field on the fly to a target line (or vector of lines) within the room; working in multi-floor-buildings; requires a router that provides intermediate targets in the same room
- 9: (__recommended__) multiple floorfield-objects (one for every __subroom__);
each object can create a floor field on the fly to a target line (or vector of lines)
within the same subroom; working in multi-floor-buildings;
requires a router that provides intermediate targets in the same subroom;
- range in which other pedestrians are considered neighbours and can influence the current agent. This value defines cell-size of the cell-grid.
### Generalized Centrifugal Force Model with lateral swaying
The [Generalized Centrifugal Force Model with lateral swaying][#Krausz] is mostly identical to the GCFM Model,
but instead of a variable semi-axis $`b`$ of the ellipse simulating the pedestrian, pedestrians perform an oscillation perpendicular to their direction of motion.
Setting `ampA` and `ampB` to 0 disables lateral swaying. If not specified, the empirical values given in [Krausz, 2012][#Krausz] are used, that is:
-`ampA` = -0.14, `ampB` = 0.21 and
-`freqA` = 0.44, `freqB` = 0.25.
[#GCFM]:http://journals.aps.org/pre/abstract/10.1103/PhysRevE.82.046111"Mohcine Chraibi, Armin Seyfried, and Andreas Schadschneider Phys. Rev. E 82, 046111"
[#gompertz]:http://trg-india.org/trg_conference_2015"Kemloh Wagoum, Armel Ulrich, Mohcine Chraibi, Jun Zhang and Gregor Lämmel. JuPedSim: An Open Framework for Simulating and Analyzing the Dynamics of Pedestrians. In 3rd Conference of Transportation Research Group of India, 2015."
[#Tordeux2015]:http://arxiv.org/abs/1512.05597"Tordeux, Antoine, Chraibi, Mohcine and Seyfried, Armin, Collision-free speed model for pedestrian dynamics. In Traffic and Granular Flow '15, to appear."
