Index: DamEngine/trunk/doc/Dam Engine - Functional Design/UseStabKernel.tex =================================================================== diff -u -r1214 -r1249 --- DamEngine/trunk/doc/Dam Engine - Functional Design/UseStabKernel.tex (.../UseStabKernel.tex) (revision 1214) +++ DamEngine/trunk/doc/Dam Engine - Functional Design/UseStabKernel.tex (.../UseStabKernel.tex) (revision 1249) @@ -4,7 +4,7 @@ For stabilily calculation the DAM engine uses the kernel used by D-Geo Stability 15.1 This use is restricted to the options described in this chapter. -\section{Model}\label{Model} +\section{REQ.Model}\label{REQModel} The DAM Engine must be able to make calculations with following models: \begin{itemize} \item Bishop Index: DamEngine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex =================================================================== diff -u -r877 -r1249 --- DamEngine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex (.../REQDataGenerationWater.tex) (revision 877) +++ DamEngine/trunk/doc/Dam Engine - Functional Design/REQDataGenerationWater.tex (.../REQDataGenerationWater.tex) (revision 1249) @@ -1,11 +1,11 @@ -\chapter {Generation pore pressures} \label{sec:GenerationPorePressures} +\chapter {REQ Generation.PorePressures} \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: +The conditions 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); @@ -153,7 +153,9 @@ \end{figure} -\section {Check for uplift}\label{sec:CheckUplift} +\section {Correction for uplift}\label{sec:CheckUplift} +The check for uplift is described in \autoref{sec:UpliftCalculation} + \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} @@ -170,6 +172,7 @@ \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. Index: DamEngine/trunk/doc/Dam Engine - Functional Design/UpliftCalculations.tex =================================================================== diff -u -r1213 -r1249 --- DamEngine/trunk/doc/Dam Engine - Functional Design/UpliftCalculations.tex (.../UpliftCalculations.tex) (revision 1213) +++ DamEngine/trunk/doc/Dam Engine - Functional Design/UpliftCalculations.tex (.../UpliftCalculations.tex) (revision 1249) @@ -1,4 +1,19 @@ -\chapter{Uplift calculations} -\label{sec:UpliftCalculations} +\chapter{Uplift calculation} +\label{sec:UpliftCalculation} +The check needs to be done as follows: +Check every point from DikeToeAtPolder to SurfaceLevelInside (from left to right) for uplift. +If uplift occurs, then correct PL3/PL4 value, so uplift does not occur. +All points in PL3 from this point to DikeToeAtRiver should be removed. +The PL3 continues from this point on with the specified slopegradient until polderlevel. +Make sure PL3 is always descending from left to right. + +A better implementation (not implemented yet) would be: +Correct plline 3 or 4 for uplift according to +TRW (Technisch Rapport Waterspanningen bij dijken) par. b1.3.4 "Stijghoogte in het eerste watervoerende pakket" + - Adjust PL3/4 for all surface points from end of profile to toe of dike, so no uplift will occur in that surface point + - From the point, closest to the dike, (firstAdjustedPLPoint) where this correction has been made the following has to be done +/ * PL3/4 will continue horizontally from firstAdjustedPLPoint over a distance L = 2* d (d is height all layers above the aquifer) + * The the PL3/4 will go down in a slope of 1:50 to the PolderLevel + Index: DamEngine/trunk/doc/Dam Engine - Functional Design/FO.tex =================================================================== diff -u -r1214 -r1249 --- DamEngine/trunk/doc/Dam Engine - Functional Design/FO.tex (.../FO.tex) (revision 1214) +++ DamEngine/trunk/doc/Dam Engine - Functional Design/FO.tex (.../FO.tex) (revision 1249) @@ -18,6 +18,8 @@ \item NWO module("Niet Waterkerende Objecten") \item WBI failure mechanisms (Piping, Macrostability) \end{itemize} + + \section{Other system documents} \label{sec:SystemDocuments} @@ -56,21 +58,35 @@ \chapter{Functional requirements} -Main purpose of the \ProgramName is to get data from DAM Clients, uses this data as calculation input and make serially calculations with one ore more kernels and generates output. Therefor this chapter is diveded in requirements concerning data, calculation and output. +Main purpose of the \ProgramName is to get data from DAM Clients, uses this data as calculation input and make serially calculations with one ore more kernels and generates output. This can be broken down to the next use cases:\newline +Use case Design - UC Design\newline +As a user I want to adapt the geometry until given safety for stability or piping is met. + +Use case Assessment - UC Assessment\newline +As a user I want to perform the assessment of regional dikes according to Leidraad Toetsen Regionale keringen. + +Use case Operational sensors - UC Operational.sensors\newline +As a user I want to make stability and/or piping calculations with the input from operational sensors. + +Since most requirements are needed for multiple use cases, the requirements are classified per theme, not per Use Case. The themes are: data, calculation and output. +The requirements per Use case are given in next table. + + \section{Data} \subsection{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. \subsection{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. -The required data is described in xsd-files in https://repos.deltares.nl/repos/dam/DamEngine/trunk/xsd. -An overview of the required data for the engine in relation to DAM UI data is described in https://repos.deltares.nl/repos/dam/DamOverall/trunk/doc/DAM General/OverviewDataUIAndEngine.xlsx. In this Functional design is referred to parameters mentioned in this overview by giving the \textcolor[rgb]{0.65,0.16,0}{\textsl{name}}. +The required data is described in xsd-files in https://repos.deltares.nl/ repos/ dam/ DamEngine/ trunk/ xsd. +An overview of the required data for the engine in relation to DAM UI data is described in https://repos.deltares.nl/ repos/ dam/ DamOverall/ trunk/ doc/ DAM General/ OverviewDataUIAndEngine.xlsx. In this Functional design is referred to parameters mentioned in this overview by giving the \textcolor[rgb]{0.65,0.16,0}{\textsl{name}}. -\section{Calculation} +\section{Calculation}\label{sec:Calculation} -The \ProgramName provides calculations for following calculation kernels, so the DAM Clients can provide this functionality. +\subsection{Kernels}\label{sec:Kernels} +The \ProgramName provides calculations with the following stability and piping kernels: \begin{enumerate} \item Stability; kernel used by D-Geo Stability 15.1 \item Stability; kernel used by D-Geo Stability 18.1 @@ -82,50 +98,23 @@ Italic printed functionalities are not implemented in DAM yet. -The \ProgramName provides three types of major calculations: -\begin{enumerate}[A.] - \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 (type A) - \item Assessment regional dikes (type A) - \item Design of geometry, given required safety factor: Design-Geometry (type B) - \item Design of geometry, given dimensions of excavation and required safety factor: Design-Excavation (type B) - \item Operational calculation from sensor data (type C) -\end{itemize} -Next to the major calculations the DAM engine must provide the following supporting calculations: -\begin{itemize} - \item generate waternet - \item generate excavations in geometries -\end{itemize} - -\subsection{REQ Calc.Stab}\label{sec:REQ CalcStab} +\subsubsection{REQ Calc.Kernel15}\label{sec:REQ CalcKernel15} The DAM engine can make stability calculations with the kernel of D-Geostability 15.1. The options used by the DAM engine are described in \autoref{sec:UseStabKernel}. -\subsection{REQ Calc.Uplift}\label{sec:REQ CalcUplift} -The DAM engine can make uplift calculations, so LiftVan calculations are only made when uplift is an issue. -The design of the uplift calculations is described in \autoref{sec:CalcUplift}. +\subsubsection{REQ Calc.Kernel18}\label{sec:REQ CalcKernel18} +The DAM engine can make stability calculations with the kernel of D-Geostability 18.1. +The options used by the DAM engine are equal to the use of the kernel of D-Geostability 15.1 and are described in \autoref{sec:UseStabKernel}. -\subsection{REQ Calc.Piping}\label{sec:REQ CalcPiping} +\subsubsection{REQ Calc.Piping}\label{sec:REQ CalcPiping} The DAM engine can make piping calculations with the DAM-piping kernel. The functional design of the DAM piping kernel is described in \autoref{sec:FODAMPipingKernel}. -\subsection{REQ Calc.Assess.General}\label{sec:REQCalcAssessGeneral} -The DAM engine provides a factor of safety. This may be one calculation or several calculations in batch. More than one calculation becomes available when using several locations and/or several subsoilcenarios. - \subsection{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}. -\subsection{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. - \subsection{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: +The DAM engine must be able to generate new profiles (surfacelines) based on a desired Dike table heigth (DTH) and/or Factor of safety. This can be done by: \begin{enumerate} \item Raising the crest \item Reducing the gradient of the slope @@ -134,13 +123,31 @@ The design of this geometry adeption is described in \autoref{sec:DesignGeometryAdaption} +\subsection{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. + \subsection{REQ Calc.Design.Excavation}\label{sec:REQDesignExcavation} This will not be part of the implementation of DAM Engine and therefor this paragraph has not yet been written. -\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{Output} +\label{sec:Output} - -\section{REQ Output.format}\label{sec:REQOutputFormat} +\subsection{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. + + +%The \ProgramName provides three types of major calculations: +%\begin{enumerate}[A.] + %\item One-fold calculation: the input goes 'through' the kernel(s) and generates one main calculation answer (assessment and scenario); + %\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 regional dikes (type A); stability and piping. + %\item Design of geometry, given required safety factor: Design-Geometry (type B); stability or piping. + %\item Design of geometry, given dimensions of excavation and required safety factor: Design-Excavation (type B) \textit{Not implemented yet.}; stability or piping. + %\item Operational calculation from sensor data (type C); stability or piping. +%\end{itemize} \ No newline at end of file Index: DamEngine/trunk/doc/Dam Engine - Functional Design/DAM Engine - Functional Design.pdf =================================================================== diff -u -r1214 -r1249 Binary files differ