Index: doc/System/DSoilModel - Test report.pdf =================================================================== diff -u Binary files differ Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.pdf =================================================================== diff -u -r189 -r191 Binary files differ Index: doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex =================================================================== diff -u -r189 -r191 --- doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 189) +++ doc/Work/D-Soil Model - Test Report/D-Soil Model - Test Report.tex (.../D-Soil Model - Test Report.tex) (revision 191) @@ -151,28 +151,28 @@ REQ 6.6 & The application must support layer properties. Layer properties are information which is related and can be allocated to a soil layer. Thus far, the "is aquifer" property is the only available layer property. In future, leak agelength sor dampingfactors may also be transferred to layer properties. \\ \hline REQ 7 & Stochastic schematization of subsoil. All the parameters of above described schematization can consist of stochastic variables or "as is" value (characteristic value or design value). All stochastic variables can be stored as a mean value with distribution parameters and the distribution type. Per mechanisms the partial factor is stored in Ringtoets such that a stochastic variable can be turned into a semi-probabilistic design value & \\ \hline REQ 7.1 & Stochastic subsoil modeling consists of soil segments (either lines or areas), each with soil profiles with a probability of appearance. Per failure mechanism the segments are defined. This stochastic subsoil modeling is presented in D-Soil Model. \\ \hline -REQ 3.4 & Import relevant reference data. Also data which is not passed through to Ringtoets should be showed in order to make good subsoil schematizations. The following items need to be shown in a relevant window: Surface lines, Characteristic points, Outside water level, PL lines, Polder water level. Note: A surface line with characteristic points and the actual polder water level can be imported and placed above a relevant 20 cross section. Surface lines will be combined with all possible subsoil scenarios in Ringtoets. They will not be available as a separate object in O-Soil Model. Also, the outer water level and other PL lines can be viewed for reference in the cross sections of the 20 profile. \\ \hline -REQ 7.3 & Overview of all available borings and CPT's in a segment/cross-section. All available ground investigation information in a section can be scrolled through and preferably dragged/dropped into a SOS scenario for viewing purposes. & \\ \hline +REQ 7.2 & Import relevant reference data. Also data which is not passed through to Ringtoets should be showed in order to make good subsoil schematizations. The following items need to be shown in a relevant window: Surface lines, Characteristic points, Outside water level, PL lines, Polder water level. Note: A surface line with characteristic points and the actual polder water level can be imported and placed above a relevant 20 cross section. Surface lines will be combined with all possible subsoil scenarios in Ringtoets. They will not be available as a separate object in O-Soil Model. Also, the outer water level and other PL lines can be viewed for reference in the cross sections of the 20 profile. \\ \hline +REQ 7.3 & Overview of all available borings and CPT's in a segment/cross-section. All available ground investigation information in a section can be scrolled through and preferably dragged/dropped into a SOS scenario for viewing purposes. \\ \hline REQ 7.4 & Overview of all available SOS scenario's in a segment. All available SOS scenarios per segment per mechanism must be presented. Preferably, available CPT's and borings can be matched with one SOS scenario. \\ \hline REQ 8.1 & A reference line can be imported form a GIS. This reference line can, for example, be used for the projection of soil investigation in longitudinal direction or to import SOS data in a relevant section. \\ \hline REQ 8.2 & Table view for soil parameters The application must support the several views to show (parts of) the subsoil schematisation. Table view to show all the information in a tabular format. The soil materials properties will only be shown in table view (not in graphical views). Property view to show details (information)of the selected object and if applicable the relation with other information(objects). \\ \hline -REQ 8.4 & Profile view to modify soil profiles .The application must support in profile view the drawing and modification of 10 and 20 soil profiles. 10 and 20 soil profile can be viewed in map view in case the location of the soil profile is available in RD (point or line). Modification of the location must be able in future development of the application. The application must support in profile view the drawing and modification of 10 and 20 soil profiles. Visualize the surface lines with their characteristic points. The application must give an overview in scenarios view of the soil profile scenarios for a soil area or segment. Since this might mean a major change in the software architecture an overview of the soil profile scenarios in another way than a scenarios view is acceptable if future development towards scenarios view maintain open. & \\ \hline +REQ 8.4 & Profile view to modify soil profiles .The application must support in profile view the drawing and modification of 10 and 20 soil profiles. 10 and 20 soil profile can be viewed in map view in case the location of the soil profile is available in RD (point or line). Modification of the location must be able in future development of the application. The application must support in profile view the drawing and modification of 10 and 20 soil profiles. Visualize the surface lines with their characteristic points. The application must give an overview in scenarios view of the soil profile scenarios for a soil area or segment. Since this might mean a major change in the software architecture an overview of the soil profile scenarios in another way than a scenarios view is acceptable if future development towards scenarios view maintain open. \\ \hline REQ 8.5 & Automatically project boreholes and CPT onto a cross section. Borehole and CPT can be allocated automatically to one or more soil profiles if it lies within a certain (user defined) distance of this cross section. If the location in RD is known the borehole or CPT is plotted perpendicular to the 20 profile if the borehole or CPT is within a user defined distance. This distance is set per cross section and is default 100 meter. The CPT/boring and the soil profile are plotted on the same vertical reference level (e.g. NAP) and scale \\ \hline -REQ 8.6 & Segments have an ID that the user can relate to. This ID must be presented in map view & \\ \hline -REQ 8.7 & Show all soil investigation with labels in mapview The name of the boring or CTP must be visible to the user in mapview & \\ \hline +REQ 8.6 & Segments have an ID that the user can relate to. This ID must be presented in map view \\ \hline +REQ 8.7 & Show all soil investigation with labels in mapview The name of the boring or CTP must be visible to the user in map view. \\ \hline REQ 8.8 & Visualize the surface lines with their characteristic points. A user must be able to view surface lines and characteristic points on top of a 10 and/ or 20 cross section. \\ \hline -REQ 8.9 & Select boreholes and CPT's onto a cross section. If automatic plotting (RE08.5) is not possible, the borehole or CPT can be dragged by the user to the right location in the 20 profile. The height reference of a borehole or CPT is assumed to be the same as in the soil profile and plotted in the height reference of the 20 profile & \\ \hline +REQ 8.9 & Select boreholes and CPT's onto a cross section. If automatic plotting (RE08.5) is not possible, the borehole or CPT can be dragged by the user to the right location in the 20 profile. The height reference of a borehole or CPT is assumed to be the same as in the soil profile and plotted in the height reference of the 20 profile \\ \hline REQ 8.10 & The application must give an overview in scenarios view of the soil profile scenarios for a soil area or segment. Since this might mean a major change in the software architecture an overview of the soil profile scenarios in another way than a scenarios view is acceptable if future development towards scenarios view maintains open. This scenarios view is not yet required in this version of the application if an overview of the scenarios per soil area or segments is provided in another manner (see also REO 5.1). \\ \hline REQ 8.11 & View files in file-related software. \newline -a. CPT's and borings in GEF format can be shown in an external program like GefPlotTool by doubleclicking the names in D-Soil Model. \newline +a. CPT's and borings in GEF format can be shown in an external program like GefPlotTool by double clicking the names in \ProgramName. \newline b. Open *.sti in \textsc{D-Geo Stability} by double clicking the name in \ProgramName. \\ \hline REQ 8.12 & In map view, relevant background information must be shown. Standard relevant information is AHN information and information from a (later to be specified) WMS server. \\ \hline REQ 7.2 & Allocation of CPT's and boreholes on a map and to a segment Imported CPT's and borings are shown on a map and can be matched to a segment. This Match can be pre-defined via a GIS-file.The application must support the allocation of soil profile scenarios to a soil area or segments. A soil profile scenario consists of a collection of 1D or 2D soil profiles with a probability of appearance. \\ \hline REQ 8.14 & Draw SOS profiles in one segment on the same height for comparison. When plotting SOS profiles next to one another, they must be plotted relative to a same reference level (e.g. NAP) and scale for simple comparison. The minimum and maximum value of the layers must also be shown. \\ \hline REQ 8.15 & Show ground investigation simultaneously to REQ 8.14 at the same reference level. When plotting soil investigations (CPT's and borings) on a reference line next to one another, they must be plotted relative to a same reference level (e.g. NAP) for simple comparison. \\ \hline -REQ 8.16 & Synchronization between different views. The user can switch between different kind of views of the data by clicking on the name. E.g. clicking on segment A in the table window, also selects this segment on the map and the properties of this segment are shown on the map. Applicable for names of: Soilsegments, soilprofiles, material, layer, CPT, boring, surfacelines & \\ \hline +REQ 8.16 & Synchronization between different views. The user can switch between different kind of views of the data by clicking on the name. E.g. clicking on segment A in the table window, also selects this segment on the map and the properties of this segment are shown on the map. Applicable for names of: Soilsegments, soilprofiles, material, layer, CPT, boring, surfacelines \\ \hline REQ 8.17 & Visibility of yield stress Yield stresses are plotted in the 2D profile as points with optional labels (label =Spanningswaarde). \\ \hline -REQ 9 & Edit and generate the building blocks of the subsoil schematization The user is able to edit all the building blocks. The user is responsible for the edits, D-Soil Model gives validations messages when applicable (e.g. minimum and maximum values). The user is supported by the application with tools. \\ \hline +REQ 9 & Edit and generate the building blocks of the subsoil schematization The user is able to edit all the building blocks. The user is responsible for the edits, \ProgramName gives validations messages when applicable (e.g. minimum and maximum values). The user is supported by the application with tools. \\ \hline REQ 9.1 & The soil materials can be named or renamed and the material properties can be created and modified in table view. Modification of the soil materials automatically updates the soil materials in the regarding soil layers. The material properties can be filtered on failure mechanism and calculation model if applicable. \\ \hline REQ 9.2 & The probably of appearance of one SOS scenario can be changed. The user is responsible for letting these scenarios add up to 100 percent. The interface should be such that the user can check this easily. \\ \hline REQ 9.3 & An existing 1D profile can be changed into a 2D profile so that the user can make changes in the cross section. A reference surface line needs to be drawn in this profile. Default width 100m. \\ \hline @@ -182,7 +182,7 @@ REQ 9.8 & The application must support the allocation of a soil material to a soil layer in one or more soil profiles. \\ \hline REQ 9.9 & Define layer as aquifer or aquitard. A soil layer in a soil profile can be defined in profile view as an aquifer. All other layers are considered to be an aquitard..This is a layer property. \\ \hline REQ 9.10 & Enter yield stresses for macrostability. The pre-consolidation pressure can be entered as a profile property and as soil material property. If the pre-consolidation pressure is a profile property it can be entered as point in profile view. The yield stresses must be shown to the user in a visual manner. \\ \hline -REQ 8.13 & Show SOS scenario's in 20 profiles. All relevant SOS scenario's (the ones from the same segment) must be visible in a 20 profile at the same reference level. The user will use this additional information to make sure the 20 subsoil schematization fits the SOS segments. \\ \hline +REQ 9.11 & Show SOS scenario's in 20 profiles. All relevant SOS scenario's (the ones from the same segment) must be visible in a 20 profile at the same reference level. The user will use this additional information to make sure the 20 subsoil schematization fits the SOS segments. \\ \hline REQ 9.12 & Modify the location of de borehole or CPT in the 2D profile. A CPT or borehole can be dragged to another location in the profile view. This will never alter the depth of the CPT or borehole, nor will it affect the "real" world position of the CPT or borehole. \\ \hline REQ 9.14 & Minimal validity check on the data. Minimal validation for the right values within given boundaries \\ \hline REQ 9.15 & Extensive validity check on the data for Ringtoets. Complete validation for a Ringtoets analyses where the user can ask if the data is complete to perform the analysis (as a WTI add-on).Validation is possible per failure mechanism. \\ \hline @@ -192,7 +192,7 @@ REQ 9.20 & Incorporate settlements underneath an embankment. The user must be able to define settlements (input cm settlement as input) underneath the embankment. \\ \hline REQ 9.21 & On a longitudinal cross section, the user is to be able to Visualize minimum and maximum of layer boundaries from the SOS data. For each 1D SOS scenario, the user must see the expected value of each layer boundary, together with the minimum and maximum value of the layer boundary. \\ \hline REQ 9.23 & On a longitudinal cross section, the user is to be able to Import soil areas and segments. The application can import soil areas (as a nice to have) and segments (must have) as shape files (polygons or poly-lines). \\ \hline -REQ 9.24 & On a longitudinal cross section, the user is to be able to Table import/export. All the tables in D-Soil Model (tables in table window, yield stresses, Sigma-tau curves etc.) must have an export as well as an import functionality (for table or column(s)). \\ \hline +REQ 9.24 & On a longitudinal cross section, the user is to be able to Table import/export. All the tables in \ProgramName (tables in table window, yield stresses, Sigma-tau curves etc.) must have an export as well as an import functionality (for table or column(s)). \\ \hline \end{longtable}