Index: dam engine/trunk/doc/Dam Engine - Functional Design/DesignGeometryAdaption.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/DesignGeometryAdaption.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/DesignGeometryAdaption.tex	(revision 368)
@@ -0,0 +1,93 @@
+\chapter{Geometry Adaption} \label{sec:DesignGeometryAdaption}
+For the purposes of policy studies or determining impact scope or emergency measures, it can be useful to generate a profile that corresponds to the stated safety factor. \ProgramName can make automatic geometry adaptations for this purpose using a number of basic assumptions.\newline
+
+Automatic profile adaptation in \ProgramName consists of the following steps:
+\begin{enumerate}
+	\item Raising the crest (see \autoref{sec:RaiseCrest})
+	\item Reducing the gradient of the slope (see \autoref{sec:ReduceSlope})
+	\item Shoulder development (see \autoref{sec:ShoulderDevelop})
+\end{enumerate}
+
+\section{Raising the crest} \label{sec:RaiseCrest}
+During this step, \ProgramName checks whether the crest height complies with the required (in other words the stated) dike table height (DTH, attribute: DikeTableHeight).\\
+If the crest height (the Z value for characteristic point Outer crest) is equal to or higher than the stated DTH, the profile will not be adapted. If the profile is lower than the stated DTH, \ProgramName adjusts the geometry and creates a new surface line based on the original slope gradients ($\alpha$ and $\beta$) and the original crest width (B), see \autoref{fig:DTHAdaptedGeometry}.\\
+The slope gradients, and the crest width, are determined on the basis of the following characteristic points: 
+\begin{itemize}
+	\item The outer slope gradient ($\alpha$) follows from the calculated gradient on the basis of the outer toe and the outer crest line. If there is an outer shoulder, the outer slope gradient is determined on the basis of the top of the outer shoulder and the outer crest line.
+	\item The crest width (B) follows from the distance between the characteristic points in the outer crest line and inner crest line.
+	\item The outer slope gradient ($\alpha$) follows from the calculated gradient on the basis of the inner toe and the inner crest line. If there is a inner shoulder, the inner slope gradient will be determined on the basis of the top of the inner shoulder and the inner crest line. 
+\end{itemize}
+
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/DTHAdaptedGeometry.png}
+	\caption{Adapted geometry for DTH}
+	\label{fig:DTHAdaptedGeometry}
+\end{figure}
+
+The adapted geometry starts at the toe at riverside (outer toe) in the initial profile, see \autoref{fig:DeletedGeometryPoints}.
+If there is no inner shoulder, the toe at polderside (inner toe) of the adapted profile will be further away on the profile than the original inner toe, see \autoref{fig:DTHAdaptedGeometry}. If the adapted geometry intersects with a inner shoulder, the top of the inner shoulder will be moved, see \autoref{fig:DeletedGeometryPoints}. 
+
+In all adapted profiles, the geometry points within the adapted profile will be removed. The characteristic points will move in accordance with the adaptation of the geometry.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/DeletedGeometryPoints.png}
+	\caption{Adapted geometry by deleting geometry points}
+	\label{fig:DeletedGeometryPoints}
+\end{figure}
+
+If there is an outer shoulder, the adapted geometry will start at the shoulder base outside, see \autoref{fig:OuterShoulderAdeptedGeometry}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/OuterShoulderAdeptedGeometry.png}
+	\caption{Adapted geometry when outer shoulder is present}
+	\label{fig:OuterShoulderAdeptedGeometry}
+\end{figure}
+
+If the geometry adaptation results in the new dike base being so wide that the entire initial geometry is contained within the adapted profile, all the intermediate geometry points, including the characteristic points in the inner shoulder, will be removed, see \autoref{fig:LargerDikeBase}. 
+
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/LargerDikeBase.png}
+	\caption{Adapted geometry with starting point for geometry of outer toe and larger dike base}
+	\label{fig:LargerDikeBase}
+\end{figure}
+
+If there is a ditch in the profile, \ProgramName will move the ditch if the adapted inner toe is further away than the location of the inner toe in the initial profile. The ditch is moved along the unchanged part of the initial profile. If the ditch is moved, \ProgramName will maintain the original distance from the inner toe to the outer edge of the ditch ($\Delta$). The original dimensions of the ditch will be maintained. See \autoref{fig:MoveDitch}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/MoveDitch.png}
+	\caption{Moving the ditch}
+	\label{fig:MoveDitch}
+\end{figure}
+
+\section{Reducing the gradient of the slope}\label{sec:ReduceSlope}
+After the adaptation of the crest height in accordance with DTH (if necessary), \ProgramName will first carry out a stability calculation. If it should emerge that the exit point of the slip circle is on the inner slope and if the calculated safety factor is less than the stated safety factors, \ProgramName will (on condition that the profile adaptation option is on) reduce the gradient of the slope until the calculated safety factor $\ge$ required safety factor and the exit point of the slip circle is on the inner slope, see \autoref{fig:ReduceSlope}. If the exit point is no longer on the inner slope and the calculated safety factor does not comply with the desired safety factor, \ProgramName will generate a stability shoulder, see \autoref{sec:ShoulderDevelop}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/ReduceSlope.png}
+	\caption{Iterative reduction of the gradient of the inner slope on the basis of the exit point of the slip circle}
+	\label{fig:ReduceSlope}
+\end{figure}
+
+\section{Shoulder development} \label{sec:ShoulderDevelop}
+\ProgramName develops a stability shoulder iteratively as long as the slip circle does not intersect with the landslide slope (see \autoref{sec:ReduceSlope}) and the stated safety level has not yet been achieved. The maximum number of iteration stages is 200. This limit prevents \ProgramName getting stuck in an infinite iteration loop if the stated safety level is not achieved.
+
+The algorithm used is based on moving the crest of the landslide shoulder in a straight line along an incline ($\alpha$), see \autoref{fig:ShoulderDevelop}. The default value is 0.33 (1:3) but it can also be stated by the user (attribute StabilityShoulderGrowSlope).
+
+The adaptation of the shoulder involves moving the inner toe in steps ($\Delta_S$). The steps are in the horizontal direction and the standard steps are 1 metre in length but they can be changed by the user (attribute StabilityShoulderGrowDeltaX). Shoulder development stops when the calculated safety factor in the adapted profile $\ge$ the stated safety factor.
+
+The inner toe is used as the starting point for shoulder development. If there is already a shoulder in the original cross-section, the crest inner shoulder point is used as the starting point. During shoulder development, the crest of the shoulder remains horizontal, as with the raising of the crest, see \autoref{sec:RaiseCrest}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/ShoulderDevelop.png}
+	\caption{Iterative shoulder development for macrostability}
+	\label{fig:ShoulderDevelop}
+\end{figure}
\ No newline at end of file
Index: dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/FO.tex	(revision 368)
@@ -0,0 +1,128 @@
+\chapter{Introduction} 
+\label{chapterIntroduction}
+
+\section{Purpose and scope of this document} \label{sec:PurposeAndScope}
+
+This document contains the functional design for the \ProgramName, a computational engine for the automated calculation of the strength of dikes.
+DAM was developed by Deltares with and for STOWA for all water authorities.
+This document describes requirements and functional design of \ProgramName. 
+What will actually will be implemented depends on the requirements of the clients using this \ProgramName.
+If some functionality is not (yet) needed, then that part does not need to be implemented. 
+
+\subsection{Future options}
+\label{sec:FutureOptions}
+As mentioned above this document contains some options that will not be implemented in the first release, but are foreseen to be implemented in the near future. Therefore although sometimes a reference will be made to these options, these will not be described in detail yet.
+
+That applies in particular to the following subjects:
+\begin{itemize}
+	\item NWO module("Niet Waterkerende Objecten")
+	\item WBI failure mechanisms (Piping, Macrostability)
+\end{itemize}
+\section{Other system documents} 
+\label{sec:SystemDocuments}
+
+The full documentation on the program comprises the following documents.
+
+\renewcommand{\arraystretch}{1.3}
+
+\begin{table}[H]
+%\caption{xxx}
+%\label{xxx}
+\begin{tabular}{|p{40mm}|p{\textwidth-40mm-24pt}|} \hline
+\textbf{Title} & \textbf{Content} \\ \hline
+\ProgramName - Architecture Overall \newline \citep{DAM_ArchitectureOverall} & Description of overall architecture of the \ProgramName and its components. \\ \hline
+\ProgramName- Functional Design (this document)  \newline  \citep{DAMEngine_FunctionalDesign} & Description of the requirements and functional design. \\ \hline
+\ProgramName - Technical Design\newline \citep{DAMEngine_TechnicalDesign}& Description of the implementation of the technical design of \ProgramName. \\ \hline
+\ProgramName - Technical documentation \newline \citep{DAMEngine_TechnicalDocumentation} & Description of the arguments and usage of different software components, generated from in-line comment with Doxygen. \\ \hline
+\ProgramName - Test Plan \newline \citep{DAMEngine_TestPlan} & Description of the different regression and acceptation tests, including target values.  \\ \hline
+\ProgramName - Test Report \newline \citep{DAMEngine_TestReport} & Description of the test results (benchmarks and test scripts). \\ \hline
+Architecture Guidelines \newline \citep{ArchitectureGuidelines} & Architecture guidelines that are used by DSC-Deltares. \\ \hline
+\end{tabular}
+\caption{\small \ProgramName system documents.}
+\label{table-SystemDocuments}
+\end{table}
+
+\section{Document revisions}
+
+\section{Document revisions}
+\label{sec:DocumentRevisions}
+\subsection{Revision 0.1}
+\label{sec:Revision01}
+First concept of the document.
+
+\chapter{Non-functional requirements}
+
+\chapter{Functional requirements}
+
+Main purpose of the \ProgramName
+The \ProgramName gets data from DAM Clients, combines this data to calculation input and make serially calculations with one ore more kernels and generates output.
+
+\section{REQ Data.Format}\label{sec:REQDataFormat}
+The \ProgramName has a defined format for the data input, so DAM Clients know how to arrange the input data.
+
+\section{REQ Data.Content}\label{sec:REQDataContent}
+The \ProgramName has a defined content for the data input, so DAM Clients know how to arrange the input data.
+
+\section{REQ Data.Combination}\label{sec:REQDataCombi}
+The \ProgramName combines data per location when data is provide in GIS-files. Locations are defined by RD-coordinates. The design of this functionality is described in \autoref{sec:DataCombination}.
+
+\section{REQ Data.Generation.Geometry}\label{sec:REQDataGenerationGeometry}
+The \ProgramName can combine a surface line with a subsoil scenario. The result is a geometry, usable for the failure mechanism Macrostability. 
+
+\section{REQ Data.Generation.Porepressures}\label{sec:REQDataGenerationPorepressures}
+The \ProgramName can combine the hydraulic data with a subsoil scenario. The result is a schematization of the pore pressures, usable for the failure mechanisms Piping and Macrostability. The design of this generation is mentioned in \autoref{sec:GenerationPorePressures}.
+
+\section{REQ Calc.Type}\label{sec:REQCalcType}
+The \ProgramName provides three types of calculations:
+\begin{enumerate}
+	\item One-fold calculation: the input goes 'through' the kernel(s) and generates one main calculation answer (assessment);
+	\item Goal-seeking calculation: the input contains one variable and a desired outcome, the answer is the variable sufficient for the goal (design);
+	\item Time-lapsed calculation; calculations are made as time serie (operational).
+\end{enumerate}
+
+More specified; the \ProgramName provides the following calculation types, so the DAM Clients can provide this functionality.
+\begin{itemize}
+	\item Assessment general
+	\item Assessment regional dikes
+	\item Operational calculation from sensor data
+	\item Design of geometry, given required safety factor: Design-Geometry
+	\item Design of normative NWO-location, given dimensions of NWO and required safety factor: Design-NWO
+\end{itemize}
+
+\section{REQ Calc.Assess.General}\label{sec:REQCalcAssessGeneral}
+The DAM engine provides a Factor of safety. This may be one calculation or several. More than one calculation becames available when using several locations and/or several scenarios.
+
+\section{REQ Calc.Assess.Loadscenarios}\label{sec:REQCalcAssessLoadscenarios}
+The DAM engine must be able to calculate several load scenarios with different input data per location.
+
+\section{REQ Calc.Assess.Regional}\label{sec:REQCalcAssessRegional}
+For the assessment of regional dikes, \ProgramName must calculate several assessment scenarios (RRD-scenario). The design of this scenario selection is descriped in \autoref{sec:RRDScenarioSelection}.
+
+\section{REQ Calc.Operational.Sensor}\label{sec:REQOperationalSensor}
+The DAM Engine must be able to use sensor data as input for the generation of water pressures.
+
+\section{REQ Calc.Design.Geometry}\label{sec:REQDesignGeometry}
+The DAM engine must be able to generate new profiles (surfacelines) based on desired Factor of safety. This can be done by:
+\begin{enumerate}
+ \item Raising the crest
+ \item Reducing the gradient of the slope
+ \item Shoulder development
+\end{enumerate}
+
+The design of this geometry adeption is worked out in \autoref{sec:DesignGeometryAdaption}
+
+\section{REQ Calc.Design.NWO}\label{sec:REQDesignNWO}
+This will not be part of the first implementation of DAM Engine and therefor this paragraph has
+not yet been written.
+
+\section{REQ Failuremechanism}\label{sec:REQFailuremechanism}
+
+The \ProgramName provides calculations for following failure mechanisms, so the DAM Clients can provide this functionality.
+\begin{enumerate}
+	\item Macrostability inwards;
+	\item Macrostability outwards;
+	\item Piping;
+\end{enumerate}
+
+\section{REQ Output.format}\label{sec:REQOutputFormat}
+The \ProgramName has a defined format for the data output, so DAM Clients know how to present the output data.
Index: dam engine/trunk/doc/Dam Engine - Functional Design/RRDScenarioSelection.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/RRDScenarioSelection.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/RRDScenarioSelection.tex	(revision 368)
@@ -0,0 +1,58 @@
+\chapter{RRD scenario selection} \label{sec:RRDScenarioSelection}
+
+For the assessment of regional dikes, \ProgramName must calculate several assessment scenarios (RRD-scenario) depending on:
+
+ \begin{itemize}
+	\item the type embankment (peat/other); green block in \autoref{fig:RRDClay} and \autoref{fig:RRDPeat};
+	\item the hydraulic shortcut (yes/no); brown block in \autoref{fig:RRDClay}, \autoref{fig:RRDPeat} and in detail in \autoref{fig:HydraulicShortcut};
+  \item the uplift situation (yes/no); purple blocks in \autoref{fig:RRDClay} and blue blocks in \autoref{fig:RRDPeat}.
+\end{itemize}
+
+This results in a variation of RRD scenarios, summed up in \autoref{tab:RRDScenarios}
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/RRDClay.png}
+  \end{center}
+  \caption{Flowchart of embankments other than peat}
+  \label{fig:RRDClay}
+\end{figure}
+
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/RRDPeat.png}
+  \end{center}
+  \caption{Flowchart of embankments of peat}
+  \label{fig:RRDPeat}
+\end{figure}
+
+\begin{figure}[H]
+  \begin{center}
+    \includegraphics[width=15cm]{pictures/HydraulicShortcut.png}
+  \end{center}
+  \caption{Flowchart of hydraulic shortcut}
+	\label{fig:HydraulicShortcut}
+\end{figure}
+
+
+\begin{table}[H]
+\centering
+\begin{tabular}{|p{18mm}|p{37mm}|p{20mm}|p{20mm}|p{\textwidth-105mm-36pt}|}
+\hline
+\textbf{RRD Scenario} & \textbf{Condition} & \textbf{Hydraulic Shortcut} & \textbf{Uplift} & \textbf{Model} \\ \hline
+1 & Dry	& yes & yes & Uplift \\ \hline
+2 & Dry & no & yes & Uplift \\ \hline
+3 & Wet	& yes & yes & Uplift \\ \hline
+4 & Wet	& no & yes & Bishop \\ \hline
+5 & Dry	& yes & yes & Bishop \\ \hline
+6 & Dry & no & yes & Bishop \\ \hline
+7 & Wet	& yes & yes & Bishop \\ \hline
+8 & Wet	& no & yes & Bishop \\ \hline
+9 & Dry	& yes/no & yes & Horizontal equilibrium \\ \hline
+10 & Wet & yes/no & yes & Piping \\ \hline
+11 & Dry & yes/no & yes & Piping \\ \hline
+\end{tabular}
+\caption{RRD scenarios}
+\label{tab:RRDScenarios}
+\end{table}
\ No newline at end of file
Index: dam engine/trunk/doc/Dam Engine - Functional Design/Literature.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/Literature.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/Literature.tex	(revision 368)
@@ -0,0 +1,3 @@
+\chapter{Literature}  \label{chapterLiterature}
+
+\bibliography{../DAM_references/dam_references}
\ No newline at end of file
Index: dam engine/trunk/doc/Dam Engine - Functional Design/DataCombination.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/DataCombination.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/DataCombination.tex	(revision 368)
@@ -0,0 +1,52 @@
+\chapter{Data combination}\label{sec:DataCombination}
+
+\section{Location}\label{sec:location}
+The locations are described with a name and RD-coordinates; a point element in GIS files.
+Each location is connected to a crosssection; a line element in GIS files.
+
+The combination of data from GIS files is made based on these point and line elements.\\
+If the input data is available in a GIS file with line elements the data is collected at the intersection of the crosssection with the line element, see \autoref{fig:GISLine}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.7\textwidth]{pictures/GISLine.png}
+	\caption{Data is collected from the line element at the intersection}
+	\label{fig:GISLine}
+\end{figure}
+
+If the input data is available in a GIS file with area elements the data is collected at from the area where the location point is situated, see \autoref{fig:GISArea}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.7\textwidth]{pictures/GISArea.png}
+	\caption{Data is collected from the area element where the location point is situated}
+	\label{fig:GISArea}
+\end{figure}
+
+If the inputdata is not available in GIS files, all input data can be linked to each location via a table (csv-format).
+
+\section{Subsoil}
+The subsoil model is made up of the following elements:
+\begin{itemize}
+	\item Soil segments
+	\item Soil profiles
+	\item Soil layers
+	\item Soil materialparameters
+\end{itemize}
+
+A soil segment is located on a map and can contain several soil scenarios. A soil scenario is a combination of a soil profile and its probability.
+Each soil profile is build up from layers (1D- profile) or areas (2D-profile). A layer (or area) has the name of a material. And finally this material is described via soil type and several parameters (such as strength parameters).\\
+All is displayed in \autoref{fig:SubSoilElements}.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/SubSoilElements.png}
+	\caption{The elements of the subsoil model and their properties}
+	\label{fig:SubSoilElements}
+\end{figure}
+
+By linking the location to a soil segment, see \autoref{sec:location}, \ProgramName combines the location to the soil profiles of the soil segment. For piping calculations this is sufficient, for macrostability calculations a 2D-profile is necessary. This is described in \autoref{sec:CombiSurfaceLineSoilProfile}.
+
+\section{Combination of surface line with soil profile}\label{sec:CombiSurfaceLineSoilProfile}
+
+
Index: dam engine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex
===================================================================
diff -u
--- dam engine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex	(revision 0)
+++ dam engine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex	(revision 368)
@@ -0,0 +1,175 @@
+\chapter {Generation pore pressures} \label{sec:GenerationPorePressures}
+
+The \ProgramName can combine the hydraulic data with a subsoil scenario. The result is a schematization of the pore pressures, usable for the failure mechanisms Piping and Macrostability. 
+
+\section{Conditions under which the automatic generation works} \label{sec:Conditions}
+Under certain circumstances, the kernel must be able to produce the pore pressures in the geometry. If the following circumstances are met, the pore pressures will be schematized following the guidelines [Technisch Rapport Waterspanningen bij dijken (2004)] during a high water tide.
+
+The requirements to automatically produce pore pressures are as follows:
+\begin{itemize}
+	\item Minimum of one and maximum of two aquifers;
+	\item The aquifers reach from one boundary to the other (CNS 8);
+	\item The generator only works if the high water table is on the left side.
+\end{itemize}
+
+\section{Procedure for schematisation of the pore pressures}\label{sec:procedure}
+
+The steps for the schematization of the pore pressures are:
+\begin{enumerate}
+	\item The schematisation of the phreatic plane (see \autoref{sec:PhreaPlane}).
+	\item Initial schematisation of piezometric heads  (see \autoref{sec:InitialPiezoHeads}).
+	\item Checking for uplift (see \autoref{sec:CheckUplift}).
+	\item Definitive schematisation of pore pressures  (see \autoref{sec:DefPorePressure}).
+\end{enumerate}
+
+\section{Schematisation of the phreatic plane}\label{sec:PhreaPlane}
+There are currently two different approaches to the schematisation of the position of the phreatic plane: :  
+\begin{enumerate}
+	\item ExpertKnowledgeRRD
+	\item ExpertKnowledgeLinearInDike
+\end{enumerate}
+
+The schematisation method can be selected by the user in the base data (attribute: PLLineCreationMethod). The schematisation method and the associated values can be defined at the location level.
+
+The phreatic plane is referred to as Piezometric Line 1 (PL1). 
+
+\subsection {ExpertKnowledgeRRD}
+The ExpertKnowledgeRDD method sets out the location of the phreatic plane at a maximum of 6 points: A to F. \autoref{fig:PL1_RRD}	lists these points. The level of the phreatic plane is defined by entering a number of vertical offsets relative to the outer water level or the ground level. \Autoref{tab:OffsetRRD} lists for each point how it is determined/recorded. The location of the phreatic plane between the points is determined on the basis of linear interpolation. 
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/PL1_RRD.png}
+	\caption{Schematisation Phreactic line (PL1) Macrostability inward using ExpertKnowledgeRRD}
+	\label{fig:PL1_RRD}
+\end{figure}
+
+\begin{table}[H]
+	\centering
+		\begin{tabular}{ |p{25mm} |p{100mm} |}
+    \hline
+\textbf{Punt}	& \textbf{Elevation determined by}	\\ \hline
+\textit{A} & Intersection of the water level with the outer slope (determined automatically) \\ \hline
+\textit{B} & Outer water level - stated offset \\ \hline
+\textit{C} & Outer water level - stated offset \\ \hline
+\textit{D} & Ground level shoulder base inside - stated offset\\ \hline
+\textit{E} & Ground level toe at polderside- stated offset\\ \hline
+\textit{F} & Intersection of polder level with ditch (is determined automatically). \\ \hline
+		\end{tabular}
+	\caption{Parameters for each schematisation point used to locate the phreatic plane in the ExpertKnowledgeRRD schematisation option}
+	\label{tab:OffsetRRD}
+\end{table}
+
+Lower levels relative to the reference point/plane are stated as positive values. When schematising a rise in the phreatic plane under the crest, the offset are stated as a negative value. 
+
+
+\subsection {ExpertKnowledgeLineairDike}
+Here, the phreatic plane starts where the outer water level (Point A in \autoref{fig:PL1Linear} intersects the outer slope. It then continues in a straight line to point E and then to point F. 
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/PL1_Lineair.png}
+	\caption{Schematisation Phreactic line (PL1) Macrostability inward using ExpertKnowledgeLineair}
+	\label{fig:PL1Linear}
+\end{figure}
+
+
+\subsection{Particular cases} \label{sec:ParticularCases}
+
+The following checks are made:
+
+\paragraph*{Free water}
+The procedure must check that the phreatic plane along the dike does not extend beyond the slope. If this the case, the location is automatically adapted to follow the surface level one centimeter lower. \\
+Free water at the polder side (right side of toe at polderside) is allowed. %Waternet creHowever the polder water level is limited by the surface level outside (right geometry boundary).%
+
+\paragraph*{No ditch, no shoulder}
+If there is no shoulder, point D will be omitted. If there is no ditch, the offset at point E will be continued with a limit of 1 cm below the surface line.
+
+\paragraph*{Phreatic line goes up}
+The procedure must ensure that the location of the phreatic plane is not below the stated polder level at points D and E as a result of the stated offsets. If this is the case, the location of the phreatic plane will automatically be matched to the polder level. In addition, the procedure must ensure that the phreatic plane at points D and E is not higher than at the preceding points. Point C may be higher than point B.
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/PL1PhreaGoesUp.png}
+	\caption{Adaption of phreactic line (PL1) when initial line would go up}
+	\label{fig:L1PhreaGoesUp}
+\end{figure}
+
+%In waternet creator WBI kernel:
+%\subsection{Minimum values below dike crest} \label{sec:MinimumValues}
+%The phreatic levels at points B and C is limited by user-defined minimal values:
+%\begin{itemize}
+	%\item Z$_{\text{min;crest river}}$, the minimum value below the dike top at river;
+	%\item Z$_{\text{min;crest polder}}$, the minimum value below the dike top at polder.
+%\end{itemize}
+
+%The minimum value below point B when point B does not correspond to the dike top at river must be deduced by interpolation or extrapolation between points (X$_{\text{crest river}}$; Z$_{\text{min;crest river}}$) and (X$_{\text{crest polder}}$; Z$_{\text{min;crest polder}}$).
+%
+
+\section {Initial schematisation of piezometric heads}\label{sec:InitialPiezoHeads}
+\ProgramName can manage a maximum of two aquifers. \ProgramName also takes the penetration layer (TAW, 2004) into account. For the time being, this option works only with 1D soil profiles. If the calculations have to be made without a penetration layer, a value of 0 should be entered (attribute: PenetrationLength).
+
+\ProgramName defines the aquifers from bottom to top (in the direction of the surface). A piezometric line (PL3) is assigned to the bottom layer (which is also an aquifer) (\autoref{fig:wsp_1WL}). The pore pressures in the penetration layer are schematised using PL2. PL4 will be allocated to any additional aquifer. \autoref{tab:piezolines} gives an overview of the various piezometric lines and associated schematisation.
+
+If several aquifers are stacked in succession one above the other, \ProgramName will allocate the same PL to all of them, assuming a hydrostatic range for the pore pressures. The separation between the aquifer and cohesive layer is then determined by the top of the highest aquifer in the stack.
+
+For the purposes of the stability calculations, \ProgramName schematises the piezometric heads in the vertical direction using linear interpolation in the soft layers. A hydrostatic range is assumed in the dike body, the soil layers where the phreatic plane is located and the aquifers. 
+
+\begin{table}[H]
+	\centering
+		\begin{tabular}{ |p{25mm} |p{100mm} |}
+    \hline
+\textbf{PL}	& \textbf{Description}	\\ \hline
+\textit{PL1} & Phreatic line. For stability calculations with a stationary phreatic plane. The  schematisation for PL1 is described in \autoref{sec:PhreaPlane}\\ \hline
+\textit{PL2} & The pore pressure at the top of the penetration layer. The PL2 is not affected by the piezometric head in the underlying aquifer and it is constant (in other words, there is no damping) over the entire width of the cross-section. The user enters the value for PL2 (attribute: HeadPL2), as well as the thickness of the penetration layer. DAM 1.0 uses the PL2 only if the thickness of the penetration layer >0 m.\newline
+Note: at present, the use of PL2 is still limited to 1D soil profiles.
+\\ \hline
+\textit{PL3} & Pore pressure in the bottom aquifer. The value can be entered (attribute: HeadPL3). If no value is entered, PL3 is considered to be the same as the outer water level stated in the scenarios (see section 2.6). 
+\newline
+The value for PL3 at the inner toe (\autoref{fig:dempingfactor}) depends on the stated damping factor (attribute: DampingPL3). This damping factor expresses the degree to which PL3 is damped to PL2. Zero means no damping (PL3 is constant). And the value 1 suggests full damping to PL2 (attribute: PL2). If no value has been entered for PL2, the polder water level will be used (attribute: PolderLevel). Beyond the inner toe, the PL3 declines to the polder level at a gradient to be stated (attribute: SlopeDampingPiezometricHeightPolderSide). The PL3 then matches the polder level. A value can be entered for the gradient of this PL slope. The default value is 0. This means there is no slope.  
+ \\ \hline
+\textit{PL4} & Pore pressure in an intermediate aquifer (if present). The schematisation for PL4 is similar to that described for PL3. However, PL3 should be read as PL4.\newline
+Note: Both PL3 and PL4 use the same gradient for the slope of the PL line on the polder side.
+\\ \hline
+		
+	\end{tabular}
+	\caption{Overview and description of piezometric lines}
+	\label{tab:piezolines}
+\end{table}
+
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/wsp_1WL.png}
+	\caption{Schematisatie van waterspanningen in de situatie van \'e\'en watervoerende laag}
+	\label{fig:wsp_1WL}
+\end{figure}
+
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=0.7\textwidth]{pictures/dempingfactor.png}
+	\caption{Gebruik van dempingsfactor (f) en reductie pi\"ezolijn aan de polderzijde (X) voor schematisatie horizontaal stijghoogteverloop}
+	\label{fig:dempingfactor}
+\end{figure}
+
+
+\section {Check for uplift}\label{sec:CheckUplift}
+\ProgramName makes calculations to see whether there is any uplift from the inner toe to the centre of the ditch bed. The formula from the VTV (2006) is used for this purpose, together with the initial schematisation for the piezometric heads (see \autoref{sec:InitialPiezoHeads})\newline
+
+\begin{equation}
+\label{eq_opdrukveiligheid}
+	opdrukveiligheid = \frac{\sigma_g}{\sigma_w}
+\end{equation}
+
+If there is no ditch present, the calculations will extend to the edge of the cross-section. If uplift is calculated,\ProgramName lowers the PL3 or PL4 to a value in which uplift just no longer occurs, in other words to the point at which there is an unstable equilibrium(zie \autoref{fig:redPL})
+
+\begin{figure}[H]
+	\centering
+		\includegraphics[width=1\textwidth]{pictures/redPL.png}
+	\caption{Lowering of piezometric head in the presence of uplift. \ProgramName checks for uplift starting at the inner toe and extending to the edge of the profile and adapts the piezometric head accordingly until an unstable equilibrium is attained.}
+	\label{fig:redPL}
+\end{figure}
+
+\section {Definitive schematisation pore pressures}\label{sec:DefPorePressure}
+The definitive schematisation for the pore pressures is produced on the basis of the initial generation of the pore pressures and the check for uplift. This involves the straight-line interpolation of values in a horizontal direction between the various calculated tipping points in the PL lines.
+