Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceAssessment.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/ReduceSlope.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMMainDataflow.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Release Notes.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/RRDPeat.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataEdit.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataEdit.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataEdit.tex (revision 3756) @@ -0,0 +1,27 @@ +\chapter{Data edit}\label{sec:USDataEdit} + +\section{Navigator}\label{sec:navigatorwindow} +Data in Navigator window is not editable. Only locations are selectable. + +\section{Tables}\label{sec:tableswindow} +In https://repos.deltares.nl/repos/dam/DamOverall/trunk/doc/DAM General/OverviewDataUIAndEngine.xlsx column Editable in UI is given which data should be editable +It is not possible to add locations. + +\section{Cross section}\label{sec:crosssectionwindow} +Data in cross section is not editable. + +\section{Properties}\label{sec:Propertieswindow} +How the data is editable varies from tab: +\begin{itemize} + \item Tab Location\newline + Data is similar editable as locations tab in table window. + \item Tab Location scenarios\newline + Data is editable, but it is not possible to add scenarios. + \item Tab Surface line (NL-Hoogte geometrie)\newline + The column characteristic points is editable via a pull down menu with characteristic points. The pull down menu contains all possible characteristic points. The validation is done directly; so if an user changes something incorrect in the surface line window, validation message appears in Validation window. Validation rules are described in \autoref{sec:ValCharPoints}. +Note: The surface line points can not be edited, so after import it is not possible to let a traffic load point coincide with another characteristic point. Traffic load points can only coincide with a another characteristic point when it is defined in the import files. + \item Tab Calculations\newline + Data is not editable. +\end{itemize} + + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataFormat.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataFormat.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataFormat.tex (revision 3756) @@ -0,0 +1,121 @@ +\chapter{Data format}\label{sec:USDataFormat} + +Validation is done during three phases: import, editing in UI and for calculation. + +\section{Validation during import} + +All required and optional import data is placed in table OverviewDataUIAndEngine.xlsx, tab DAM\_input. + +\ProgramName can import data from csv files and shape files +The sequence of import is + 1. csv files (except scenarios.csv), overwritten by: + 2. shape files, overwritten by: + 3. scenario.csv +If data is not present during import the default value is used, when a default is available. Default values are mentioned in OverviewDataUIAndEngine.xlsx + +Required data +Data can be required when importing and/or required when calculating. +In OverviewDataUIAndEngine.xlsx is described what data is required and when. Example: crosssection and dikering$\_$ are only required when using shapefiles (see column remark).\newline +If data is required for import and is missing or invalid, the exception handling is dependent of the kind of data, see \autoref{table:ExceptionHandlingReqData}. +Messages are given in the log window. + +\begin{table}[H] +\begin{tabular}{|p{40mm}|p{\textwidth-40mm-24pt}|} \hline +\textbf{Parameter} & \textbf{Exception handling} \\ \hline +location$\_$id in location.csv (or via shape) & All locations with missing location$\_$id are not imported and message is given. \\ \hline +location$\_$id in scenarios.csv (or via shape) & All scenarios with missing location$\_$id are not imported and message is given. \\ \hline +surfaceline in location.csv$\_$id & All locations with missing surfaceline$\_$id are not imported and message is given. \\ \hline +Profielnaam in surfacelines.csv$\_$id & All surfacelines with missing surfaceline$\_$id are not imported and message is given. \\ \hline +dikering$\_$id via shape & Project is not imported and message is given. \\ \hline +segment$\_$id in locations.csv or via shape & All locations with missing segment$\_$id are not imported and message is given. \\ \hline +segment$\_$id in segment.csv & All locations using segments with missing segment$\_$id are not imported and message is given. \\ \hline +calculation$\_$type in segments.csv & All locations using segments with missing calculation$\_$type are not imported and message is given. \\ \hline +soilprofile$\_$id in segments.csv & All locations using segments with missing soilprofile$\_$id are not imported and message is given. \\ \hline +top$\_$level in soilprofiles.csv& All locations linked (via segment) to soilprofiles with missing top$\_$level are not imported and message is given. \\ \hline +location$\_$scenario$\_$id & All scenarios with missing location$\_$scenario$\_$id are not imported and message is given. \\ \hline +characteristic points (required) & All locations with missing required characteristic points are not imported and message is given. \\ \hline +crosssection (via shape) & All locations with missing cross section are not imported and message is given. \\ \hline +\end{tabular} +\caption{Exception handling required data during import} +\label{table:ExceptionHandlingReqData} +\end{table} + +In OverviewDataUIAndEngine.xls, tab DAM\_input also the optional data is listed. If these parameters are not present, no error or warning is given. When a default is available, this value is used, otherwise the parameters is NULL. +If the parameter is required for calculation and the value is NULL and the kernel does not provide a default, an error message is given. + +\subsection{Editing characteristic points}\label{sec:ValCharPoints} +When the characteristic points are edited by the user in the UI, they must be validated by rules in following table. Blue text validations are not implemented yet. + +\begin{figure}[H] + \centering + \includegraphics[width=1\textwidth]{pictures/Figure_CharacteristicPointsInMacroStability.png} + \caption{Characteristic points on the surface line} + \label{fig:CharPoints} +\end{figure} + + +\begin{tabular}{|p{35mm}|p{35mm}|p{\textwidth-72pt-105mm}|p{13mm}|p{11mm}|p{11mm}|} \hline +\textbf{Name EN} & \textbf{Name NL} & \textbf{Symbol} & \textbf{Unit} & \textbf{Min value} & \textbf{Max value} \\ \hline +\multirow{2}{35mm}{Surface level outside} & \multirow{2}{35mm}{Maaiveld buitenwaarts} & X$_{C}$ & m & - & - \\ \cline{3-6} + & & Z$_{C}$ & m NAP & - & - \\ \hline +\multirow{2}{35mm}{Dike toe at river} & \multirow{2}{35mm}{Teen Dijk buitenwaarts} & X$_{D}$ & m & $>$X$_{C}$ & $<$X$_{E}$ \\ \cline{3-6} + & & Z$_{D}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{C}$} & $<$Z$_{G}$ \\ \hline +\multirow{2}{35mm}{Shoulder top outside} & \multirow{2}{35mm}{Kruin buitenberm} & X$_{E}$ & m & $>$X$_{D}$ & $<$X$_{F}$ \\ \cline{3-6} + & & Z$_{E}$ & m NAP &\textcolor[rgb]{0,0,1}{ $>$Z$_{D}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{F}$} \\ \hline +\multirow{2}{35mm}{Shoulder base outside} & \multirow{2}{35mm}{Insteek buitenberm} & X$_{F}$ & m & $>$X$_{E}$ & $<$X$_{G}$ \\ \cline{3-6} + & & Z$_{F}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{E}$ }& \textcolor[rgb]{0,0,1}{$<$Z$_{G}$ }\\ \hline +\multirow{2}{35mm}{Dike top at river} & \multirow{2}{35mm}{Kruin buitentalud} & X$_{G}$ & m & $>$X$_{F}$ & $<$X$_{H}$ \\ \cline{3-6} + & & Z$_{G}$ & m NAP & $>$Z$_{D}$ & - \\ \hline +\multirow{2}{35mm}{Traffic load outside} & \multirow{2}{35mm}{Verkeersbelasting buitenwaarts} & X$_{H}$ & m & \textcolor[rgb]{0,0,1}{$>$X$_{C}$ }& \textcolor[rgb]{0,0,1}{$<$X$_{I}$} \\ \cline{3-6} + & & Z$_{H}$ & m NAP &\textcolor[rgb]{0,0,1}{$>$Z$_{G}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{I}$} \\ \hline +\multirow{2}{35mm}{Traffic load inside} & \multirow{2}{35mm}{Verkeersbelasting binnenwaarts} & X$_{I}$ & m & \textcolor[rgb]{0,0,1}{$>$X$_{H}$ }& \textcolor[rgb]{0,0,1}{$<$X$_{S}$} \\ \cline{3-6} + & & Z$_{I}$ & m NAP &\textcolor[rgb]{0,0,1}{$>$Z$_{H}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{J}$} \\ \hline +\multirow{2}{35mm}{Dike top at polder} & \multirow{2}{35mm}{Kruin binnentalud} & X$_{J}$ & m & $>$X$_{I}$ & $<$X$_{K}$ \\ \cline{3-6} + & & Z$_{J}$ & m NAP & $>$Z$_{M}$ & -\\ \hline +\multirow{2}{35mm}{Shoulder base inside} & \multirow{2}{35mm}{Insteek binnenberm} & X$_{K}$ & m & $>$X$_{J}$ & $<$X$_{L}$ \\ \cline{3-6} + & & Z$_{K}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{J}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{L}$} \\ \hline +\multirow{2}{35mm}{Shoulder top inside} & \multirow{2}{35mm}{Kruin binnenberm} & X$_{L}$ & m & $>$X$_{K}$ & $<$X$_{M}$ \\ \cline{3-6} + & & Z$_{L}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{K}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{M}$ }\\ \hline +\multirow{2}{35mm}{Dike toe at polder} & \multirow{2}{35mm}{Teen dijk binnenwaarts} & X$_{M}$ & m & $>$X$_{L}$ & $<$X$_{N}$ \\ \cline{3-6} + & & Z$_{M}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{L}$} & $<$Z$_{J}$ \\ \hline +\multirow{2}{35mm}{Ditch dike side} & \multirow{2}{35mm}{Insteek sloot dijkzijde} & X$_{N}$ & m & $>$X$_{M}$ & $<$X$_{O}$ \\ \cline{3-6} + & & Z$_{N}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{M}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{O}$} \\ \hline +\multirow{2}{35mm}{Bottom ditch dike side} & \multirow{2}{35mm}{Slootbodem dijkzijde} & X$_{O}$ & m & $>$X$_{N}$ & $<$X$_{P}$ \\ \cline{3-6} + & & Z$_{O}$ & m NAP & $>$Z$_{N}$ & $<$Z$_{P}$ \\ \hline +\multirow{2}{35mm}{Bottom ditch polder side} & \multirow{2}{35mm}{Slootbodem polderzijde} & X$_{P}$ & m & $>$X$_{O}$ & $<$X$_{Q}$ \\ \cline{3-6} + & & Z$_{P}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{O}$} &\textcolor[rgb]{0,0,1}{ $<$Z$_{Q}$} \\ \hline +\multirow{2}{35mm}{Ditch polder side} & \multirow{2}{35mm}{Insteek sloot polderzijde} & X$_{Q}$ & m & $>$X$_{P}$ & $<$X$_{R}$ \\ \cline{3-6} + & & Z$_{Q}$ & m NAP & \textcolor[rgb]{0,0,1}{$>$Z$_{P}$} & \textcolor[rgb]{0,0,1}{$<$Z$_{R}$ }\\ \hline +\multirow{2}{35mm}{Surface level inside} & \multirow{2}{35mm}{Maaiveld binnenwaarts} & X$_{R}$ & m & - & - \\ \cline{3-6} + & & Z$_{R}$ & m NAP & - & - \\ \hline +\end{tabular} + +If a required characteristic point is missing, (validation)message must be given: Characteristic point is missing.\newline +Required characteristic points are: +\begin{itemize} + \item Surface level outside + \item Dike toe at river + \item Dike top at river + \item Dike top at polder + \item Dike toe at polder + \item Surface level inside +\end{itemize} + +If a set of characteristic points is not complete, (validation)message must be given: Set Characteristic points is not complete. NL: Set karakteristieke is niet compleet. \newline +Sets of characteristic points (Name and points from table) are: +\begin{itemize} + \item TrafficLoad (H and I in table) NL: Verkeersbelasting + \item ShoulderOutside (E and F in table) NL: Buitenberm + \item ShoulderInside (K and L in table) NL: Binnenberm + \item Ditch (N,O,P and Q in table) NL: Sloot +\end{itemize} + +Note: All sets are optional, but when one of the characteristic points is asigned, the others of the set must also be present. + +\section{Validation during editing} +\ProgramName validates during the import of the data and during editing by user in the User interface. Minimal and maximum values are given in OverviewDataUIAndEngine.xlsx. +The data is also validated by the used kernels when calculations are started. + +\section{Validation for calculation} +\ProgramName validates during the import of the data and during editing by user in the User interface. +The data is also validated by the used kernels when calculations are started. Messages are given in the log window. Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/pictures/DAMComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Manual.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex (revision 3756) @@ -0,0 +1,92 @@ +\chapter{Introduction} +\label{chapterIntroduction} + +\section{Purpose and scope of this document} \label{sec:PurposeAndScope} + +This document contains the functional design for the \ProgramName, a user interface for the DAM Engine. The DAM Engine is designed 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\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} +\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 can import data and combines this data to make geotechnical calculations. After calculations (made by DAM Engine) the \ProgramName shows the results and make analyzation possible. + +\section{User story Open project} +As a geotechnical engineer I want to open existing projects to see what data is used and which calculations are made with what result. + +\section{User story Data format} +As a geotechnical engineer I want to store my data in a predescribed format, so that I can reuse the data. The design of this functionality is described in \autoref{sec:USDataFormat}. + +\section{User story GIS Data combination} +As a geotechnical engineer I want to combine GIS data per location, so that I don't have to do that by hand. The design of this functionality is described in \autoref{sec:DataExtraction} + +\section{User story Soil Data combination} +As a geotechnical engineer I want to combine subsoil with surfaceline per location, so that I don't have to draw 2D geometries. The design of this functionality is described in \autoref{sec:GeometryGeneration} + +\section{User story DAM Live configuration} +As a geotechnical engineer I want to make a DAM Live configuration, so that I can make calculations with DAM engine, using sensors for the input of piezometric lines. The design of this functionality is described in \autoref{sec:DAMLiveConfiguration}. + +\section{User story Data display} +As a geotechnical engineer I want to see the data per location in tables, cross section and map view, so I can check the data before calculation. The design of this functionality is described in \autoref{sec:USDataDisplay}. + +\section{User story Data editing} +As a geotechnical engineer I want to edit the data per location, so I can adept the data before calculation. The design of this functionality is described in \autoref{sec:USDataEdit}. + +\section{User story Calculation settings} +As a geotechnical engineer I want to see and be able to adept the calculations settings, so I can decide what calculations are made. +The design of this functionality is described in \autoref{sec:USCalcSettings}. + +\section{User story Display results} +As a geotechnical engineer I want to see the results of the calculations of the DAM Engine, so I can evaluate the calculations. +%The design of this functionality is described in \autoref{sec:USResultsDisplay}. + +\section{User story Export data} +As a geotechnical engineer I want to export data as tables (CSV-format) and/or shapes, so I can use the data for other purposes. +The design of this functionality is described in \autoref{sec:USDataExport}. + + + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineDataModelMain.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tcp =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tcp (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tcp (revision 3756) @@ -0,0 +1,12 @@ +[FormatInfo] +Type=TeXnicCenterProjectInformation +Version=4 + +[ProjectInfo] +MainFile=DAM UI - Functional Design.tex +UseBibTeX=1 +UseMakeIndex=1 +ActiveProfile=LaTeX ⇨ PDF +ProjectLanguage=en +ProjectDialect=US + Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tex (revision 3756) @@ -0,0 +1,130 @@ +\documentclass[signature]{deltares_report} +\usepackage[titletoc]{appendix} +\usepackage{lipsum} +%----------------------------------------------- + +\begin{document} +\pagestyle{empty} +\cleardoublepage +% + +\newcommand{\ProgramName}{DAM UI} +\newcommand{\ProgramNamePlusSpace}{DAM UI } + +\title{\ProgramName} +\subtitle{Technical Design} +\projectnumber{1210702-000} +\client{Deltares - Geo engineering DKS} +\reference{1210702-000-GEO-0009} +\classification{-} + +\date{Jan. 2017} +\version{0.1} + +\keywords{Dike, safety assessment, design, software, macro stability, piping} + +\references{Refer to \autoref{chapterLiterature}.} + +\summary{This document contains the technical design for \ProgramName, an application that computes the strength of a complete dikering with respect to several failure mechnanisms, such as macro stability and piping.\\ +\\ +\textbf{\footnotesize{Samenvatting}} \\ +Dit document bevat het technisch ontwerp voor \ProgramName, een User Interface applicatie die een gebruiker in staat stelt om voor een dijktraject berekeningen uit te voeren voor verschillende faalmechanismen, waaronder macrostabiliteit en piping.} + +\versioni{0.1} +\datei{Jan 2017} +\authori{Tom The} +\revieweri{John Bokma} +\approvali{Maya Sule} + +\status{draft} +\disclaimer{This is a draft report, intended for discussion purposes only. No part of this report may be relied upon by either principals or third parties.} + +\deltarestitle + + +%------------------------------------------------------------------------------ +\chapter{Introduction} \label{chapterIntroduction} + +\section{Purpose and scope of this document} \label{sec:1.1} + +This document contains the technical design for the standalone program \ProgramName, a software package for the automated calculation of the strength of dikes. DAM was developed by Deltares with and for STOWA for all water authorities. + + +\section{Other system documents} \label{sec:1.2} + +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 +Functional Design \newline \citep{DAMUI_FunctionalDesign} & Description of the requirements and functional design of \ProgramName. \\ \hline +Technical Design (this document) \newline \citep{DAMUI_TechnicalDesign}& Description of the technical design of \ProgramName. \\ \hline +Technical documentation \newline \citep{DAMUI_TechnicalDocumentation} & Description of the arguments and usage of different software components, generated from in-line comment with Doxygen. \\ \hline +Test Plan \newline \citep{DAMUI_TestPlan} & Description of the different regression and acceptation tests, including target values, of \ProgramName. \\ \hline +Test Report \newline \citep{DAMUI_TestReport} & Description of the test results (benchmarks and test scripts),of \ProgramName. \\ \hline +User Manual \newline \citep{DAMUI_Manual} & Description of the different functionalites available in the \textit{User Interface} and background information. \\ \hline +\end{tabular} +\caption{\small \ProgramNamePlusSpace system documents.} +\label{table-SystemDocuments} +\end{table} + + +%------------------------------------------------------------------------------ +\chapter{System Architecture} \label{chapterSystemArchitecture} + +\section{DAM components} \label{sec:DamComponents} + +\ProgramNamePlusSpace is part of the whole DAM system that contains several components. Please see \autoref{fig-DamComponents} for an overview of the components of DAM. In \citep{DAM_ArchitectureOverall} a description of the overall architecture of the DAM system can be found. + +\begin{figure}[H] + \begin{center} + \includegraphics[width=15cm]{pictures/DamComponents.pdf} + \end{center} + + \caption{\small \ProgramNamePlusSpace and its components.} + \label{fig-DamComponents} +\end{figure} + +The arrows illustrate the dependencies of the components. + + + + +%------------------------------------------------------------------------------ +\chapter{Architectural Choices} \label{chapterArchitecturalChoices} + +\lipsum[1-2] + + +%------------------------------------------------------------------------------ +\chapter{Data Model} \label{chapterDataModel} + +\lipsum[1-2] + + +%------------------------------------------------------------------------------ +\chapter{Data Description} \label{chapterDataDescription} + +\lipsum[1-2] + + +%------------------------------------------------------------------------------ +\chapter{Module Description} \label{chapterModuleDescription} + +\lipsum[1-2] + + +%------------------------------------------------------------------------------ +\chapter{Literature} \label{chapterLiterature} + +\bibliography{../DAM_references/dam_references} + +\pagestyle{empty} +\mbox{} + +%------------------------------------------------------------------------------ +\end{document} Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/LargerDikeBase.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DTHAdaptedGeometry.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityDesign.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/wsp_1WL.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/ShoulderDevelop.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceAssessmentRegional.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/MoveDitch.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/OpenProject.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/OpenProject.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/OpenProject.tex (revision 3756) @@ -0,0 +1,14 @@ +\chapter{Open Project}\label{sec:USOpenProject} + +To be able to open a project, the user must be able to build a project, to save it and to open it. + +\section{Building a project}\label{sec:BuildingProject} +The user can define a project by defining different sources, see \autoref{sec:USDataFormat} and \autoref{sec:USDataCombi} + +\section{Saving a project} \label{sec:SavingProject} +The project can be saved at a location defined by the user. + +\section{Opening a project}\label{sec:OpeningProject} +The user must be able to open an excisting project. When calculations were made, also the calculation results must be shown. +When a project is calculated in a previous version of DAM (i.e. DAM 18.1 instead of 19.1), the calculations must not be shown because the calculations can be outdated due to newer versions of used kernels. + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/Figure_CharacteristicPointsInMacroStability.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DeletedGeometryPoints.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/PL1_Lineair.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/dempingfactor.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Release Notes.docx =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf (revision 3756) @@ -0,0 +1,63 @@ +%PDF-1.4 +%���� +6 0 obj +<>stream +x��YMo7���=t�$�_Ǵh�!��� Iv��$Ē���w���r +�R�B� +�7;��y;CR���;땋���ݏ�ݻ�s7(o��������c��{�m:��tF���>u������A-��W8�����vPz�v�y���u����+��v88Y����SI�u|��wQi ��׈"��j�� ���`�J��Rn������ɨ�#%|Of2Xtl< 4~3Ke��o3��t�WiP��}�\Ql �f���7�� +N���1���V]#?�a�&��E����Rm���z�����6�-~6�M8�|�je0��~��W��q�kM��/��Ӻ[�M��zF#���P���2��Wκ�lzC\�Bp=.�u�G��VR\� 4����"�Y`KԌE�cn�>�+�"@�a]� �������d�Xj�Fy�,�;�l{�I�>��41nQT��ҭHh��M�n��!� �n!�2+~9͑����1y���W��4��@�rI� +8)3 +JG �6O��5�6S��TM�s5���I�|\�1�|ͣ����l�m�f�&me�M�f�+��q�䒄\����wTN& �'o>n�j��c�"y�O[��c�vq����\�"i�7��N�FF�M�N�~u�tL�$��u �5.9F�t��+A�U�A��B�![�fY�L��'�Y�e�q�.�>Ӽ��y���ُ�ɛ�ј��M�o�n� r=N�SD�:_>K�䍨�:Wt�<�ο1p�R�c=�D)�dB�h�`�H>�0�S +m>� ���SB5��@�tc(��G n��OI>�a�OY�)7��-,/ǵ�K���s~��f\<�7�� �z3�:���q�A���߬�KU d�q�x��F ��2�@K �'Z���h�!��J (�C��2��€Ђ�Ђ�J e� +-��Aƿ�Nf��Q +�4Ӑ�~��W���vA�Z#����6V�Vd�Q�Z= mlBg��5���6���%�q +m���(c�mh���2�вTCˢL� -[>�ڗ��?bm���d�2�n�]���^���n7�A=13bOO?߉ͯ� -�˷rh���徎��1�$H�3~|���C�r�8���V��z��X�S��m1!�C�3фX۞��n���W�\!�����{㫒�tQ�g��&9غշ��?��=L�|6՝y^�f�~�Y��oh�|�Y�Txʦv�����Tr6[%Giu�}�,/H�2� e���$�Z�h�F�a��"LQ��0� +���+?΄� 񐳆�\a�{��.�T�a\�J��#�uՠ(�=�'��#�0F�}eBE�<͉�r� 3N�9'b�D�H!OR�8���V?'���O�ǡ�����|� ����O7�q�q2���'=���غ�ckg[#��#56����&g���O��>�\9!�.��� Ю̳&Ԭ �)c�5� +endstream +endobj +8 0 obj +<>/Font<>>>/Parent 7 0 R/MediaBox[0 0 410 620]>> +endobj +3 0 obj +<> +endobj +1 0 obj +<> +endobj +2 0 obj +<> +endobj +5 0 obj +<> +endobj +4 0 obj +<> +endobj +7 0 obj +<> +endobj +9 0 obj +<> +endobj +10 0 obj +<> +endobj +xref +0 11 +0000000000 65535 f +0000001833 00000 n +0000001863 00000 n +0000001745 00000 n +0000001913 00000 n +0000001888 00000 n +0000000015 00000 n +0000001938 00000 n +0000001534 00000 n +0000001989 00000 n +0000002034 00000 n +trailer +<]/Root 9 0 R/Size 11>> +%iText-5.4.1 +startxref +2188 +%%EOF Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/CalcSettings.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/CalcSettings.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/CalcSettings.tex (revision 3756) @@ -0,0 +1,14 @@ +\chapter{Calculation settings}\label{sec:USCalcSettings} +\section{Macrostability}\label{sec:Macrostability} +\section{Piping}\label{sec:piping} + +\subsection{Models} +In DAM the following piping models can be used: +\begin{itemize} + \item Bligh + \item Sellmeijer VNK + \item Sellmeijer 4 forces + \item Sellmeijer revised (WBI) +\end{itemize} + +For the description of the models, see https://publicwiki.deltares.nl/display/DAM/Piping Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/Literature.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/Literature.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/Literature.tex (revision 3756) @@ -0,0 +1,3 @@ +\chapter{Literature} \label{chapterLiterature} + +\bibliography{../DAM_references/dam_references} \ No newline at end of file Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityOperational.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceDesign.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/SubSoilElements.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineDataModelLocation.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/Differences with previous release.txt =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/Differences with previous release.txt (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/Differences with previous release.txt (revision 3756) @@ -0,0 +1,60 @@ +MWDAM-1057/1056: +For design results, the actual values for all kind of Z-values which are based on the redesigned surface line +are corrrected in the new UI. + +MWDAM-1057/1056/1155 +For design results, the profilename and the profile probability are now always filled. + +MWDAM-1057/1056 +When performing a calculation, selected but not relevant calculations are now given back in the calcultion log +as not relevant to inform the user. An example of this is when a location is selected with both piping as well +as stability profiles but only a stability calculation is performed. The, for each piping profile a message is +logged to say that this is not relevant. Also, when calculations fail the preparation stage of the calculation +this is logged to inform the user. + +MWDAM-1057 +The combination of outwards stability and zone areas is no longer allowed. + +MWDAM-1161 +In Release, when for model BishopUpliftVan an UpliftVan calculation failed for one the location-profile combinations, all the combinations for this location were not calculated with Bishop anymore. In new version all combinations are calculated. When one the calculations fails, the overall result for this combination is the failed one. + +MWDAM-1034 +The displayed uplift factor for Piping (Bligh, Sellmeijer4Forces and SellmeijerVNK) was not correct. The calculation was made correctly. + +MWDAM-1034 +The PL3/PL4 values in Piping results in Dam 15.1 were corrected for uplift. This should only be done for stability calculations. + +MWDAM-1180 +The parameter UseNewMinDistanceDikeToeStartDitch is not correctly applied. While testing you have to work around this. To correctly compare with Dam 15.1.2.24738, the parameter should always be set to True (because that is the current behaviour). + +MWDAM-1219 +As must be clear from the issue itself, the actual problem is not with the determination of the pl-line 4 but with the determination of the correct scenario (i.e. Hydraulic Shortcut versus No Hydraulic Shortcut). This was due that in the original dam a mistake was made in the determination of the Location With Lowest UpliftFactor. In that old version, it was assumed that eacht surface line (in RD) is given from left to right but never bothered to check this. So, for surface lines running from right to left (as is the case here) this produced a wrong result. In the new (engine) version this mistake has been corrected by the fact that the engine always uses localised surface lines which always run from left to right. So the engine results are the correct results. + +MWDAM-1223 +When design was made for piping calculations in combination with DTH adaption the Sf piping was set to '1' if crest was adapted to DTH. Now real safety factor is calculated. + +MWDAM-1225 +Message The surfaceline points are not ascending (x-values) for same project no message in DAM 15.1 +Surfaceline validator in DAM 15.1 was not correct and accepted vertical lines in surfacelines. Vertical lines has to be avoided in D-Geo Stability due to possible failing calculations. + +MWDAM-1227 +As with MWDAM-1219 the real problem is the correct determination of the Location With Lowest UpliftFactor. Old DAM uses (wrongly) global surface line whereas the engine uses the correct localised surface line. The effect here is a different value for xCoordinateLastUpliftPoint which is passed on to the DGSMStabDam.dll which determines the grid. + +MWDAM-1237 +DAM 15.1 always calculated with Psi=Phi since Psi wsa no input in D-Geo Stability 15. Later versions of D-Geo Stability (also 18.1) consider Psi as input. Also DAM 18.1 always calculates with Psi=Phi. Note: When *.sti files are used with a different value for Psi are 'reset' to psi=phi. + +MWDAM-1238 +Piping design calculation with geometry adaption gives wrong safety factor in result in release 15.1. +This issue has been solved, so the safety factors in design calculation with geometry adaption will be different than in the 15.1 release version. The new answers are the correct answers. + +MWDAM-1261-DAM Design: Undo/Redo does not work properly; same bug but different effect in 15.1 to 18.1 + +MWDAM-1272 DAM 15.1 assigned PL4 to a layer which was intercepted by the surface line. + +MWDAM-1273 +See MWDAM-1219 above as this has the same cause for the problem: In Old DAM, the determination of the regional scenarios is done based on een suface line given in global RD coordinates. This while all plline data is local. So trying to find the proper phreatic level for any given point of the surface line ALWAYS results in the last level of line PL1 as the point of the surfacel line is way betong the PL1 line. The new version has all data in local coordinates so the proper phreatic level is found, resulting in a better uplift factor and therefor other results (amongst which the proper status for hydraulic shortcut). + +MWDAM-1274 +In v15.1, in the determination of regional assessment scenarios, extending the 1D geometry to the surface level (when needed) was done by stretching the top layer. This should have been done by adding a layer on top of the original top layer with DikeEmbankmentMaterial as material. In v18, this correct way is implemented. Note that the difference in results may be neglectable is most cases. + + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataDispay.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataDispay.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataDispay.tex (revision 3756) @@ -0,0 +1,43 @@ +\chapter{Data display}\label{sec:USDataDisplay} + +\section{Navigator}\label{sec:navigatorwindow} +Give an overview of all imported locations. +Make the locations selectable for calculation + +\section{Tables}\label{sec:tableswindow} +Show per row the imported data per location, see https://repos.deltares.nl/repos/dam/DamOverall/trunk/doc/DAM General/OverviewDataUIAndEngine.xlsx for the data to be shown. +If column csv contains 'locations', item must be shown in the table. + +\section{Cross section}\label{sec:crosssectionwindow} +Show the cross section of the selected location (selected in either the navigator window or the table window). Make it possible to scroll throw the different soilprofiles. + +Show the soilprofiles with material colors. + +Show the characteristic points on the surfaceline. + +\section{Properties}\label{sec:Propertieswindow} +Show location data in a tab, named Location (NL: Locatie) +Show location scenarios in a tab, named Location scenarios (NL: Locatie scenario\'s) +Show surfacelines points in a tab, named Surfaceline (NL: Hoogtegeometrie). +This tab contains a table named Points (NL: Punten) with columns: +\begin{itemize} + \item Characteristic point (NL: Karakteristiek punt) + editable via pull down menu with characteristic points, see OverDataUIAndEngine.xls + \item [m] + \item [m NAP] +\end{itemize} + +Example: see D-Soil Model. + + +\section{Map}\label{sec:map} +Show the locations as a dot on a map with Open street map as background. +Background can also be empty. +Display imported shapefiles when selected by user. + +\section{General}\label{sec:DisplayGeneral} +When selecting a location in navigation, table or map window, the other windows must 'follow': selecting same location. +When selecting a soilprofile in the calculations table or in the cross section window, the other window must 'follow': selecting same soil profile. + +Show popup of source of data if the mouse is above textedit or cell of table. +The text of the popup is placed in https://repos.deltares.nl/repos/dam/DamOverall/trunk/doc/DAM General/OverviewDataUIAndEngine.xlsx. Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/RRDClay.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/SourcePictures.pptx =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/OuterShoulderAdeptedGeometry.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DSoilmodel.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DSoilmodel.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DSoilmodel.tex (revision 3756) @@ -0,0 +1,31 @@ +\chapter{Use of D-Soilmodel}\label{sec:DSoilmodel} + +D-Soil Model is used for the import of subsoil and geometry. +D-Soil Model and DAM 18.1 use the similar source files, see table +\begin{table}[] +\begin{tabular}{lll} +DAM 18.1 & D-Soil Model & DAM 19.1 \\ +soilmaterials.mdb & soilmaterials.mdb & \multirow{6}{*}{projectnaam.soil} \\ +soilprofiles.csv & soilprofiles.csv & \\ +segments.csv & segments.csv & \\ +segments.shp & segments.shp & \\ +surfacelines.csv & surfacelines.csv & \\ +characteristicpoints.csv & characteristicpoints.csv & \\ +locations.csv & & locations.csv \\ +scenarios.csv & & scenarios.csv \\ +shp-bestanden & & shp-bestanden +\end{tabular} +\label{Source files for D-Soil Model and DAM} +\end{table} + +To way to use the projectname.soil instead of the separate source files is described in this chapter, devided per source file. + +\section{Soilmaterials} + +\section{Soilprofiles-1D} + +\section{Soilprofiles-2D} + +\section{Segments} + +\section{Geometry} Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Test report/DAM UI Test Report.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex (revision 3756) @@ -0,0 +1,70 @@ +\documentclass[signature]{deltares_report} +\usepackage[titletoc]{appendix} +\usepackage{lipsum} +\usepackage{multirow} +%----------------------------------------------- + +\begin{document} +\pagestyle{empty} +\cleardoublepage +% + +\newcommand{\ProgramName}{DAM UI\xspace} +\newcommand{\kernel}{failuremechanism kernel\xspace} + +\title{\ProgramName} +\subtitle{Functional Design} +\projectnumber{1210702-000} +\client{Deltares - Geo engineering DKS} +\reference{1210702-000-GEO-0003} +\classification{-} + +\date{Sep. 2019} +\version{0.1} + +\keywords{Dike, safety assessment, design, software, macro stability, piping} + +\references{Refer to \autoref{chapterLiterature}.} + +\summary{This document contains the functional design for \ProgramName, a software module that computes the strength of a complete dikering with respect to several failure mechanisms, such as macro stability and piping.\\ +\\ +\textbf{\footnotesize{Samenvatting}} \\ +Dit document bevat het functioneel ontwerp voor \ProgramName, een software module die een gebruiker in staat stelt om voor een dijktraject berekeningen uit te voeren voor verschillende faalmechanismen, waaronder macrostabiliteit en piping.} + +\versioni{0.1} +\datei{sep 2019} +\authori{Irene van der Zwan} +\revieweri{Kin Sun Lam \newline Andr\'e Grijze} +\approvali{Leo voogt} + +\status{draft} +\disclaimer{This is a draft report, intended for discussion purposes only. No part of this report may be relied upon by either principals or third parties.} + +\deltarestitle + +\include{DAM_UI_FO} +\include{OpenProject} +\include{DataFormat} +\include{DataCombination} +\include{DAMLiveConfiguration} +\include{DataDisplay} +\include{DataEdit} +\include{CalcSettings} +\include{DataExport} +\include{DSoilmodel} +\include{Literature} + + +%------------------------------------------------------------------------------ +\appendix\chapter*{Appendix} \addcontentsline{toc}{chapter}{Appendix} +\include{AppendixA} + + + +%----------------------------------------------------------------------------- + +\pagestyle{empty} +\mbox{} + +%------------------------------------------------------------------------------ +\end{document} \ No newline at end of file Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tcp =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tcp (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM - Technical Design/DAM - Technical Design.tcp (revision 3756) @@ -0,0 +1,12 @@ +[FormatInfo] +Type=TeXnicCenterProjectInformation +Version=4 + +[ProjectInfo] +MainFile=BM GrasBuitentalud - Test Plan.tex +UseBibTeX=1 +UseMakeIndex=1 +ActiveProfile=LaTeX ⇨ PDF +ProjectLanguage=en +ProjectDialect=US + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/Picture1.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/PL1PhreaGoesUp.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/PL1_RRD.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/GISLine.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/redPL.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf (revision 3756) @@ -0,0 +1,71 @@ +%PDF-1.4 +%���� +6 0 obj +<>stream +x��ZK�$� +�ׯ�19���:Ɓm��� �C�à�ww��nx�N��#��JZw�{��tv0��E�(}�$V�:}u;��bu{?}};�0�:i��V��W�e�~�����n�i�MF�6Y�])��d��~���Zݗ���˪�P7Fk�Y�h!�2"Ԯ��\��oo�z�\��v��b��+p���(�v\�`���2��)�(c,=7j3���J�����`u�j���D�zY�ƩZ +  +�ƨ�L���c��k1$7ЏS�|C�Տ߾:�np�,����+~��7e��O��5-��Zz�I�"�n7�_�~�l�/w��_o�Gū���I��T{�Z�Lm�ww��M{c��eA�۞���`�y$��i8kUO!7�,Zy3Y��*��.�*�":*���F������b�~wml�|�4��|�?s3۰*���@W�����,iZBV��P>i���b{��,�- -� +,wƕ2��^,�qԛ������S +�y��}Ԁ���7��c��ހH7�_�L��4���YU>� f����cXgo�W��� +��Bs���t:�p��� ��7�/X�_U\��b�ch�fgC�=jqԽ�z��,�a�X\/l�i��`��?\AĩԮ�m2�q���mDr$7�����Q %�ƈ����s &*�� �{�9��>/Font<>>>/Parent 7 0 R/MediaBox[0 0 550 830]>> +endobj +3 0 obj +<> +endobj +4 0 obj +<> +endobj +2 0 obj +<> +endobj +5 0 obj +<> +endobj +1 0 obj +<> +endobj +7 0 obj +<> +endobj +9 0 obj +<> +endobj +10 0 obj +<> +endobj +xref +0 11 +0000000000 65535 f +0000002527 00000 n +0000002477 00000 n +0000002364 00000 n +0000002452 00000 n +0000002502 00000 n +0000000015 00000 n +0000002557 00000 n +0000002153 00000 n +0000002608 00000 n +0000002653 00000 n +trailer +<]/Root 9 0 R/Size 11>> +%iText-5.4.1 +startxref +2807 +%%EOF Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/GISArea.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataExport.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataExport.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataExport.tex (revision 3756) @@ -0,0 +1,12 @@ +\chapter{Data export}\label{sec:USDataExport} + +The user must be able to export the following data from \ProgramName: + +Surfacelines with characteristic points +The surface lines and the corresponding characteristic points must be exported in the same format as the import files. Its is a complete set of all locations of the project. + +Scenarios file + +Calculation file + +Calculation image Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataCombination.tex =================================================================== diff -u --- DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataCombination.tex (revision 0) +++ DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/DataCombination.tex (revision 3756) @@ -0,0 +1,88 @@ +\chapter{Data combination}\label{sec:USDataCombi} + +DAM can generate input for the kernels by combining the data from the source files. This is done by linking via the location id and via GIS-files (see \autoref{sec:DataExtraction}). + +\section{Id/Name}\label{sec:IdNameValidation} +The data is combined by matching Id's (Names) between the several data sources. Not all characters can be used when defining Id's. The following characters are valid: \newline +"ABCDEFGHIJKLMNOPQRSTUVWXYZ" \newline +"abcdefghijklmnopqrstuvwxyz" \newline +"01234567879" \newline +"!\#\textdollar \% \&()*+,-.\/" \newline +":;<=>?@" \newline +"[\textbackslash ]\textasciicircum \_\textasciigrave " \newline +"\{|\}\textasciitilde " \newline +" " (space)\newline +A validation of the Id's must be done when performing the data combination. + +\section{Data extraction}\label{sec:DataExtraction} + +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}. + +When a parameter is available in a line shape, \ProgramName will check, during import of data, if the cross section of a location intersects the shapefile of the parameter. When so, this parameter is connected to this location. +If a cross section intersects more than one line of the shapefile, no parameters are connected at all and a message is given that this location is not imported. + +\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{Geometry Generation}\label{sec:GeometryGeneration} + +The \ProgramName can combine a surface line with a subsoil scenario. The result is a geometry, usable for the failure mechanism Macrostability. + +\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 via the locations.csv column segment\textunderscore id, \ProgramName combines the location to all soil profiles of the soil segment. +The use of D-Soil Model for this purpose is decribed in \autoref{sec:DSoilmodel}. +The procedure for combining a surfaceline with a soil profile is described in \autoref{sec:CombiSurfaceLineSoilProfile}. + +\section{Combination of surface line with soil profile}\label{sec:CombiSurfaceLineSoilProfile} + +\subsection{Combination of surface line with a 1D soilprofile}\label{sec:CombiSurfaceLine1DSoilProfile} +A 1D soil profile is a summation of layers with layer boundaries (Z-values) and materialnames. Combination with a surfaceline is uncomplicated if all the Z-values of the surface line are within the boundaries of the soil profile. +If not, the user can define a filling material. + +\subsection{Transfer of 1D soilprofile}\label{sec:Transfer1D} +The user can vertically transfer the 1D profiles by defining a characteristic point as a reference level. This means that the Z-value of the characteristic point is the top of all 1D-soilprofiles of that location. This reference level is given per project. So if the surfacelevelinside is the reference, for each location the 1D-soilprofiles will start at the Z-value of the surfacelevelinside of that location. On top of the 1D soilprofile the filling material is used. + +\subsection{Combination of surface line with a 2D soilprofile}\label{sec:CombiSurfaceLine2DSoilProfile} +A 2D profile already has a topboundary with different Z-values. Combination with a surface line is more complicated since this top boundary and surfacel may differ in X and/or Z-values. +The origin of the surfaceline can differ from the origin of the top boundary of the soil profile. The user can define this difference. The surfaceline is determing the final length of the combinated 2D-profile. +If the surface line xxx soil profile length: subsoil at the right side will be deleted +If the surface line xxx soil profile length: subsoil at the right side will be generated with Z-values at boundary. + Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/HydraulicShortcut.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceOperational.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/19.3.2/doc/DAM - Manual.docx =================================================================== diff -u Binary files differ