Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineDataModelMain.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/GISArea.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM_UI_FO.tex (revision 1763) @@ -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 calculation input for the DAM Engine. After calculations made by DAM Engine the \ProgramName can show the results and make analyzation possible. + +\section{REQ Import.Project}\label{sec:REQImportProject} +The \ProgramName can import an excisting project. + +\section{REQ Data.Format}\label{sec:REQDataFormat} +The \ProgramName has a defined format for the data input, so DAM users 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 users know which input data to provide. + +\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 Calc.Settings}\label{sec:REQCalcSettings} +The \ProgramName ables the user to change calculations settings. + +\section{REQ Display.result}\label{sec:REQDisplayResults} +The \ProgramName can display the results of the calculations of the DAM Engine as: +\begin{itemize} + \item factor of safety (macrostability and piping) + \item slip plane as picture (macrostability) + \item new geometry (design mode) + \item colored location on map (asssessment mode) +\end{itemize} + +\section{REQ Link.Standalone}\label{sec:REQLinkStandalone} +The \ProgramName can open a single calculation in a stand alone version of an UI of the used kernel. + +\section{REQ Export.data}\label{sec:REQExportData} +The \ProgramName can export data as tables (CSV-format) and/or shapes. + +\section{REQ Save.Project}\label{sec:REQSaveProject} +The \ProgramName can save a project. Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/Literature.tex =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/Literature.tex (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/Literature.tex (revision 1763) @@ -0,0 +1,3 @@ +\chapter{Literature} \label{chapterLiterature} + +\bibliography{../DAM_references/dam_references} \ No newline at end of file Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/HydraulicShortcut.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/ReduceSlope.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceOperational.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceAssessment.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/redPL.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/dempingfactor.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/RRDClay.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/PL1_Lineair.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tex =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tex (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tex (revision 1763) @@ -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/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessment.pdf (revision 1763) @@ -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/18.1.2/doc/DAM UI - Functional Design/pictures/OuterShoulderAdeptedGeometry.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DeletedGeometryPoints.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DTHAdaptedGeometry.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMMainDataflow.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/SourcePictures.pptx =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/RRDPeat.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/Differences with previous release.txt =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/Differences with previous release.txt (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/Differences with previous release.txt (revision 1763) @@ -0,0 +1,57 @@ +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 uplift factor for Piping (Bligh, Sellmeijer4Forces and SellmeijerVNK) is different because it was the WTI uplift factor in Dam 15.1.2.24738 (this was noticed while solving issue MWDAM-1034). + +MWDAM-1034 +The adjusted PL3/PL4 values in Piping results in Dam 15.1.2.24738 are not 0.0, but those are the values for stability; for piping no adjustment has to be made (this was noticed while solving issue MWDAM-1034). + +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-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. + +MWDAM-1272 +In v15.1 the in between aquifer layer is detected by searching from above to the first found aquifer layer. This is not completely correct. It should be the first aquifer layer that is not on top (so covered by an aquitard layer). This has been corrected in v18.1 . Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceAssessmentRegional.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/MoveDitch.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/ShoulderDevelop.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/wsp_1WL.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/SubSoilElements.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Release Notes.docx =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineSequenceDesign.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DAM UI - Functional Design.tex (revision 1763) @@ -0,0 +1,60 @@ +\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{Jul. 2017} +\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{Jan 2018} +\authori{Irene van der Zwan} +\revieweri{Kin Sun Lam \newline Andr\'e Grijze} +\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 + +\include{DAM_UI_FO} +\include{Literature} + +%------------------------------------------------------------------------------ +\appendix\chapter*{Appendix} \addcontentsline{toc}{chapter}{Appendix} +\include{DataCombination} + + + +%----------------------------------------------------------------------------- + +\pagestyle{empty} +\mbox{} + +%------------------------------------------------------------------------------ +\end{document} \ No newline at end of file Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityOperational.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tcp =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tcp (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/DAM - Technical Design.tcp (revision 1763) @@ -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/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityDesign.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineActivityAssessmentRegional.pdf (revision 1763) @@ -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/18.1.2/doc/DAM UI - Functional Design/pictures/PL1PhreaGoesUp.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/Picture1.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/LargerDikeBase.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/PL1_RRD.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DataCombination.tex =================================================================== diff -u --- DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DataCombination.tex (revision 0) +++ DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/DataCombination.tex (revision 1763) @@ -0,0 +1,60 @@ +\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 all soil profiles of the soil segment. 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{Combination of surface line with a 2D soilprofile}\label{sec:CombiSurfaceLine2DSoilProfile} +A 2D profile already has a topboundary with different Z-values. Combiniation 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/18.1.2/doc/DAM UI - Functional Design/pictures/GISLine.png =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM - Technical Design/pictures/DAMComponents.pdf =================================================================== diff -u Binary files differ Index: DamClients/DamUI/tags/18.1.2/doc/DAM UI - Functional Design/pictures/DAMEngineDataModelLocation.pdf =================================================================== diff -u Binary files differ