From 95ff7de296dd69d51bae37beaaa69fae65ce78d6 Mon Sep 17 00:00:00 2001
From: Ulrich Kemloh <kemlohulrich@gmail.com>
Date: Mon, 2 Feb 2015 14:58:57 +0100
Subject: [PATCH] update exit_crossing_strategy
---
JuPedSim.tex | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/JuPedSim.tex b/JuPedSim.tex
index a551175..d2403cc 100644
--- a/JuPedSim.tex
+++ b/JuPedSim.tex
@@ -597,7 +597,7 @@ For the definition of the GCFM the user is refereed to \cite{Chraibi2010a}.
<model_parameters>
<solver>euler</solver>
<stepsize>0.01</stepsize>
- <exitCrossingStrategy>4</exitCrossingStrategy>
+ <exit_crossing_strategy>4</exit_crossing_strategy>
<linkedcells enabled="true" cell_size="2.2" />
<force_ped nu="0.3" dist_max="3" disteff_max="2" interpolation_width="0.1" />
<force_wall nu="0.2" dist_max="3" disteff_max="2" interpolation_width="0.1" />
@@ -635,7 +635,7 @@ For the definition of the GCFM the user is refereed to \cite{Chraibi2010a}.
\paragraph{stepsize} integration step size in seconds. Be careful not to choose a large value otherwise the system might become unstable.
The recommended value $10^{-3}$ s.
-\paragraph{exitCrossingStrategy} defines how a pedestrian crosses a line $L = [P_1, P_2]$. Possible values are:
+\paragraph{exit\_crossing\_strategy} defines how a pedestrian crosses a line $L = [P_1, P_2]$. Possible values are:
\begin{itemize}
\item \textbf{1}: The direction of the pedestrian is towards the middle of $L$ ($\frac{P_1+P2}{2}$)
\item \textbf{2}: The direction is given by the nearest point on $L$ to the position of the pedestrian.
@@ -701,7 +701,7 @@ Both models differ only in the definition of the repulsive force (see \autoref{e
<model_parameters>
<solver>euler</solver>
<stepsize>0.01</stepsize>
- <exitCrossingStrategy>3</exitCrossingStrategy>
+ <exit_crossing_strategy>3</exit_crossing_strategy>
<linkedcells enabled="true" cell_size="2.2" />
<bmax mu="0.25" sigma="0.01" />
<bmin mu="0.20" sigma="0.01" />
@@ -919,7 +919,7 @@ xsi:noNamespaceSchemaLocation="http://xsd.jupedsim.org/0.6/jps_ini_core.xsd">
<model_parameters>
<solver>euler</solver>
<stepsize>0.01</stepsize>
- <exitCrossingStrategy>4</exitCrossingStrategy>
+ <exit_crossing_strategy>4</exit_crossing_strategy>
<linkedcells enabled="true" cell_size="2.2" />
<force_ped nu="0.3" dist_max="3" disteff_max="2" interpolation_width="0.1" />
<force_wall nu="0.2" dist_max="3" disteff_max="2" interpolation_width="0.1" />
@@ -946,7 +946,7 @@ xsi:noNamespaceSchemaLocation="http://xsd.jupedsim.org/0.6/jps_ini_core.xsd">
<model_parameters>
<solver>euler</solver>
<stepsize>0.01</stepsize>
- <exitCrossingStrategy>3</exitCrossingStrategy>
+ <exit_crossing_strategy>3</exit_crossing_strategy>
<linkedcells enabled="true" cell_size="2.2" />
<force_ped nu="3" b="0.25" c="3.0"/>
<force_wall nu="10" b="0.70" c="3.0"/>
@@ -1347,7 +1347,7 @@ In the master inifile you can use python syntax to give different values for the
\item \textbf{geometry}: Give a directory name containing different xml-files. In case you have only one file, just specify its name.
\item \textbf{num\_threads}: (Optional) Number of CPUs to be used in the simulation. If not given (and openmp is activated), the maximum of cores in the machine is used. Otherwise num\_threads=1.
\item \textbf{number}: Number of agents
-\item \textbf{exitCrossingStrategy}: Strategy for the desired direction %,exit\_crossing\_strategy
+\item \textbf{exit\_crossing\_strategy}: Strategy for the desired direction
\item \textbf{model\_id}: operational model
\item \textbf{cell\_size}: Cell size
\item \textbf{router\_id}: Router
--
GitLab