Datgel CPT Tool User Guide

User Guide
Datgel
CPT Tool gINT Add-In 3

DCT-UG-001 - 3.02 August 2012
Disclaimer
The information in this publication is subject to change without notice and does not represent a commitment on the part of Datgel Pty Ltd. The software described in this document is furnished under a license agreement or nondisclosure agreement. The software must be used or copied only in accordance with the terms of the agreement. Every effort was made to ensure accuracy of this information. However, Datgel Pty Ltd makes no warranty as to the correctness of this information or the supplied files. Printed in Australia. All rights reserved worldwide. No part of this publication may be reproduced in any form or by any means without the prior written consent of Datgel Pty Ltd. Comments are welcome and become the property of Datgel Pty Ltd. All products mentioned are trademarks of the respective producers. Copyright 2012 Datgel Pty Ltd. All rights reserved. Datgel Pty Ltd Suite 8, Level 1, The Hub 89 - 97 Jones Street Ultimo NSW 2007 Australia Tel: Fax: Email: Website: +61 2 8202 8600 +61 2 8202 8606 info@datgel.com www.datgel.com
Contents
About Datgel CPT Tool 3 .................................................................................................... vi
New in Version 3 ............................................................................................................................ vi Versions Used When Writing This Document ............................................................................... vii Support ......................................................................................................................................... vii System Requirements ................................................................................................................... vii Field Colours ................................................................................................................................ viii
Installation and Licensing ............................................................................................ 1

1.1 1.2 1.3 1.4 1.5 1.6 1.7 1.8 DLL Program Installation .......................................................................................................1 Virtual Memory Configuration ................................................................................................2 Which Database Structure? DGD SI, DGD EN or AGS RTA .............................................2 Merge gINT Library Objects ..................................................................................................3 Merge gINT Project File Tables and Fields ...........................................................................4 Initial Configuration................................................................................................................7 Validate or Activate License ..................................................................................................9 Upgrading From Version 2 to Version 3 ................................................................................9 Introduction .........................................................................................................................11 Preliminaries .......................................................................................................................11 Importing CPT and Dissipation Data ...................................................................................11 Configuring Parameters and CPT Data Analysis ................................................................13 Transfer Summary of Material Description ..........................................................................14 Output a Log .......................................................................................................................15 More Information .................................................................................................................15 Main Group .........................................................................................................................16 CPT .....................................................................................................................................16 CPT-Liquefaction.................................................................................................................21 CPT-Foundation ..................................................................................................................21 CPT-Configuration...............................................................................................................23 DG_COM_UNIT_CONVERSION ........................................................................................30 DG_CPT_AUTO_FILTER ...................................................................................................30 DG_CPT_CORRELATION_SUMMARY_CONFIG ..............................................................30 DG_CPT_DATA_CORRECTION_FORMULA_CONFIG .....................................................30 DG_CPT_DEPTH_ELEVATION_SCALE ............................................................................30 DG_CPT_FENCE_BLOCK .................................................................................................30 DG_CPT_FIELD_MAP ........................................................................................................30 DG_CPT_FORMULA_CONFIGURATION ..........................................................................30 DG_CPT_LOG_BLOCK ......................................................................................................30 DG_CPT_MEASUREMENT_SYSTEM ..........................................................................30 DG_CPT_MODIFIED_TIME_FACTOR ..........................................................................30 DG_CPT_PILE_AXIAL_CAPACITY_LCPC_BEARING..................................................31 DG_CPT_PILE_AXIAL_CAPACITY_LCPC_FRICTION .................................................31 DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL .........................................................31 DG_CPT_PORE_PRESSURE_FILTER_POSITION ......................................................31 DG_CPT_SCALE_TYPE ................................................................................................31 DG_CPT_SOIL_CLASS_DATA .....................................................................................31 DG_CPT_SOIL_CLASS_METHOD ...............................................................................31 DG_CPT_SOIL_CLASS_ZONES ...................................................................................32 DG_CPT_SOIL_TYPE ...................................................................................................32 DG_CPT_SYMBOLOGY ................................................................................................33 DG_CPT_SYMBOLOGY_SCALES_UNITS ...................................................................33 DG_CPT_TERMINATION ..............................................................................................33 DG_CPT_TEST_METHOD ............................................................................................33 DG_CPT_TRANSFER_SUMMARY_DESC_CONSISTENCY ........................................33
Datgel DCT-UG-001 - 3.02 - August 2012
Quick Start Tutorial ................................................................................................... 11

2.1 2.2 2.3 2.4 2.5 2.6 2.7
Project Tables ........................................................................................................... 16

3.1 3.2 3.3 3.4 3.5
Library Tables ........................................................................................................... 30

4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.8 4.9 4.10 4.11 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.23 4.24 4.25
CPT Tool gINT Add-In 3 User Guide
4.26 4.27 4.28 4.29
DG_CPT_TYPE ............................................................................................................. 33 DG_CPT_ZERO_LOCATION ........................................................................................ 33 DG_IMPORT_USER_IMPORT_PARAMETERS ........................................................... 33 DG_LOG_CONSISTENCY_DENSITY ........................................................................... 33 Tools Menu ......................................................................................................................... 35 File Browse Types .............................................................................................................. 35 File Types ........................................................................................................................... 35 Overwrite Option ................................................................................................................. 36 Correspondence File........................................................................................................... 36 Advanced Options............................................................................................................... 36 Importing Multiple Strokes/Tests into one PointID .............................................................. 39 Importing only the File Name from the Full File Path .......................................................... 40
Data Import ................................................................................................................ 35

5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8
6 7 8 9
CPT Filter .................................................................................................................. 41 Groundwater and Overwater Testing ......................................................................... 42

7.1 7.2 Groundwater Depth for Standard Onshore Testing............................................................. 42 Overwater Testing............................................................................................................... 42
Bulk Unit Weight and Void Ratio................................................................................ 46 Initiation of the CPT Data Calculation ........................................................................ 47
9.1 9.2 9.3 9.4 9.5 Primary Table Calculations ................................................................................................. 47 Batch Calculation ................................................................................................................ 48 Order of Calculation ............................................................................................................ 49 Calculation settings ............................................................................................................. 50 Dissipation Test .................................................................................................................. 51 Friction Ratio Calculation Method .................................................................................. 53 Applying the Depth Correction due to Inclination Calculation ......................................... 55 Introduction .................................................................................................................... 56 Formula Toolbar ............................................................................................................. 57 Data Tool Toolbar .......................................................................................................... 58 Formulas Group ............................................................................................................. 60 Configuration Group ....................................................................................................... 61 Merge/Copy Formulas.................................................................................................... 63 Introduction .................................................................................................................... 67 Formula Toolbar ............................................................................................................. 68 Data Tool Toolbar .......................................................................................................... 68 Formulas Group ............................................................................................................. 70 Key Set Group ............................................................................................................... 71 Configuration Group ....................................................................................................... 72 Offset and Correction Group .......................................................................................... 73 Preconfigured in Library ................................................................................................. 75 Creating a New Soil Behaviour Type in a Library ........................................................... 76 Project Soil behaviour Type ........................................................................................... 79 Undrained Shear Strength and Consistency Term ......................................................... 81 Relative Density and Relative Density Term .................................................................. 84 Soil Behaviour Type Index ............................................................................................. 86 SPT N60 Value .............................................................................................................. 87 SPT Average N60 Value ................................................................................................ 88 Shear Wave Velocity ...................................................................................................... 88 Unit Weight .................................................................................................................... 90 Small-Strain Shear Modulus .......................................................................................... 91 Youngs Modulus............................................................................................................ 92
10 11 12
Derived Parameters ................................................................................................... 52

10.1 11.1 12.1 12.2 12.3 12.4 12.5 12.6
Depth Correction Due to Inclination ........................................................................... 54 Formula Tool ............................................................................................................. 56
13
Data Correction Tool ................................................................................................. 67

13.1 13.2 13.3 13.4 13.5 13.6 13.7
14
Soil Behaviour Type .................................................................................................. 75

14.1 14.2 14.3
15
Correlations ............................................................................................................... 81
15.1 15.2 15.3 15.4 15.5 15.6 15.7 15.8 15.9
ii
15.10 15.11 15.12 15.13 15.14 15.15 15.16 15.17 15.18 15.19
Constrained Modulus......................................................................................................92 Coefficient of Volume Change ........................................................................................93 Compression Index ........................................................................................................93 Preconsolidation Stress and Overconsolidation Ratio ....................................................94 Angle of Friction .............................................................................................................96 Effective Cohesion .........................................................................................................97 Sensitivity .......................................................................................................................98 Coefficient of Lateral Earth Pressure ..............................................................................98 Rigidity Index ..................................................................................................................99 Hydraulic Conductivity ..................................................................................................101 State Parameter ...........................................................................................................102 Soil Behaviour Type Index 1, NCEER ..........................................................................104 Fines Content (FC) .......................................................................................................105 Clean-Sand Equivalent Normalised Cone Resistance ..................................105 Cyclic Resistance Ratio (CRR) .....................................................................................106 Cyclic Stress Ratio (CSR) ............................................................................................108 Factor of Safety (FoS) ..................................................................................................109 Residual Shear Strength (Sr) ........................................................................................111 Maximum Shear Strain, .....................................................................................111 Lateral Displacement Index 1, LDI ...............................................................................112 Post Liquefaction Volumetric Strain, ........................................................................112 Post Liquefaction Reconsolidation Settlement, S .........................................................113 Soil Description ............................................................................................................114 Unit End Bearing ..........................................................................................................114 Unit Side Friction ..........................................................................................................115 End Bearing Capacity ...................................................................................................116 Side Friction Capacity...................................................................................................116 Ultimate Axial Capacity.................................................................................................116 Minimum Layer Thickness ............................................................................................118 Soil Group Thickness ...................................................................................................118 Configuration of description and consistency summary transfer ..................................119
16
Liquefaction Assessment ........................................................................................ 102

16.1 16.2 16.3 16.4 16.5 16.6 16.7 16.8 16.9 16.10 16.11 16.12
17
Pile Axial Capacity .................................................................................................. 114

17.1 17.2 17.3 17.4 17.5 17.6
18
Transfer Description and Consistency Summary .................................................... 117

18.1 18.2 18.3
19 20 21 22
Lower-Best-Upper Correlations ............................................................................... 120 Correlation Summary .............................................................................................. 121

20.1 20.2 Default Configuration ....................................................................................................121 Custom Configuration ...................................................................................................121
Configuring the Design Line .................................................................................... 124 qc and qt Averaging ................................................................................................. 126
22.1 22.2 22.3 Moving Average ...........................................................................................................126 Stepped Average ..........................................................................................................126 Strata Average .............................................................................................................126
23 24
Exclude Fines Layers .............................................................................................. 127 Dissipation Test Analysis ........................................................................................ 128
24.1 24.2 24.3 Procedure to analyse a dissipation test in normally consolidated soil ..........................128 Procedure to analyse a dissipation test in overconsolidated soil ..................................131 Procedure to use forward extrapolation ........................................................................133 Symbology Table Structure ..........................................................................................135 Configurable Options ....................................................................................................138 Introduction...................................................................................................................141 Project Field Units ........................................................................................................141 Library Configuration ....................................................................................................142 Unit Conversion of the Current Project .........................................................................145
25 26
Symbology .............................................................................................................. 135

25.1 25.2 26.1 26.2 26.3 26.4
Unit Conversion....................................................................................................... 141
27
Formula Tool and Data Correction Tool Functions.................................................. 147

iii Datgel DCT-UG-001 - 3.02 - August 2012
27.1 27.2
Functions ..................................................................................................................... 147 Special Functions ......................................................................................................... 148 Log Reports ................................................................................................................. 161 Fences Reports ............................................................................................................ 163 Graph Reports ............................................................................................................. 164
28
Reports .................................................................................................................... 161

28.1 28.2 28.3
29
References .............................................................................................................. 175
iv
Appendixes
Appendix A Tutorial: Creating a Log and Fence Report Column for a new Derived Parameter Appendix B Tutorial: Creating a New Correlation in the Formula Tool Appendix C Tutorial: Creating a Log and Fence Report Column for a new Correlation Appendix D Tutorial: Creating a New Unit System Appendix E Tutorial: Entering a New Unit Quantity Appendix F Tutorial: How to change a field unit and make it work with reports Appendix G Tutorial: How create and configure a new CPT Data table
Tables
Table 1 - Field Colours .......................................................................................................................... viii Table 2 - Derived Parameters................................................................................................................ 52 Table 3 - Log Reports .......................................................................................................................... 161 Table 4 - Dynamic Log Report Variables ............................................................................................. 162 Table 6 - Fence Report Variables ........................................................................................................ 163 Table 7 - Graph Reports ...................................................................................................................... 164
About Datgel CPT Tool 3

The Datgel CPT Tool gINT Add-In 3 is designed to streamline the processing and interpretation of Cone Penetration Test and Dissipation Test data: Designed for flexibility and user configuration ASCII data files in numerous standard and propriety formats may be imported Filter rod changes Calculate derived parameters The soil type and consistency/density may be interpreted based on user defined parameters, and then a summary can be transferred to your soil description and consistency/density table More than 100 preconfigured published correlations are calculated, written to the database and ready for presentation on your graphs and logs User-definable correlation formulas Pile axial capacity Liquefaction related correlations Dissipation test analysis More than 300 customisable log, graph and fence reports User definable line colours, types and scales
You need to complete the installation procedure (see Installation and Licensing on page 1) and activate (see Datgel Product Licensing System User Guide) before you can use the CPT Tool.
New in Version 3
1. 2. 3. 4. 5. 6. 7. 8. 9. User definable units, allowing for the use of English/Imperial units Correlations for hydraulic conductivity and State Parameter Soil behaviour types correlations by Eslami Fellenius (1997), Ramsey (2002), and Schmertmann (1978) Option to store site specific SBT definition in the project database Non-normalised Soil Behaviour Type Index, ISBT, Robertson (2010) Soil behaviour type index by Been and Jefferies (1992) Pile axial capacity Liquefaction factor of safety, residual shear strength, lateral displacement and settlement Database schema restructure of project and point level parameters
10. Log and fence report speed improvement 11. Support for AGS 4 12. Control minimum thickness of a SBT layer 13. Option to average qc over sleeve range for Rf and Fr calculation 14. Correlation summary command 15. Import of more data file formats: Vertek (*.ecp), Gregg Drilling (*.cor) and Datem Neptune (*.cdf) 16. Enhanced support for gINT Professional Plus with SQL Server
CPT Tool gINT Add-In 3 User Guide Datgel DCT-UG-001 - 3.02 - August 2012
vi
17. Faster, multithread calculation
Versions Used When Writing This Document

This user guide has been written using: CPT Tool gINT Files 3.0.2 CPT Tool DLL 3.0.2 gINT Professional Plus 8.30.03.84 or later Windows 7 64 bit operating system
Support
12 months support and maintenance is included with the license purchase. For technical support please email support@datgel.com or call +61 2 8202 8600.
System Requirements
gINT
The product runs optimally using gINT 8.2.008 or 8.1.2.008 (23/Jun/2010 12:00:00 PM) or higher. gINT Professional or gINT Professional Plus is recommended as the tool includes fence and graph reports. The product will run using gINT Logs.
Hardware and Operating System

Same system requirements as gINT.
Required Windows Components

1. 2. Windows Installer 3.1 .NET 3.5 Framework SP1
Conventions and typography used in this guide

Note: Tips and additional Information to help you.
> | Used to indicate a series of menu commands. e.g. Select File > Open. Used to indicate a gINT Application Group, Application, Table Group or Table , e.g. DATA DESIGN | Project Database Items you must select, command buttons, or items in a list. e.g. Navigate to UTILITIES | Convert Projects (4th tab). Use to emphasize the importance of a point such as parameters. e.g. Data Entry Check Omit Must Save prompt when save is required Names of keys on the keyboard. for example, SHIFT, CTRL, or ALT. Key combinations, for example CTRL+P, or ALT+F4.
Bold Text Italics Emphasis CAPITALS KEY+KEY
vii
Code Snippet
Code sample
Indicates a code snippet within a paragraph Indicates a sample program codes inserted in user guide e.g. public override string ToString () Used for formatting file name and paths e.g. di_lib.glb or V:\10 gINT\Datgel Install Files\ Database table name, e.g. POINT_TABLE. Database field name; e.g. PointID Command line, presented exactly as it must be entered e.g. Cdir
File name or path Table_Name Field_Name Command line
Field Colours
Each of the fields in the project tables have been coloured to improve the data entry process as indicated below in Table 1. Table 1 - Field Colours
Field Colour Yellow Pastel Purple Pastel Green Brown - Green Pastel Beige Pastel Red Pastel Blue Pastel Orange Grey Field Name and Explanation gINT Key Field mandatory data entry AGS Data data associated with the AGS Data Interchange format Calculated Field data is written to this field by Datgels code Data Enter and Calculated field Data Entry Field data should be entered into this field, or data in this field influences the calculation Legacy Data Field historic data entered here, is from typically an old database Output Option used to control how the data displayed on a report Remark or Metadata Field additional data associated with the primary information Read-only
Note: The Datgel CPT Tool is supplied with three versions database options DGD SI metric with long table (e.g. CPT_POINT_PARAMETERS) and field names, DGD EN same names as DGD SI but with English/Imperial units, and AGS RTA with short AGS RTA-compliant names (e.g. GEOL) for non CPT tables. Both names are usually given, although only one is relevant to any given site. Screen images are not duplicated and usually show only the DGD SI version.
viii
Installation and Licensing
If youre trialling the CPT Tool, then please first work through the following sections: 1.1 DLL Program Installation, 1.3 Which Database Structure? DGD SI, DGD EN or AGS RTA, and 2 Quick Start Tutorial. Please also watch the CPT Tool video on datgel.com. There are four parts to the installation process: DLL program installation Merge gINT library objects Merging project tables and fields Configure settings in library and project/data template Activate the product license
The first three steps can be completed in any order and are described below. The activation procedure must be done last and is described in the Datgel Product Licensing System User Guide.
1.1
DLL Program Installation
The CPT Tool requires that the Microsoft .net 3.5 framework is installed on the PC prior to the installation of the CPT Tool. If your PC does not have the .net 3.5 framework SP1 installed, then it will be automatically installed during the CPT Tool installation process. You need local administrator rights to the PC to install the CPT Tool. To install the CPT Tool: Ensure that gINT is closed Run the setup.exe file Follow the prompts
In the following screen, you can either accept the default location for the new file, or change it by clicking Browse. The Disk Cost button shows the space required versus space available on each of your disks.
1.2
Virtual Memory Configuration
We recommend this setting is applied to Windows in order to achieve optimal batch calculation memory use and speed. 1. Start Menu, right click on Computer > Properties > Advanced System Settings > Advanced tab > Performance section > Settings button > Advanced Tab > Virtual memory section > Change button Uncheck Automatically manage paging file size for all drives Select Custom size radio button. Set Initial size to the same as your installed RAM (e.g. if 8GB RAM, then enter 8192MB) Set Max size to double your installed RAM (e.g. if 8GB RAM, then enter 16384MB)
2. 3. 4. 5.
1.3
1. 2. 3.
Which Database Structure? DGD SI, DGD EN or AGS RTA

DGD SI stands for Datgel Database with SI/metric units and long table (e.g. CPT_POINT_PARAMETERS) and field names. DGD EN stands for Datgel Database with English/Imperial units and long table (e.g. CPT_POINT_PARAMETERS) and field names. AGS RTA, based on the structure prescribed by the Roads and Traffic Authority of NSW, Australia, and the Association of Geotechnical and Geoenvironmental Specialists. The database has short AGS RTA-compliant names (e.g. GEOL) for non CPT Tables. This option uses metric/SI units. From version 3 the CPT specific tables use the DGD naming convention.
At this point you must decide which CPT Tool database structure to use. The options are:
Unless youre currently using an AGS RTA style database, we recommend you adopt the DGD database most relevant for your local practice.
1.4
Merge gINT Library Objects
Note: If youre in one of the following situations then proceed to Section 1.7 Validate or Activate License. In the trial version of the CPT Tool, the library will be locked and you cannot merge any gINT Library Objects into your Library file, or make changes to this Library file. In this case, you have to use the locked library as-is. Steps 1.4 to 1.6 have been done by Datgels developers or done previously by you or a colleague. If you dont have existing gINT files then you may wish to just use the example CPT Tool gINT Files provided on the DVD. If you have purchased the CPT Tool, then you have full access to the library objects, and you may proceed with the following steps to merge the gINT Library components into your Library file. 1. 2. 3. Make a backup copy of your existing library file. By default this is located at: C:\Users\Public\Documents\Bentley\gINT\libraries\ Start gINT and open the library and project file you wish to use the Datgel CPT Tool with. If have existing library tables with the same name as those in the CPT Tool files, please now delete those tables. To do this, go to DATA DESIGN | Library Tables > File > List, select the rows to delete, and press the Delete key. If you have an older version of the CPT Tool in your gINT files, it is simpler to delete the library objects prior to merging the new version. This is done by navigating to each library application, e.g. Log Blocks, displaying the List of objects, and deleting those starting with DG CPT. Select UTILITIES | Lib Merge/Copy. Browse the Source Library File for datgel cpt tool dgd lib #.## <Unit>.glb Check the Query On Overwrite box, then move all source tables, except Material Composite Symbols and Tiles, to the yellow box on the right side by clicking the >> button.
4.
5. 6. 7.
8.
Click Execute. The process may take several minutes.
This merges the CPT Tool Add-In menu item, gINT Rules modules, user system data and other library tables relevant for the use of the CPT Tool.
Depending on which page sizes you tend to use, you may find it convenient to not merge the Letter (LET) and 11x17 or the A4 and A3 reports.
1.5
1.
Merge gINT Project File Tables and Fields

Open your existing project/data template in DATA DESIGN | Project Database.
2.
If you have existing tables for CPT data or old tables for the CPT Tool, you should delete them now. A simple way to delete multiple tables is to call Tables > List or to delete, click the delete key, and click OK. , select the tables
3.
Select Tables > Import Multiple Tables... then browse for either file datgel cpt tool dgd #.## <unit>.gpj or datgel cpt tool dgd #.## <unit>.gdt.
4.
At the minimum, select the following tables to import, and click OK. The select blue rows are required. The tables indicated by red boxes are used by reports and should be merged if your project doesnt have existing equivalent tables. The rest of the tables are generally ItemKey tables and are used as lookup lists by fields. a) DGD
b) AGS RTA
5.
Merge fields from POINT. Change the object selector to POINT, and call Tables > Merge fields from other file, select datgel cpt tool dgd #.## <unit>.gpj or datgel cpt tool dgd #.## <unit>.gdt, then select POINT, and select the fields to merge. We suggest if youre unsure, merge them all and reconcile them later. Merge fields from PROJECT. Follow a similar process to that for POINT.
6.
7.
Consider report changes to suit your custom project database. Many of the gINT reports provided with the CPT Tool reference the red boxed tables, and you may need to update the field references in the reports to work with your custom project database. In particular you need to consider fields on the POINT and PROJECT tables. The DATA DESIGN | Project Database | Tools > Compare Databases function will list the table, field, and property differences between databases. Use this to compare your companys project file to the CPT Tool project file. The DATA DESIGN | Project Database | Tools > Replace Field Names function will assist you to update the CPT library objects to use the fields and tables in your custom project file.
8.
In DATA DESIGN | Project Database change the yellow object selector list to the POINT table, call the command Tables > Properties... move to the gINT Rules tab, and place DATGEL DGD!OnSave in the gINT Rules Procedure on Save text box. (This can also be configured in INPUT)
9.
In INPUT call the command gINT Rules > System Events... and place Datgel Dgd!beforecommand in the Before Command text box. (This can also be configured in DATA DESIGN | Library Data)
10. Move to INPUT, and run the Add-Ins > Datgel Administrator Tools > Lookup List Check Tool to search for broken lookup list references, and rectify as needed. This step requires the Datgel Administrator Tools to be installed and licensed.
1.6
1.
Initial Configuration
Move to INPUT and reorder the tables within the CPT table group. Select the Table Group, and call Tables > Input Sequence
Following the library and project merge steps, the following items should be configured:
a) CPT
b) CPT-Liquefaction
c) CPT-Foundation
d) CPT-Configuration
2.
Move to DATA DESIGN | Library Data, and configure the Graphic_1 and Graphic_2 fields on DG_CPT_SOIL_CLASS_ZONES library table; see 4.19 DG_CPT_SOIL_CLASS_ZONES on page 32. Select the most appropriate graphics in your library for each soil type zone. Configure DG_LOG_CONSISTENCY_DENSITY library table to be consistent with your soil description standard. By default, the table is configured with date consistent with Australian Standard, ASTM and New Zealand Geotechnical Society. We have configured example data for BS 5930 in DG_LOG_CONSISTENCY_DENSITY_BS_00.xlsx, and if required you can delete the data in the library table and copy/merge in the data from the Excel file.
3.
4.
Move to INPUT and configure the table and field names for Lithology/Stratigraphy and Consistency/Density as described in 18.3 Configuration of description and consistency summary transfer on page 119 . In SYMBOL DESIGN | Bitmap Symbols, import your company logo into the existing symbol called LOGO. This symbol is referenced by all the Tools reports. Alternatively you can adjust the DRAWINGS | Drawing Library DG COM LOGO to reference a different Bitmap Symbols. Review how your logo appears on the DRAWINGS | Drawing Library block DG COM FIGURE TITLE BLOCK. If required change the block x and y offset.
5.
6. 7.
Update the import correspondence files (*.gci) for the numerous CPT formats to work with your custom gINT project file. Particularly the POINT and PROJECT tables. Assign correct page sizes and printer to reports. In order to export a report to pdf or other image format the correct page size must be assigned. a) Ensure a printer driver installed on your pc has A3 and 11x17 size. b) Use the command REPORT DESIGN | File > Set printer for reports, pick the printer with A3 from the printer list, and select the A3 size reports from the reports list. c) Then go to each A3 and 11x17 size report in REPORT DESIGN by changing the yellow drop down list. Display the report properties, File > Page > Properties, and set the page size to A3 or 11x17. You may also need to adjust the margins. Click Ok. d) Review the page margins and outlines by clicking on Zoom Page, and move to the next report.
8.
If you have upgraded from an older version, may now reapply custom configurations such as: a) b) c) d) Create new fields in CPT project tables Merge formulas into the Formula Tool Configure DG_CPT_SYMBOLOGY and DG_CPT_SYMBOLOGY_SCALES_UNITS Configure reports
1.7
Validate or Activate License
After installation (and before using the CPT Tool Add-in), validate or activate the user license as described in Chapter 2 of the Datgel Product Licensing System User Guide.
1.8
1.8.1
Upgrading From Version 2 to Version 3

DLL program
You may simply install the DLL program over the top of a previous installation.
1.8.2
gINT Files
We suggest you delete all old CPT Tool specific project tables from your data template, and all CPT specific library objects from your library. Then merge the new CPT Tool into your library and data template as describe above. You will need to design a correspondence file to migrate old project to the new project/data template structure. We have provided two correspondence files that you can use as a basis: datgel_cpt_tool_dgd_2.19_to_3.02_02.gci ags rta 2.21 to ags rta 3.02 00.gci
We recommend you open the relevant file above in DATA DESIGN | Correspondence Files, and do the following:
1. 2. 3. 4. 5.
Adjust the Source File and Target File properties to point to your old and new data template / project file. Click Refresh Fields All (F5). Save correspondence with a new name. Try converting one file using UTILITES | Convert Projects. Note that gINT will automatically make a backup of the project with an extension *.or#. Review the converted file to ensure all data was correctly converted.
When converting projects it will be faster if you a have a library open that doesnt have gINT Rules modules for the CPT Tool, so that all calculations are supressed.
10
2
2.1
Quick Start Tutorial

Introduction
This tutorial will introduce you to the basic operations of the CPT Tool; it assumes you have a basic understanding of gINT INPUT and OUTPUT. If this is the first time youve used gINT then we suggest you read C:\Program Files (x86)\Bentley\gINT\docs\welcome_to_gint_8.pdf.
2.2
1. 2.
Preliminaries
First work your way through sections 1.1 DLL Program Installation and 1.3 Which Database Structure? DGD SI, DGD EN or AGS RTA. Start gINT, and check youre running 8.2.008 (23/Jun/2010 12:00:00 PM) or 8.1.2.008 or later by reviewing the version number on the Help > About gINT dialog. If youre running an older update, then you should download and install the latest gINT version from Bentleys SELECT website or the Datgel trial page on www.datgel.com. This tutorial will use our standard DGD SI CPT Tool gINT Files, located on the DVD in folder gINT Files\DGD SI\. If you havent done so, copy the folders on the DVD to a location on your local or network drives. You can also use a set of custom gINT files that already have the CPT Tool tables and objects merged in, as described in section 1 Installation and Licensing. Now, open the datgel cpt tool dgd lib X.XX SI.glb, using File > Change Library. Create a new project, select the command File > New Project > Clone Data Template..., and select the datgel cpt tool dgd X.XX SI.gdt file, and click Open. Then provide the name Tutorial 1.gpj and click Save.
3.
4. 5.
2.3
1.
Importing CPT and Dissipation Data

Launch the Data Import Tool, by calling the command Add-Ins > Datgel CPT Tool > Data Import.
The CPT Tool splash screen should now appear, signifying you are now using the CPT Tool license. If youre using a trial license then a form will appear telling you how many uses are left. If nothing happens, then double check you have installed the CPT Tool program by running the setup.exe file located in the Installation Files folder on the DVD. If you havent previously validated your license, i.e. by entering the serial number, license number, contact details, and server name in the case of a network license. Then you will
11
be prompted to do so now, and you should refer to Chapter 2 of the Datgel Product Licensing System User Guide, which was included on the DVD in the Documentation folder. You should now see the Data Import Tool form.
2.
In this tutorial we will import GEF files. a) Set File Type to GEF 1.1.0 (*.gef) b) Set Overwrite Option to Never c) Set Correspondence File to \datgel_cpt_tool_dgd_si_X.XX_gef_XX.gci. The gci can be found in the gINT Files\DGD SI\ folder on the DVD. The gci file translates the data during the import process between a temporary CSV file created by the CPT Tool code and the DGD database tables and fields. Select the Browse button in the top right of the form, and browse to the \Example CPT Data Files\ folder from the DVD. Select: "GEF_01.GEF" "GEF_01_D01.GEF" "GEF_01_D02.GEF". The *D* files are dissipation test files related to the GEF_01.GEF file. The form should now look similar to the screenshot (apart from the folder paths).
d) Click Execute. There will be a short pause while the Datgel code translates the data, then you will see a gINT progress form.
12
Finally when the import is complete a gINT Import Log form will display.
It can be useful to review the Source and Target record counts to confirm the data has imported. The Log also lists overwrite and lookup warnings. In this case the warnings are of little consequence. You may now like to step through the tables in the project file, and observe the imported data. Note that some values, such as those on the Project Parameters table are default values stored in the data template file we used to make the new project.
2.4

Configuring Parameters and CPT Data Analysis

CPT | CPT Data - Upper: Test Number, Cone ID, and (optionally) Groundwater Depth. Set Groundwater Depth to 0. CPT | CPT Data - Lower: Depth, qc, fs, u2 (for CPTu) CPT | Cone Information: Cone ID, Cone Area Ratio (for CPTu), Cone Sleeve Offset (used to filter rod change noise for fs), and Cone Diameter (used by dissipation test analysis)
The following information must be entered for the basic CPT Calculations to occur:
13
CPT-Configuration | Point Parameters: (optionally) Groundwater Depth CPT-Configuration | Project Parameters: Most fields should be set, and these will be used as default values. In particular to enable basic calculations you should define: Bulk Unit Weight, default is 17 kN/m3 Bulk Unit Weight Saturated, default is 18 kN/m3 Soil Class Method 1, change to Robertson 1990 Extrapolated Soil Class Method 2, leave default
Refer to section 7 Groundwater and Overwater Testing for a detailed explanation of where to set groundwater data. When you change the value of related fields the CPT Tool table calculation will automatically initiate. You can suppress the automatic calculation by checking Suppress Automatic Calculation on Project Parameters, and the calculation can be run later as part of a batch calculation (for more information see section 9 Initiation of the CPT Data Calculation). The resulting CPT | CPT Data screen should look like this:
2.5
Transfer Summary of Material Description
We will now transfer a summary of the soil layers to the Strata Main table. Call the command Add-Ins > Datgel CPT Tool > Transfer Description and Consistency for current PointID, then move to Main Group | Strata Main to see the transferred descriptions. You can edit the description data, and it will not be over written unless you call the Add-In command again.
14
2.6
Output a Log
To produce a log output click on the OUTPUT tab. From the Logs tab, click on the yellow drop down list and select the Report CPTU SU DR A3L. Then click on the PointID browse button and select PointID GEF_01.
Then click preview, and you should see this:
2.7
More Information
Refer to section 24 Dissipation Test Analysis for a tutorial on that subject.
15
Project Tables
The test and interpreted data is stored in the project database. A number of constants and assumptions are required in derivations. Many may be set at a project level on Project Parameters and Project Correlation Parameters, for each PointID on Point Parameters and Point Correlation Parameters, by depth for a PointID on Point Material Properties and a few for each push (on CPT Data Upper). This gives the user full control on which level in the hierarchy to use.
3.1
3.1.1
Main Group
POINT
When an Elevation is changed the Tool will calculate. The PointID and HoleDepth fields must be defined.
3.2
3.2.1
CPT
CPT Data Upper (CPT_GENERAL)
This table defines each CPT stroke within a PointID, since under some circumstances multiple CPT strokes take place in the same hole. Each stroke has a unique Test Number.
3.2.2
CPT Data Lower (CPT_DATA)
This table stores the actual raw depth related data for each push and derived results related to each reading.
16
3.2.3
Cone Information - Upper (CPT_CONE_INFORMATION)
The cone and equipment constants are stored on this table. For example, two important constants are the Cone Area Ratio and Cone Sleeve Offset.
3.2.4
Cone Information - Lower (CPT_CONE_CALIBRATION)
This table can be used to record the calibration dates for each cone.
17
3.2.5
Lower best Upper Correlations (CPT_DATA_LOWER_BEST_UPPER)
This table is a one-to-one child of CPT_DATA, and stores a selection of correlations with results for Lower Bound, Best Estimate and Upper Bound.
3.2.6
Dissipation Test (CPT_DISSIPATION_TEST_GENERAL and CPT_DISSIPATION_TEST_READINGS)
These tables store the Dissipation Test raw and derived data.
18
3.2.7
Enviro Data (CPT_DATA_ENVIRONMENTAL)
This table is a one-to-one child of CPT_DATA, and stores environmental and some geophysics related results. For the most part this is included for AGS Format compatibility, and the data on this table is not displayed on the standard CPT Tool reports.
3.2.8
BPT Data (CPT_BPT_GENERAL & CPT_BPT_DATA)
Spherical Ball Penetrometer Data is stored on these tables. In future versions correlations will be added.
19
3.2.9
Point Correlation Summary (CPT_POINT_CORELATION_SUMMARY)
This table is populated by the Correlation Summary command / functionality.
3.2.10
Correlation Summary (CPT_STROKE_CORELATION_SUMMARY)
This table was added to support AGS 4 Format. Currently users must manually enter summary data in this table.
20
3.3
3.3.1
CPT-Liquefaction
Liquefaction Data (CPT_LIQUEFACTION_DATA)
One-to-one child of CPT_DATA which stores liquefaction related correlation results.
3.3.2
Liquefaction Point Parameters (CPT_LIQUEFACTION_POINT_PARAMETERS)
Stores point level parameters for liquefaction correlation calculations.
3.3.3
Liquefaction Project Parameters (CPT_LIQUEFACTION_PROJECT_PARAMETERS)
Stores project level parameters for liquefaction correlation calculations.
3.4
3.4.1
CPT-Foundation
Pile Data (CPT_DATA_PILE)
One-to-one child of CPT_DATA which stores pile capacity correlation results.
21
3.4.2
Foundation Point Parameters Upper (CPT_FOUNDATION_POINT_PARAMETERS)
Point level parameters used by foundation calculations.
3.4.3
Foundation Point Parameters Lower (CPT_FOUNDATION_POINT_PARAMETERS_PROFILE)
Depth profile of material type used by pile capacity calculation.

22
3.4.4
Foundation Project Parameters (CPT_FOUNDATION_PROJECT_PARAMETERS)
Project level parameters used by foundation calculations.
3.5
3.5.1
CPT-Configuration
Point Parameters - Upper (CPT_POINT_PARAMETERS)
This table stores the Point level constants and assumption values related to derived parameters and soil behaviour type calculations. Hence if you wish to set the groundwater depth for all strokes for a PointID then that value should be entered into the Groundwater_Depth field on the CPT_POINT_PARAMETERS Table.
23
3.5.2
Point Correlation Parameters - Upper (CPT_POINT_CORRELATION_PARAMETERS)
Point level constants for correlations are stored in this table.
3.5.3
Point Correlation Parameters - Lower (CPT_POINT_MATERIAL_PROPERTIES)
A bulk unit weight, u0, e, Nk, Nkt depth profile may be defined for each PointID on the CPT_POINT_MATERIAL_PROPERTIES table. The depth ranges for a particular PointID must not overlap in any way. You will not be able to save the table if overlapping depth ranges are entered.
3.5.4
Project Parameters (CPT_PROJECT_PARAMETERS)
Project level constants and parameters related to derived parameter and soil behaviour type calculations are stored on this table.
24
3.5.5
Project Correlation Parameters (CPT_PROJECT_CORRELATION_PARAMETERS)
Project level correlation parameters and constants are stored on this table.
3.5.6
Project Output Options (CPT_PROJECT_OUTPUT_OPTIONS)
This table stores the project level report output options.
25
3.5.7
Point Symbology (CPT_POINT_SYMBOLOGY)
This table stores Point level overrides for the settings on CPT_PROJECT_SYMBOLOGY and DG_CPT_SYMBOLOGY.
3.5.8
Project Symbology (CPT_PROJECT_SYMBOLOGY)
This table stores Project level overrides for the settings on DG_CPT_SYMBOLOGY. You can set scales, line types etc. for each parameter here for the entire project.
26
3.5.9
Design Line (CPT_DESIGN_LINE and CPT_DESIGN_LINE_DATA)
These tables define the design line for Cone Resistance and all correlations. In the case of Cone Resistance the data is written to the CPT Data table, and can display on log and fence reports. For correlations the data is optionally displayed on Graph reports, and not written to CPT Data. You can assign the Design Line to use on the Project Parameter and Point Parameter tables.
27
3.5.10
Soil Class Method (CPT_SOIL_CLASS_METHOD)
Definition of project specific Soil Behaviour Type methods.
3.5.11
Soil Class Zones (CPT_SOIL_CLASS_ZONES and CPT_SOIL_CLASS_DATA)
Definition of project specific Soil Behaviour Type zones and polygon data.
28
3.5.12
Formula Configuration (CPT_FORMULA_CONFIGURATION)
This is a hidden table, and stores Project level formulas.
3.5.13
Data Correction Configuration (CPT_DATA_CORRECTION_FORMULA_CONFIG)
This is a hidden table and stores Project level Data Correction formulas.
29
4
4.1
Library Tables
DG_COM_UNIT_CONVERSION
This section lists library tables that are important to calculation of the CPT Tool and reports.
This table contains a list of the units, conversion factors and equations, and is referenced to convert values from one unit to another throughout the CPT Tool.
4.2
DG_CPT_AUTO_FILTER
This table is a simple lookup for the filter options.
4.3
DG_CPT_CORRELATION_SUMMARY_CONFIG
This table stores Library level data for the correlation summary function.
4.4
DG_CPT_DATA_CORRECTION_FORMULA_CONFIG
This table stores Library level data correction formulas.
4.5
DG_CPT_DEPTH_ELEVATION_SCALE
Attribute table used by log reports.
4.6
DG_CPT_FENCE_BLOCK
Lookup and attribute table used by fence reports.
4.7
DG_CPT_FIELD_MAP
Stores the table and field name configuration used by the CPT Tool calculation. This allows the user to set non-standard field and table names. If a parameter is missing the DGD name is used as default. This table also stores units, field rules and default values used for Unit Conversion for each unit system.
4.8
DG_CPT_FORMULA_CONFIGURATION
These table stores Library level formulas for the Formula Tool.
4.9
DG_CPT_LOG_BLOCK
Lookup and attribute table used by dynamic log reports.
4.10
DG_CPT_MEASUREMENT_SYSTEM
This table is a simple lookup for the measurement system type options, based on the GEF standard.
4.11
DG_CPT_MODIFIED_TIME_FACTOR
Used for dissipation analysis.
30
4.12
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_BEARING
Used for pile axial capacity calculations.
4.13
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_FRICTION
4.14
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL
4.15
DG_CPT_PORE_PRESSURE_FILTER_POSITION
Used for dissipation analysis.
4.16
DG_CPT_SCALE_TYPE
This table is a simple lookup for the soil classification graph type options.
4.17
DG_CPT_SOIL_CLASS_DATA
This table stores the soil classification polygon data. Users can add their own classification methods.
4.18
DG_CPT_SOIL_CLASS_METHOD
This table stores the names and graphing options for each soil classification method.
31
4.19
DG_CPT_SOIL_CLASS_ZONES
This table stores the descriptions and graphics for each soil classification zone.
4.20
DG_CPT_SOIL_TYPE
This table is a simple lookup for the soil type options.
32
4.21
DG_CPT_SYMBOLOGY
This table stores the library defaults for line colour and types etc. The field references are used by reports and should not be altered.
4.22
DG_CPT_SYMBOLOGY_SCALES_UNITS
Stores parameter scales for each Unit System.
4.23
DG_CPT_TERMINATION
This table is a simple lookup of reasons for terminating a CPT stroke, based on the GEF standard.
4.24
DG_CPT_TEST_METHOD
List of test standards.
4.25
DG_CPT_TRANSFER_SUMMARY_DESC_CONSISTENCY
This table stores the target table and field names soil description and consistency data summary transfer.
4.26
DG_CPT_TYPE
List of AGS Format CPT Types.
4.27
DG_CPT_ZERO_LOCATION
This table is a simple lookup for zero location.
4.28
DG_IMPORT_USER_IMPORT_PARAMETERS
Stores user import parameters for the Import Tool.
4.29
DG_LOG_CONSISTENCY_DENSITY
This table stores the soil consistency and relative density terms and ranges. These are used to calculate the fields Relative_Density_Term_# and Undrained_Shear_Strength_Term_# on CPT_DATA table. Configure DG_LOG_CONSISTENCY_DENSITY library table to be consistent with your soil description standard. By default, the table is configured with date consistent with Australian Standard, ASTM and New Zealand Geotechnical Society. We have configured example data for BS 5930 in DG_LOG_CONSISTENCY_DENSITY_BS_00.xlsx, and if required you can delete the data in the library table and copy/merge in the data from the Excel file.
33
34
Data Import
The Data Import Tool allows you to import data from various file formats into gINT. The command is located in INPUT Add-Ins > Datgel CPT Tool > Data Import.
On load the default setting will populate the form. In addition, the previous correspondence file used for each file type be loaded as default.
5.1

Tools Menu
Load Defaults: Loads all selections, field values and the initial directory that has been previously saved as default. Save Defaults: Saves defaults for File Browse Type, Friction Sleeve Offset, and Overwrite Option. Set Initial Directory: Sets the initial browse directory so that every time you browse, it will start at the set directory. About: Displays the version information of the Data Import Tool.
5.2

File Browse Types

Individual Files: Select one or more files in a single folder manually. Folder: Select a folder and all relevant files in that folder are selected automatically. Folder and Sub-Folders: Select a folder and all relevant files in that folder and its sub-folders are selected automatically.
Files paths may be manually entered or deleted from the large text box.
5.3

File Types
A.P. van den Berg Gorilla! (*.*) CPT and Dissipation Access database files (*.gpj; *.mdb) AGS (*.ags) Datem Neptune (*.cdf)
35
Delimited Depth qc fs u (*.*) simple file with no header, and data delimited by tab, ",", ";", or ":". The u data is not required, and the columns must be in the order Depth qc fs u. The file name (without the extension) will be used as the PointID. Douglas Partners (*.*) GEF 1.1.0 (*.gef) CPT and Dissipation. The friction shift is applied for 1.0.0 version files only See: http://www.geffiles.org/
Geomil PlotCPT (*.T*) gINT CSV (*.csv; *.txt) regular gINT compliant csv file. gINT Excel (*.xls) regular gINT compliant excel file. Gregg Drilling and Conetec (*.cor) Hogentogler (*.cpd) Pagani (*.cpt) Pagani (*.dat) ProbeDrill (*.txt; *.dis) you must import *.txt and *.dis files together. The *.dis file and *.txt file for the one location MUST has the same file name Swedish Geotechnical Format (SGF), used by Geotech AB and Envi A.B. (*.cpt; *.dpt; *.ini) See: http://www.sgf.net/home/page.asp?sid=862&mid=2&PageId=21095
Vertek (*.ecp)
5.4
Overwrite Option
These are the standard gINT overwrite options.
5.5
Correspondence File
gINT correspondence files need to be developed or altered to meet the needs of each companies gINT project database for each data source file type. We have provided example files that meet the needs of Datgels standard project files.
5.6
Advanced Options
Click on the Advanced button to show the Advanced Options panel. To hide the Advanced Options panel once it is open, click on the Simplified button.
36
There are two features in the Advanced Options panel, Create Temp Import File and User Import Parameters.
5.6.1
Create Temp Import File
During the import process the initial data files are read and transferred to a temporary file in gINT compatible CSV format. If this box is checked, the Data Import Tool will bring up a new window showing the contents of this temporary file, and will not continue with the import. This can be saved as a CSV, and used as the source when designing an import correspondence file.
37
In this interface, click Save As to save the text as a file, or Print to print the text on a printer. You must save the text as a file before you can modify the text. This file can be imported into gINT with the Data Import Tool with gINT CSV selected as the File Type.
5.6.2
User Import Parameters
The User Import Parameters feature allows you to insert custom fields into the tables in the temporary import file, thus allowing you to reference the custom field in the correspondence file, and import the parameter value into gINT. The benefit of this is that you may import values that are not in the data file without needing to modify the data file itself. The User Import parameters configuration is stored in a library table called DG_IMPORT_TOOL_USER_IMPORT_PARAMETERS. This table must exist in the current library to use the User Import Parameters, if it does not exist then the grid will be disabled. To save the User Import Parameters to the configuration table, go to Tools > Save User Import Parameters to Library. The User Import Parameters currently only works for Swedish Geotechnical Format (SGF) (*.cpt; *.dpt; *.ini) files. The Parameters will be created as fields in all tables in the temporary import file, and will be prefixed with UIV, followed by a space. Each row of the table will have the specified value in the column. This will apply for all files selected for import.
38
Description of the columns are as below: Parameter The name of the parameter. The parameters will be created as fields in all tables in the temporary import file, and will be prefixed with UIV, followed by a space. E.g. UIV Baselate Penetration. Unit The unit of the parameter. This field is metadata and is optional. It does not affect the User Import Parameter in any way. Value The Value of the parameter. Each row of the table will have the specified value in the corresponding parameter column. Description Description of the Parameter. This field is metadata and is optional. It does not affect the User Import Parameter in any way.
5.7
Importing Multiple Strokes/Tests into one PointID
The Depths in all strokes within the one PointID must have the same zero depth reference, hence if multiple strokes are done down a borehole, then when importing the Depth field must be populated with pre-drill Depth plus the push depth. This can be achieved in the correspondence file if the predrill depth in recoded in the source data file. Gorilla files are a common offshore data file format, and we have seen files with the start depth of each test recorded in fields titled Reference Level and Depth Borehole.
[TEST] <GORILLA! header> job number=BH-CPTU-S8-BL client=PETRONAS CARIGALI job description=SEPAT 8 LOCATION . . . operator=ZAHID/HILMI CPT Tool gINT Add-In 3 User Guide Datgel DCT-UG-001 - 3.02 - August 2012
39
reference level=3.0 reference point=M.S.L pre drilled=0.0 GORILLA!-remark 1= . . . GORILLA! serie #= <user header> NORM=KTN/PCSB/08/268/SI START DEPTH= Seabed ref level= Seabed ref point= Depth borehole=3.0 Vanedepth= [SCALING FACTORS] . . . [DATA] *D:0.02#1:0.01#2:0.000#4:4#0:28! *D:0.04#1:0.01#2:0.000#4:4#0:29! *D:0.06#1:0.03#2:0.000#4:3#0:30! *D:0.08#1:0.04#2:0.001#4:4#0:31! *D:0.10#1:0.05#2:0.001#4:4#0:32!
Gorilla File Example with relevant depth information highlighted Two correspondence files read the start depth from the different fields and calculate the true depth of each reading below the borehole reference level (typically seabed). datgel_cpt_tool_dgd_X.XX_gorilla_cpt_Depth_Borehole_##.gci datgel_cpt_tool_dgd_X.XX_gorilla_cpt_Reference_Level_##.gci
After importing a set of test files for one PointID, you will need to manually set the POINT.HoleDepth field with the correct maximum depth of the test.
5.8
Importing only the File Name from the Full File Path
If the full file path of the source file is being imported, but you only want to import the file name, you can modify the gINT correspondence file (.gci) to extract the file name from the full file path to import into gINT. Open the gINT correspondence file in a text editor, and then search for the field name where the file path is being directed to (for example, File_Reference). Replace the existing expression with the following:
<<GetListItem<<Original Expression>>,"\",<<ListCount(<<Original Expression>>)>>,"\")>>)>>
Where <<Original Expression>> is the original expression that retrieves the full file path for that particular field.
40
CPT Filter
The tool can filter out rod change noise for and . The filter algorithm works based on Penetration_Rate (mm/s), and if it is not in the data file, then it is calculated based on elapsed time. You can set the Filter_Threshold_Penetration_Rate on the CPT_PROJECT_PARAMETERS and CPT_POINT_PARAMETERS, or use the default of 6 mm/s. If you manually run the filter then the threshold rate increases 1 mm/s each run per CPT push, i.e. the applied threshold rate = Filter_Threshold_Penetration_Rate + Filter_Count Data is only filtered if it is less than 95% of the mean of the previous two values, and the third and fourth values ahead. In order for the be defined. filtering to take place, the Cone_Sleeve_Offset on the CPT_CONE_INFORMATION table must
If the Auto_Filter_Calculation on the CPT_PROJECT_PARAMETERS or CPT_POINT_PARAMETERS tables is set to Automatic (whichever is lower in the hierarchy with data), then the Filter will run once on import and set the Filter_Count field on the CPT_GENERAL table to 1. If Filter_Count field on the CPT_GENERAL table is set to less than 1 or null, the filter will run On Save. The filter may be run manually more times using the command INPUT | Add-Ins > Datgel CPT Tool > CPT Filter. However the cursor must be in the bottom half of the CPT_DATA table.
41
7
7.1
Groundwater and Overwater Testing

Groundwater Depth for Standard Onshore Testing
The ground water depth is critical to many derived results, and can be defined in a number of ways. In order of priority: 1. 2. 3. 4. CPT_GENERAL table, Groundwater_Depth field CPT_POINT_PARAMETERS table, Groundwater_Depth field CPT_PROJECT_PARAMETERS table, Groundwater_Depth field CPT_PROJECT_PARAMETERS table, Groundwater_Elevation field
In the CPT_PROJECT_PARAMETERS table, the Water_Density_Field field is also required, and should be set appropriately for fresh or salt water. On the CPT_GENERAL table define: CPT_GENERAL.Water_Depth: Nothing CPT_GENERAL.Zero_Location: S Surface or Nothing CPT_GENERAL.Pre_drilled_Depth: Nothing or value as required, doesnt influence calculation CPT_GENERAL.Groundwater_Depth: Distance from ground level (0 depth) to the groundwater surface, or use Groundwater_Depth fields on other tables listed above
In situ pore pressure is calculated relative to the atmospheric pressure using the following formula:
Where: is the depth below the reference level is the groundwater depth below the reference level is the unit weight of water (defined as density in CPT_PROJECT_PARAMETERS.Water_Density_Field)
7.2

Overwater Testing
CPT_GENERAL.Water_Depth or CPT_POINT_PARAMETERS.Water_Depth CPT_GENERAL.Zero_Location CPT_GENERAL.Pre_drilled_Depth CPT_GENERAL.Groundwater_Depth
The critical fields related to pore pressure calculation for over water testing are:
42
If CPT_GENERAL.Water_Depth or CPT_POINT_PARAMETERS.Water_Depth fields have data then only CPT_GENERAL.Groundwater_Depth will be used, and the Groundwater fields on CPT_PROJECT_PARAMETERS are ignored. This is only the case for over water testing. In the CPT_PROJECT_PARAMETERS table, the Water_Density_Field field is also required, and should be set appropriately for fresh or salt water. The following sections describe how to handle the various overwater scenarios. The aim of corrections is to make the derived data in all strokes within the one PointID comparable. Derived parameters for tests using scenarios Zero at Seabed and Zero at Bottom of Borehole are comparable after the zero corrections have been applied, and the results are relative to the seabed.
7.2.1
Zero on Deck / Surface
In this case the transducers, including depth, are zeroed on deck (at atmospheric pressure). Measured parameters dont require zero corrections. Define CPT_GENERAL.Water_Depth or CPT_POINT_PARAMETERS.Water_Depth: Distance from seawater surface to seabed surface (required for Total Stress) CPT_GENERAL.Zero_Location: S - Surface CPT_GENERAL.Pre_drilled_Depth: Nothing or value as required, doesnt influence calculation CPT_GENERAL.Groundwater_Depth: Distance from deck level (0 depth) to the seawater surface
In situ pore pressure is calculated relative to the atmospheric pressure using the following formula:
Where: is the depth below the reference level is the groundwater depth below the reference level is the unit weight of water (defined as density in CPT_PROJECT_PARAMETERS.Water_Density_Field) Total Stress and Effective Stress are calculated relative to deck/ground surface.
7.2.2
Zero at Seabed
In this scenario the transducers are zeroed at the seabed, with the hydrostatic pressure at that water depth. Define: CPT_GENERAL.Water_Depth or CPT_POINT_PARAMETERS.Water_Depth: Distance from seawater surface to seabed, doesnt influence calculation CPT_GENERAL.Zero_Location: SB - Seabed CPT_GENERAL.Pre_drilled_Depth: Nothing or value as required, doesnt influence calculation
43
CPT_GENERAL.Groundwater_Depth: Nothing
The in situ pore pressure, total stress and effective stress are calculated relative to the seabed, hence:
Where: is the depth below the seabed is the unit weight of water (defined as density in CPT_PROJECT_PARAMETERS.Water_Density_Field) is the unit weight of saturated soil
7.2.3
Zero at Bottom of Borehole
This scenario applies when testing overwater and the transducers are zeroed the bottom of a predrilled borehole. It is common for multiple 3 m strokes to be done down a borehole, possibly alternated with other in situ tests and sampling. The corrections allow the multiple pushes to be comparable, by correcting the readings relative to the seabed surface. Define CPT_GENERAL.Water_Depth or CPT_POINT_PARAMETERS.Water_Depth: Distance from seawater surface to seabed, doesnt influence calculation CPT_GENERAL.Zero_Location: BB Bottom Borehole CPT_GENERAL.Pre_drilled_Depth: Distance from seabed to bottom of borehole (where CPT started) CPT_GENERAL.Groundwater_Depth: Nothing
In this scenario the calculation code:
and
will be corrected using the following formulas before they are used by the
The in situ pore pressure, total stress and effective stress are calculated relative to the seabed, hence:
The CPT Tool calculation assumes data in the Depth field = d + z Lunne et al. (1997) and Fugro (1995)
44
Where: is the cone resistance corrected is the cone resistance measured is the pore pressure corrected is the pore pressure measured is the cone area ratio is the unit weight of water (defined as density in CPT_PROJECT_PARAMETERS.Water_Density_Field) is the pre-drilled depth, depth from the seabed to bottom of the borehole where the CPT started is the depth below the bottom of the borehole is the unit weight of saturated soil 1. The depth reference level for all strokes in a PointID must be the same. Hence, when importing pushes with the reference depth at the bottom of the borehole the correspondence file must include the calculation Depth = d + z. 2. Dissipation tests measured pore pressure and in situ pore pressure are corrected as described above. And again Depth of the Dissipation test must = d + z.
45
8
1.
Bulk Unit Weight and Void Ratio

CPT_POINT_MATERIAL_PROPERTIES table (Point Parameters Bottom half). This allows the user to enter a depth profile. If a depth range is missing a value, then the CPT_PROJECT_PARAMETERS table is used. CPT_PROJECT_PARAMETERS table. A saturated and unsaturated unit weight must be defined, the former is applied bellow the water table and the later above the water table.
Unit Weight and Void Ratio may be defined in two locations and are used in the order listed:
2.
If Unit Weight and Void Ratio are not defined in either table, then the Bulk Unit Weight and Void Ratio will not be defined, and most other parameters cannot be calculated.
46
9
9.1
Initiation of the CPT Data Calculation

Primary Table Calculations
The primary CPT calculation is initiated by changing data then saving on the following tables (or the split screen parent of these tables): POINT CPT_GENERAL CPT_DATA, and any one to one child tables of CPT_DATA CPT_DATA_ENVIRONMENTAL CPT_DATA_LIQUEFACTION CPT_DATA_LOWER_BEST_UPPER CPT_DATA_PILE CPT_CONE_INFORMATION CPT_DESIGN_LINE CPT_DESIGN_LINE_DATA CPT_FOUNDATION_POINT_PARAMETERS CPT_FOUNDATION_POINT_PARAMETERS_PROFILE CPT_FOUNDATION_PROJECT_PARAMETERS CPT_LIQ_POINT_PARAMETERS CPT_LIQ_PROJECT_PARAMETERS CPT_POINT_CORRELATION_PARAMETERS CPT_POINT_MATERIAL_PROPERTIES CPT_POINT_PARAMETERS CPT_PROJECT_CORRELATION_PARAMETERS CPT_PROJECT_PARAMETERS
Additional tables can be configured to initiate the CPT calculation. This is set in the CPT_FIELD_MAP library table, by checking the Change_Initiates_Calc check box for the table record. See the appendix for instructions on setting up a new CPT Table, and configuring it to initiate the CPT calculation if values have changed. The calculation will only take place if a Pastel Beige coloured field has been modified on the above tables. This allows you to change metadata fields that do not have any effect on the calculation without having to recalculate the CPT test. The exception to this is the CPT_DATA table, and one to one child tables of CPT_DATA. The calculation will occur if any cell has been modified, regardless of colour. The CPT calculation on POINT will only run when an existing POINT record has records on the CPT_DATA table, and the Elevation has changed and the new Elevation has a value.
47
The automated CPT calculation when saving on these tables can be stopped by checking Suppress_Automatic_Calculation on CPT_PROJECT_PARAMETERS. If it is checked, then the CPT will be flagged for pending calculation (see section 9.2). The calculation will not run when converting projects. Unless the Suppress_Calculation_on_Import on CPT_PROJECT_PARAMETERS is checked, the calculation will take place upon import. The table below lists the action taken on import under all combinations of the Suppress_Calculation_on_Import and Suppress_Automatic_Calculation values.
Suppress Calculation on Import FALSE TRUE FALSE TRUE Suppress Automatic Calculation FALSE FALSE TRUE TRUE Action Taken CPT calculated CPT not calculated, not flagged pending calculation CPT Calculated CPT flagged pending calculation
When calling gINT Rules > Recalculate Current Table from a CPT Table, a form will display, giving you the following options:
Yes: will recalculate all CPTs in the project, this is equivalent to changing a value on the Project Parameter table. This is the fastest way to revaluate the entire database of CPTs. A progress bar will be shown to display the progress of the calculation. This is normally the option to pick. No: will use gINTs native recalculate current table, which can be a very inefficient way to calculate the database of CPTs. This option is not recommended. Cancel: Cancels the call, and nothing is calculated.
9.2
Batch Calculation
The Batch Calculation feature allows the user to make changes to their CPT data, and flag the affected CPTs as pending for calculation instead of running the calculation immediately. An example of where this feature may be useful is if you needed to enter the groundwater depth for each CPT on the CPT_GENERAL table. It is much more convenient to calculate the CPTs after you have entered the groundwater depth for all tests at once rather than calculate each time you change of the groundwater depth. A CPT is flagged for calculation by inserting the current date time into the Calculation_Pending field on the CPT_GENERAL table. When the CPT is calculated, the Calculation_Pending field is cleared for that CPT. The CPT Tool will flag CPTs for batch calculation in place of running the CPT calculation, if the Suppress_Automatic_Calculation checkbox on CPT_PROJECT_PARAMETERS is checked. Like the CPT calculation, the Batch Calculation feature will flag all CPTs that were affected by the change. For
48
example, changing the values for a Cone ID record in the CPT_CONE_INFORMATION table will flag all CPTs that reference the modified Cone ID for batch calculation. The Batch Calculation Form allows you to view a list of flagged CPTs that are pending calculation, and calculate all, or a selection of CPTs. To launch the Batch Calculation Form, call the command INPUT | Add-Ins > Datgel CPT Tool > Batch Calculation, or press Ctrl + Shift + B. You should see a window similar to the following.
The form will display a list of the CPTs that have been flagged as pending calculation on the Pending Tests to Calculate grid. When OK is clicked, the Batch Calculation Form will initiate the calculation for the CPTs that are listed on the Selected Tests to Calculate grid. You may use a combination of left click, left click-drag, ctrl + click and shift + click to select the desired CPTs, and the arrow buttons in the middle to move CPTs to the right or left grid. An explanation of the commands is as below: Show All Tests Check this to show all CPTs in the Pending Tests to Calculate grid, regardless of if they have been flagged pending calculation. Uncheck to hide the non-flagged CPTs. Clear All Pending Clears the Calculation Pending flag on all CPTs without calculating them. Select All Pending Selects all CPT calculations pending OK Closes the form and initiates the CPT calculation for CPTs listed in the Selected Tests to Calculate grid. Calculated CPTs will be cleared of the Calculation Pending flag. A progress form will appear to display the progress of the calculations. Cancel Closes the form without calculating any CPTs.
9.3
1. 2. 3. 4.
Order of Calculation
Derived parameters Soil Behaviour Type Formula Tool Library formulas Formula Tool Project formulas
The order of calculation is:
49
9.4
Calculation settings
The calculation settings form may be displayed be either calling the command Add-Ins > Datgel CPT Tool > Settings, or clicking on the Settings hyperlink located in the bottom left corner of the batch Calculation form.
Batch Calculation Batch Size Denominator: The denominator of the fraction applied to available memory in order to calculate the size of each sub-batch. The default value is 32, meaning that 1/32nd of available memory will be used to store each sub-batch's data. Log Formula Exceptions: Include errors from the Formula Tool formulas in the Batch Calculation Report, in order to help optimise the performance of formula calculations
Threading Maximum Threads Per Processor: Each CPT calculation is performed in a separate multitasking process called a "Thread". The maximum number of CPT calculations (Threads) that can be concurrently handled by a processor. 1 or 2 are the only recommended values. Processor Count Method: The number of CPUs on a computer can be calculated in a number of ways, depending on the number of actual CPUs installed, the number of cores in each CPU and whether the CPU has hyperthreading capabilities. The default value is "UseLogicalProcs", which includes cores and hyperthreading. Batch Queue Priority Size Factor: CPT calculation Threads retrieve raw data from a Queue. Priority can be given to Threads that insert raw data on the Queue by setting this factor to a number higher than 1. This number should not be changed unless you are instructed to do so by a member of the Datgel technical support team. Batch Queue Size Factor: CPT calculation Threads retrieve raw data from a queue. This setting controls the maximum size of the queue as a factor of the Thread Pool's maximum size. The default setting is 2. Only values between 2 and 4 are recommended. Thread Pool Size Factor: CPT Calculation Threads are recycled to save memory usage. This value sets the number of Threads the Thread Pool manages as a factor of the maximum concurrent Threads ("Maximum Threads per Processor" x "Number of Processors". The default factor is 3. Only values between 3 and 6 are recommended.
50
9.5
Dissipation Test
The Dissipation test calculation is independent of the rest of the CPT table calculations. You may need to manually make the Dissipation test recalculate after changing relevant CPT parameters / data for a PointID.
51
10 Derived Parameters
The following table presents the derived parameters. These calculations are hard coded, and are calculated before the Formula Tool. Table 2 - Derived Parameters
DGD Field Name Penetration_Rate Bulk_Unit_Weight In_Situ_Pore_Pressure Excess_Pore_Pressure Normalised_Excess_Pore_ Pressure Total_Stress Effective_Stress Total_Cone_Resistance STCT_TOTS STCT_EFFS STCT_QT STCT_BUW STCT_PWPI STCT_PWPE Bulk Unit Weight In Situ u Delta u Normalised Delta u Total Stress Effective Stress qt Normalis ed AGS RTA Field Name Caption Symbol Unit Description Rate calculated based on Time_Elapsed and Depth Bulk unit weight, In situ pore pressure, , refer to section 7 for a full explanation. Excess pore pressure, Normalised excess pore pressure, normalised In situ total vertical stress, In situ effective vertical stress, Total cone resistance, ; or if the instrument is zeroed at the bottom of the borehole (downhole) Total_Cone_Resistance_Mo ving_Average Total_Cone_Resistance_Mo ving_Average_Inc Net_Cone_Resistance Corrected_Sleeve_Friction STCT_QNET STCT_FT Moving Average qt Moving Average qt Included qn ft Moving average qt over distance defined on CPT_PROJECT_PARAMETERS Moving average qt that are not excluded over distance defined on CPT_PROJECT_PARAMETERS Net cone resistance, Sleeve friction corrected for pore pressure effects,
( )
Friction_Ratio
STCT_FRR
Rf
Friction ratio, ,
, or
See section 10.1 for additional information. Normalised_Friction_Ratio STCT_FR Fr Normalised friction ratio,
If is not found, and if Calc_Qt_Fr_based_on_qc on CPT_PROJECT_PARAMETERS is set to true, then is used in place of .
52
DGD Field Name Normalised_Cone_Resistan ce
AGS RTA Field Name STCT_QNOR
Caption Qt
Symbol
Unit -
Description Normalised cone resistance,

( )
If is not found, and if Calc_Qt_Fr_based_on_qc on CPT_PROJECT_PARAMETERS is set to true, then is used in place of . Stress_Normalised_Cone_R esistance Stress_Normalise d_Cone_Resistan ce qt1 Stress normalised cone resistance (Kulhawy and Mayne 1990, Jamiolkowski et al 2001),
Pore_Pressure_Ratio
STCT_BQ
Bq
Pore pressure ratio,
Differential_Pore_Pressure_ Ratio Dimensionless_Penetration _Resistance
STCT_DPPR
DPPR
Differential pore pressure ratio,
Qt(1-Bq)+1
)+1 -
Dimensionless penetration resistance
10.1
Friction Ratio Calculation Method
The field Friction_Ratio_Calculation_Method on CPT_PROJECT_PARAMETERS defines the method of calculation. The options are: qt or qc on same row as fs: All data is taken form the same row, this is the default Average qt or qc over sleeve: Uses average (arithmetic mean) qt or qc over range of sleeve
53
11 Depth Correction Due to Inclination

The Depth Correction Due to Inclination feature allows you to calculate and apply the depth correction to the Depth field in the CPT_DATA table, according to the formula detailed below. When this calculation is applied, Depth values in CPT_DATA are moved to Penetration_Length, and the corrected depth is written to Depth. The depth of cone penetration tests can be corrected for inclination by the equation: Where: is the penetration depth, in m. This value is written to Depth. is the penetration length, in m. This value is taken from Depth, and is copied into Penetration_Length. is a correction factor for the effect of the inclination of the cone penetrometer relative to the vertical axis Equations for the calculation of the correction factor for the influence of the inclination of the cone penetrometer relative to the vertical axis, on the penetration depth: a) For a now-directional inclinometer,
Where: is the measured angle between the vertical axis and the axis of the cone penetrometer, in . This value is taken from Slope_Indicator in CPT_DATA.
b) For a bi-axial inclinometer,
Where: is the angle between the vertical axis and the axis and the projection of the cone penetrometer on the fixed vertical plane, in . This value is taken from Slope_Indicator_1 in CPT_DATA. is the angle between the vertical axis and the axis and the projection of the cone penetrometer on a vertical plane that is perpendicular to the plane , in . This value is taken from Slope_Indicator_2 in CPT_DATA. The Depth Correction function will use the bi-axial correction factor if Slope_Indicator_1 and Slope Indicator_2 have data. The now-directional correction factor will be used if Slope_Indicator has data. Bi-axial has precedence over now-directional. If Slope_Indicator, Slope_Indicator_1 and Slope_Indicator_2 all have data, then bi-axial correction factor will be used.
54
11.1
Applying the Depth Correction due to Inclination Calculation
The command apply the depth correction calculation is located in INPUT | Add-Ins > Datgel CPT Tool > Depth Correction due to Inclination. This command will only run from the CPT_DATA table, meaning you must be on this table before you can run the command. The depth correction calculation will only be applied if the Penetration_Length field is empty for all rows for the selected CPT. This is to ensure that the depth correction calculation is only applied once. If you wish to recalculate or reapply the correction, you must either clear the values in the Penetration_Length field, or cut/paste the Penetration_Length values to the Depth field. The depth correction calculation can only be run if the Depth and Penetration_Length fields are in the same units (e.g. ft or m), and the units of Slope_Indicator, Slope_Indicator_1 and Slope_Indicator_2 are in degrees. Alternatively, the command INPUT | Add-Ins > Datgel CPT Tool > Depth Correction due to Inclination for multiple Strokes can be used to apply the depth correction calculation to all or selected list of CPTs. This command can be run from any table in INPUT. You should see a window similar to the following:
You may use a combination of left click, left click-drag, ctrl + click and shift + click to select the desired CPTs, and the arrow buttons in the middle to move CPTs to the right or left grid. Click OK to apply the depth correction calculation. The progress bar and label on the bottom right will display the current status of the calculation process. The depth correction calculation will only be applied if the Penetration_Length field is empty for all rows for a particular CPT, and the program will skip the CPT if a Penetration_Length value is found for a CPT. A list of skipped CPTs will be displayed at the end of the calculation process.
55
12 Formula Tool
12.1 Introduction
The Formula Tool allows you to review and edit the preconfigured correlation formulas provided with the CPT Tool, and provides a way for you to define new correlation formulas. A tutorial on defining a formula is presented in Appendix B. To launch the Formula Tool Configuration form, call the command INPUT | Add-Ins > Datgel CPT Tool > Formula Tool Configuration. You should see a window similar to the following.
56
12.2
Formula Toolbar
Hovering the mouse cursor over each item will show a tooltip with a short description of the item.
Name New Formula Save Formula Icon/Image Keyboard Shortcut Ctrl + N Ctrl + S Description Creates a new empty formula Saves all changes to the gINT Library or Project database, depending on the selected Location Deletes the currently selected formula Reverts any changes made to the current formula to the state it was last saved Makes a copy of the currently selected formula, and adds it to the end of the Formula Grid. After copying, the copied formula will be selected, and you must enter a new unique name. Checks the Enabled check box column for all formulas in the Formulas Grid Unchecks the Enabled check box column for all formulas in the Formulas Grid Location the Formula Configurations are stored. Select Library to load the Configuration stored in the current gINT Library, and Project to load the Configuration stored in the current gINT Project. At the time of CPT calculation, The Library formulas will be evaluated and calculated first, followed by the Project formulas. Hence a formula in the Project can override a formula in the Library. Generates a report containing full details of the currently selected formula, evaluated validation result and any errors or missing Table Field references in the current formula. Clicking the button will prompt you for a new text file path, and then automatically open the text file in a text editor program after the report has been generated. Generates a report containing full details of the all formulas showing in the formula grid, evaluated validation result and any errors or missing Table Field references for each formula. Clicking the button will prompt you for a new text file path, and then automatically open the text file a text editor program after the report has been generated. Shows the Merge/Copy Formulas Form. See the Merge/Copy Formulas section below for full details.
Delete Formula Undo Changes Copy Current Formula
Ctrl + D Ctrl + U Ctrl + Shift + C
Enable all Formulas Disable all Formulas Location
Generate Validation Report for Current Formula
Generate Validation Report for All Formulas
Merge/Copy Formulas
57
12.3
Data Tool Toolbar
Name Refresh Data Tool Icon/Image Keyboard Shortcut Ctrl + R Description Clears, re-reads and reloads the Table and Field drop down list items from the current gINT Project and Library. Use this to update the drop down list if you have added a new table or field after the Formula Configuration Form has been opened. Pastes the selected table and field as formatted text into the last focused configuration field. Refer to the Table Field Data Tool section of the manual for detailed information Pastes the selected function text into the last focused configuration field. Refer to 25 for detailed information
Table Field Data Tool
Function Data Tool
12.3.1
The Table Field Data Tool pastes the selected table and field as formatted text into the last focused configuration field. The drop down list contains all tables and fields in the current gINT Project and Library database. When a Table is selected, the Field list will automatically filter to show only the fields for the selected table. The Table and Field drop down lists consist of three columns:
Table Name/Field Name database name of the Table or Field Caption The caption text as configured in the Caption field in the gINT Table or Field Properties Description The description text as configured in the Description field in the gINT Table or Field Properties
The drop down list can be sorted by a column by clicking on the column header. The columns can be resized by clicking and dragging the edges of the column header left or right. The drop down list window can be resized by clicking and dragging the bottom right corner of the window. The drop down list lists the Project tables first, then the Library. A delimiter row as seen below divides the Project Tables from the Library Tables.
58
The Paste button will insert the selected table field into a formatted, table field reference text into the last focused configuration text field or grid cell. The Paste button can insert text into the following Configuration fields: Description Any cell in the Variables Grid Formula Write Value To
The table field reference format is as below:

<<Table Name.Field Name>>
Table field references in the Formula field are required to be surrounded by quotation marks. The Table Field Data Tool will automatically add the quotation marks if pasting in the Formula field. The table field reference format for the Formula field is as below:
"<<Table Name.Field Name>>"
The pasted text will be inserted at the current position of the cursor in the fields. Any highlighted text will be replaced by the inserted text. Selecting an entire cell in the Variables grid will replace the contents of that cell with the inserted text.
12.3.2
Function Data Tool
The Table Field Data Tool pastes the selected function text into the last focused configuration field. The Function drop down list contains all functions, constants and operators that are available in the Formula Tool, it the correct syntax. Each function is categorised as a type, and selecting a type in the Type drop down list will filter the function drop down list by that type.
The Function drop down list consists of three columns: Type type of function, can be filtered by a particular type by selecting a type in the Type drop down list Function the function, constant or operator in the correct syntax as required by the Formula Tool. The typical syntax composition of a function consists of the function name, followed by
59
an open bracket, followed by a comma separated list of function parameters, followed by a closed bracket. FunctionName(Parameter 1, Parameter 2 [,...]) The function name is case sensitive. All function parameters are required, unless noted otherwise. If a function accepts an arbitrary number of parameters, it is denoted by ... . Description A short description about the function
The Paste button will insert the selected function into last focused configuration text field or grid cell. The Paste button can insert text into the following Configuration fields: Description Any cell in the Variables Grid Formula Write Value To
Refer to section 27 Formula Tool and Data Correction Tool Functions for detailed information about the functions.
12.4
Formulas Group
The Formulas Group contains a list of formulas stored in the currently selected location. Each row in the Grid represents one formula, and is listed in the order they are to be evaluated from first to last. Selecting a formula by either by clicking on a row, or pressing the up or down keys in the Grid will display the configuration associated with the selected formula in the Configuration Group. The Name column values cannot be changed in this grid. It must be done in the Configuration Group after the formula has been selected. The Order of the formula can be changed in the Formulas Group with the up down buttons on the top left. Descriptions of the bottom are listed below from top to bottom: Move to Top Moves the currently selected formula to the top of the grid Move Up Moves the currently selected formula up by one row
60
Move Down Moves the currently selected formula down by one row Move to Bottom moves the currently selected formula to the bottom of the grid
The formulas can be enabled or disabled by clicking on the corresponding check box in the Enabled column. When the formula grid is active, pressing the Spacebar key will also toggle the enabled check box for the currently selected rows. You can select multiple rows by left clicking and dragging down on the row header, or by holding the ctrl key while left clicking on the row headers.
12.5
Configuration Group
The Configuration Group contains all the configurable options for the formula that is currently selected in the Formulas Grid. Name Name of the formula. The formula name must be unique for the configuration location. This means that you may have two formulas with the same name with one in current Library and one in the current Project. You will not be able to select another formula, or save the formula until a unique name is entered. Order A numeric value of the order the formula will be evaluated. If the result of the current formula is required to evaluate another formula, then the current formula should be placed at a higher order to than the other formula. The order cannot be changed in the Configuration Group. Move the selected formula up or down using the up down buttons left of the Formulas Grid. The numeric Order value will update itself when the order has changed. Iteration - The round of iteration in which the current formula will be evaluated. Default value is 1. Functions which calculate the average of a correlation that is evaluated by the Formula Tool need to be run at a later iteration to the correlation. Description Description of the formula. It is not used or required in the formula calculation, and hence it is an optional field.
61
Table/Field References to Variables Declare the variables that are used in the formula expression in this grid. The rows in this grid can be changed with the up down buttons on the left of this grid. Column definitions are listed below: Variable Name Name of the variable. The variable name can consist of alphanumeric characters [a-z, A-Z, 1-9], but must have at least one alphabetic character, and is case sensitive. It cannot contain the following: o Symbols, such as `, $, # o White spaces or carriage return In addition, a duplicate variable names for a particular formula is not permitted, and a variable name cannot be exactly the same as a function name. Expression Table Field reference to where the variable value is to be retrieved from, or a text or numeric value. The following is a list of rules and specifications regarding the Expression: o Table Field references must be in the format of <<Table.Field>> o If the referenced field is from the CPT_DATA table, then it will take the value from the field of the current row the CPT Tool is calculating. o If the referenced field is from any other table, it will retrieve the first result from a query to that table, filtered by the PointID and ItemKey values of the current CPT calculation, where appropriate. o To use the variable as a constant, enter a numeric value, or text that is not in the format of <<Table.Field>> Unit Unit the value is required to be in to be used in the formula expression. The Formula Tool will convert the variable from its source unit to the unit defined in this column before the value is used in the formula. The source unit can only be retrieved if the value in the Expression is a table/field reference, and is taken from the Unit field property of the named field. If no unit is specified, then the variable value is used as-is. If a unit is specified, but a conversion factor cannot be determined, then the value is null. Validation Value Value used to evaluate the formula when the Validate button is clicked, and in the Validation Reports. The Validation Value has no effect on the actual CPT calculation, and is solely used in the Formula Configuration Form.
Formula The formula expression. Refer to section 27 Formula Tool and Data Correction Tool Functions for a full list of available functions. Variables declared in the Variables Grid above can be referenced in the formula expression. String constants must be surrounded with quotation marks "" in order to differentiate it from a variable reference. Spaces and carriage returns may be used liberally to improve readability. Table field references in the formula expression must be surrounded by quotation marks, i.e. "<<Table.Field>>". The Table Field Data Tool will automatically add the quotation marks when pasted in the formula expression field.
Write Value To The Table Field reference to where the result of the formula evaluation is to be written to. The value in this field must be in the <<Table.Field>> format, and must be from the CPT_DATA table or a one to one child there of.. Validate Click this button to evaluate the current formula expression, with the Validation Value set as the Variables. If the evaluation was successful, the result will be written to the adjacent text field. The Formatting Type and Value will be applied to the result, if defined. Use Validate to spot check your formula expression for syntax errors, and to verify the formula returns an expected result. Result Unit Unit of the result of the equation. The evaluated result of the formula is converted from the Result Unit to the unit of the Write Value To field, if the two units are different. If Result Unit is empty, the value is not converted and is written to the Write Value To Field as-is. The lookup list of values in this field is sourced from the Field Units library table. Enabled Check or uncheck to enable or disable the formula respectively from evaluating in the CPT calculation
62
Formatting Type and Value Formats the result to either decimal or significant figures, to the nearest specified value. The formatting only applies to formula expressions that return a numeric value. OK Saves the current state of the formulas in the Formula Configuration form to the selected location, and closes the form. Cancel Discards any changes made in the Formula Configuration form and closes the form. The formulas will remain at the exact same state as before the Formula Configuration form was opened. You will be prompted to save if changes are detected.
12.6
Merge/Copy Formulas
The Merge/Copy Formulas Form facilitates the merging/copying of CPT Tool formulas between gINT Projects and Libraries. The Form will automatically handle the differences between the configuration tables in Project and Library, and also the differences between the current version and older versions of the formula configuration tables. The Form will allow you to choose which formula to merge, indicating whether the formula exists in the target gINT Project/Library. The Merge/Copy Formulas Form is accessible from the Formula Configuration Form. Open the form, then go to Tools > Merge/Copy Formulas, or click on the Toolbar Icon .
12.6.1
Source and Target Group
Select the source and target of the Formula Tool Formulas in these groups. The selected files must be a gINT Project (*.gpj) or a gINT Library (*.glb) file, and must contain a valid CPT Tool Formula Configuration Table. There are four ways to select a file: Browse Button Brings up a file selection dialog and allows you to navigate and select a gINT file
63
Current Library Selects the currently open gINT Library file Current Project Selects the currently open gINT Project file Text Box You may type in or copy/paste in the file path in the text box
By default, the Target file will be set to the current Formula Configuration source of the Formula Tool Configuration Form.
12.6.2
Validation
The source and target files must be validated before you can select Formulas to merge, or execute the Merge/Copy. If you have used the Browse Button, Current Library or Current Project buttons to select the file, the Form will automatically validate the file for you. If you have entered the file path manually, you must click on the Validate button to validate the selected file. The results of the validation can be seen next to the Validate button as a green or red coloured text. The possible values are listed below:
Validation Result OK (Library, Version 2) OK (Library, Version 3) OK (Project, Version 2) OK (Project, Version 3) Error Description Valid CPT Tool gINT Library (*.glb) version 2.17 and older, CPT Tool DLL version 2.2.0 and older Valid CPT Tool gINT Library (*.glb) version 2.18 and newer, CPT Tool DLL version 2.2.1 and newer Valid CPT Tool gINT Project (*.gpj) version 2.17 and older, CPT Tool DLL version 2.2.0 and older Valid CPT Tool gINT Project (*.gpj) version 2.18 and newer, CPT Tool DLL version 2.2.1 and newer Not a valid CPT Tool file
The Target Table field is missing from Version 2 CPT Tool gINT Files. Therefore, the Table from the Write Value To field is extracted from the value and used as the Table. You may override this by entering a table name in the Override Target Table text field. From CPT Tool gINT files 2.15 and older, the Result Unit field is missing. If you are merging formulas from these version of gINT Files, you must review the formulas after merging to ensure the Result Unit has been set. If the validation result is an error, mouse over the text to see a tooltip popup detailing the reason why the file could not be validated.
12.6.3
Override Target Table
Override Target Table allows you to manually set the target table, overriding the Table in the source. This is useful if for example, you were merging formulas into DGD CPT Tool from the AGS RTA CPT Tool files, the table names would be STCT in AGS RTA, and CPT_DATA in DGD. Enter the exact table name into this field, for example, CPT_DATA. If a value for Override Target Table is entered, the Formula Selection Form will use this value (and the Formula Name) to determine if a Formula exists in the Target file.
64
12.6.4
Selecting Formulas to Merge
Once the Source and Target files have been set and validated, click on the Browse Button on the Formulas to Merge into Target text field to bring up the Formula Selection Form.
The Formula Selection Form will not open under the following conditions, and you will be prompted with the reason. Source and Target files have not been validated, or validation has failed for either of the files Source and Target files are the same Target file is version 2 The Merge/Copy Formulas Form does not support merging formulas into older versions of the CPT Tool.
The left grid will list out all the available formulas found in the Source file. The Exists in Source column will specify if the Formula exists in the Target file, for the given Table and Name. If a value has been entered in the Override Target Table, it will use that value to determine the existing Formulas. To select the formulas to merge, use a combination left click, click-drag, ctrl + left click and shift + click to select the formulas from the left grid, and use the arrow buttons in the centre of the form to move formulas into the right grid. Click the OK button to return to the Merge/Copy Formulas Form. The selected formulas will be listed in the text box, and this is an indication that Formulas have been selected for merging.
You may click on the Browse Button to review and adjust your Formula selection. If you perform any of the following actions, the selected Formulas will be cleared, and you will need to reselect your Formulas to merge: Enter a different Source or Target file, by clicking on the Current Library, Current Project or Browse Buttons, or modifying the file path manually in the text field Modifying the Override Target Table value
65
12.6.5
Execution of Merge/Copy Formulas
When you have selected Formulas to merge, click on the Execute button to merge in the formulas into the Target file. If a Formula has been marked as Exists, the existing Formula in the Target is overwritten. If not, then a new Formula record will be created in the Target.
66
13 Data Correction Tool

13.1 Introduction
The Data Correction Tool allows you to apply one-off corrections to a selection of existing CPT data in your gINT Project. The two fundamental correction types are the application of a formula (Correction), and shifting a record up or down by a relative number of units, such as metres (Offset). Each correction is defined as a Formula and can either be an Offset or a Correction. The correction can be applied to any field from the CPT_DATA table, including Depth. However, if you are correcting Depth, you must ensure that the correction will not result in duplicate depth values for a given CPT. The Formulas stored in the library are executed first, in the order they are listed in the grid, followed by the Formulas in the project, in the order they are listed in the grid. If you wish to apply an offset and a correction to one particular field, then you must create two Formulas, one for the offset and the correction, and ensure they are listed in the desired order. To launch the Data Correction Tool, call the command INPUT | Add-Ins > Datgel CPT Tool > Data Correction Tool. You should see a window similar to the following.
67
13.2
Formula Toolbar
Name New Formula Save Formula Delete Formula Undo Changes Copy Current Formula Paste Formula Enable all Formulas Disable all Formulas Icon/Image Keyboard Shortcut Ctrl + N Ctrl + S Ctrl + D Ctrl + U Ctrl + Shift + C Ctrl + Shift + V Ctrl + Shift + E Ctrl + Shift + D Description Creates a new empty formula in the current formula grid Saves all changes to the gINT Library and Project database Deletes the currently selected formula Reverts any changes made to the current formula to the state it was last saved Makes a copy of the currently selected formula, and stores it in memory. Inserts the previously copied formula into the current formula grid Checks the Enabled check box column for all formulas in the current Formulas Grid Unchecks the Enabled check box column for all formulas in the current Formulas Grid
13.3
Data Tool Toolbar
Name Refresh Data Tool Icon/Image Keyboard Shortcut Ctrl + R Description Clears, re-reads and reloads the Table and Field drop down list items from the current gINT Project. Use this to update the drop down list if you have added a new table or field after the Data Correction Tool has been opened. Pastes the selected table and field as formatted text into the last focused configuration field. Refer to the Table Field Data Tool section of the manual for detailed information Pastes the selected function text into the last focused configuration field. Refer to 25 for detailed information
Function Data Tool
13.3.1
The Table Field Data Tool pastes the selected table and field as formatted text into the last focused configuration field. The drop down list contains all tables and fields in the current gINT Project database. When a Table is selected, the Field list will automatically filter to show only the fields for the selected table.
68
Currently, the Data Correction Tool only supports referencing fields on CPT_DATA, hence the Table has been fixed to CPT_DATA. The Table and Field drop down lists consist of three columns:
Table Name/Field Name database name of the Table or Field Caption The caption text as configured in the Caption field in the gINT Table or Field Properties Description The description text as configured in the Description field in the gINT Table or Field Properties
The drop down list can be sorted by a column by clicking on the column header. The columns can be resized by clicking and dragging the edges of the column header left or right. The drop down list window can be resized by clicking and dragging the bottom right corner of the window. The Paste button will insert the selected table field into a formatted, table field reference text into the last focused configuration text field or grid cell. The Paste button can insert text into the following Configuration fields: Description Any cell in the Variables Grid Formula Name
The table field reference format is as below:

<<Table Name.Field Name>>
Table field references in the Formula field are required to be surrounded by quotation marks. The Table Field Data Tool will automatically add the quotation marks if pasting in the Formula field. The table field reference format for the Formula field is as below:
"<<Table Name.Field Name>>"
The pasted text will be inserted at the current position of the cursor in the fields. Any highlighted text will be replaced by the inserted text. Selecting an entire cell in the Variables grid will replace the contents of that cell with the inserted text.
13.3.2
Function Data Tool
The Table Field Data Tool pastes the selected function text into the last focused configuration field. The Function drop down list contains all functions, constants and operators that are available in the Formula Tool, it the correct syntax. Each function is categorised as a type, and selecting a type in the Type drop down list will filter the function drop down list by that type.
69
The Function drop down list consists of three columns: Type type of function, can be filtered by a particular type by selecting a type in the Type drop down list Function the function, constant or operator in the correct syntax as required by the Formula Tool. The typical syntax composition of a function consists of the function name, followed by an open bracket, followed by a comma separated list of function parameters, followed by a closed bracket. FunctionName(Parameter 1, Parameter 2 [,...]) The function name is case sensitive. All function parameters are required, unless noted otherwise. If a function accepts an arbitrary number of parameters, it is denoted by ... . Description A short description about the function
The Paste button will insert the selected table field into a formatted, table field reference text into the last focused configuration text field or grid cell. The Paste button can insert text into the following Configuration fields: Description Any cell in the Variables Grid Formula Name
Refer to section 27 Formula Tool and Data Correction Tool Functions for detailed information about the functions.
13.4
Formulas Group
The Formulas Group contains a list of formulas stored in the currently selected tab. The formulas listed in the Library tab are stored in the gINT Library, and the Project tab in the current gINT Project
70
database. Each row in the Grid represents one formula, and is listed in the order they are to be evaluated from first to last. Selecting a formula by either by clicking on a row, or pressing the up or down keys in the Grid will display the configuration associated with the selected formula in the Configuration Group. The Name column values cannot be changed in this grid. It must be done in the Configuration/Offset and Correction Group after the formula has been selected. The Enabled column maybe edited from the grid by clicking on the cell or pressing the space bar for the selected cell. The Order of the formula can be changed in the Formulas Group with the up down buttons on the top left. Descriptions of the bottom are listed below from top to bottom: Move to Top Moves the currently selected formula to the top of the grid Move Up Moves the currently selected formula up by one row Move Down Moves the currently selected formula down by one row Move to Bottom moves the currently selected formula to the bottom of the grid
13.5
Key Set Group
Select the CPTs/Strokes you wish to run the data correction calculations to in this group. Source Table is fixed to CPT_GENERAL, which is the most appropriate table for selecting key sets for running calculations on the CPT_DATA table. Source Table The table containing the key sets that define a unique list of CPTs. The table is currently fixed to CPT_GENERAL. Key Set Selector Defines the selection of CPTs to be calculated. Click on the button on the right end of the text box to display the Key Set Selector Window. A window similar to the following should appear:
71
You may use a combination of left click, left click-drag, ctrl + click and shift + click to select the desired CPTs, and the arrow buttons in the middle to move CPTs to the right or left grid.
13.6
Configuration Group
The Configuration Group contains options identifying, defining and ordering for the currently selected formula in the Formulas grid. Name Name of the formula. The formula name must be unique for the formula grid. This means that you may have two formulas with the same name in the current Library and Project, but not in the Library or Project only. You will not be able to select another formula, or save the formula until a unique name is entered. Order a numeric value of the order the formula will be evaluated. If the result of the current formula is required to evaluate another formula, then the current formula should be placed at a higher order to than the other formula. The order cannot be changed in the Configuration Group. Move the selected formula up or down using the up down buttons left of the Formulas Grid. The numeric Order value will update itself when the order has changed. Iteration - The round of iteration in which the current formula will be evaluated. Default value is 1. Functions which calculate the average of a correlation that is evaluated by the Formula Tool need to be run at a later iteration to the correlation. Description Description of the formula. It is not used or required in the data correction calculation, and hence it is an optional field. Source/Target Field The field on the Source Table where the value for the formula is read and written to. This field can be any field on the Source Table, including key fields. Use the drop-down combo box to select the field from the current Source Table. Validate Click this button to evaluate the current formula expression, with the Validation Value set as the Variables. The Validate button is only enabled if the current formula is a Correction type. If the evaluation was successful, the result will be written to the adjacent text field. The Formatting Type and Value will be applied to the result, if defined. Use Validate to spot check your formula expression for syntax errors, and to verify the formula returns an expected result. Enabled Check or uncheck to enable or disable the formula respectively from evaluating in the CPT calculation
72
Formatting Type and Value Formats the result to either decimal or significant figures, to the nearest specified value. The formatting only applies to formula expressions that return a numeric value. OK Saves the current state of the formulas in the Data Correction Tool to the selected location, and closes the window. Cancel Discards any changes made in the Data Correction Tool and closes the window. The formulas will remain at the exact same state as before the Formula Configuration form was opened. You will be prompted to save if changes are detected.
13.7
Offset and Correction Group
The Offset and Correction group defines the formula type and options related to the for the currently selected formula.
13.7.1
Offset
This formula type allows for the vertical offset of columns/channels. For example, the offset of sleave friction data.
Offset or Correction Choose the formula type, Offset or Correction. If Offset is selected, the Offset subgroup is enabled, and the Correction subgroup is disabled, and vice versa. Offset Reference Field Field that defines the offset reference field on the currently selected Source table. The Offset calculation will read values in this field as a reference to offset the values in the source/target field. A typical Offset Reference Field value would be Depth. Direction Determines the offset direction. Increase offsets the value to a greater depth, whereas Decrease offsets the value to a lesser depth. Offset By The value to offset the source/target field by. The unit of this value is taken from the Offset Reference Field. For example, if the Offset Reference Field of Depth is in Metres, then the Offset By value will also be in Metres. The Offset By value must be positive.
73
13.7.2
Correction
This formula type allows for the alteration in value of data for a column based on a Formula. For example: 1. 2. Re-zero the Depth column, to correct for an incorrect start depth applied during acquisition. Subtract 101.4 kPa from measured pore pressure.
Table/Field References to Variables Declare the variables that are used in the formula expression in this grid. The rows in this grid can be changed with the up down buttons on the left of this grid. Column definitions are listed below: Variable Name Name of the variable. The variable name can consist of alphanumeric characters [a-z, A-Z, 1-9], but must have at least one alphabetic character, and is case sensitive. It cannot contain the following: o Symbols, such as `, $, # o White spaces or carriage return In addition, duplicate variable names for a particular formula is not permitted, and a variable name cannot be exactly the same as a function name. Expression Table Field reference to where the variable value is to be retrieved from, or a text or numeric value. The following is a list of rules and specifications regarding the Expression: o Table Field references must be in the format of <<Table.Field>> o Referenced fields must be from the CPT_DATA table, and it will take the value from the field of the current row the CPT Tool is calculating. o To use the variable as a constant, enter a numeric value, or text that is not in the format of <<Table.Field>> Validation Value Value used to evaluate the formula when the Validate button is clicked, and in the Validation Reports. The Validation Value has no effect on the actual CPT calculation, and is solely used in the Formula Configuration Form.
Formula The formula expression. Refer to section 27 Formula Tool and Data Correction Tool Functions for a full list of available functions. Variables declared in the Variables Grid above can be referenced in the formula expression. String constants must be surrounded with quotation marks "" in order to differentiate it from a variable reference. Spaces and carriage returns may be used liberally to improve readability. Table field references in the formula expression must be surrounded by quotation marks, i.e. "<<Table.Field>>". The Table Field Data Tool will automatically add the quotation marks when pasted in the formula expression field.
74
14 Soil Behaviour Type

6 unique SBT methods are included in the library file, and users may configure additional methods stored in the library or the project file. The order of priority for SBT selection used by the calculation is: 1. 2. 3. 4. CPT_POINT_PARAMTERS.Project_Soil_Class_Method_# CPT_POINT_PARAMTERS.Soil_Class_Method_# CPT_PROJECT_PARAMTERS.Project_Soil_Class _Method_# CPT_PROJECT_PARAMTERS.Soil_Class_Method_#
14.1

Preconfigured in Library
Eslami Fellenius 1997 Ramsey 2002 Robertson 1990 Robertson 1990 Extrapolated (axis extrapolated out one order of magnitude) Robertson et al. 1986 Robertson et al. 1986 Schmertmann 1978 Schneider et al. 2008 (defined by formula in papers table 6) vs. (Applicable when u2 isnt measured)
The CPT Tool is supplied with five material type interpretation methods:
Additional methods may be defined by users in the DG_CPT* library tables. See section 14.2 Creating a New Soil Behaviour Type. The CPT_DATA table allows for two methods to be defined. The methods are set on the CPT_PROJECT_PARAMETERS and the CPT_POINT_PARAMETERS tables. If the interpretation is done using 2 graphs, then the first single (not a list of numbers) result is used as the overall material classification. Examples: If Soil Zone 1 Graph 1 = 5 and Soil Zone 1 Graph 2 = 6, then Soil Class Number 1 will = 5 If Soil Zone 1 Graph 1 = 9,10,11,12 and Soil Zone 1 Graph 2 = 9, then Soil Class Number 1 will =9
If a point lies on the border of two zones, then the soil zone will be an appended string of both numbers, e.g. 9,10. The material type graph reports will print a black dot for these dual points. If the graph parameters are not within the range of the graph, then the Description field is set to No Match. If the X and/or Y axes of the graph are in a particular measurement unit (e.g. MPa), then the unit must be defined in the Graph_#_Parameter_Field_X_Unit and Graph_#_Parameter_Field_Y_Unit fields in the DG_CPT_SOIL_CLASS_METHOD table respectively. The value from the field reference defined in Graph_#_Parameter_Field_X or Graph_#_Parameter_Field_Y is converted from the unit it is currently in to the
75
unit defined in the unit specified in the Graph_#_Parameter_Field_X_Unit and Graph_#_Parameter_Field_Y_Unit fields before determining which zone the value lies in.
14.2
Creating a New Soil Behaviour Type in a Library
Creating a new soil behaviour type involves adding data to library tables, and creating Graph reports. As an example we will add a new SBT method titled GEO. 1. Create the points and a graph for the new method in Excel. Ensure there are no gaps and points of neighbouring zones coincide The polygons must be closed, i.e. the first point is the same as the last point It doesnt matter if the lines progress clockwise or anti-clockwise
2.
DG_CPT_SOIL_CLASS_METHOD
76
3. Graph 2 is optional 4. DG_CPT_SOIL_CLASS_ZONES
5.
DG_CPT_SOIL_CLASS_DATA
77
6. 7.
You may now return to INPUT, set the new SBT method on the Project or Point Parameters tables, and calculate a CPT. The results will now print on log reports. Now create a new graph report. This can be most efficiently done by copying the pre-existing Graph report titled CPT ROBERTSON ET AL. 1986 QT VS. RF. Use the command File > Copy page... and name the new report CPT GEO QT VS. RF. Now open the report properties and make the following changes
Property General Tab Description Report Variable Soil Class Method Report Variable Graph Number Report Variable Default Title Report Variable Y Axis Unit Conversion Factor Dependent Tab Data Expression 1 Minimum Value <<Calc(<<Report Var.Y Axis Unit Conversion Factor>> * <<CPT_DATA.Total_Cone_Resistance>>)>> <<Let(SourceUnit = "MPa")>>_ <<Let(TargetUnit = <<Report Var.Y Axis Unit>>)>>_ <<Let(UnitConversionFactor = <<User System Data.DG Com Unit Conversion Factor>>)>>_ <<Calc(<<Get(UnitConversionFactor)>> * 0.1)>> Soil behaviour type classification graph - GEO, total cone resistance (qt) versus friction ratio (Rf) <<Let(A="GEO")>><<Get(A)>> <<Calc(1)>> GEO qt vs. Rf - [[PointID]] <<Let(SourceField = <<CPT_DATA.Total_Cone_Resistance>>)>>_ <<Let(SourceUnit = <<FieldUnits(<<CPT_DATA.Total_Cone_Resistance>>)>>)>>_ <<Let(TargetUnit = <<Report Var.Y Axis Unit>>)>>_ <<User System Data.DG Com Unit Conversion Factor>> New Value
8.
78
Maximum Value
<<Let(SourceUnit = "MPa")>>_ <<Let(TargetUnit = <<Report Var.Y Axis Unit>>)>>_ <<Let(UnitConversionFactor = <<User System Data.DG Com Unit Conversion Factor>>)>>_ <<Calc(<<Get(UnitConversionFactor)>> * 100)>>
Data Representation Tab > Curves from Equations sub form Repeat the following for each Zone, incrementing the Zone = # each row Curve Equation <<Let(Zone = 1)>>_ <<IndDepList>>_ <<SqlList(_ ";"_ ,_ select [DG_CPT_SOIL_CLASS_DATA].[X] & "," & [DG_CPT_SOIL_CLASS_DATA].[Y] _ from [DG_CPT_SOIL_CLASS_DATA] in '<<LibFileSpec>>'_ where [DG_CPT_SOIL_CLASS_DATA].[Method] = '<<Report Var.Soil Class Method>>' AND _ [DG_CPT_SOIL_CLASS_DATA].[Graph_Number] = '<<Report Var.Graph Number>>' and _ [DG_CPT_SOIL_CLASS_DATA].[Zone] = '<<Get(Zone)>>' _ order by [DG_CPT_SOIL_CLASS_DATA].[Point_Number]_ )>> 10 Solid 0.2 Light Blue
Number of Points Line Type Line Thickness Line Colour
Override Line/DM Expression Tab Data marker Colour Expression 1 <<User System Data.DG CPT SBT Graph 1 DMK Colour>>
When you update the User Report Variable in the GENERAL tab, ensure that you entered correct Soil Class Method name (eg. GEO). This will make sure if all the user system data referring to the right method. In the new CPT Tool we have also added new feature for unit conversion (section 22 Unit Conversion), thus the Data Expression, Minimum Value and Maximum Value in the Dependent tab will also be converted accordingly.
9.
You may now move to OUTPUT and preview the report.
14.3
Project Soil behaviour Type
Project specific Soil Behaviour Type configurations may be stored in the project database. The relevant project tables are within the CPT-Configuration table group: CPT_SOIL_CLASS_DATA CPT_SOIL_CLASS_METHOD CPT_SOIL_CLASS_ZONES Soil Class Data Soil Class Method Soil Class Zones
The process of defining a Project SBT is very similar to defining a Library SBT. In the project file we can use split screens and have data relationships between tables, which makes the user interface more intuitive and logical. One major data entry differences is that Point Number on Soil Class Data is a text
79
type field, and it needs data that will order correctly as text, hence enter numbers padded with a zero e.g. 01.
80
15 Correlations
The primary references for the correlation was Mayne (2007) and Lunne et al. (1997). Many of the correlations listed in this section use constants within a formula. Users can set the constants in the following tables. The tables are listed in order of priority. 1. 2. 3. CPT_POINT_MATERIAL_PROPERTIES CPT_POINT_PARAMETERS or CPT_POINT_CORRELATION_PARAMETERS CPT_PROJECT_CORRELATION_PARAMETERS or CPT_PROJECT_PARAMETERS
For example, if the Relative_Density_1_C0 field on CPT_POINT_ CORRELATION_PARAMETERS has a value it will be used in preference to the value, if any, on the CPT_PROJECT_CORRELATION_PARAMETERS table. The fields in the CPT_POINT_MATERIAL_PROPERTIES table allow the constants to be defined for depth ranges for a particular PointID. A top and bottom depth must be specified when using the CPT_POINT_MATERIAL_PROPERTIES table, and the depth ranges must not overlap.
15.1
15.1.1
Undrained Shear Strength and Consistency Term

Undrained Shear Strength 1
) in Undrained_Shear_Strength_1 is defined as:
Undrained Shear Strength 1 ( When qt has data,
Otherwise,
NCHRP Synthesis 368 p 39 and are defined on the CPT_POINT_MATERIAL_PROPERTIES, CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. Different values for and can be defined for when or is either greater than or equal to, or less than a defined break point. Each of these tables have six fields from which the and values, and the and break point values are stored and retrieved for the calculation of .
Field Name Undrained_Shear_Strength_1_Nk_qc_BP Undrained_Shear_Strength_1_Nk_qc_LT_BP Undrained_Shear_Strength_1_Nk_qc_GTE_BP Description
Break point used to determine which calculation
to use in the
Used as the in the calculation, where does not have data, and is less than the break point. Used as the in the calculation, where does not have data, and is greater than or equal to the break point.
81
Field Name Undrained_Shear_Strength_1_Nkt_qt_BP Undrained_Shear_Strength_1_Nkt_qt_LT_BP Undrained_Shear_Strength_1_Nkt_qt_GTE_BP
Description
Break point used to determine which calculation
to use in the has data,
Used as the in the calculation, where and is less than the break point.
Used as the in the calculation, where has data, and is greater than or equal to the break point.
The fields in the CPT_POINT_MATERIAL_PROPERTIES table allow the and to be defined for depth ranges for a particular PointID. A top and bottom depth must be specified when using the CPT_POINT_MATERIAL_PROPERTIES table, and the depth ranges must not overlap. If the CPT_POINT_MATERIAL_PROPERTIES table is populated for the calculated PointID, the or that lies within the depth range of the current depth of the row in the CPT_DATA table is used to calculate . If a matching depth range for the current depth is not found, or or is missing, then the value is taken from the CPT_POINT_CORRELATION_PARAMETERS or the CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.1.2
Undrained Shear Strength 1 Term
The Undrained_Shear_Strength_Term_1 is defined based on the value of the Undrained_Shear_Strength_1 field and the values in the DG_LOG_CONSISTENCY_DENSITY library table.
15.1.3

Otherwise,
Where: is stored in the Undrained_Shear_Strength_2_Nkt field. is stored in the Undrained_Shear_Strength_2_Nk field. The variables are stored on CPT_POINT_MATERIAL_PROPERTIES, CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The fields in the CPT_POINT_MATERIAL_PROPERTIES table allow the and to be defined for depth ranges for a particular PointID. A top and bottom depth must be specified when using the CPT_POINT_MATERIAL_PROPERTIES table, and the depth ranges must not overlap. If the CPT_POINT_MATERIAL_PROPERTIES table is populated for the calculated PointID, the or that lies within the depth range of the current depth of the row in the CPT_DATA table is used to calculate . If a matching depth range for the current depth is not found, or or is missing, then the value is
82
taken from the CPT_POINT_CORRELATION_PARAMETERS or the CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.1.4
The Undrained_Shear_Strength_Term_2 is defined based on the value of the Undrained_Shear_Strength_2 field and the values in the DG_LOG_CONSISTENCY_DENSITY library table.
15.1.5

) based on CSSM in Undrained_Shear_Strength_3 is defined as:
Wroth (1984), NCHRP Synthesis 368 p 39 Where: is taken from the first of these fields with data: Effective_Friction_Angle_3 and Effective_Friction_Angle_1 is taken from Overconsolidation_Ratio_1 , typically low to medium sensitivity clays are , and sensitive and structured clays are , and is stored in the Undrained_Shear_Strength_3_Lambda field. is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.1.6
The Undrained_Shear_Strength_Term_3 is defined based on the value of the Undrained_Shear_Strength_3 field and the values similar to that in DG_LOG_CONSISTENCY_DENSITY library table.
15.1.7

Undrained Shear Strength 4 (
Trak et al. (1980), Terzaghi et al. (1996), NCHRP Synthesis 368 p 40 Where: is taken from Preconsolidation_Stress_1 is 0.22 in the published formula, and is stored in the Undrained_Shear_Strength_4_C1 field. is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
83
15.1.8
15.1.9

Undrained Shear Strength 5 (
Robertson (2009), pp 28-29 Where: is taken from Excess_Pore_Pressure field is taken from Undrained_Shear_Strength_5_N field is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.1.10
15.2
15.2.1
Relative Density and Relative Density Term

Relative Density 1
) in Relative_Density_1 is defined as: ( )
Relative density (
Baldi et al. (1986) and Al-Homoud and Wehr (2006), CPT in Geotechnical Practice p 83 Where: and are in kPa
is stored in the Relative_Density_1_C0 field. Published value for normally consolidated 157, over consolidated 181 is stored in the Relative_Density_1_C1 field. Published value is 0.55 is stored in the Relative_Density_1_C2 field. Published value for normally consolidated 2.41, over consolidated 2.46 is the Wehr Correction for Calcareous Soils, this constant is defined in the Relative_Density_1_Wehr_Correction field and was suggested in Al-Homoud and Wehr (2006). If the field is empty the default is 1.
84
The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.2.2
Relative Density Term 1
Relative density term in Relative_Density_Term_1 is defined based on Relative_Density_1 on the CPT_DATA table and the values in the DG_LOG_CONSISTENCY_DENSITY library table.
15.2.3
Relative Density 2
) in Relative_Density_2 is defined as: [ ( ) ]
Relative density (
Jamiolkowski et al. (2001), NCHRP Synthesis 368 pp 41-42 Where: is stored in the Relative_Density_2_C1 field. Published value is 0.268 for all sands is stored in the Relative_Density_2_C2 field. For average compressibility: C2 = -0.675, for high compressibility and sands of carbonate or calcareous composition: C2 <= 1.0, for low compressibility: C2 >= -2.0 The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.2.4
15.2.5
Relative Density 3
) in Relative_Density_3 is defined as: [ ]
Relative density (
Kulhawy and Mayne (1990), CPT in Geotechnical Practice p 84 Where:
is stored in the Relative_Density_3_C1 field. Published values range from 0.91 for low compressibility, 1.0 for medium compressible sands, to 1.09 for highly compressible is time in years and stored in the Relative_Density_3_t field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
85
15.2.6
15.3
15.3.1
Soil Behaviour Type Index

Soil Behaviour Type Index 1
The soil behaviour type index ( ) in Soil_Behaviour_Type_Index_1 is defined as:
Robertson and Wride (1998), CPT in Geotechnical Practice p 151 Where: is 3.47 in the published formula, and is stored in the Soil_Behaviour_Type_Index_1_C1 field. is 1.22 in the published formula, and is stored in the Soil_Behaviour_Type_Index_1_C2 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.3.2
The soil behaviour type index ( ) in Soil_Behaviour_Type_Index_2 is defined as:
Jefferies and Davies (1993), NCHRP Synthesis 368 p 27 Where: is 3 in the published formula, and is stored in the Soil_Behaviour_Type_Index_2_C1 field. is 1.5 in the published formula, and is stored in the Soil_Behaviour_Type_Index_2_C2 field. is 1.3 in the published formula, and is stored in the Soil_Behaviour_Type_Index_2_C3 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.3.3

) in Soil_Behaviour_Type_Index_3 is defined as: )) ( ( ) ) )
The non-normalised Soil Behaviour Type Index ( (( (
Robertson (2010), CPT 10, paper 2-56 (http://www.cpt10.com/PDF_Files/2-56RobSBT.pdf) Where:
86
is 3.47 in the published formula and is stored in the Soil_Behaviour_Type_Index_3_C1 field. is taken from the Total_Cone_Resistance field on the CPT_DATA table. is taken from the Cone_Resistance field on the CPT_DATA table. is the Atmospheric pressure, 101.4 kPa, and is set in the Formula Tool. is taken from the Friction_Ratio field on the CPT_DATA table. is 1.22 in the published formula and is stored in the Soil_Behaviour_Type_Index_3_C2 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.3.4
The soil behaviour type index ( ) in Soil_Behaviour_Type_Index_4 is defined as: ( )
Been and Jefferies (1992), Soil liquefaction, a critical state approach, pp. 206-207 Where: is 3 in the published formula, and is stored in the Soil_Behaviour_Type_Index_4_C1 field. is 1.5 in the published formula, and is stored in the Soil_Behaviour_Type_Index_4_C2 field. is 1.3 in the published formula, and is stored in the Soil_Behaviour_Type_Index_4_C3 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.4
15.4.1
The SPT
SPT N60 Value

SPT N60 Value 1
in SPT_N60_1 is defined as:
Robertson and Wride (1998), CPT in Geotechnical Practice p 151 Where: is 8.5 in the published formula, and is stored in the SPT_N60_1_C1 field. is 4.6 in the published formula, and is stored in the SPT_N60_1_C2 field. is the Atmospheric pressure, 100 kPa, and cannot be changed in the CPT Tool. is stored in the Soil_Behaviour_Type_Index_1 field.
87
15.4.2
The SPT
SPT N60 Value 2

in SPT_N60_2 is defined as:
Jefferies and Davies (1993) Where: is 0.85 in the published formula, and is stored in the SPT_N60_2_C1 field. is 4.75 in the published formula, and is stored in the SPT_N60_2_C2 field. is stored in the Soil_Behaviour_Type_Index_2 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.5
SPT Average N60 Value
The SPT average N60 value is a stepped average of SPT N60 values in the SPT_N60_1 or SPT_N60_2 fields in the CPT_DATA table for each defined depth interval step. The average of the N60 values is calculated for each depth interval step, and the result is recorded in the SPT_ Average_N60_1 or SPT_Average_N60_2 fields in the CPT_DATA table for each row in that interval step. The depth interval distance is defined on the SPT_N60_Average_Interval field on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables, and is in metres.
15.6
15.6.1
Shear Wave Velocity

Shear Wave Velocity 1 (All Soils)
Shear Wave velocity 1 ( ) in Shear_Wave_Velocity_1 is defined as:
Mayne (2006), NCHRP Synthesis 368 p 30 Where: is in kPa is 118.8 in the published formula, and is stored in the Shear_Wave_Velocity_1_C1 field. is 18.5 in the published formula, and is stored in the Shear_Wave_Velocity_1_C2 field.
88
15.6.2
Shear Wave Velocity 2 (All Soils)
( Hegazy and Mayne (1995), NCHRP Synthesis 368 p 30 Where: and are in kPa
is 10.1 in the published formula, and is stored in the Shear_Wave_Velocity_2_C1 field. is 11.4 in the published formula, and is stored in the Shear_Wave_Velocity_2_C2 field. is 1.67 in the published formula, and is stored in the Shear_Wave_Velocity_2_C3 field. is 0.3 in the published formula, and is stored in the Shear_Wave_Velocity_2_C4 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of for that row. is calculated when the Soil_Type_1 field value on the CPT_DATA table has any value
15.6.3
Shear Wave Velocity 3 (Clays)
Mayne and Rix (1995), NCHRP Synthesis 368 p 30 Where: is in kPa is 1.75 in the published formula, and is stored in the Shear_Wave_Velocity_3_C1 field. is 0.627 in the published formula, and is stored in the Shear_Wave_Velocity_3_C2 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of Mixed for that row. is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Fine or
15.6.4
Shear Wave Velocity 4 (Sands)
89
Baldi et al. (1989), NCHRP Synthesis 368 p 30 Where: and are in MPa
is 277 in the published formula, and is stored in the Shear_Wave_Velocity_4_C1 field. is 0.13 in the published formula, and is stored in the Shear_Wave_Velocity_4_C2 field. is 0.27 in the published formula, and is stored in the Shear_Wave_Velocity_4_C3 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Coarse or Mixed for that row.
15.7
15.7.1
Unit Weight
Dry Unit Weight 1 (Sands)
) in Dry_Unit_Weight_1 is defined as:
Dry Unit Weight 1 (
Mayne (2007), NCHRP Synthesis 368 p 31 Where: is 1.89 in the published formula, and is stored in the Dry_Unit_Weight_1_C1 field. is 11.8 in the published formula, and is stored in the Dry_Unit_Weight_1_C2 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Coarse or Mixed for that row.
15.7.2
Saturated Unit Weight 1

) in Saturated_Unit_Weight_1 is defined as:
Saturated Unit Weight 1 (
Mayne (2007), NCHRP Synthesis 368 p 31 Where: is in m/s and is in m
90
is 8.32 in the published formula, and is stored in the Saturated_Unit_Weight_1_C1 field is 1.61 in the published formula, and is stored in the Saturated_Unit_Weight_1_C2 field is Depth is taken from the first of these fields with data: Shear_Wave_Velocity_Extrapolated or Shear_Wave_Velocity_1 The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation is applicable to all soil types.
15.7.3
Saturated Unit Weight 2

) in Saturated_Unit_Weight_2 is defined as:
Saturated Unit Weight 2 (
Mayne (2007), NCHRP Synthesis 368 p 32 Where: is in kPa is 2.6 in the published formula, and is stored in the Saturated_Unit_Weight_2_C1 field is 15 in the published formula, and is stored in the Saturated_Unit_Weight_2_C2 field is 26.5 in the published formula, and is stored in the Saturated_Unit_Weight_2_C3 field is Specific Gravity of Solids, typically 2.4 to 2.9, and is stored in the Specific_Gravity_of_Solids field on CPT_PROJECT_CORRELATION_PARAMETERS The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation is applicable to all soil types.
15.8
15.8.1
Small-Strain Shear Modulus

Small-Strain Shear Modulus 1 (Sands)
) of sand in Small_Strain_Shear_Modulus_1 is defined as:
Small-Strain Shear Modulus 1 (
Rix and Stokoe (1992), CPT in Geotechnical Practice p 94 Where: , and are in kPa
91
is 1634 in the published formula, and is stored in the Small_Strain_Shear_Modulus_1_C1 field is -0.75 in the published formula, and is stored in the Small_Strain_Shear_Modulus_1_C2 field The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Coarse or Mixed for that row.
15.8.2
Small-Strain Shear Modulus 2

) in Small_Strain_Shear_Modulus_2 is defined as:
Small-Strain Shear Modulus 2 (
Elastic theory, CPT in Geotechnical Practice p 74 and 94, NCHRP Synthesis 368 p 31 Where: is taken from the first of these fields with data: Shear_Wave_Velocity_Extrapolated or Shear_Wave_Velocity_1 is taken from Bulk_Unit_Weight This correlation of is applicable to all soil types.
15.9
Youngs Modulus
) in Youngs_Modulus_1 is defined as:
Small Strain Youngs Modulus 1 (
Elastic theory, CPT in Geotechnical Practice p 74 and 94, NCHRP Synthesis 368 p 32 Where: = 0.2 is applied and can be varied in the Formula Tool. Published literature states: applies for drained soils and = 0.5 applies for undrained soils is taken from Small_Strain_Shear_Modulus_2 This correlation of is applicable to all soil types. = 0.2
15.10
15.10.1
Constrained Modulus
Constrained Modulus 1
The constrained modulus 1 ( ) in Constrained_Modulus_1 is defined as:
Kulhawy and Mayne (1990), NCHRP Synthesis 368 p 33, CPT in Geotechnical Practice p 72 Where:
92
is 8.25 in CPT in Geotechnical Practice, and is stored in the Constrained_Modulus_1_C1 field. NCHRP Synthesis 368 suggest values ranging from 1 to 20, with normal soils approximately 5. The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.10.2
Constrained Modulus 2
The constrained modulus 2 ( ) in Constrained_Modulus_2 is defined as:
Burns and Mayne (2002), NCHRP Synthesis 368 pp 33-34 Where: is 0.02 for organic plastic clays, up to 2 for over consolidated quartz sands in the published literature, and is stored in the Constrained_Modulus_2_C1 field is taken from Small_Strain_Shear_Modulus_2 The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This global approach to defining based on soil type with depth. is potentially inaccurate, it would be better to define the constant
15.11
Coefficient of Volume Change

) in Coefficent_Volume_Change_1 is defined as:
The coefficient of volume change 1 (
CPT in Geotechnical Practice p 71 Where: the constrained modulus, and is taken from the Constrained_Modulus_1 field.
15.12
Compression Index
The Compression Index 1 ( ) in Compression_Index_1 is defined as:
CPT in Geotechnical Practice p 71 Where: is the Void Ratio, and is stored in the Void_Ratio field. is the constrained modulus, and is taken from the Constrained_Modulus_1 field. The constant and are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
93
15.13
15.13.1
Preconsolidation Stress and Overconsolidation Ratio

Preconsolidation Stress 1 and Overconsolidation Ratio 1
) of clay in Preconsolidation_Stress_1 is defined as:
The Preconsolidation Stress 1 (
Mayne (1995), Demers and Leroueil (2002), NCHRP Synthesis 368 p 34 Where: is 0.33 in the published formula, and is stored in the Preconsolidation_Stress_1_C1 field. The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 1 in Overconsolidation_Ratio_1 is defined as:
is taken from Preconsolidation_Stress_1 field
15.13.2

Chen and Mayne (1996), NCHRP Synthesis 368 p 34 Where: is 0.53 in the published formula, and is stored in the Preconsolidation_Stress_2_C1 field. The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 2 in Overconsolidation_Ratio_2 is defined as:
15.13.3

Mayne (2005), NCHRP Synthesis 368 p 35 Where: is 0.6 in the published formula, and is stored in the Preconsolidation_Stress_3_C1 field.
94
The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 3 in Overconsolidation_Ratio_3 is defined as:
15.13.4

Robertson (2009), Guide to CPT p 31 Where: is 0.25 in the published formula, and is stored in the Preconsolidation_Stress_4_C1 field is 1.25 in the published formula, and is stored in the Preconsolidation_Stress_4_C2 field The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 4 in Overconsolidation_Ratio_4 is defined as:
15.13.5

) of sand in Preconsolidation_Stress_5 is defined as:
( )
[ Mayne (2005), NCHRP Synthesis 368 p 35 Where:
is 0.192 in the published formula, and is stored in the Preconsolidation_Stress_5_C1 field is 0.22 in the published formula, and is stored in the Preconsolidation_Stress_5_C2 field is 0.31 in the published formula, and is stored in the Preconsolidation_Stress_5_C3 field is 0.27 in the published formula, and is stored in the Preconsolidation_Stress_5_C4 field is taken from Effective_Friction_Angle_3
95
The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 5 in Overconsolidation_Ratio_5 is defined as:
15.13.6

) of all soil types in Preconsolidation_Stress_6 is defined as:
Mayne (2007), NCHRP Synthesis 368 pp 37 Where: , , and are in kPa
is 0.101 in the published formula, and is stored in the Preconsolidation_Stress_6_C1 field is 0.102 in the published formula, and is stored in the Preconsolidation_Stress_6_C2 field is 0.478 in the published formula, and is stored in the Preconsolidation_Stress_6_C3 field is 0.420 in the published formula, and is stored in the Preconsolidation_Stress_6_C4 field is taken from Small_Strain_Shear_Modulus_2 The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. The overconsolidation ratio 6 in Overconsolidation_Ratio_6 is defined as:
15.14
15.14.1
Angle of Friction
Angle of Friction 1
) in Effective_Friction_Angle_1 is defined as: [ ]
The angle of internal friction of mixed soils (
Mayne and Campanella (2005), NCHRP Synthesis 368 pp 38-39 Where: is 29.5 in the published formula, and is stored in the Effective_Friction_Angle_1_C1 field.
96
is 0.121 in the published formula, and is stored in the Effective_Friction_Angle_1_C2 field. is 0.256 in the published formula, and is stored in the Effective_Friction_Angle_1_C3 field. is 0.336 in the published formula, and is stored in the Effective_Friction_Angle_1_C4 field. This correlation of is only applicable for and hence will only be calculated if Pore_Pressure_Ratio field on the same row lies within this range. in the
15.14.2
Angle of Friction 2
) in Effective_Friction_Angle_2 is defined as: ( ( ))
The angle of internal friction of sands (
Robertson and Campanella (1983), NCHRP Synthesis 368 p 38 Where: is 0.1 in the published formula, and is stored in the Effective_Friction_Angle_2_C1 field. is 0.38 in the published formula, and is stored in the Effective_Friction_Angle_2_C2 field. This correlation of is only applicable for Sands and hence will only be calculated if the Soil_Type_1 field value is coarse or mixed.
15.14.3
Angle of Friction 3
) in Effective_Friction_Angle_3 is defined as:
The angle of internal friction of sand (
Kulhawy and Mayne (1990), NCHRP Synthesis 368 p 38 Where: is 17.6 in the published formula, and is stored in the Effective_Friction_Angle_3_C1 field. is 11.0 in the published formula, and is stored in the Effective_Friction_Angle_3_C2 field. This correlation of is only applicable for Sands and hence will only be calculated if the Soil_Type_1 field value is coarse or mixed.
15.15
15.15.1
Effective Cohesion
Effective Cohesion 1
The cohesion ( ) in Effective_Cohesion_1 is defined as:
Mayne and Stewart (1988), Mesri and Abdel-Ghaffar (1993), NCHRP Synthesis 368 p 44 Where: is 0.02 in the published formula, and is stored in the Effective_Cohesion_1_C1 field.
97
is taken from Preconsolidation_Stress_1 field.
15.16
15.16.1
Sensitivity
Sensitivity 1
The Sensitivity ( ) in Sensitivity_1 is defined as:
Schmertmann (1978), Rad and Lunne (1986), CPT in Geotechnical Practice p 68 Where: is a value between 5 and 10 in the published formula, and is stored in the Sensitivity_1_Ns field. The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.16.2
Sensitivity 2
in Sensitivity_2 is defined as:
The Sensitivity
Mayne (2007), NCHRP Synthesis 368 p 41 Where: is 0.073 in the published formula, and is stored in the Sensitivity_2_C1 field. The constant is stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is based on the assumption of OCR < 2, The value of is recorded in the Sensitivity_2 field on the CPT_DATA table. and .
15.17 15.17.1
Coefficient of Lateral Earth Pressure

Coefficient of Lateral Earth Pressure 1
Coefficient of Lateral Earth Pressure 1 ( ) for uncemented sands and well behaved clays in Coefficient_Lateral_Earth_Pressure_1 is defined as:
Mayne (2007), NCHRP Synthesis 368 p 42 Where:
98
is taken from the Overconsolidation_Ratio_1 field for fine material and the Overconsolidation_Ratio_5 for coarse material, on the CPT_DATA table. is taken from the Effective_Friction_Angle_3 and Effective_Friction_Angle_1 field on the CPT_DATA table. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.17.2

) for sand in Coefficient_Lateral_Earth_Pressure_2 is defined as: ( ) ( )
Coefficient of Lateral Earth Pressure 2 (
Mayne (2007), NCHRP Synthesis 368 p 43 Where: is taken from the Overconsolidation_Ratio_5 field on the CPT_DATA table. is 0.192 in the published formula, and is stored in the Coefficient_Lateral_Earth_Pressure_2_C1 field. is 0.22 in the published formula, and is stored in the Coefficient_Lateral_Earth_Pressure_2_C2 field. is 0.31 in the published formula, and is stored in the Coefficient_Lateral_Earth_Pressure_2_C3 field. is 0.27 in the published formula, and is stored in the Coefficient_Lateral_Earth_Pressure_2_C3 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.17.3

) for fine grained soils in Coefficient_Lateral_Earth_Pressure_3 is
Coefficient of Lateral Earth Pressure 3 ( defined as:
( Kulhawy and Mayne (1990), CPT Guide p 32 Where:
is 0.1 in the published formula, and is stored in the Coefficient_Lateral_Earth_Pressure_3_C1 field. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables.
15.18
15.18.1
Rigidity Index
Rigidity Index 1
Rigidity index 1 ( ) for fine material is recorded in the Rigidity_Index_1 is defined as:
99
[( Mayne (2001), NCHRP Synthesis 368 p 46 Where:
) (
is 1.5 in the published formula, and is stored in the Rigidity_Index_1_C1 field. is 2.925 in the published formula, and is stored in the Rigidity_Index_1_C2 field. is 2.925 in the published formula, and is stored in the Rigidity_Index_1_C3 field. is the Cam clay constant, slope of the critical state line and is defined as:
for the calculation of the Cam clay constant on the CPT_DATA table.
is taken from the Effective_Friction_Angle_1 field
The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table has a value of Fine for that row.
15.18.2
Rigidity Index 2
Rigidity index 2 ( ) for fine material based on plasticity index and OCR is recorded in the Rigidity_Index_2 is defined as: { Keaveny and Mitchel (1986), NCHRP Synthesis 368 p 46 Where: is 0.0435 in the published formula, and is stored in the Rigidity_Index_2_C1 field. is 137 in the published formula, and is stored in the Rigidity_Index_2_C2 field. is 0.385 in the published formula, and is stored in the Rigidity_Index_2_C3 field. is 3.2 in the published formula, and is stored in the Rigidity_Index_2_C4 field. is 0.8 in the published formula, and is stored in the Rigidity_Index_2_C5 field. is the Plasticity Index, and is stored in the Plasticity_Index field. is taken from the Overconsolidation_Ratio_4 field on the CPT_DATA table. The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table has a value of Fine for that row.
100
15.19
15.19.1
Hydraulic Conductivity
Hydraulic Conductivity 1
The hydraulic conductivity (permeability) method 1 (K 1) in Hydraulic_Conductivity_1_Min and Hydraulic_Conductivity_1_Max are defined in the following table. Soil Behaviour Type Robertson et al. 1986 or Robertson et al. 1986 qc vs. Rf must be calculated for this correlation to be defined.
Zone 1 2 3 4 5 6 7 8 9 10 11 12 Soil Behaviour Type (SBT) Sensitive fine grained Organic soils Clay Silty clay to clay Clayey silt to silty clay Sandy silt to clayey silt Silty sand to sandy silt Sand to silty sand Sand Gravelly sand to dense sand Very stiff fine-grained soil Very stiff sand to clayey sand Range of hydraulic conductivity (permeability) K (m/s) 3x10-9 to 3x10-8 1x10-8 to 1x10-6 1x10-10 to 1x10-9 1x10-9 to 1x10-8 1x10-8 to 1x10-7 1x10-7 to 1x10-6 1x10-5 to 1x10-6 1x10-5 to 1x10-4 1x10-4 to 1x10-3 1x10-3 to 1 1x10-8 to 1x10-6 3x10-7 to 3x10-4
Robertson (2009), pp41, Table 6
15.19.2
Hydraulic Conductivity 2
The hydraulic conductivity (permeability) method 2 (K 2) in Hydraulic_Conductivity_2_Min and Hydraulic_Conductivity_2_Max are defined in the following table. Soil Behaviour Type Robertson 1990 or Robertson 1990 Extrapolated must be calculated for this correlation to be defined.
Zone 1 2 3 4 5 6 7 8 9 Soil Behaviour Type (SBTN) Sensitive fine grained Organic soils Clay Silt mixtures Sand mixtures Sands Gravelly sands to dense sands Very stiff sand to clayey sand Very stiff fine-grained soil Range of hydraulic conductivity (permeability) k (m/s) 3x10-9 to 3x10-8 1x10-8 to 1x10-6 1x10-10 to 1x10-9 3x10-9 to 1x10-7 1x10-7 to 1x10-5 1x10-5 to 1x10-3 1x10-3 to 1 1x10-8 to 1x10-6 1x10-8 to 1x10-6
Robertson (2009), pp41, Table 7
101
16 Liquefaction Assessment
16.1
16.1.1
State Parameter
State parameter 1
Based on the method by Been et al. (1987), the state parameter method 1, Y1, in State_Parameter_1 is calculated from: ( )
Soil liquefaction, a critical state approach, pp. 191-193 In which: ( )
is the normalised cone resistance, and is stored in Normalised_Cone_Resistance on CPT_DATA is the coefficient of lateral earth pressure, and is stored in Coefficient_of_Lateral_Earth_Pressure is stored in Soil_and_Rigidity_Coefficient_k is stored in Soil_and_Rigidity_Coefficient_m
16.1.2
State parameter 2
Based on the method by Shuttle and Jefferies (1998), the state parameter 2, Y2, in State_Parameter_2 with constant rigidity index is calculated from: ( )
In which: ( ( ) )
Where: is the normalised cone resistance, and is stored in the Normalised_Cone_Resistance in CPT_DATA Table. is rigidity index and is stored in Rigidity_Index field is critical state ratio and is stored in Critical_State_Ratio field
102
is dilation parameter and is stored in Dilation_Parameter field is plastic hardening modulus and is stored in Plastic_Hardening_Modulus field is slope of CSL line and is stored in Lambda field
16.1.3
State parameter 3
The state parameter 3, Y3, in State_Parameter_3 with varying rigidity index is similar to state parameter 2 except for the rigidity index that is calculated from: ( )
is rigidity index in reference pressure and is stored in Rigidity_Index field is the reference pressure (100 kPa). is effective vertical overburden stress in Effective_Stress in CPT_DATA Table
16.1.4
State parameter 4
( )
The state parameter 4, Y4, in State_Parameter_4 is defined based on the method by Plewes (1992) as:
Soil liquefaction, a critical state approach, pp. 202-204 Where: ( ( ) )
is the normalised cone resistance, and is stored in the Normalised_Cone_Resistance in CPT_DATA Table. is pore pressure ratio and is stored in Pore_Pressure_Ratio in CPT_DATA Table is the coefficient of lateral earth pressure, and is stored in the Coefficient_of_Lateral_Earth_Pressure field. is normalised friction ratio and is stored in Normalised_Friction_Ratio in CPT_DATA Table is critical state ration and is stored in Critical_State_Ratio field
103
16.1.5
State parameter 5
The state parameter 5, Y5, in State_Parameter_5 is defined based on the method by Been and Jefferies (1992) as: ( )
Soil liquefaction, a critical state approach, pp. 202-204 Where: ( ( ) )
is the normalised cone resistance, and is stored in the Normalised_Cone_Resistance on CPT_DATA is pore pressure ratio and is stored in Pore_Pressure_Ratio in CPT_DATA Table is the coefficient of lateral earth pressure, and is stored in the Coefficient_of_Lateral_Earth_Pressure field. is soil behaviour type index (method 4, Been and Jefferies 1992) and is stored in Soil_Behaviour_Type_Index_4 in CPT_DATA Table is critical state ration and is stored in Critical_State_Ratio
16.2
Soil Behaviour Type Index 1, NCEER
Soil behaviour type index 1, , in Soil_Behaviour_Type_Index_1_NCEER is defined based on the method by Robertson and Wride (1998) as: Where ( And )
The power n ranges between 0.5 for sands to 1.0 for clays. First assume that n=1, and calculate the then if it is clayey and is correct. If we should recalculate the with n=0.5, then if the new it means the soil is sand and the calculated is correct. If recalculated it means the soil is likely to be very silty and should be recalculated with n=0.75.
104
16.3
16.3.1
Fines Content (FC)

Fines Content 1
Fines content 1, in Fines_Content_1 is based on the method by Robertson and Wride 1998:
is soil behaviour type index 1, NCEER, and is stored in the Soil_Behaviour_Type_Index_1_NCEER on CPT_DATA_LIQUEFACTION.
16.3.2
Fines Content 2
Fines content 2, in Fines_Content_2 is based on the method by Suzuki et al. 1998:
Soil liquefaction during earthquakes, p. 79 is soil behaviour type index 1, NCEER, and is stored in Soil_Behaviour_Type_Index_1_NCEER on CPT_DATA_LIQUEFACTION.
16.4
16.4.1
Clean-Sand Equivalent Normalised Cone Resistance

Clean-Sand Equivalent Normalised Cone Resistance 1
The clean-sand equivalent normalised cone resistance 1, in qc1N_cs_1 is calculated by the following equation: ( Robertson and Wride (1998), NCEER 2001 pp. 822-823 Where, For For The power n ranges between 0.5 for sands to 1.0 for clays and is a reference pressure (100 kPa). )
16.4.2
The clean-sand equivalent normalised cone resistance 2, in qc1N_cs_2 based on method by Idriss and Boulanger (2008) is defined as:
( )
105
Soil liquefaction during earthquakes, pp. 84-89 and 111 Where: is the reference pressure (100 kPa). is effective vertical overburden stress in Effective_Stress on CPT_DATA is the fine content 2 in Fines_Content_2 on CPT_DATA_LIQUEFACTION
16.4.3
The clean-sand equivalent normalised cone resistance 3, in qc1N_cs_3, based on method by Idriss and Boulanger (2008), using the fines content equation proposed by Robertson and Wride 1998, is defined as:
( )
Soil liquefaction during earthquakes, pp. 84-89 and 111 Where: is the reference pressure (100 kPa) is effective vertical overburden stress in Effective_Stress on CPT_DATA is the fines content 1 in Fines_Content_1 on CPT_DATA_LIQUEFACTION
16.5
16.5.1
Cyclic Resistance Ratio (CRR)

Cyclic Resistance Ratio 1
The clean-sand based cyclic resistance ratio method 1, in Cyclic_Resistance_Ratio_1 for standard earthquake of magnitude 7.5 method by Robertson and Wride (1998), is calculated by:
106
Robertson and Wride (1998), NCEER 2001 pp. 822-823 Where: is the clean-sand equivalent normalised cone resistance 1, in qc1N_cs_1 on CPT_DATA_LIQUEFACTION
16.5.2
Cyclic resistance ratio 2, in Cyclic_Resistance_Ratio_2 for standard earthquake of magnitude 7.5, is based on critical state approach and calculated from:
Jefferies & Been 2006, Soil liquefaction, a critical state approach, p 395 Where: is state parameter and is by default is set to method 1 which is stored in State_Parameter_1 in CPT_DATA_LIQUEFACTION Table. The default method is in Cyclic_Resistance_Ratio_2_Y_Method in LIQUIFACTION_PROJECT_PARAMETERS table is 0.03 and stored in Cyclic_Resistance_Ratio_2_a in LIQUIFACTION_PROJECT_PARAMETERS table is -11 and stored in Cyclic_Resistance_Ratio_2_b in LIQUIFACTION_PROJECT_PARAMETERS table
16.5.3
The cyclic resistance ratio method 3, in Cyclic_Resistance_Ratio_3 for standard earthquake of magnitude 7.5 is calculated by: ( ) ( ) ( )
Idriss & Boulanger 2008, Soil liquefaction during earthquakes, p. 100 and 95 Where: is the clean-sand equivalent normalised cone resistance 2 and is stored in qc1N_cs_2 on CPT_DATA_LIQUEFACTION.
16.5.4
The cyclic resistance ratio method 4, in Cyclic_Resistance_Ratio_4 for standard earthquake of magnitude 7.5 is calculated by: ( ) ( ) ( )
Idriss & Boulanger 2008, Soil liquefaction during earthquakes, p. 100 and 95 Where: is the clean-sand equivalent normalised cone resistance 3 and is stored in qc1N_cs_3 on CPT_DATA_LIQUEFACTION. Per Idriss & Boulanger 2008 with fines content from Robertson and Wride 1998 and m taken as 0.5.
107
16.6
16.6.1
Cyclic Stress Ratio (CSR)

Cyclic Stress Ratio 1
Cyclic stress ratio 1, in Cyclic_Stress_Ratio_1 is defined based on the relation proposed by Seed and Idriss (1971) as: ( NCEER 2001, p818 Where: is peak horizontal acceleration at the ground surface generated by earthquake, and is stored in Peak_Ground_Acceleration g is the acceleration of gravity and is stored in Gravity is total vertical overburden stress in Total_Stress in CPT DATA is effective vertical overburden stress in Effective_Stress in CPT_DATA Table is the stress reduction coefficient. T. F. Blake (1996) approximated the mean values of as: ) ( )( )
16.6.2
Cyclic Stress Ratio 2
Cyclic stress ratio method 2, in Cyclic_Stress_Ratio_2 is defined based on the relation proposed by Idriss and Boulanger (2008) as: ( ) ( )( )
Soil liquefaction during earthquakes, p. 68 Where: is peak horizontal acceleration at the ground surface generated by earthquake, and is stored in Peak_Ground_Acceleration g is the acceleration of gravity and is stored in Gravity is total vertical overburden stress in Total_Stress on CPT DATA is effective vertical overburden stress in Effective_Stress on CPT_DATA
108
16.7
16.7.1
Factor of Safety (FoS)

Factor of Safety 1
The factor of safety method 1, in Factor_of_Safety_1 is defined as: ( NCEER 2001, p 828 Where: ( ) )
CRR is the cyclic resistance ratio method 1 and is stored in Cyclic_Resistance_Ratio_1 CSR is the cyclic stress ratio 1 and is stored in Cyclic_Stress_Ratio_1 is effective vertical overburden stress in Effective_Stress on CPT_DATA is the reference pressure (100 kPa) is between -0.2 to -0.4 with default value of -0.244; The paper suggested a relationship with Dr which has not been applied here is the earthquake magnitude and is stored in Earthquake_Magnitude is the correction factor for sloping ground and is stored in Correction_Factor_for_Sloping_Ground
16.7.2
Factor of Safety 2
The factor of safety method 2, in Factor_of_Safety_2 is defined as: ( NCEER 2001, p 828 Where: ( ) )
CRR is the cyclic resistance ratio method 2 and is stored in Cyclic_Resistance_Ratio_2 CSR is the cyclic stress ratio 1 and is stored in Cyclic_Stress_Ratio_1 is effective vertical overburden stress in Effective_Stress on CPT_DATA
109
is the reference pressure (100 kPa) is between -0.2 to -0.4 with default value of -0.244; The paper suggested a relationship with Dr which has not been applied here is the earthquake magnitude and is stored in Earthquake_Magnitude is the correction factor for sloping ground and is stored in Correction_Factor_for_Sloping_Ground
16.7.3
Factor of Safety 3
The factor of safety method 3, in Factor_of_Safety_3 is defined as: ( ( ) ) ( )
Soil liquefaction during earthquakes, pp. 93-102 Where: CRR is the cyclic resistance ratio method 3, and is stored in Cyclic_Resistance_Ratio_3 CSR is the cyclic stress ratio method 2 and is stored in Cyclic_Stress_Ratio_2 is the earthquake magnitude and is stored in Earthquake_Magnitude is the correction factor for sloping ground and is stored in Correction_Factor_for_Sloping_Ground is effective vertical overburden stress in Effective_Stress on CPT_DATA
16.7.4
Factor of Safety 4
The factor of safety method 4, in Factor_of_Safety_4 is defined as: ( ( ) ) ( )
Soil liquefaction during earthquakes, pp. 95-102 Where:

110
CRR is the cyclic resistance ratio method 4, and is stored in Cyclic_Resistance_Ratio_4 CSR is the cyclic stress ratio method 2 and is stored in Cyclic_Stress_Ratio_2 is the earthquake magnitude and is stored in Earthquake_Magnitude is the correction factor for sloping ground and is stored in Correction_Factor_for_Sloping_Ground is effective vertical overburden stress in Effective_Stress on CPT_DATA This follows the procedure defined by New Zealand Department of Building and Housing, Interim guidance for repairing and rebuilding foundations in Technical Category 3, Appendix C to the Guidance Document: Revised guidance on repairing and rebuilding houses affected by the Canterbury earthquake sequence (November 2011)
16.8
Residual Shear Strength (Sr)

, in Residual_Shear_Stregth_1 is defined as:
Residual shear strength,
( Soil liquefaction, a critical state approach, p 324 Where:
is the normalised cone resistance, and is stored in the Normalised_Cone_Resistance on CPT_DATA is effective vertical overburden stress in Effective_Stress on CPT_DATA and are best fit constants equal to 0.03 and 0.1, respectively
is rigidity index and is stored in Rigidity_Index is critical state ration and is stored in Critical_State_Ratio is dilation parameter and is stored in Dilation_Parameter is plastic hardening modulus and is stored in Plastic_Hardening_Modulus is slope of CSL line and is stored in Lambda
16.9
Maximum Shear Strain,
Maximum shear strain in Maximum_Shear_Strain_1, is calculated based on the method by Idriss and Boulanger (2008):
)(
)]
111
Soil liquefaction during earthquakes, pp. 141-142 Where: is the factor of safety, and is stored in Factor_of_Safety_3 on CPT_DATA_LIQUEFACTION is the clean-sand equivalent normalised cone resistance 2, in qc1N_cs_2 on CPT_DATA_LIQUEFACTION
16.10
Lateral Displacement Index 1, LDI
The lateral displacement index 1, LDI, in Lateral_Displacement_Index_1 is calculated by integrating maximum shear strains versus depth, Soil liquefaction during earthquakes, p. 140 and 142 The maximum shear strains are limited to 0.5 in calculating the LDI. (p. 142, 1st paragraph)
16.11
16.11.1
Post Liquefaction Volumetric Strain,

Post Liquefaction Volumetric Strain 1
Post liquefaction volumetric strain 1, in Post_Liq_Volumetric_Strain_1, method by Yoshimine et al. (2006), is calculated as:
Soil liquefaction during earthquakes, p. 153 Where: is the clean-sand equivalent normalised cone resistance 2, in qc1N_cs_2 on CPT_DATA_LIQUEFACTION
16.11.2
Post Liquefaction Volumetric Strain 2
Post liquefaction volumetric strain 2, in Post_Liq_Volumetric_Strain_2, method by Zhang et al. (2002), is calculated as,
112
Can. Geotech. J. Vol. 39, 2002, p. 1180 Where: is the factor of safety, and is stored in Factor_of_Safety_4 on CPT_DATA_LIQUEFACTION is the clean-sand equivalent normalised cone resistance 3 in qc1N_cs_3 on CPT_DATA_LIQUEFACTION. For cases that are less than 33, it was set to 33.
16.12
16.12.1
Post Liquefaction Reconsolidation Settlement, S

Post Liquefaction Reconsolidation Settlement 1
Post liquefaction reconsolidation settlement 1 in Post_Liq_Reconsolidation_Settlement_1 is calculated from post liquefaction volumetric strain 1: Where: is the post liquefaction volumetric strain 1, and is stored in Post_Liq_Volumetric_Strain_1 on CPT_DATA_LIQUEFACTION
16.12.2
Post Liquefaction Reconsolidation Settlement 2
Post liquefaction reconsolidation settlement 2 in Post_Liq_Reconsolidation_Settlement_2 is calculated from post liquefaction volumetric strain 2: Where: is the post liquefaction volumetric strain 2, and is stored in Post_Liq_Volumetric_Strain_2 on CPT_DATA_LIQUEFACTION
113
17 Pile Axial Capacity

17.1 Soil Description
, The soil description in Pile_Axial_Capacity_Soil_Description_1 is defined based on the cone resistance, according to table below:
Nature of soil Soft clay and mud Moderately compact clay Silt and loose sand Compact to stiff clay and compact silt Soft chalk Moderately compact sand and gravel Weathered to fragmented chalk Compact to very compact sand and gravel
(MPa) <1 1 to 5 5 >5 5 5 to 12 >5 > 12
CPT in geotechnical practice, pp. 152-154
17.2
Unit End Bearing
The unit end bearing, , in Pile_Axial_Capacity_Unit_End_Bearing_1 based on the method by Bustamante and Gianeselli (1982) is defined as:
The method also is known as LCPC method CPT in geotechnical practice, pp. 152-154 Where is read from table below (CPT in geotechnical practice, p152, Table 6.4) based on the cone resistance and soil type. is the equivalent average cone resistance at the base of the pile, is the mean value measured along two fixed distances a (a=1.5 D, where D is the pile diameter) above (-a) and below (+a) the pile tip. The values are bounded to a maximum of 1.3 along the length a to +a, and the minimum of 0.7 along the a, in which is the mean value of between a and +a.
Nature of soil Soft clay and mud Moderately compact clay Silt and loose sand Compact to stiff clay and compact silt Soft chalk CPT Tool gINT Add-In 3 User Guide Factor (MPa) <1 1 to 5 5 >5 5 Group I 0.4 0.35 0.4 0.45 0.2 Group II 0.5 0.45 0.5 0.55 0.3 Datgel DCT-UG-001 - 3.02 - August 2012
114
Moderately compact sand and gravel Weathered to fragmented chalk Compact to very compact sand and gravel
5 to 12 >5 > 12
0.4 0.2 0.3
0.5 0.4 0.4
Group I: plain bored piles, mud bored piles, micro piles (grouted under low pressure), cased bored piles, hallow auger bored piles, piers, barretes. Group II: cast screwed piles, driven precast piles, prestress tubular piles, driven cast piles, jacked metal piles, micropiles (small diameter piles grouted under high pressure with diameter < 250 mm), driven grouted piles (low pressure grouting), driven metal piles, driven rammed piles, jacket concrete piles, high pressure grouted piles of large diameter.
17.3
Unit Side Friction
The unit side friction, , in Pile_Axial_Capacity_Unit_Side_Friction_1 based on the method by Bustamante and Gianeselli (1982) is defined as:
CPT in geotechnical practice, pp. 152-154 Where table 6.5). and maximum limit of are given in the following table (CPT in geotechnical practice,
Nature of soil
Coefficient (MPa) A I B 90 80 150 120 120 200 80 300 A 90 40 60 60 100 100 60 150 II B 30 80 120 120 120 200 80 200 A 0.015 0.035 (0.08) 0.035 0.035 (0.08) 0.035 0.08 (0.12) 0.12 (0.15) 0.12 (0.15) I
Maximum limit of II B 0.015 0.035 (0.08) 0.035 0.035 (0.08) 0.035 0.035 (0.08) 0.08 (0.12) 0.08 (0.12) A 0.015 0.035 (0.08) 0.035 0.035 (0.08) 0.035 0.08 (0.12) 0.12 (0.15) 0.12 (0.15) B 0.015 0.035 0.035 0.035 0.035 0.08 0.12 0.12
(MPa) III A 0.035 0.08 0.08 0.08 0.08 0.12 0.15 0.15 0.12 0.20 0.20 0.20 0.20 B
Soft clay and mud Moderately compact clay Silt and loose sand Compact to stiff clay and compact silt Soft chalk Moderately compact sand and gravel Weathered to fragmented chalk Compact to very compact sand and gravel
<1 1 to 5 5 >5 5 5 to 12 >5 > 12
30 40 60 60 100 100 60 150
Category-IA: : plain bored piles, mud bored piles, , hallow auger bored piles, micro piles (grouted under low pressure), cast screwed piles, piers, barretes. IB: cased bored piles, driven cast piles. IIA: driven precast piles, prestress tubular piles, jacket concrete piles. IIB: driven metal piles, jacked metal piles. IIIA: ), driven grouted piles, driven rammed piles. IIIB: high pressure grouted piles of large diameter >250mm, micropiles (grouted under high pressure). Note: maximum limit unit skin friction, : bracket values apply to carefl execution and minimum disturbance of soil due to construction.
115
17.4
End Bearing Capacity
The end bearing capacity, , in Pile_Axial_Capacity_End_Bearing_1 is calculated as the product between the pile end area, , and the unit end bearing, :
17.5
Side Friction Capacity
The friction capacity, , in Pile_Axial_Capacity_Side_Friction_1 is the product between the outer pile shaft area, , by the the unit side friction, , as: CPT in geotechnical practice, pp. 152-154
17.6
Ultimate Axial Capacity
The ultimate pile axial capacity, , in Pile_Axial_Capacity_Ultimate_1 consists of two components: side friction capacity, , and end bearing capacity, , as:
116
18 Transfer Description and

Consistency Summary
This command transfers a summary of the configured material type classification to a Stratigraphy/Lithology table, and the calculated Relative Density Term Field (e.g. Relative_Density_Term_1) and Undrained Shear Strength Term field (e.g. Undrained_Shear_Strength_Term_1) to the Consistency/Density table. The command to transfer a single PointID is located in INPUT | Add-Ins > Datgel CPT Tool > Transfer Description and Consistency for current PointID, and can be called from child tables of POINT. Alternatively, the command INPUT | Add-Ins > Datgel CPT Tool > Transfer Description and Consistency for multiple PointIDs can be used to select and transfer multiple PointIDs at once. This can be done on any table in INPUT. The Transfer Description and Consistency for multiple PointIDs form is as below:
Use the arrow buttons in the middle to add PointIDs to the Selected Key Sets column. The Overwrite Options are as follows: Overwrite without prompting Clears any existing data for the particular PointID in the Description and Consistency tables before transferring the description and consistency data. Prompt on overwrite Prompts the user if they wish to Overwrite, Append or Cancel if there is existing data in the Description or Consistency tables for a particular PointID. If there is no data in the Description or Consistency table, it will transfer the data silently for that PointID. Do not overwrite Transfers data into the Description and Consistency tables, only if there is no existing data in those tables. If there is existing data for a particular PointID, the program will append new data to the existing data for that PointID.
117
The CPT Description data is processed and consolidated before it is transferred to the Description table. The order of operation is: 1. 2. 3. Minimum Layer Thickness Consolidation of like layers Soil Group Thickness
18.1
Minimum Layer Thickness
This option can be used to exclude geotechnically insignificant layers, e.g. say the purpose of your CPT is for pile design, then you may wish to ignore a 30 mm clay lens within a much larger sand layer. If a layer thickness is less than the value in CPT_PROJECT_PARAMETERS table Minimum_Thickness_Soil_Layer field, then the layer will be removed and: 1. 2. 3. If the layer above is the same coarse or fine type, then the Bottom will be set to the Bottom of the removed layer. If the layer below is the same coarse or fine type, then the Depth will be set to the Depth of the removed layer. Otherwise the Bottom field for the layer above will be updated.
The Consistency and Density transfer is not affected by the Minimum_Thickness_Soil_Layer field. This filter will not apply if Minimum_Thickness_Soil_Layer is blank.
18.2
Soil Group Thickness
If a layer is less than the value in CPT_PROJECT_PARAMETERS table Soil_Class_Group_Thickness field, then it will be appended to the layer above if they are both the same coarse or fine type. The Consistency and Density transfer is not affected by the Soil_Class_Group_Thickness field. This filter will not apply if Soil_Class_Group_Thickness is blank.
118
18.3
Configuration of description and consistency summary transfer
Before using the transfer command, first configure the custom fields and tables using the command in INPUT | Add-Ins > Datgel CPT Tool > Transfer Description and Consistency Configuration.
1. Set field and table names using the pick lists. All fields are required unless noted. Description of each group is listed below: Description Table where the soil description will be transferred to. Description Graphic 2 Field is an optional field, and can be left blank. Consistency Table where the consistency/relative density will be transferred to. Source Table where the soil description, consistency and Soil Behaviour Type will be transferred from. Soil Class Method Table where the Soil Class Method is defined.
2. Click OK.
119
19 Lower-Best-Upper Correlations
A selected set of correlations are calculated with Lower Bound (LB), Best Estimate (BE) and Upper Bound (UB) configurations. Like other correlations, these are calculated by the Formula Tool and parameters may be set on CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables. Users should configure the parameters to suit site conditions.
Log columns, fence columns and graph reports are included to display this data. The text LB BE UB is in the name of these reports. The default configuration of the Correlation Summary uses this data.
120
20 Correlation Summary
The Correlation Summary function allows for the automatic calculation of depth ranges of like material, and the calculation of correlation value averages of the said depth ranges. It is designed to user definable, allowing the user to configure source table/fields, and provides the option for the user to manually define the depth ranges.
20.1
Default Configuration
The default configuration is designed to summarise data on CPT_DATA_LOWER_BEST_UPPER, and write the result to CPT_POINT_CORRELATION_SUMMARY. Some parameters may be configured on the CPT_PROJECT_PARAMETERS table, indicated by the red box.
20.2
Custom Configuration
The library table DG_CPT_CORRELATION_SUMMARY_CONFIG stores the configuration. An unlimited number of correlation fields may be summarised; the user needs to keep adding records into the configuration table with incrementing trailing numbers in the Name values.
121
There are two parts to the calculation and hence two parts to the configuration, namely Interval Calculation and Average Calculation. The calculation logic and configuration parameters are defined below.
20.2.1
Interval Calculation
Multiple fields may be used to define the intervals. Each set of parameters is to be suffixed with a number (#).
20.2.1.1
Parameters
Parameter names and their definitions are defined below. IntervalMinimumThickness: Minimum thickness of an interval, intervals thinner than this value will be appended to surrounding intervals. Can be a field reference or explicit value. IntervalSourceField#: gINT field reference for field used for interval definition IntervalSourceBreakVariance#: A new interval is made when the value in IntervalSourceField# varies from IntervalSourceField# value at the beginning of the interval by more than the value in IntervalSourceBreakVariance. Can be a field reference or explicit value. IntervalSourceDepthMaximumGap#: If the vertical gap between IntervalSourceField# nonnull values is greater than IntervalSourceDepthMaximumGap# then a new interval is made. The bottom depth of the interval above is the depth of the last record with data. A new interval with top depth equal to the current depth is created. Can be a field reference or explicit value.
20.2.1.2
Calculation Logic
For each set of IntervalSourceField#, IntervalSourceBreakVariance# and IntervalSourceDepthMaximumGap#, the code steps through the Source table and makes a new interval when: 1. The value in IntervalSourceField# varies from IntervalSourceField# value at the beginning of the interval by more than the value in IntervalSourceBreakVariance#.
122
2.
If the vertical gap between IntervalSourceField# non-null values is greater than IntervalSourceDepthMaximumGap# then a new interval is made. The bottom depth of the interval above is the depth of the last record with data. A new interval with top depth equal to the current depth is created.
Then a distinct list of all interval top and bottom depths is made from all interval source sets.
20.2.2
20.2.2.1
Average Calculation
Parameters
Parameter names and their definitions are defined below. TargetBottomField: field name of the bottom field IntervalUseExistingTargetDepths: True to use existing depths on Point Correlation Summary table, data in named target columns will be cleared before updating new data. Can be a field reference or explicit value. AverageSourceField#: Field reference for source data. All AverageSourceField# must be from the same table AverageTargetField#: Field reference for target location. All AverageTargetField# must be from the same table
The target table is assumed to have a gINT KeySet of PointID,Depth.
20.2.2.2
Calculation Logic
For each interval the code loops through and calculates the average of AverageSourceField# in the interval and writes the result to AverageTargetField#, Depth and TargetBottomField.
123
21 Configuring the Design Line

The CPT_DESIGN_LINE and CPT_DESIGN_LINE_DATA tables define the design line for Cone Resistance and all correlations. In the case of Cone Resistance the data is written to the CPT_DATA table, and can display on log and fence reports. For correlations the data is optionally displayed on Graph reports, and not written to CPT Data. You can assign the Design Line to use on the Project Parameter and Point Parameter tables.
To be able to print a design line on the and columns on the log reports, the Design line must first be defined in the CPT_DESIGN_LINE and CPT_DESIGN_LINE_DATA tables. To enter data in the CPT_DESIGN_LINE_DATA table (lower screen); enter a Design Line ID in the CPT_DESIGN_LINE table (upper screen). Enter a description if desired. Then click on the CPT_DESIGN_LINE_DATA table. Each row represents a node (point or corner) in the Design Line, where the Elevation or Depth represents the vertical axis and the Cone_Resistance represents the horizontal axis. The Node ID determines the order in which the nodes are drawn, as the Design Line is constructed by drawing a line from one node to the next. When the values in either the CPT_DESIGN_LINE or CPT_DESIGN_LINE_DATA tables are modified, you will be prompted with the following:
124
Every row in the CPT_DATA table has a Cone_Resistance_Design_Line value, which is calculated based on which Design Line is assigned and the depth of the current row. Therefore, it is necessary to recalculate the CPT_DATA table to reflect any changes made in these tables if an existing Design Line is modified. However, if entering a new Design Line, it is unlikely the new Design Line is assigned to any PointIDs, so it is unnecessary to recalculate the CPT_DATA table. The Elevation value will always take precedence over Depth when calculating the Design Line. If there are both Elevation and Depth values in this table, then only the Elevation values are used, and the Depth values are ignored. Only if the entire Elevation column is left blank, the Depth values are used. Once the Design Lines have been defined, they can be assigned to PointIDs in the CPT_POINT_PARAMETERS table or on the CPT_PROJECT_PARAMETERS. The two fields in this table related to the Design Line are Design_Line and Show_Design_Line. The Design_Line field is a pick list of the design Lines defined in the CPT_DESIGN_LINE Table, and the Show_Design_Line field is a check box which determines whether the Design Line is shown on the CPT log reports or not. The Design Line is represented on the CPT log reports as a thick black line.
125
22 qc and qt Averaging
22.1 Moving Average
The Cone_Resistance_Moving_Average and Total_Cone_Resistance_Moving_Average field on CPT_DATA is an average of and values above and below the given depth. The distance above and below can be configured in the CPT_PROJECT_PARAMETERS table, in the field Moving_Average_Thickness. The thickness defines the depth range of the and values taken, where the given depth is in the middle of the range. For example, specifying a Moving_Average_Thickness of 1 m, the from the given depth. and values are taken from 0.5m
22.2
Stepped Average
Similar concept to moving average, except the interval is a fixed depth scale, e.g. 0 m to 1 m, 1 m to 2 m etc. The step distance id defined in Stepped_Average_Thickness on CPT_PROJECT_PARAMETERS.
22.3
Strata Average
Strata average takes intervals from the STRATA_MAIN table. Hence you first need to run the Transfer Description and Consistency function, and then recalculate the CPT_DATA table.
126
23 Exclude Fines Layers

A fines layer is defined by consecutive rows that have been classified as fine in the Soil_Type_1 field. If the fines layer is thicker than a predetermined length, then the Exclude field is checked and records within a buffer distance are also have Exclude checked. The Exclude field can be used to control what records print on the CPT reports. The minimum thickness to exclude the Fines layer can be defined in the Exclude_Fines_Layer_Thickness field in the CPT_PROJECT_PARAMETERS table or the CPT_POINT_PARAMETERS table. The value in the CPT_POINT_PARAMETERS table takes precedence. Likewise, the buffer thickness of the records above and below the fines layer to exclude can be defined in the field in the Exclude_Fines_Layer_Buffer field in the CPT_PROJECT_PARAMETERS or the CPT_POINT_PARAMETERS table. This function requires the following fields to be present: CPT_DATA table Exclude, type Boolean, cell colour Field - Calculated Exclude_Fines_Layer_Thickness, type Double, Unit m, Cell colour Field Enter Data Exclude_Fines_Layer_Buffer, type Double, Unit m, Cell colour Field Enter Data Exclude_Fines_Layer_Thickness, type Double, Unit m, Cell colour Field Enter Data Exclude_Fines_Layer_Buffer, type Double, Unit m, Cell colour Field Enter Data
CPT_POINT_PARAMETERS table,
CPT_PROJECT_PARAMETERS table
You may wish to add a Body Data Output Condition on plot vs. depth entities on reports to reference the Exclude field to determine whether or not to output the record.
127
24 Dissipation Test Analysis

Dissipation tests may be analysed using the strain path method (SPM) proposed by Houlsby and Teh (1988). Further, dissipation tests carried out in over consolidated soils maybe corrected using the square root time method as proposed in Sully et al. (1999), and short tests may be extrapolated forward to estimate tx. Horizontal coefficient of consolidation in Teh (1988): is calculated using the method proposed by Houlsby and
is the modified dimensionless time factor and depends on the degree of dissipation at time t. For 50% dissipation is 0.245. and are rigidity index and penetrometer radius respectively. t is the time elapsed to reach to the desired dissipation degree (usually equals to ) Vertical coefficient of consolidation in is calculated by dividing the by Ratio_ch_to_cv.
24.1
1. 2.
Procedure to analyse a dissipation test in normally consolidated soil

Import the data as described in section 5 Data Import. Navigate to INPUT | CPT | Dissipation Test, and open the required PointID and Test Number. This example will use PointID V-Diss test NC, which is the same as the test at 14.625 m in data file Probedrill_01.dis. After import the screen will look similar to the following screen shot.
3. 4.
Ensure the ground water depth is defined, see section 7 Groundwater. Set CPT_GENERAL.Groundwater_Depth to 1.50. In this example the Pore_Pressure_Filter_Position must be set to u2.
128
5.
Rigidity_Index, Ir, maybe automatically looked up from CPT_DATA.Rigidity_Index_1 from the record with the same depth or next smaller depth, or may be manually defined by first checking the field Override_Rigidity_Index, Override Ir, and then entering a value. In this example we will manually define 150. Initial_Pore_Pressure, ui, must be manually set, and is typically the first pore pressure reading of the test. In this example we will manually define 579.6. Corrected_Initial_Pore_Pressure from back-extrapolation, uc, and Gradient_Corrected_Line, are not typically required for normally consolidated soils. In this example these two fields are left blank. In_Situ_Pore_Pressure is automatically calculated based on the groundwater depth (described in section 7 Groundwater). By checking Override_In_Situ_Pore_Pressure, the user can manually set u0. In this example we will allow u0 to automatically calculate. Degree_Dissipation defines the degree of dissipation, typically 50, or a lower value if t50 was not reached. In this example we will use 50.
6. 7.
8.
9.
10. Forward_Extraplolation_Y_Intercept and Forward_Extrapolation_Gradient can be used to define a best fit line to forward extrapolate to a t beyond the recorded data when the test doesnt reach the required Degree Dissipation. In this example these two fields are left blank. 11. Ratio_ch_to_cv is the ratio of horizontal coefficient of consolidation to vertical coefficient of consolidation. In this example we will use 3. 12. Now click the Save button, and the recalculated screen should be similar to the following screen shot.
13. To preview the graph report, click on the bottom half of the screen and the click the Preview icon. Graph!cpt diss. pore pressure vs. sqr t should already be set as the default report for this table. The preview should be similar to the following figure.
129
130
24.2
Procedure to analyse a dissipation test in overconsolidated soil
This example uses PointID V-Diss test OC, which corresponds with the data in file Geotech_AB_04.cpt and Geotech_AB_04.dpt. 1. 2. 3. Follow steps 1 to 6 and 8 to 12 described above, however in this example set Ir to 200, ui to 240.0, and Ratio ch to cv to 5. You may also like to use the minimum and maximum scale fields to control the graph report scale extents. As you can see in the following graph, the pore pressure first increases before decreasing. This is a typical Type III over consolidated response described in Sully et al 1999. The uc and Gradient Corrected Line must be correctly defined (see figure 7 in Sully et al 1999). The simplest procedure is to preview the Graph report cpt diss. pore pressure vs. sqr t by clicking on the INPUT preview button , estimate uc and the gradient, close the preview and enter the estimated numbers in the fields. Repeat the procedure until you are happy with the magenta coloured line.
131
132
24.3
Procedure to use forward extrapolation
The forward extrapolation option allow the user to define a straight line in measure pore pressure square root minute space that will be used to estimate tx beyond the recorded data range. An example of it use is illustrated below. In this example, PointID = V-Diss test NC 2, the data was recorded for only 64 seconds which corresponds with 5.5% degree of dissipation. Using the forward extrapolation line we can estimate t50. 1. 2. Enter data in CPT_DISSIPATION_TEST_GENERAL as described in previous examples. The simplest procedure to define the Forward_Extraplolation_Y_Intercept and Forward_Extrapolation_Gradient fields is to preview the Graph report cpt diss. pore pressure vs. sqr t by clicking on the INPUT preview button , estimate y intercept and gradient, close the preview and enter the estimated numbers in the fields. Repeat the procedure until you are happy with the orange coloured line. An alternative is to print the same report in output and manually define the line on paper and then enter the values in the fields.
133
134
25 Symbology
The Symbology feature in the CPT Tool provides a way to dynamically configure the output and presentation of derived parameter and correlation plots, graphs and text entities in the CPT gINT log and fence reports with relative ease. Almost all aspects of the entities are configurable, from the plot line colour/type, minimum/maximum scale, to units and header text.
25.1
Symbology Table Structure
The Symbology configuration can be applied to differing levels of scope, from the Library (global), Project and PointID. On output of a report, the configuration in the PointID level takes precedence over Project, followed by Library. If no configuration exists for the PointID level, it will look to the Project level, then Library. This hierarchical system allows you to configure differing sets of configuration to a particular project, or a single/selected group of PointIDs, with the default configuration being in the library.
25.1.1
Library
There are two Symbology tables in the gINT library, DG_CPT_SYMBOLOGY and DG_CPT_SYMBOLOGY_SCALES_UNITS. DG_CPT_SYMBOLOGY is the place to store your default/project level configuration of your CPT derived parameters/correlation entities in your CPT log, fence and graph reports.
DG_CPT_SYMBOLOGY_SCALES_UNITS is the place to store configuration options that may differ in value depending on the currently selected unit system.
135
25.1.2
Project
The project-specific Symbology table in the gINT Project database is called CPT_PROJECT_SYMBOLOGY. Configuration values entered here apply to all CPTs in the current project only. Configuration values entered in this table will override the values in the library Symbology table.
136
25.1.3
Point
The project-specific Symbology table in the gINT Project database is called CPT_POINT_SYMBOLOGY. Configuration values entered here apply to all CPTs in the current project only. Configuration values entered in this table will override the values in the library Symbology table.
137
25.2
25.2.1
Field Name Parameter
Configurable Options
CPT_SYMBOLOGY
Description Unique identifier of the correlation or parameter. New Parameters can be added in DG_CPT_SYMBOLOGY only. Table/Field reference of the parameter. Value is used in the CPT log/fence reports, and must be in <<TABLE.Field>> format. This value should only be modified if you have renamed the corresponding field in your Project database. Table/Field reference of the parameter. Value is used in SQL Queries in the CPT log/fence reports, and must be in [TABLE].[Field] format. This value should only be modified if you have renamed the corresponding field in your Project database. Table reference of the parameter. Value is used in SQL Queries in the CPT log/fence reports, and must be in [Table] format. Line colour displayed to represent the parameter in the CPT log/fence report plot entities. Line type displayed to represent the parameter in the CPT log/fence report plot entities. Line type displayed to represent the comparison parameter in the comparison CPT log/fence report plot entities. Line thickness displayed to represent the parameter in the CPT log/fence report plot entities. Data Marker displayed to represent the parameter in the CPT log/fence report plot entities and graph reports, in millimetres. Height of Data Marker displayed to represent the parameter in the CPT log/fence report plot entities in millimetres. Height of Data Marker displayed to represent the parameter in the CPT graph reports, in millimetres. Enter True to show the parameter in the CPT log/fence report plot entities, False to hide. Name of the parameter. This value will appear in the header of the CPT log/Fence report plot entities, and in the axis label of CPT graphs. Name takes precedence over Abbreviation on log and graph reports, and Abbreviation takes precedence over Name on fence reports. If the Parameter is a part of a grouped/numbered series (e.g. Undrained Shear Strength 1, Undrained Shear Strength 2, etc.), then the name of the first parameter in the series will be displayed in the header of the plot. Abbreviated name of the parameter. This value will appear in the header of the CPT log/Fence report plot entities, and in the axis label of CPT graphs. Name takes precedence over Abbreviation on log and graph reports, and Abbreviation takes precedence over Name on fence reports. If the parameter is a part of a grouped/numbered series (e.g. Undrained Shear Strength 1, Undrained Shear Strength 2, etc.), then the abbreviation of the first parameter in the series will be displayed in the header of the plot. Configured In Library, Project, Point Library
gINT Field Name
SQL Field Name
Library
SQL Table Name Line Colour Line Type Comparison Line Type Line Thickness Data Marker Data Marker Height Log Data Marker Height Graph Show on Report Name
Library Library, Project, Point Library, Project, Point Library, Project, Point Library, Project, Point Library, Project, Point Library, Project, Point Library, Project, Point Library, Project, Point Library
Abbreviation
Library
138
Field Name Reference
Description Reference of the parameter. This value will appear in headers and legends in CPT log, fence and graph reports. Reference Short takes precedence over Reference on log and fence reports. Legends in the CPT graph reports only use Reference. Shortened reference of the parameter. This value will appear in headers and legends in CPT log and fence reports. Reference Short takes precedence over Reference on log and fence reports. Reference Short is not used in Graph Reports. Legend type displayed in the header of CPT log/Fence report plot entities. Number displays the number in the series of parameters, a line and data marker that represents that parameter, for each parameter in the series. Reference displays the reference as entered in the Reference or Reference Short fields in the Symbology for each parameter in the series. The reference text is coloured to the line colour assigned to the parameter. Check to make the scale fields on point and project symbology grey/read-only Field in the design line data table related to the parameter, set in format [Table}.[Field]. Only set this for parameter 1 of a set of correlations. For example, Coefficient Lateral Earth Pressure 1 has a value of [CPT_DESIGN_LINE_DATA].[Coefficient_Lateral_Earth_Pressure]
Configured In Library
Reference Short
Library
Header Legend Type
Library, Project, Point
Scale Not Applicable Design Line Field
Library Library
25.2.2
Field Name Unit System Parameter Unit
Description Unit System the parameter configuration is applicable to Unique identifier of the correlation or parameter. Unit of the parameter, value will be displayed in the header section of the log/fence column. Minimum axis scale of the CPT log/fence report plot entities. gINT Expressions can be entered in the library Symbology table only. Numeric values can be entered in all Symbology tables. If the Parameter is a part of a grouped/numbered series (e.g. Undrained Shear Strength 1, Undrained Shear Strength 2, etc.), then the minimum scale of the first parameter in the series will be displayed on the plot. Maximum axis scale of the CPT log/fence report plot entities. gINT Expressions can be entered in the library Symbology table only. Numeric values can be entered in all Symbology tables. If the Parameter is a part of a grouped/numbered series (e.g. Undrained Shear Strength 1, Undrained Shear Strength 2, etc.), then the maximum scale of the first parameter in the series will be displayed on the plot. Automatically define the minimum and maximum scale for the CPT log/fence report plot entity. PointID retrieves the minimum and maximum values for the PointID currently outputted. Project retrieves the minimum and maximum values for the entire project. Clear the cell to turn off automatic scale. Number of decimal places to round the minimum and maximum scales to, if Automatic Scale is used.
Minimum Scale
Maximum Scale
Automatic Scale
Automatic Scale Round To
139
Field Name Number of Divisions
Description Number of divisions in the CPT log/fence report plot entities. This value controls the number of division lines visible in the plot entity, as well as the scale values at each division. If the Parameter is a part of a grouped/numbered series (e.g. Undrained Shear Strength 1, Undrained Shear Strength 2, etc.), then the number of divisions of the first parameter in the series will be applied to the plot. Legend type displayed in the header of CPT log/Fence report plot entities. Number displays the number in the series of parameters, a line and data marker that represents that parameter, for each parameter in the series. Reference displays the reference as entered in the Reference or Reference Short fields in the Symbology for each parameter in the series. The reference text is coloured to the line colour assigned to the parameter.
Header Legend Type
140
26 Unit Conversion
26.1 Introduction
The CPT Tool is designed to report data in the same unit it is stored in, this must be the case because doing large numbers of unit conversion calculations on reports would make report generation too slow for practical use. The unit conversion feature of the CPT Tool allows the user to define the unit of measurement used in storing, calculating and reporting data in the CPT Tool project database. In addition, the unit conversion feature can convert a project database from one particular set of units to another set of units. By default, all derived parameter calculations is in SI units. Therefore, if the values required for the calculation are not in SI units, they will be converted to SI units for the calculation, and the results converted back to the target unit. For example, the CPT Tool calculation assumes Cone Resistance in MPa, and will convert the Cone Resistance value to MPa if it is stored in a different unit, such as tsf or kPa. A list of available unit systems is stored in the DG_COM_UNIT_SYSTEM Library Lookup List. The current unit system is stored in the read-only Unit_System field in the CPT_PROJECT_PARAMETERS table. The CPT Tool has two preconfigured unit systems that are ready to use. These are the SI and English unit systems. You may adjust these as required, or create a new unit system. Three tutorials related to Units are included as appendices. Appendix D - Tutorial: Creating a New Unit System Appendix E - Tutorial: Entering a New Unit Quantity Appendix F - Tutorial: How to change a field unit and make it work with reports
26.2
Project Field Units
The unit of a field in the project database is determined by the value in the Units field property.
141
26.3
Library Configuration
The configuration tables reside in the gINT library file. It is crucial that these configuration tables exist and are configured for the CPT Tool to function correctly.
26.3.1
DG_COM_UNIT_CONVERSION
All units, conversion factors and equations are listed in this table.
Column Name Source_Unit Formatted_Source_Unit Description Unit to be converted to base SI unit. The unit must exist in the gINT Field Units Library table. Formatted version of the unit for displaying on reports. If you wish to display text that is different to the source unit when presented on reports (such as apply a subscript or superscript to the unit), enter the text expression in this column. If blank, the Source_Unit value will be used to display units on reports. Multiplier factor to convert the Source unit to the base SI unit. If the conversion cannot be represented by a factor, leave blank and enter an expression in the Source_To_SI_Conversion_Equation column. The conversion factor takes precedence over the conversion equation. The inverse of this value is used to convert a value that is in SI units to the Source unit. Equation to convert the Source unit to the base SI unit. <<Source>> is a variable that represents the value that is to be converted, and must be included in the equation. The Source to SI Conversion Equation is only used if the Source to SI Conversion Factor cannot be retrieved. The SI unit serves as the base unit for conversions, and acts as a bridge for converting one unit to another, by converting a source unit to the SI unit, and then converting the SI unit value to the target unit by applying the inverse of the factor or equation that converts the target unit to the SI unit.
Source_To_SI_Conversion_Factor
Source_To_SI_Conversion_Equation
SI_Unit
142
26.3.2
DG_CPT_FIELD_MAP
This table stores unit conversion related configuration specific for fields in the database. The records in this table are not automatically ordered by Table_Name and Field_Name, so it is recommended that you maintain the order of the records manually in a logical/alphabetical order by right-clicking on a row header and selecting Insert Row, or by entering a new row at the bottom, then right-click + drag on the row header to change the row position.
Column Name Table Name Field Name Location Description Table Name Field Name Database location of the Table Field. The two options are Project and Library. However, unit conversion feature only applies to fields in the Project database. This is a required field. These columns store the unit for the table field. The name of the column represents the unit system. For example, SI stores the units for the SI unit system, and English stores the units for the English unit system, for the named field of the current row. The column names must be listed in the DG_COM_UNIT_SYSTEM library lookup list, as the column names are used as the unit system lookup values in the Unit Conversion Add-In and the DG_CPT_SYMBOLOGY_SCALES_UNITS table. Minimum value field rule property value to be applied to the current named field for the unit system.
English SI <<Unit System>>
English_FR_Minimum SI_FR_Minimum <<Unit System>>_FR_Minimum English_FR_Maximum SI_FR_Maximum <<Unit System>>_FR_Maximum
Maximum value field rule property value to be applied to the current named field for the unit system.
143
Column Name English_FR_Decimals_Displayed SI_FR_Decimals_Displayed <<Unit System>>_FR_Decimals_Displayed English_FR_Round_To_Nearest SI_FR_Round_To_Nearest <<Unit System>>_FR_Round_To_Nearest English_FR_Format_Type SI_FR_Format_Type <<Unit System>>_FR_Format_Type English_Default SI_Default <<Unit System>>_Default
Description Decimals displayed field rule property value to be applied to the current named field for the unit system.
Round to Nearest field rule property value to be applied to the current named field for the unit system.
Format type field rule property value to be applied to the current named field for the unit system. Available options include Decimal Format, Scientific Notation, Significant Figures and BSI Moisture Content. Default value field property value to be applied to the current named field for the unit system.
26.3.3
This table allows you to configure Log/Fence report column units, minimum/maximum scales and line divisions for each Unit System/Parameter combination, which will most likely differ between unit systems. The CPT Log/Fence report columns will automatically apply the report options depending on the current unit system. The records in this table are not automatically ordered by Unit_System and Parameter, so it is recommended that you maintain the order of the records manually in logical/alphabetical order by rightclicking on a row header and selecting Insert Row, or by entering a new row at the bottom, then rightclick + drag on the row header to change the row position.
Column Name Unit System Parameter Description Unit System Parameter name
144
Column Name Unit
Description Unit the parameter is in for the named unit system
26.4
Unit Conversion of the Current Project
The Unit Conversion Add-In Command is used to convert the current gINT project database from one unit system to another unit system, as configured in the library configuration tables. To open the Unit Conversion form, call the command Add-Ins > Datgel CPT Tool > Unit Conversion.
Current Unit System Unit system of the project file Convert To Unit system to convert the current project file to Validate Runs a validation check on the unit conversion configuration for the unit system selected in the Convert To drop down list. The validation involves the following checks: Check all required configuration tables fields exist. This includes the Unit System, Field Rules and Default value fields in DG_CPT_FIELD_MAP, which are prefixed with the name of the unit system. Check the table/fields listed in DG_CPT_FIELD_MAP exist in the current project database. Check that for all table/fields that is to be converted from its current unit to a target unit, a conversion factor or equation can be determined. For example, if a particular field is in metres and the target unit for that field configured in DG_CPT_FIELD_MAP is kilograms, the conversion factor cannot be determined.
A log report will appear listing any failed validation checks. All validation errors must be corrected for the unit conversion to execute. Execute Runs a validation check, and then if successful, executes the unit conversion process based on the configuration for the unit system selected in the Convert To drop down list. The unit conversion process is as below: The unit system selected in the Convert To drop down list is the Target unit system. The current unit for each field is taken from the Unit field property, and is taken as the Source unit. The value in the selected unit system column in DG_CPT_FIELD_MAP for the corresponding table/field as named in the Table_Name and Field_Name fields is taken as the Target unit. A unit conversion factor from the Source unit to the Target unit is determined from the DG_COM_UNIT_CONVERSION table. The conversion factor is determined by multiplying the factor to convert the Source unit to the base SI unit, then multiplying the inverse of the factor to convert the target unit to the base SI unit. The equation is used if the factor is missing.
145
The values for the named fields in the current project database are multiplied by the conversion factor. If either the Source or Target unit is empty, then no conversion takes place for that field. The Target Unit, Field Rules and default values are applied to each table/field listed in DG_CPT_FIELD_MAP. The name of the target unit system is written to the Unit_System field on the CPT_PROJECT_PARAMETERS table.
If any errors are found in the validation check, the conversion will not be executed. If the unit conversion is run on a gINT Project file (*.gpj), a backup file will be made in the same directory before the unit conversion is applied. The file will be prefixed with a time stamp, and renamed to have an extension of (*.dbk). If there are any errors that occur during the unit conversion process, or you wish to revert the changes made by the unit conversion, rename the *.dbk file to *.gpj. Some units of the fields may not appear to be updated immediately after the unit conversion process. Close the project file and reopen it to see the field unit changes.
146
27 Formula Tool and Data Correction

Tool Functions
27.1
Type Constants Constants Constants Constants Log and Exponential Log and Exponential Log and Exponential Log and Exponential Log and Exponential Miscellaneous Miscellaneous Miscellaneous Miscellaneous
Functions
Description , 3.14159 Euler's Constant e, 2.71828 Boolean constant true Boolean constant false Natural Logarithm Logarithm base 10 Logarithm base 2 Exponential (e^x) Power If Absolute Value / Magnitude Binomial coefficients First Data, returns first non-empty value from list Function Name Pi e true false ln(x) log(x) lg(x) exp(x) pow(x) if(cond, trueval, falseval) abs(x) binom(n, i) first(x1,x2,x3,...) LookupIntervalRange("<<Current Interval Table.Field>>","<<Lookup Value Table.Field>>","<<Top Interval Table.Field>>","<<Bottom Interval Table.Field>>") mod(x,y) x%y MovingAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>",Thickness) rand() SteppedAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>",Thickness) SteppedExtrapolation("<<Current Interval Table.Field>>","<<Values to Extrapolate Table.Field>>") sqrt(x) sum(x,y,...) str(x) TableIntervalAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>","<<Top Interval Table.Field>>","<<Bottom Interval Table.Field>>") +
Miscellaneous Miscellaneous Miscellaneous
Lookup Interval Range Modulus Modulus
Miscellaneous Miscellaneous
Moving Average Random number (between 0 and 1)
Miscellaneous
Stepped Average
Miscellaneous Miscellaneous Miscellaneous Miscellaneous
Stepped Extrapolation Square Root Sum Str (number to string)
Miscellaneous Operators
Table Interval Average Addition
147
Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Operators Rounding Rounding Rounding Rounding Statistical Statistical Statistical Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric Trigonometric
Subtraction Division Multiplication Unary Plus Unary Minus Power Modulus Boolean Not Boolean And Boolean Or Equal Not Equal Less Than Greater Than or Equal Less or Equal Greater Than or Equal Round Round Floor Ceiling Average Minimum Maximum Sine (in radians) Cosine (in radians) Tangent (in radians) Arc Sine (in radians) Arc Cosine (in radians) Arc Tangent (in radians) Arc Tangent (with 2 parameters, in radians) Hyperbolic Sine (in radians) Hyperbolic Cosine (in radians) Hyperbolic Tangent (in radians) Inverse Hyperbolic Sine (in radians) Inverse Hyperbolic Cosine (in radians) Inverse Hyperbolic Tangent (in radians)
/ * +x -x ^ % ! && || == != < > <= >= round(x) round(x, p) floor(x) ceil(x) avg(x1,x2,x3,...) min(x1,x2,x3,...) max(x1,x2,x3,...) sin(x) cos(x) tan(x) asin(x) acos(x) atan(x) atan2(y, x) sinh(x) cosh(x) tanh(x) asinh(x) acosh(x) atanh(x)
27.2
Special Functions
Functions that require explanation in greater detail are listed in this section.
148
27.2.1
Lookup
Lookup("<<Lookup Table.Field>>","SQL Where Clause"[,Is Library Lookup true/false][, Required Unit])
The Lookup function returns the first value from the specified field of the Lookup table, where the record satisfies the conditions of the SQL Where Clause, and if a project table, is a corresponding keyset record. The Lookup function is only available in the Formula Tool. Below is a definition of the parameters for Lookup: "<<Lookup Table.Field>>" Table field reference of the value to look up. This can be from either Project or Library. "SQL Where Clause" SQL compatible Where Clause to filter the lookup results. Table/Field references must be in the <<Table.Field>> format, and must be from the same table as the Table in <<Lookup Table.Field>>. Variables defined in the Variables grid can be referenced here. For example, if a variable called qc has been declared as a Variable in the Variables grid, there Where Clause can reference qc, and it will be replaced with the value during the calculation. When using variable references with operators, there must be a space between the variable and the operator. For example, (Qc = 1) is ok, (Qc=1) is not. Is Library Lookup true/false (optional) Determines whether to query the library only, or the project only, or both library and project. Entering true will force the function to query the library only, false will force the function to query the project only. If omitted, the function will try to query the library first, if table/field does not exist then it will query the project. Required Unit (optional) Unit the returned value must be in. If the Required Unit does not match the unit of the <<Lookup Table.Field>>, then it will be converted to the Required Unit.
The Lookup function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. Below is an example usage of the Lookup function.
Lookup( "<<DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL.Soil_Description>>" , "(<<DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL.Soil_Type>> = SoilType) and (qc > <<DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL.Cone_Resistance_Minimum>>) and (qc <= <<DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL.Cone_Resistance_Maximum>>)" , true )
27.2.2
LookupIntervalRange
LookupIntervalRange("<<Current Interval Table.Field>>","<<Lookup Value Table.Field>>","<<Top Interval Table.Field>>","<<Bottom Interval Table.Field>>")
The Lookup Interval Range function returns the a value for a specified field from another depth related table, where the current interval value in the CPT_DATA table lies in between the Top and Bottom intervals in the other table. The LookupIntervalAverage function is only available in the Formula Tool. Below is a definition of the parameters for LookupIntervalRange:
149
"<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value that is used as a search criteria for the value on the other table. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth.
"<<Lookup Value Table.Field>>" Other table field reference for the value to retrieve. "<<Top Interval Table.Field>>" Other table field reference to the field that contains the top interval values "<<Bottom Interval Table.Field>>" Other table field reference to the field that contains the bottom interval values
The Current Interval must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table. The Top and Bottom interval, and Lookup Value table field references must refer to fields from the same table. The LookupIntervalRange function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. The LookupIntervalRange function assumes that there is only one set of top and bottom intervals for each CPT data keyset, and that the top and bottom interval values do not create overlapping layers. If more than one matching value for the current interval is found, then the first value is returned. The LookupIntervalRange function assumes <<Current Interval Table.Field>>, <<Top Interval Table.Field>> and <<Bottom Interval Table.Field>> to be in the same units (e.g. m). Below is an example usage of the Lookup Interval Range function that retrieves the Void Ratio value from the Void_Ratio field in the CPT_MATERIAL_PROPERTIES table, where the current CPT_DATA depth lies between the top and bottom depths in the CPT_MATERIAL_PROPERTIES table.
LookupIntervalRange( "<<CPT_DATA.Depth>>" , "<<CPT_POINT_MATERIAL_PROPERTIES.Void_Ratio>>" , "<<CPT_POINT_MATERIAL_PROPERTIES.Depth>>" , "<<CPT_POINT_MATERIAL_PROPERTIES.Bottom>>" )
27.2.3
MaxMinValueOutOfRange
MaxMinValueOutOfRange("<<Value Table.Field>>",Boundary Value [,Value Less Than Boundary])
The Maximum Minimum Value out of Range function returns the maximum or minimum value out of a range of values that exceeds a boundary value. The MaxMinValueOutOfRange function is only available in the Formula Tool. For example, if the <<Value Table.Field>> is <<CPT_DATA.Cone_Resistance>>, the Boundary Value is 27 and Less Than Boundary set to False then wherever a range of Cone Resistance values exceed 27, it will return the highest Cone Resistance within that range, at the row where the highest value occurs. Below is a definition of the parameters for MaxMinValueOutOfRange: "<<Value Table.Field>>" Table field reference to the value to retrieve the range of values exceeding the boundary, and the maximum or minimum value within that range
150
Boundary Value Boundary value, must be numeric Value Less Than Boundary Value Less Than Boundary is a boolean field, assign true to retrieve minimum, false or leave blank to get maximum. This parameter is optional. If the parameter is empty or not defined, False (maximum) is assumed.
MaxMinValueOutOfRange("<<CPT_DATA.Cone_Resistance>>",27,True)
The Maximum Minimum Value out of Range function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form.
27.2.4
MovingAverage
MovingAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>",Thickness[,Stop Calculation on Gaps])
The Moving Average function returns an arithmetic mean of values above and below the current interval field value. Below is a definition of the parameters for MovingAverage: "<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value, and the range of averages. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth. "<<Values to Average Table.Field>>" Table field reference for the values to average. The data set of the average is obtained from this field. The field does not need to be a numeric type, but the values must be numeric. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. Thickness Defines the interval range of the values taken for the average, where the current interval is the middle of the range. Therefore, the minimum and maximum range of the average would be the current interval + thickness / 2 and current interval - thickness / 2 respectively. Stop Calculation on Gaps Stops retrieving values above or below the current interval field value if an empty value is found. Assign True to stop calculation on gaps, false otherwise. This parameter is optional. If the parameter is empty or not defined, False (do not stop calculation on gaps) is assumed.
The Current Interval and the Values to Average table field references must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table. If the MovingAverage function is used with a correlation evaluated by the Formula Tool, then the Iteration of the moving average formula must be greater than the iteration of the correlation. The MovingAverage function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. The MovingAverage function assumes the thickness is in the same units as <<Current Interval Table.Field>>. Below is a working example configuration of Moving Average:
151
In this example, an average of values above and below the given depth will be written to the Cone_Resistance_Moving_Average field in the CPT_DATA field. The distance above and below can be configured in the CPT_PROJECT_PARAMETERS table, in the field Moving_Average_Thickness. The thickness defines the depth range of the values taken, where the given depth is in the middle of the range. For example, specifying a Moving_Average_Thickness of 1 m, the given depth. values are taken from 0.5 m from the
27.2.5
MovingAverageConstrainedLCPC
MovingAverageConstrainedLCPC( "<<Current Interval Table.Field>>", Current Interval Required Unit, "<<Values to Average Table.Field>>", Values to Average Required Unit, DistanceLesserDepth, DistanceGreaterDepth, ConstrainingMinimumFactor, ConstrainingMaximumfactor)
The Moving Average Constrained LCPC function calculates a type of moving average known as the LCPC method as specified in the paper written by Bustamete and Giasenelli (1982). This function used to calculating the Pile Unit End Bearing Below is a definition of the parameters for MovingAverage: "<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value, and the range of averages. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth. Current Interval Required Unit Unit the current interval must be in. If the current interval value is not in the specified unit, it will be converted to be in that unit. "<<Values to Average Table.Field>>" Table field reference for the values to average. The data set of the average is obtained from this field. The field does not need to be a numeric
152
type, but the values must be numeric. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. Values to Average Required Unit Unit the values to average must be in. If the Values to Average value not in the specified unit, it will be converted to be in that unit. Distance Lesser Depth Furthermost distance above the current interval i.e. over the cone. This represents in the LCPC method definition. Distance Greater Depth Furthermost distance below the current interval i.e. below the pile point. This represents in the LCPC method definition. Constraining Minimum Factor Factor multiplied to to determine the minimum peak clipping boundary. Value given in the LCPC method definition is 0.7. Constraining Maximum Factor Factor multiplied to to determine the maximum peak clipping boundary. Value given in the LCPC method definition is 1.3.
The Current Interval and the Values to Average table field references must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table.. If the MovingAverageConstrainedLCPC function is used with a correlation evaluated by the Formula Tool, then the Iteration of the moving average formula must be greater than the iteration of the correlation. The MovingAverageConstrainedLCPC function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. Below is a working example configuration of Pile Unit End Bearing:
153
27.2.6
NextValue
NextValue("<<Next Value Table.Field>>" [,Required Unit])
Next Value function gets the value from the next row from the current calculation row for the specified field. NextValue only works for the current calculation table CPT_DATA, or a one to one child of CPT_DATA. If a formula has a reference to the NextValue function, the CPT Calculation will calculate from the bottommost row to the topmost row for that formula.
154
Below is a definition of the parameters for NextValue: "<<Next Value Table.Field>>" Table field reference to retrieve the next value from. As explained above, the Field must be one from CPT_DATA, or a one to one child of CPT_DATA. Required Unit (optional) Unit the returned value must be in. If the Required Unit does not match the unit of the <<Next Value Table.Field>>, then it will be converted to the Required Unit.
Below is an example usage of the NextValue Function:

NextValue("<<CPT_DATA_PILE.Pile_Axial_Capacity_Side_Friction_1>>","MN")
27.2.7
PreviousValue
PreviousValue("<<Previous Value Table.Field>>" [,Required Unit])
The Previous Value function gets the value from the row previous to the current calculation row for the specified field. PreviousValue only works for the current calculation table CPT_DATA, or a one to one child of CPT_DATA. Below is a definition of the parameters for PreviousValue: "<<Previous Value Table.Field>>" Table field reference to retrieve the previous value from. As explained above, the Field must be one from CPT_DATA, or a one to one child of CPT_DATA. Required Unit (optional) Unit the returned value must be in. If the Required Unit does not match the unit of the <<Previous Value Table.Field>>, then it will be converted to the Required Unit.
Below is an example usage of the PreviousValue Function:

PreviousValue("<<CPT_DATA_PILE.Pile_Axial_Capacity_Side_Friction_1>>","MN")
27.2.8
SteppedAverage
SteppedAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>",Thickness)
The Stepped Average function returns an arithmetic mean of values within an interval range that increments by the specified thickness. A graph of a set of stepped average values against the interval will appear as horizontal steps of equal width that step up or down. Below is a definition of the parameters for SteppedAverage: "<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value, and the range of averages. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be depth. "<<Values to Average Table.Field>>" Table field reference for the values to average. The data set of the average is obtained from this field. The field does not need to be a numeric type, but the values must be numeric. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. Thickness Defines the interval increment range of the values taken for the average.
The Current Interval and the Values to Average table field references must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table.. The SteppedAverage function assumes the thickness is in the same units as <<Current Interval Table.Field>>.
155
The SteppedAverage function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. If the SteppedAverage function is used with a correlation evaluated by the Formula Tool, then the Iteration of the moving average formula must be greater than the iteration of the correlation. Below is a working example configuration of SPT N60 Stepped Average:
The SPT average N60 value is a stepped average of values in the SPT_N60_1 field on the CPT_DATA table for each defined depth interval step. The average of the N60 values is calculated for each depth interval step, and the result is recorded in the SPT_Average_N60_1 field in the CPT_DATA table for each row in that interval step. The depth interval distance (thickness) is defined on the SPT_N60_Average_Interval field on CPT_POINT_PARAMETERS and CPT_PROJECT_PARAMETERS tables. The first function dictates that the value in the CPT_POINT_PARAMETERS table has precedence over the CPT_PROJECT_PARAMETERS table. For example, specifying a SPT_N60_Average_Interval of 1 m, the stepped average value at a depth of 0.5 m would be the average SPT N60 values between 0 m and 1 m.
27.2.9
SteppedExtrapolation
SteppedExtrapolation("<<Current Interval Table.Field>>","<<Values to Extrapolate Table.Field>>")
The Stepped Extrapolation function returns a value that is extrapolated to the midpoint between the current value to extrapolate, and the next value to extrapolate. From the current value to extrapolate to the midpoint, Stepped Extrapolation returns the current value to extrapolate, and from the midpoint to the next value to extrapolate, Stepped Extrapolation returns the next value to extrapolate. Below is a definition of the parameters for SteppedExtrapolation: "<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value, and is a reference point to determine the midpoint between two values to extrapolate. As denoted by the parameter name, the table field reference must be surrounded with quotation marks.
156
The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth. "<<Values to Extrapolate Table.Field>>" Table field reference for the values to extrapolate. The field does not need to be a numeric type, but the values must be numeric. As denoted by the parameter name, the table field reference must be surrounded with quotation marks.
The Current Interval and the Values to Extrapolate table field references must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table.. The Stepped Extrapolation cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. Below is a working example configuration Shear Wave Velocity Extrapolated:
Results:
157
27.2.10
TableIntervalAverage
TableIntervalAverage("<<Current Interval Table.Field>>","<<Values to Average Table.Field>>","<<Top Interval Table.Field>>","<<Bottom Interval Table.Field>>")
The Table Interval Average function returns an arithmetic mean of values within an interval range specified on another Table. A graph of a set of table interval average values against the interval will appear as horizontal steps whose width is top and bottom intervals specified on the corresponding table. Conceptually, the Table Interval Average is similar to the Stepped Average, but the step widths are defined by the Top and Bottom interval values. The TableIntervalAverage function is only available in the Formula Tool. Below is a definition of the parameters for TableIntervalAverage: "<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value, and the range of averages. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth. "<<Values to Average Table.Field>>" Table field reference for the values to average. The data set of the average is obtained from this field. The field does not need to be a numeric type, but the values must be numeric. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. "<<Top Interval Table.Field>>" Table field reference to the field that contains the top interval values "<<Bottom Interval Table.Field>>" Table field reference to the field that contains the bottom interval values
The Current Interval and the Values to Average table field references must refer to a field from the CPT_DATA table, or a one to one child of the CPT_DATA table. The Top and Bottom interval table field references must refer to fields from the same table. The TableIntervalAverage function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form. The TableIntervalAverage function assumes that there is only one set of top and bottom intervals for each CPT data keyset, and that the top and bottom interval values do not create overlapping layers. The TableIntervalAverage function assumes <<Current Interval Table.Field>>, <<Top Interval Table.Field>> and <<Bottom Interval Table.Field>> to be in the same units (e.g. m). Below is a working example configuration of Strata Average:
158
In this example, the cone resistance is averaged between the strata layers as defined by the Depth and Bottom fields in the STRATA_MAIN table, for the current PointID.
27.2.11
ValueOutOfRangeAtInterval
ValueOutOfRangeAtInterval( "<<Current Interval Table.Field>>", "<<Source Table.Field>>", Boundary Value, Interval Value [,Value Less Than Boundary])
The Value out of Range at Interval function returns values in the Source field that exceed a boundary value at specified intervals. If the value exceeds the boundary value but does not occur on the interval value, then no value is returned. The ValueOutOfRangeAtInterval function is only available in the Formula Tool. Consider this example:
<<Current Interval Table.Field>> is <<CPT_DATA.Depth>> <<Source Table.Field>> is <<CPT_DATA.Cone_Resistance>> Boundary Value is 27 Interval Value is 0.25 Less Than Boundary set to False
At every 0.25 depth intervals (e.g. 1, 1.25, 1.50), the function will check to see if Cone Resistance at that depth interval is greater than the Boundary Value. If Cone Resistance at a depth of 2.75 is 30, then the function will return 30. If the Cone Resistance is not greater than the Boundary Value, or it is greater than the boundary value but is not at the specified depth interval, then no value is returned. Below is a definition of the parameters for ValueOutOfRangeAtInterval:
159
"<<Current Interval Table.Field>>" Table field reference to the interval that determines the current interval value. As denoted by the parameter name, the table field reference must be surrounded with quotation marks. The values in the interval field must be uniformly increasing or decreasing in value with no duplicates. A typical interval field would be Depth.
"<<Value Table.Field>>" Table field reference to the value to check if they exceed the boundary Boundary Value Boundary value, must be numeric Value Less Than Boundary Value Less Than Boundary is a boolean field, assign true to return the value if it is less than the Boundary Value, false to return the value if it is greater than the Boundary Value. This parameter is optional. If the parameter is empty or not defined, False (greater than Boundary Value) is assumed.
The Value out of Range at Interval function cannot be evaluated via the Validate button or in Validation Reports from the Formula Tool Configuration Form.
160
28 Reports
28.1
Name CPT A4P CPT DYNAMIC 11X17L CPT DYNAMIC A3L CPT DYNAMIC A4P CPT DYNAMIC LETP CPT LETP CPT MATERIAL A4P CPT MATERIAL LETP CPT QC ONLY A4P CPT QC ONLY LETP CPT SOIL BEHAVIOUR TYPE INDEX A4P CPT SOIL BEHAVIOUR TYPE INDEX LETP CPTU A4P CPTU COMPARISON A4 CPTU COMPARISON LETP CPTU DERIVED MATERIAL A4P CPTU DERIVED MATERIAL LETP CPTU LETP CPTU LIQUEFACTION 11X17L CPTU LIQUEFACTION A3L CPTU MATERIAL A4P CPTU MATERIAL LETP CPTU MEASURED MATERIAL A4P CPTU MEASURED MATERIAL LETP CPTU MOVING AVERAGE A4P CPTU NL A4P CPTU NL EN A4P CPTU NORMALISED N60 11X17L CPTU NORMALISED N60 A3L CPTU PHI 11X17L CPT Tool gINT Add-In 3 User Guide
Log Reports
Description CPT / Friction cone report with qc, fs and Rf. Dynamic CPT report. Dynamic CPT report. Dynamic CPT report. Dynamic CPT report. CPT / Friction cone report with qc, fs and Rf. CPT / Friction cone report with qc, fs, Rf and soil description. CPT / Friction cone report with qc, fs, Rf and soil description CPT qc only. CPT qc only. CPT report with qt, Fr, Bq Ic 1 and Ic 2. CPT report with qt, Fr, Bq Ic 1 and Ic 2. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Bq. CPT/CPTU Comparison log using POINT.Associated_PointID. CPT/CPTU Comparison log using POINT.Associated_PointID. CPTU / Piezocone derived report with qt, Rf, Bq and material description. CPTU / Piezocone derived report with qt, Rf, Bq and material description. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Bq. CPTU / Piezocone report with liquefaction related data. CPTU / Piezocone report with liquefaction related data. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf, Bq and material description. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf, Bq and material description. CPTU / Piezocone measured report with qc, fs, u, u0 and material description. CPTU / Piezocone measured report with qc, fs, u, u0 and material description. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Bq. CPTU / Piezocone report to Dutch Standard in English with qc, fs, u, Rf. CPTU / Piezocone report to Dutch Standard in English with qc, fs, u, Rf. CPTU normalised parameters (qc, qt, Rf, Bq, Penetration Rate, Qt, Fr), interpreted soil type, N60 and material description. CPTU normalised parameters (qc, qt, Rf, Bq, Penetration Rate, Qt, Fr), interpreted soil type, N60 and material description. CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, Datgel DCT-UG-001 - 3.02 - August 2012
Table 3 - Log Reports
161
Phi', material description and consistency. CPTU PHI A3L CPTU SU 11X17L CPTU SU A3L CPTU SU A4P CPTU SU DR 11X17L CPTU SU DR A3L CPTU SU DR CC 11X17L CPTU SU DR CC A3L CPTU SU LETP CPTU WITHOUT DESIGN LINE A4P SCPTU ALL A4P SCPTU ALL LETP SCPTU CORRELATED A4P SCPTU CORRELATED LETP SCPTU MEASURED EXTRAP A4P SCPTU MEASURED EXTRAP LETP CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, Phi', material description and consistency. CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, su, material description and consistency. CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, su, material description and consistency. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Su. CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, Dr, su, material description and consistency. CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type, Dr, su, material description and consistency. CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, Dr, su, Cc, material description and consistency. CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, Dr, su, Cc, material description and consistency. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Su. CPTU / Piezocone report with qt, fs or ft, u, u0, Rf and Bq. SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Measured & Extrapolated). SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Measured & Extrapolated). SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Correlated). SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Correlated). SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Measured, Extrapolated & Correlated). SCPTU / Piezocone report with qt, fs, ub, t50 and Vs (Measured, Extrapolated & Correlated).
28.1.1
Name Comparison
Dynamic Logs
Value False to show one PointID, True to two PointIDs on the page, one in red and the other in blue. This will override the value set in POINT.Associated_PointID Defines the type of depth or elevation scale that will display on the left side of the log. Select the parameters in order from left to right of page.
Table 4 - Dynamic Log Report Variables
Override Associated PointID Depth Elevation Scale Column 1 . Column 10 Width 1 Width 10 Show qt qc Average Legend Show qc Average Legend Show qt Average Legend
Select the width of the columns corresponding with parameter defined above. If a Width field is left blank for a Column that has a value, then these columns will automatically fill the available width. Options to show standard legends in the footer of the report page.
162
Show Dissipation Legend Show Design Line Legend Legend 1 Legend 5 Header Legend Type Defines if numbers or the reference names will display in the column header. Select up to 5 parameters that will display reference legends in the footer of the page.
28.2
Name
Fences Reports
Description A3 landscape fence report with 6 plot column options and CPT classification colour column A3 landscape fence report with 6 plot column options and CPT classification colour column A4 landscape fence report with 6 plot column options and CPT classification colour column A4 portrait fence report with 6 plot column options and CPT classification colour column Letter landscape fence report with 6 plot column options and CPT classification colour column Letter portrait fence report with 6 plot column options and CPT classification colour column
Table 5 - Fence Reports
CPT FENCE 11X17L CPT FENCE A3L CPT FENCE A4L CPT FENCE A4P CPT FENCE LETL CPT FENCE LETP
Table 6 - Fence Report Variables

Name Title Drawn Drawn Date Checked Checked Date Figure Number Revision Sheet Override Sitemap Scale Default Value Inferred Subsurface Section Notes Enter fence report title Persons initials/name Enter date Persons initials/name Enter date Enter text. If left blank, it will default to Figure 1. Enter Revision Enter Sheet Enter a value to override the default sitemap scale C = Soil classification method colour (default) L = Legend/material graphic L C = Legend/ Soil classification method colour S = Stick/line Enter default fence report title. Shown if Title is empty. Enter a parameter to display on the right side of the fence post, furthest from the centre of the PointID Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text
Stick CPT
Default Title Column R3 Width R3 (mm)
163
Column R2 Width R2 (mm)
Enter a parameter to display on the right side of the fence post Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text Enter a parameter to display on the right side of the fence post, closest to the centre of the PointID Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text Enter a parameter to display on the left side of the fence post, closest to the centre of the PointID Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text Enter a parameter to display on the left side of the fence post Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text Enter a parameter to display on the left side of the fence post, furthest from the centre of the PointID Enter the column width of the parameter. If left blank, it will use the default column width defined for that parameter. Typical values are 10 mm for line and bar plots, 4 mm for text Enter a parameter to display a legend for the line, colour, data marker and reference text for each correlation of that parameter Enter a parameter to display a legend for the line, colour, data marker and reference text for each correlation of that parameter Enter a parameter to display a legend for the line, colour, data marker and reference text for each correlation of that parameter Enter a parameter to display a legend for the line, colour, data marker and reference text for each correlation of that parameter
Column R1 Width R1 (mm)
Column L1 Width L1 (mm)
Legend 1
Legend 2
Legend 3
Legend 4
28.2.1
Adding the CPT Tool fence stick to a non-CPT Tool fence report
This may be achieved by referencing the Fence Block Int!dg cpt stick. You may like to apply the following code to the Block Properties Output Condition to ensure the CPT Tool columns dont print for non-CPT PointIDs: <<CBool(<<Count(<<CPT_DATA.Depth>>)>>)>>
28.3
Name
Graph Reports
Description Ball Bearing Pressure (qb) vs. depth.
Table 7 - Graph Reports
BPT QB VS DEPTH A4P
164
BPT QB VS DEPTH LETP CPT COEFF LATERAL EARTH PRESS DEPTH A4P CPT COEFF LATERAL EARTH PRESS DEPTH LETP CPT COEFF LATERAL EARTH PRESSURE RL A4P CPT COEFF LATERAL EARTH PRESSURE RL LETP CPT COEFFICIENT VOLUME CHANGE DEPTH A4P CPT COEFFICIENT VOLUME CHANGE DEPTH LETP CPT COEFFICIENT VOLUME CHANGE RL A4P CPT COEFFICIENT VOLUME CHANGE RL LETP CPT COMPRESSION INDEX DEPTH A4P CPT COMPRESSION INDEX DEPTH LETP CPT COMPRESSION INDEX RL A4P CPT COMPRESSION INDEX RL LETP CPT CONSTRAINED MODULUS DEPTH A4P CPT CONSTRAINED MODULUS DEPTH LETP CPT CONSTRAINED MODULUS RL A4P CPT CONSTRAINED MODULUS RL LETP CPT DISS. NORMALISED EX U VS. LIN T A4L CPT DISS. NORMALISED EX U VS. LIN T A4P CPT DISS. NORMALISED EX U VS. LIN T LETL CPT DISS. NORMALISED EX U VS. LIN T LETP CPT DISS. NORMALISED EX U VS. LOG T A4L CPT DISS. NORMALISED EX U VS. LOG T A4P CPT DISS. NORMALISED EX U VS. LOG T LETL CPT DISS. NORMALISED EX U VS. LOG T LETP CPT DISS. NORMALISED EX U VS. SQR T A4L
Ball Bearing Pressure (qb) vs. depth. Coefficient Lateral Earth Pressure (K0) correlations versus Depth. Coefficient Lateral Earth Pressure (K0) correlations versus Depth. Coefficient Lateral Earth Pressure (K0) correlations versus Elevation. Coefficient Lateral Earth Pressure (K0) correlations versus Elevation. Coefficient Volume Change (mv) correlations versus Depth. Coefficient Volume Change (mv) correlations versus Depth. Coefficient Volume Change (mv) correlations versus Elevation. Coefficient Volume Change (mv) correlations versus Elevation. Compression Index (Cc) correlations versus Depth. Compression Index (Cc) correlations versus Depth. Compression Index (Cc) correlations versus Elevation. Compression Index (Cc) correlations versus Elevation. Constrained Modulus (M) correlations versus Depth. Constrained Modulus (M) correlations versus Depth. Constrained Modulus (M) correlations versus Elevation. Constrained Modulus (M) correlations versus Elevation. Dissipation test graph of normalised excess pore pressure versus linear time, grouped by PointID. Dissipation test graph of normalised excess pore pressure versus linear time. Dissipation test graph of normalised excess pore pressure versus linear time, grouped by PointID. Dissipation test graph of normalised excess pore pressure versus linear time. Dissipation test graph of normalised excess pore pressure versus log time, grouped by PointID. Dissipation test graph of normalised excess pore pressure versus log time. Dissipation test graph of normalised excess pore pressure versus log time, grouped by PointID. Dissipation test graph of normalised excess pore pressure versus log time. Dissipation test graph of normalised excess pore pressure versus square root time, grouped by PointID.
165
CPT DISS. NORMALISED EX U VS. SQR T A4P CPT DISS. NORMALISED EX U VS. SQR T LETL CPT DISS. NORMALISED EX U VS. SQR T LETP CPT DISS. PORE PRESSURE VS. LIN T A4L CPT DISS. PORE PRESSURE VS. LIN T A4P CPT DISS. PORE PRESSURE VS. LIN T LETL CPT DISS. PORE PRESSURE VS. LIN T LETP CPT DISS. PORE PRESSURE VS. LOG T A4L CPT DISS. PORE PRESSURE VS. LOG T A4P CPT DISS. PORE PRESSURE VS. LOG T LETL CPT DISS. PORE PRESSURE VS. LOG T LETP CPT DISS. PORE PRESSURE VS. SQR T A4L CPT DISS. PORE PRESSURE VS. SQR T A4P CPT DISS. PORE PRESSURE VS. SQR T LETL CPT DISS. PORE PRESSURE VS. SQR T LETP CPT EFFECTIVE COHESION DEPTH A4P CPT EFFECTIVE COHESION DEPTH LETP CPT EFFECTIVE COHESION RL A4P CPT EFFECTIVE COHESION RL LETP CPT ESLAMI FELLENIUS 97 QE VS. FS A4P CPT ESLAMI FELLENIUS 97 QE VS. FS LETP CPT ESLAMI FELLENIUS 97 QE VS. FS M A4P CPT ESLAMI FELLENIUS 97 QE VS. FS M LETP CPT FINES CONTENT DEPTH A4P CPT FINES CONTENT DEPTH LETP CPT FINES CONTENT RL A4P
Dissipation test graph of normalised excess pore pressure versus square root time. Dissipation test graph of normalised excess pore pressure versus square root time, grouped by PointID. Dissipation test graph of normalised excess pore pressure versus square root time. Dissipation test graph of normalised excess pore pressure versus linear time, grouped by PointID. Dissipation test graph of pore pressure versus linear time. Dissipation test graph of normalised excess pore pressure versus linear time, grouped by PointID. Dissipation test graph of pore pressure versus linear time. Dissipation test graph of normalised excess pore pressure versus log time, grouped by PointID. Dissipation test graph of pore pressure versus log time. Dissipation test graph of normalised excess pore pressure versus log time, grouped by PointID. Dissipation test graph of pore pressure versus log time. Dissipation test graph of normalised excess pore pressure versus square root time, grouped by PointID. Dissipation test graph of pore pressure versus square root time. Dissipation test graph of normalised excess pore pressure versus square root time, grouped by PointID. Dissipation test graph of pore pressure versus square root time. Effective Cohesion (c') correlations versus Depth. Effective Cohesion (c') correlations versus Depth. Effective Cohesion (c') correlations versus Elevation. Effective Cohesion (c') correlations versus Elevation. Soil behaviour type classification graph - Eslami Fellenius (1997), Effective Cone Resistance (qe) versus Sleeve Friction (fs). Soil behaviour type classification graph - Eslami Fellenius (1997), Effective Cone Resistance (qe) versus Sleeve Friction (fs). Soil behaviour type classification graph - Multiple PointIDs per page - Eslami Fellenius (1997), Effective Cone Resistance (qe) versus Sleeve Friction (fs). Soil behaviour type classification graph - Multiple PointIDs per page - Eslami Fellenius (1997), Effective Cone Resistance (qe) versus Sleeve Friction (fs). Fines Content versus Depth. Fines Content versus Depth. Fines Content versus Elevation.
166
CPT FINES CONTENT RL LETP CPT FRICTION ANGLE DEPTH A4P CPT FRICTION ANGLE DEPTH LETP CPT FRICTION ANGLE RL A4P CPT FRICTION ANGLE RL LETP CPT HYDRAULIC CONDUCTIVITY DEPTH A4P CPT HYDRAULIC CONDUCTIVITY DEPTH LETP CPT HYDRAULIC CONDUCTIVITY RL A4P CPT HYDRAULIC CONDUCTIVITY RL LETP CPT IC 1 DEPTH A4P CPT IC 1 DEPTH LETP CPT IC 1 RL A4P CPT IC 1 RL COLOUR A4P CPT IC 1 RL COLOUR LETP CPT IC 1 RL LETP CPT IC 2 DEPTH A4P CPT IC 2 DEPTH LETP CPT IC 2 RL A4P CPT IC 2 RL COLOUR A4P CPT IC 2 RL COLOUR LETP CPT IC 2 RL LETP CPT IC 3 DEPTH A4P CPT IC 3 DEPTH LETP CPT IC 3 RL A4P CPT IC 3 RL COLOUR A4P CPT IC 3 RL COLOUR LETP CPT IC 3 RL LETP CPT IC 4 DEPTH A4P CPT IC 4 DEPTH LETP CPT IC 4 RL A4P CPT IC 4 RL COLOUR A4P
Fines Content versus Elevation. Friction Angle (Phi') correlations versus Depth. Friction Angle (Phi') correlations versus Depth. Friction Angle (Phi') correlations versus Elevation. Friction Angle (Phi') correlations versus Elevation. Hydraulic Conductivity (K) correlations versus Depth. Hydraulic Conductivity (K) correlations versus Depth. Hydraulic Conductivity (K) correlations versus Elevation. Hydraulic Conductivity (K) correlations versus Elevation. Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation with differing colours for each PointID. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation with differing colours for each PointID. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 2 versus Depth. Jefferies and Davies (1993). Soil Behaviour Type Index (Ic) 2 versus Depth. Jefferies and Davies (1993). Soil Behaviour Type Index (Ic) 2 versus Elevation. Jefferies and Davies (1993). Soil Behaviour Type Index (Ic) 2 versus Elevation with differing colours for each PointID. Jefferies and Davies (1993). Soil Behaviour Type Index (Ic) 2 versus Elevation with differing colours for each PointID. Jefferies and Davies (1993). Soil Behaviour Type Index (Ic) 2 versus Elevation. Jefferies and Davies (1993). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Depth. Robertson (2000). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Depth. Robertson (2000). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Elevation. Robertson (2000). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Elevation with differing colours for each PointID. Robertson (2000). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Elevation with differing colours for each PointID. Robertson (2000). Non-normalised Soil Behaviour Type Index (ISBT) 3 versus Elevation. Robertson (2000). Soil Behaviour Type Index (Ic) 4 versus Depth. Been and Jefferies (1992). Soil Behaviour Type Index (Ic) 4 versus Depth. Been and Jefferies (1992). Soil Behaviour Type Index (Ic) 4 versus Elevation. Been and Jefferies (1992). Soil Behaviour Type Index (Ic) 4 versus Elevation with differing colours for each PointID. R&W NCEER.
167
CPT IC 4 RL COLOUR LETP CPT IC 4 RL LETP CPT LIQ CRR DEPTH A4P CPT LIQ CRR DEPTH LETP CPT LIQ CRR RL A4P CPT LIQ CRR RL LETP CPT LIQ CSR DEPTH A4P CPT LIQ CSR DEPTH LETP CPT LIQ CSR RL A4P CPT LIQ CSR RL LETP CPT LIQ FOS DEPTH A4P CPT LIQ FOS DEPTH LETP CPT LIQ FOS RL A4P CPT LIQ FOS RL LETP CPT LIQ IC 1 NCEER DEPTH A4P CPT LIQ IC 1 NCEER DEPTH LETP CPT LIQ IC 1 NCEER RL A4P CPT LIQ IC 1 NCEER RL LETP CPT LIQ IC 4 QT(1-BQ)+1 A4P
Soil Behaviour Type Index (Ic) 4 versus Elevation with differing colours for each PointID. Been and Jefferies (1992). Soil Behaviour Type Index (Ic) 4 versus Elevation. Been and Jefferies (1992). Cyclic Resistance Ratio (CRR) at standard M7.5 earthquake correlations versus Depth. Cyclic Resistance Ratio (CRR) at standard M7.5 earthquake correlations versus Depth. Cyclic Resistance Ratio (CRR) at standard M7.5 earthquake correlations versus Elevation. Cyclic Resistance Ratio (CRR) at standard M7.5 earthquake correlations versus Elevation. Cyclic Stress Ratio (CSR) versus Depth. Cyclic Stress Ratio (CSR) versus Depth. Cyclic Stress Ratio (CSR) versus Elevation. Cyclic Stress Ratio (CSR) versus Elevation. Liquefaction Factor of Safety at standard M7.5 earthquake correlations versus Depth. Liquefaction Factor of Safety at standard M7.5 earthquake correlations versus Depth. Liquefaction Factor of Safety at standard M7.5 earthquake correlations versus Elevation. Liquefaction Factor of Safety at standard M7.5 earthquake correlations versus Elevation. Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation. Robertson and Wride (1998). Soil Behaviour Type Index (Ic) 1 versus Elevation. Robertson and Wride (1998). Soil behaviour type index classification graph - Been and Jefferies (1992), Dimensionless Penetration Resistance (Qt(1-BQ)+1) versus Normalised Friction Ratio (Fr). Soil behaviour type index classification graph - Been and Jefferies (1992), Dimensionless Penetration Resistance (Qt(1-BQ)+1) versus Normalised Friction Ratio (Fr). Lateral Displacement Index (LDI) correlations versus Depth. Lateral Displacement Index (LDI) correlations versus Depth. Lateral Displacement Index (LDI) correlations versus Elevation. Lateral Displacement Index (LDI) correlations versus Elevation. Maximum Shear Strain (gamma max) versus Depth. Maximum Shear Strain (gamma max) versus Depth. Maximum Shear Strain (gamma max) versus Elevation. Maximum Shear Strain (gamma max) versus Elevation.
CPT LIQ IC 4 QT(1-BQ)+1 LETP
CPT LIQ LATERAL DISP INDEX DEPTH A4P CPT LIQ LATERAL DISP INDEX DEPTH LETP CPT LIQ LATERAL DISP INDEX RL A4P CPT LIQ LATERAL DISP INDEX RL LETP CPT LIQ MAXIMUM SHEAR STRAIN DEPTH A4P CPT LIQ MAXIMUM SHEAR STRAIN DEPTH LETP CPT LIQ MAXIMUM SHEAR STRAIN RL A4P CPT LIQ MAXIMUM SHEAR STRAIN RL LETP
168
CPT LIQ POST VOL STRAIN DEPTH A4P CPT LIQ POST VOL STRAIN DEPTH LETP CPT LIQ POST VOL STRAIN RL A4P CPT LIQ POST VOL STRAIN RL LETP CPT LIQ POST VOL STRAIN ZHANG CPT LIQ QC1N CS DEPTH A4P CPT LIQ QC1N CS DEPTH LETP CPT LIQ QC1N CS RL A4P CPT LIQ QC1N CS RL LETP CPT LIQ RECONS SETTLEMENT DEPTH A4P CPT LIQ RECONS SETTLEMENT DEPTH LETP CPT LIQ RECONS SETTLEMENT RL A4P CPT LIQ RECONS SETTLEMENT RL LETP CPT LIQ SR DEPTH A4P CPT LIQ SR DEPTH LETP CPT LIQ SR RL A4P CPT LIQ SR RL LETP CPT OCR DEPTH A4P CPT OCR DEPTH LETP CPT OCR RL A4P CPT OCR RL LETP CPT PILE ULT AXIAL CAPACITY DEPTH A4P CPT PILE ULT AXIAL CAPACITY DEPTH LETP CPT PILE ULT AXIAL CAPACITY RL A4P CPT PILE ULT AXIAL CAPACITY RL LETP CPT PRECONSOLIDATION STRESS DEPTH A4P CPT PRECONSOLIDATION STRESS DEPTH LETP CPT PRECONSOLIDATION STRESS RL A4P CPT PRECONSOLIDATION STRESS RL LETP CPT PROJECT SBT LINEARLINEAR A4P CPT PROJECT SBT LINEAR-
Post Liquefaction Volumetric Strain (epsilon v) correlations versus Depth. Post Liquefaction Volumetric Strain (epsilon v) correlations versus Depth. Post Liquefaction Volumetric Strain (epsilon v) correlations versus Elevation. Post Liquefaction Volumetric Strain (epsilon v) correlations versus Elevation. Post liquefaction volumetric strain versus clean-sand equivalent normalised cone resistance 1, Zhang et al. (2002). qc1N cs versus Depth. qc1N cs versus Depth. qc1N cs versus Elevation. qc1N cs versus Elevation. Post Liquefaction Reconsolidation Settlement (S) correlations versus Depth. Post Liquefaction Reconsolidation Settlement (S) correlations versus Depth. Post Liquefaction Reconsolidation Settlement (S) correlations versus Elevation. Post Liquefaction Reconsolidation Settlement (S) correlations versus Elevation. Residual Shear Strength (sr) correlations versus Depth. Residual Shear Strength (sr) correlations versus Depth. Residual Shear Strength (sr) correlations versus Elevation. Residual Shear Strength (sr) correlations versus Elevation. Overconsolidation Ratio (OCR) correlations versus Depth. Overconsolidation Ratio (OCR) correlations versus Depth. Overconsolidation Ratio (OCR) correlations versus Elevation. Overconsolidation Ratio (OCR) correlations versus Elevation. Pile ultimate axial capacity versus Depth - Bustamante and Gianselli / LCPC (1982). Pile ultimate axial capacity versus Depth - Bustamante and Gianselli / LCPC (1982). Pile ultimate axial capacity versus Elevation - Bustamante and Gianselli / LCPC (1982). Pile ultimate axial capacity versus Depth - Bustamante and Gianselli / LCPC (1982). Preconsolidation Stress (Sig p') correlations versus Depth. Preconsolidation Stress (Sig p') correlations versus Depth. Preconsolidation Stress (Sig p') correlations versus Elevation. Preconsolidation Stress (Sig p') correlations versus Elevation. Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition.
169
LINEAR LETP CPT PROJECT SBT LINEAR-LOG A4P CPT PROJECT SBT LINEAR-LOG LETP CPT PROJECT SBT LOG-LINEAR A4P CPT PROJECT SBT LOG-LINEAR LETP CPT PROJECT SBT LOG-LOG A4P CPT PROJECT SBT LOG-LOG LETP CPT QC QT VS DEPTH A4P CPT QC QT VS DEPTH COLOUR A4P CPT QC QT VS DEPTH COLOUR LETP CPT QC QT VS DEPTH FT PSI A4P CPT QC QT VS DEPTH FT PSI LETP CPT QC QT VS DEPTH LETP CPT QC QT VS ELEVATION A4P CPT QC QT VS ELEVATION COLOUR A4P CPT QC QT VS ELEVATION COLOUR LETP CPT QC QT VS ELEVATION LETP CPT RAMSEY 2002 QT VS. BQ A4P CPT RAMSEY 2002 QT VS. BQ LETP CPT RAMSEY 2002 QT VS. BQ M A4P CPT RAMSEY 2002 QT VS. BQ M LETP CPT RAMSEY 2002 QT VS. FR A4P CPT RAMSEY 2002 QT VS. FR LETP CPT RAMSEY 2002 QT VS. FR M A4P Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition. Soil behaviour type classification graph - project definition. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth with differing colours for each PointID. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth with differing colours for each PointID. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Two scales on each axis, m and ft, and MPa and psi. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Two scales on each axis, m and ft, and MPa and psi. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Depth. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Elevation. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Elevation with differing colours for each PointID. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Elevation with differing colours for each PointID. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Cone Resistance (qc) or Corrected Total Cone Resistance (qt) versus Elevation. If qt is found, the graph will plot qt. Otherwise, qc is plotted. Soil behaviour type classification graph - Ramsey (2002), Normalised Cone Resistance (Qt) versus Pore Pressure Ratio (Bq). Soil behaviour type classification graph - Ramsey (2002), Normalised Cone Resistance (Qt) versus Pore Pressure Ratio (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Ramsey (2002), Normalised Cone Resistance (Qt) versus Pore Pressure Ratio (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Ramsey (2002), Normalised Cone Resistance (Qt) versus Pore Pressure Ratio (Bq). Soil behaviour type classification graph - Ramsey (2002), Normalised Cone Resistance (Qt) versus Normalised Friction Ratio (Fr). Soil behaviour type classification graph - Ramsey (2002), Normalised Cone Resistance (Qt) versus Normalised Friction Ratio (Fr). Soil behaviour type classification graph - Multiple PointIDs per page - Ramsey (2002), Normalised Cone Resistance (Qt) versus Normalised Friction Ratio (Fr).
170
CPT RAMSEY 2002 QT VS. FR M LETP CPT RELATIVE DENSITY DEPTH A4P CPT RELATIVE DENSITY DEPTH LETP CPT RELATIVE DENSITY RL A4P CPT RELATIVE DENSITY RL LETP CPT RF VS DEPTH A4P CPT RF VS DEPTH LETP CPT RF VS ELEVATION A4P CPT RF VS ELEVATION COLOUR A4P CPT RF VS ELEVATION COLOUR LETP CPT RF VS ELEVATION LETP CPT RIGIDITY INDEX DEPTH A4P CPT RIGIDITY INDEX DEPTH LETP CPT RIGIDITY INDEX RL A4P CPT RIGIDITY INDEX RL LETP CPT ROBERTSON 90 QT VS. BQ A4P CPT ROBERTSON 90 QT VS. BQ EXTRAP A4P CPT ROBERTSON 90 QT VS. BQ EXTRAP LETP CPT ROBERTSON 90 QT VS. BQ EXTRAP M A4P CPT ROBERTSON 90 QT VS. BQ EXTRAP M LETP CPT ROBERTSON 90 QT VS. BQ LETP CPT ROBERTSON 90 QT VS. BQ M A4P CPT ROBERTSON 90 QT VS. BQ M LETP CPT ROBERTSON 90 QT VS. FR A4P CPT ROBERTSON 90 QT VS. FR EXTRAP A4P CPT ROBERTSON 90 QT VS. FR EXTRAP LETP CPT ROBERTSON 90 QT VS. FR EXTRAP M A4P CPT ROBERTSON 90 QT VS. FR EXTRAP M LETP CPT Tool gINT Add-In 3 User Guide
Soil behaviour type classification graph - Multiple PointIDs per page - Ramsey (2002), Normalised Cone Resistance (Qt) versus Normalised Friction Ratio (Fr). Relative Density (Dr) correlations versus Depth. Relative Density (Dr) correlations versus Depth. Relative Density (Dr) correlations versus Elevation. Relative Density (Dr) correlations versus Elevation. Friction ratio (Rf) vs depth. Friction ratio (Rf) vs depth. Friction Ratio (Rf) versus Elevation. Friction ratio (Rf) vs elevation with differing colours for each PointID. Friction ratio (Rf) vs elevation with differing colours for each PointID. Friction Ratio (Rf) versus Elevation. Rigidity Index (Ir) correlations versus Depth. Rigidity Index (Ir) correlations versus Depth. Rigidity Index (Ir) correlations versus Elevation. Rigidity Index (Ir) correlations versus Elevation. Soil behaviour type classification graph - Robertson 1990, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson 1990, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson 1990, normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990 (extrapolated graph), normalised cone resistance (Qt) versus normalised Datgel DCT-UG-001 - 3.02 - August 2012
171
friction ration (Fr). CPT ROBERTSON 90 QT VS. FR LETP CPT ROBERTSON 90 QT VS. FR M A4P CPT ROBERTSON 90 QT VS. FR M LETP CPT ROBERTSON ET AL. 86 QC VS. RF A4P CPT ROBERTSON ET AL. 86 QC VS. RF LETP CPT ROBERTSON ET AL. 86 QC VS. RF M A4P CPT ROBERTSON ET AL. 86 QC VS. RF M LETP CPT ROBERTSON ET AL. 86 QT VS. BQ A4P CPT ROBERTSON ET AL. 86 QT VS. BQ LETP CPT ROBERTSON ET AL. 86 QT VS. BQ M A4P CPT ROBERTSON ET AL. 86 QT VS. BQ M LETP CPT ROBERTSON ET AL. 86 QT VS. RF A4P CPT ROBERTSON ET AL. 86 QT VS. RF LETP CPT ROBERTSON ET AL. 86 QT VS. RF M A4P CPT ROBERTSON ET AL. 86 QT VS. RF M LETP CPT SCHMERTMANN 1978 A4P CPT SCHMERTMANN 1978 LETP CPT SCHMERTMANN 1978 M A4P CPT SCHMERTMANN 1978 M LETP CPT SCHNEIDER ET AL. 08 LOGLOG A4P Soil behaviour type classification graph - Robertson 1990, normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990, normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson 1990, normalised cone resistance (Qt) versus normalised friction ration (Fr). Soil behaviour type classification graph - Robertson et. al. 1986, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Robertson et. al. 1986, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Robertson et. al. 1986, total corrected cone resistance (qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson et. al. 1986, total corrected cone resistance (qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, total corrected cone resistance (qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, total corrected cone resistance (qt) versus pore pressure parameter (Bq). Soil behaviour type classification graph - Robertson et. al. 1986, total corrected cone resistance (qt) versus friction ratio (Rf). Soil behaviour type classification graph - Robertson et. al. 1986, total corrected cone resistance (qt) versus friction ratio (Rf). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, total corrected cone resistance (qt) versus friction ratio (Rf). Soil behaviour type classification graph - Multiple PointIDs per page - Robertson et. al. 1986, total corrected cone resistance (qt) versus friction ratio (Rf). Soil behaviour type classification graph - Schmertmann 1978, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Schmertmann 1978, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Schmertmann 1978, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Schmertmann 1978, cone resistance (qc) versus friction ratio (Rf). Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Log-Log plot for use with clays, clayey silts, silts, sandy silts and sands with no negative penetration pore pressures. Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Log-Log plot for use with clays, clayey silts, silts, sandy silts and sands with no negative penetration pore pressures. Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Log-Log plot for use with clays, clayey silts, silts, sandy silts and sands with no negative penetration pore pressures.
CPT SCHNEIDER ET AL. 08 LOGLOG LETP
CPT SCHNEIDER ET AL. 08 LOGLOG M A4P
172
CPT SCHNEIDER ET AL. 08 LOGLOG M LETP
Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Log-Log plot for use with clays, clayey silts, silts, sandy silts and sands with no negative penetration pore pressures. Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Semilog plot for use with clay soils with large negative excess penetration pore pressures. Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Semilog plot for use with clay soils with large negative excess penetration pore pressures. Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Semilog plot for use with clay soils with large negative excess penetration pore pressures. Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus pore pressure parameter (Bq). Semilog plot for use with clay soils with large negative excess penetration pore pressures. Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Semilog plot for use with sands and transitional soils with small negative excess penetration pore pressures. Soil behaviour type classification graph - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Semilog plot for use with sands and transitional soils with small negative excess penetration pore pressures. Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Semilog plot for use with sands and transitional soils with small negative excess penetration pore pressures. Soil behaviour type classification graph - Multiple PointIDs per page - Schneider et al 2008, normalised cone resistance (Qt) versus normalised pore pressure parameter (Delta u2 / Sigma'v0). Semilog plot for use with sands and transitional soils with small negative excess penetration pore pressures. Sensitivity (St) correlations versus Depth. Sensitivity (St) correlations versus Depth. Sensitivity (St) correlations versus Elevation. Sensitivity (St) correlations versus Elevation. Shear Wave Velocity (Vs) correlations and measured versus Depth. Shear Wave Velocity (Vs) correlations and measured versus Depth. Shear Wave Velocity (Vs) correlations versus Elevation. Shear Wave Velocity (Vs) correlations versus Elevation. Small Strain Shear Modulus (G0 or Gmax) correlations versus Depth. Small Strain Shear Modulus (G0 or Gmax) correlations versus Depth. Small Strain Shear Modulus (Go or Gmax) correlations versus Elevation. Small Strain Shear Modulus (Go or Gmax) correlations versus Elevation.
CPT SCHNEIDER ET AL. 08 QT VS. BQ A4P CPT SCHNEIDER ET AL. 08 QT VS. BQ LETP CPT SCHNEIDER ET AL. 08 QT VS. BQ M A4P
CPT SCHNEIDER ET AL. 08 QT VS. BQ M LETP
CPT SCHNEIDER ET AL. 08 SEMI-LOG A4P
CPT SCHNEIDER ET AL. 08 SEMI-LOG LETP
CPT SCHNEIDER ET AL. 08 SEMI-LOG M A4P
CPT SCHNEIDER ET AL. 08 SEMI-LOG M LETP
CPT SENSITIVITY DEPTH A4P CPT SENSITIVITY DEPTH LETP CPT SENSITIVITY RL A4P CPT SENSITIVITY RL LETP CPT SHEAR WAVE VELOCITY DEPTH A4P CPT SHEAR WAVE VELOCITY DEPTH LETP CPT SHEAR WAVE VELOCITY RL A4P CPT SHEAR WAVE VELOCITY RL LETP CPT SMALL STRAIN SHEAR MOD DEPTH A4P CPT SMALL STRAIN SHEAR MOD DEPTH LETP CPT SMALL STRAIN SHEAR MODULUS RL A4P CPT SMALL STRAIN SHEAR MODULUS RL LETP
173
CPT SPT N60 DEPTH A4P CPT SPT N60 DEPTH LETP CPT SPT N60 RL A4P CPT SPT N60 RL LETP CPT STATE PARAMETER DEPTH A4P CPT STATE PARAMETER DEPTH LETP CPT STATE PARAMETER RL A4P CPT STATE PARAMETER RL LETP CPT SU DEPTH A4P CPT SU DEPTH LETP CPT SU LB BE UB DEPTH A4P CPT SU LB BE UB DEPTH LETP CPT SU LB BE UB RL A4P CPT SU LB BE UB RL LETP CPT SU RL A4P CPT SU RL LETP CPT SU VS DEPTH VANE TV PP A4P CPT SU VS DEPTH VANE TV PP LETP CPT UNIT WEIGHT DEPTH A4P CPT UNIT WEIGHT DEPTH LETP CPT UNIT WEIGHT RL A4P CPT UNIT WEIGHT RL LETP CPT YOUNGS MODULUS DEPTH A4P CPT YOUNGS MODULUS DEPTH LETP CPT YOUNGS MODULUS RL A4P CPT YOUNGS MODULUS RL LETP
SPT N60 correlations versus Depth. SPT N60 correlations versus Depth. SPT N60 correlations versus Elevation. SPT N60 correlations versus Elevation. State Parameter correlations versus Depth. State Parameter correlations versus Depth. State Parameter correlations versus Elevation. State Parameter correlations versus Elevation. Undrained Shear Strength (Su) correlations versus Depth. Undrained Shear Strength (Su) correlations versus Depth. Undrained Shear Strength (Su) correlations versus Depth. Undrained Shear Strength (Su) correlations versus Depth. Undrained Shear Strength (Su) correlations versus Elevation. Undrained Shear Strength (Su) correlations versus Elevation. Undrained Shear Strength (Su) correlations versus Elevation. Undrained Shear Strength (Su) correlations versus Elevation. Undrained shear strength vs depth. Plots Su from CPT, in situ vane, in situ torvane, in situ pocket penetrometer. Each test type to have different data marker and CPT to have a line (no data marker). Undrained shear strength vs depth. Plots Su from CPT, in situ vane, in situ torvane, in situ pocket penetrometer. Each test type to have different data marker and CPT to have a line (no data marker). Unit Weight correlations versus Depth. Unit Weight correlations versus Depth. Unit Weight correlations versus Elevation. Unit Weight correlations versus Elevation. Young's Modulus (E) correlations versus Depth. Young's Modulus (E) correlations versus Depth. Young's Modulus (E) correlations versus Elevation. Young's Modulus (E) correlations versus Elevation.
174
29 References
Al-Homoud, A.S. and Wehr, W. (2006). Experience of Vibrocompaction in Calcareous Sand of UAE. Geotechnical and Geological Engineering, Volume 24, Number 3 / June, 2006, pp. 757-774. Baldi, G., Bellotti, R., Ghionna, V., Jamiolkowski, M. and Pasqualini, E. (1986). Interpretation of CPTs and CPTUs; 2nd part: drained penetration of sands. Proceedings of the Fourth International Geotechnical Seminar, Singapore, pp. 143-56. Baldi, G., Bellotti, R., Ghionna, V., Jamiolkowski, M. and LoPresti, D.C.F. (1989). Modulis of Sands from CPTs and DMTs. Proceedings, 12th International Conference on Soil Mechanics and Foundation Engineering, Vol. 1, Rio de Janeiro, Brazil, 1989, Balkema, Rotterdam, The Netherlands, pp. 165-170. Been, K., Lingnau, B.E., Crooks, J.H.A. and Leach, B. (1987). Cone Penetration Test Calibration For Erksak (Beaufort Sea) Sand, Canadian Geotechnical Journal, 24, 4, 601-610. Been, K. and Jefferies, M.G. (1992); Towards Systematic CPT Interpretation. Proceedings Wroth Memorial Symposium, Thomas Telford, London, pp. 121134 Burland, J.B. (1989). Small is Beautiful: The Stiffness of Soils at Small Strains, Canadian Geotechnical Journal, Vol. 26, No. 4, 1989, pp. 499-516. Burns, S.E. and Mayne, P.W. (2002). Interpretation of Seismic Piezocone Results for the Evaluation of Hydraulic Conductivity in Clays, Geotechnical Testing Journal, Vol. 25, No. 3, 2002, pp. 333-340. Bustamante, M. and Gianeselli, L. (1982). Pile Bearing Capacity Prediction by Means of Static Penetrometer CPT, Proceedings of the 2nd European Symposium on Penetration Testing, ESOPT-II, Amesterdam, 2, 493-500, Balkema Pub., Rotterdam. Chen, B.S..-Y. and Mayne, P.W. (1996). Statistical Relationships Between Piezocone Measurements and Stress History of Clays, Canadian Geotechnical Journal, Vol. 33, No. 3, 1996, pp. 488-498. Demers, D. and Leroueil, S. (2002). Evaluation of Preconsolidation Pressure and the Overconsolidation Ratio from Piezocone Tests of Clay Deposits in Quebec, Canadian Geotechnical Journal, Vol. 39, No. 1, 2002, pp. 174-192. Fugro 1995. Descriptions of Methods and Practices, Cone Penetration Test, FEBV/CDE/APP/001 Issue 16. Eslami, A. and Fellenius, B. H. (1997). Pile Capacity by Direct CPT and CPTu methods applied to 102 case histories. Canadian Geotechnical Journal, Vol. 34, No. 6, pp. 880-898. Hegazy, Y.A. and Mayne, P.W. (1995). Statistical Correlations Between Vs and CPT Data for Different Soil Types, Proceedings, Symposium on Cone Penetration Testing, Vol. 2, Swedish Geotechnical Society, Linkping, Sweden, 1995, pp. 173-178. Houlsby, G.T. and Teh, C.I. (1988). Analysis of piezocone in clay. Proceedings of the International Symposium on Penetration Testing, ISOPT-1, Orlando, 2, 777-83, Balkema Pub., Rotterdam. Idriss, I.M. and Boulanger, R.W. (2008). Soil liquefaction during earthquakes, Earthquake Engineering Research Institute, MNO-12 International Society for Soil Mechanics and Geotechnical Engineering (ISSMGE) (2001). International Reference Test Procedure for the Cone Penetration Test (CPT) and the Cone Penetration Test with
175
pore pressure (CPTU), Report of the ISSMGE Technical Committee 16 on Ground Property Characterisation from In-situ Testing, 1999 (corrected 2001). Jamiolkowski, M., LoPresti, D.C.F. and Manassero, M. (2001). Evaluation of Relative Density and Shear Strength of Sands from Cone Penetration Test and Flat Dilatometer Test, Soil Behaviour and Soft Ground Construction (GSP 119), American Society of Civil Engineers, Reston, Va., 2001, pp. 201238 Jefferies, M.G. and Been K (2006). Soil liquefaction - A critical state approach, Taylor & Francis Jefferies, M.G. and Davies, M.P. (1993). Use of CPTu to Estimate Equivalent SPT N60, Geotechnical Testing Journal, Vol. 16, No. 4, Dec. 1993, pp. 458-468. Keaveny, J.M. and Mitchell, J.K. (1986). Strength of Fine-Graining Soils Using the Piezocone, Use of In Situ Tests in Geotechnical Engineering (GSP 6), American Society of Civil Engineers, Reston, Va. 1986, pp. 668-699. Kulhawy, F.H. and Mayne, P.H. (1990). Manual on estimating soil properties for foundation design. Electric Power Research Institute, EPRI, August, 1990. Lunne, T. Robertson, P. K., Powell, J.J.M (1997). Cone Penetration Testing in Geotechnical Practice, Spoon Press. Mayne, P.W. (2001). Stress-Strain-Strength-Flow Parameters from Enhanced In-Situ Tests, Proceedings, International Conference on In-Situ Measurement of Soil Properties and Case Histories, Bali, Indonesia, 2001, pp. 27-48 Mayne, P.W. (2005). Integrated Ground Behaviour: In-Situ and Lab Tests, Deformation Characteristics of Geomaterials, Vol. 2 (Proc. Lyon, France), Taylor & Francis, London, United Kingdom, 2005, pp.155177. Mayne, P.W. (2006). The 2nd James K. Mitchell Lecture: Undisturbed Sand Strength from Seismic Cone Tests, Geomechanics and Geoengineering, Vol. 1, No. 4, 2006, pp. 239-247. Mayne, P. W. (2007). NCHRP Synthesis 368, Cone Penetration Testing, Transport Research Board, Washington D.C. Mayne, P.W. and Stewart, H.E. (1988). Pore Pressure Response of K0 Consolidated Clays, Journal of Geotechnical Engineering, Vol. 114, No. 11, 1988, pp. 1340-1346. Mayne, P.W. and Rix, G.J. (1995). Correlations Between Shear Wave Veolicaty and Cone Tip Resistance in Clays, Soils & Foundations, Vol. 35, No. 2, 1995, 107-110 Mayne, P.W. and Brown, D.A. (2003). Site Characterization and Engineering Properties of Natural Soils, Vol. 2, Swets and Zeitlinger, Lisse, The Netherlands, 2003, pp. 1323-1339. Mayne, P.W. and Campanella, R.G. (2005). Versatile Site Characterization by Seismic Piezocone, Proceedings, 16th International Conference on Soil Mechanics and Geotechnical Engineering, Vol. 2 (Osaka), Millpress, Rotterdam, The Netherlands, 2005, pp. 721-724. Mesri, G. and Abdel-Ghaffar, M. (1993). Cohesion Intercept in Effective Stress Stability Analysis, Journal of Geotechnical Engineering, Vol. 119, No. 8, 1993, 1229-1249. Rad, N.S. and Lunne, T. (1986). Correlations between piezocone results and laboratory soil properties. Norwegian Geotechnical Institute, Oslo, Report 52155-39. Ramsey, N. (2002). A Calibrated Model for The Interpretation Of Cone Penetration Tests (Cpts) In North Sea Quaternary Soils. Proceedings of OSIG Conference, November 26 - 28, 2002, London, UK
176
Rix, G.J and Stokoe, K.H. (1992). Correlation of Initial Tangent Modulus and Cone Resistance, Proceedings of the International Symposium on Calibration Chamber Testing, Potsdam, New York, 1991, pp. 351-362, Elsevier Robertson, P.K. (1990). Soil classification using the cone penetration test. Canadian Geotechnical Journal, 27(1), 151-8. Robertson, P.K. (2009). Performance based earthquake design using the CPT., Keynote lecture, ISTokyo Robertson, P.K (2010). Soil behaviour type from the CPT: an update, Gregg Drilling & Testing Inc., Signal Hill, California, USA, CPT 10, paper 2-56. Robertson, P.K. and Campanella, R.G. (1983). Interpretation of Cone Penetration Tests: Sands, Canadian Geotechnical Journal, Vol. 20, No. 4, 1983, pp. 719-733. Robertson, P.K., Campanella, R.G., Gillespie, D. and Greig, J. (1986). Use of piezometer cone data. Proceedings of the ASCE Specialty Conference In Situ 86: Use of In Situ Tests in Geotechnical Engineering, Blacksburg, 1263-80, American Society of Engineers (ASCE). Robertson, P.K and Wride, C.E. (1998). Evaluating cyclic liquefaction potential using the cone penetration test, Canadian Geotechnical Journal 35 (3), pp. 442-459. Robertson, P.K. and Cabal, K.L. (2009). Guide to Cone Penetration Testing for Geotechnical Engineering, Gregg Drilling & Testing Inc., 3rd Edition, January 2009. Schmertmann, J.H. (1978). Guidelines for cone penetration test, performance and design. US Federal Highway Administration, Washington, DC, Report, FHWA-TS-78-209, 145. Schneider, J.A., Randolph, M.F., Mayne, P.W., and Ramsey, N. (2008). Analysis of factors influencing soil classification using normalised piezocone tip resistance and pore pressure parameters. Journal of Geotechnical and Geoenvironmental Engineering, November 2008, pp 1569-1586 Sully, J. P., Robertson, P. K., Campanella, R. G., and Woeller, D. J. (1999). An approach to evaluation of field CPTU dissipation data in overconsolidated fine-grained soils. Canadian Geotechnical Journal, 36, pp 369-381. Shuttle, D.A., and Jefferies, M.G. (1998). Dimensionless and Unbiased CPT Interpretation in Sand. International Journal of Numerical and Analytical Methods in Geomechanics, 22, 351391.Terzaghi, K., Peck, R. and Mesri, G. (1996). Soil Mechanics in Engineering Practice, 3rd ed., John Wiley & Sons, New York, N.Y., 1996. Trak, B., LaRochelle, P., Tavenas, F., Leroueil, S. And Roy, M. (1980). A New Approach to the Stability Analysis of Embankments on Sensitive Clays, Canadian Geotechnical Journal, Vol. 17, No. 4, 1980, pp. 526-544. Youd, T., Idriss, I., Andrus, R., Arango, I., Castro, G., Christian, J., Dobry, R., Finn, W., Harder, L., Hynes, M., Ishihara, K., Koester, J.,Liao, S., Marcuson, W., Martin, G., Mitchell, J., Moriwaki, Y., Power, M., Robertson, P., Seed, R., and Stokoe, K. (2001). Liquefaction Resistance of Soils: Summary Report from the 1996 NCEER and 1998 NCEER/NSF Workshops on Evaluation of Liquefaction Resistance of Soils. J. Geotech. Geoenviron. Eng., 127(10), 817833. doi: 10.1061/(ASCE)1090-0241(2001)127:10(817)Wroth, C.P. (1984). The Interpretation of In-Situ Soil Tests, Geotechnique, Vol. 34, No. 4, Dec 1984, pp. 449-489. Zhang, G., Robertson, P.K. and Brachman, R.W.I. (2002). Estimating Liquefaction-Induced Ground Settlements from CPT for Level Ground. Canadian Geotechnical Journal, 39, pp 1168-1180.
177
Appendix A Tutorial: Creating a Log and Fence Report Column for a new Derived Parameter
Aim
In this tutorial, we will be creating a dynamic log column and fence column for the derived parameter Effective Cone Resistance, .
Creating the Data Field

We will start by creating the field that will store the data for this parameter on the CPT_DATA table. Go to the CPT_DATA table in INPUT | CPT > CPT Data tab, click on the bottom half of the screen and then call the command Tables > Add Field. Fill in the fields with the following values, and click OK when finished.
Field Name Name Caption Type Description Units Cell Color Value Effective_Cone_Resistance qe Double Effective Cone Resistance, qe kPa Field - Calculated
The new field will appear on the far right side of the table, but you may change the position of the field by clicking and dragging the header across, and change the field width by clicking and dragging the edge of the field header. The new field should look similar to the following:
Update your data template by calling the command Tools > Make Data Template, and overwriting your existing data template.
Creating the User System Data

Go to DATA DESIGN | User System Data and call the command File > New. Enter DG CPT Param Effective Cone Resistance in the Name, optionally enter a description and click OK.
Enter the following code in the Data or Expression then click Save.
A-1
<<Let(Param = "Effective Cone Resistance")>>
Your screen should look similar to the following:
Adding the Configuration to the Library Table

This step requires adding new records into the CPT Tool Library configuration tables, namely DG_DPT_SYMBOLOGY, DG_CPT_SYMBOLOGY_SCALES_UNITS, DG_CPT_LOG_BLOCK, DG_CPT_FENCE_BLOCK and DG_CPT_FIELD_MAP. Go to DATA DESIGN | Library Data, and select DG_DPT_SYMBOLOGY from the yellow drop down list. Enter a new record in DG_DPT_SYMBOLOGY with the following values, then click Save.
Column Name Parameter gINT Field Name SQL Field Name SQL Table Name Line Colour Line Type Comparison Line Type Line Thickness Data Marker Height Log Value Effective Cone Resistance <<CPT_DATA.Effective_Cone_Resistance>> [CPT_DATA].[Effective_Cone_Resistance] [CPT_DATA] Very Light Blue Solid Solid 0.2 0
A-2
Column Name Show on Report Name Abbreviation
Value True Effective Cone Resistance q<<SUB>>e<<SUB>>
Select DG_CPT_SYMBOLOGY_SCALES_UNITS from the yellow drop down list and enter two new records with the following values, then click Save. 1st Record:
Column Name Unit System Parameter Unit Minimum Scale Maximum Scale Number of Divisions Value SI Effective Cone Resistance MPa 0 40 4
2nd Record:
Column Name Unit System Value English
A-3
Column Name Parameter Unit Minimum Scale Maximum Scale Number of Divisions
Value Effective Cone Resistance tsf 0 4 4
Select DG_CPT_LOG_BLOCK from the yellow drop down list and enter a new record with the following values, then click Save. You may right-click and drag the row header to change the position of the record appears on the table.
Column Name Name Description Log Width Parameter Value qe Effective Cone Resistance, qe 40 Effective Cone Resistance
A-4
Select DG_CPT_FENCE_BLOCK from the yellow drop down list and enter a new record with the following values, then click Save.
Column Name Name Description Width Parameter Value qe Effective Cone Resistance, qe 10 Effective Cone Resistance
A-5
Select DG_CPT_FIELD_MAP from the yellow drop down list and enter a new record with the following values, then click Save. You may right-click and drag the row header to change the position of the record appears on the table.
Column Name Table Name Field Name Location Parameter Name SI English Value CPT_DATA Effective_Cone_Resistance Project CptDataEffectiveConeResistanceField MPa tsf
If the calulation is done by a formual hard coded in our DLL then The Parameter Name must be created by Datgels developers. If the formual is for the parmataer is in the Formula Tool, then the Parameter Name should be empty.
A-6
Creating the Dynamic Log Block

To create the Dynamic Log Block, we will make a copy of an existing derived parameter Dynamic Log Block and modify it to work with the new derived parameter. In this tutorial, we will be using the Differential Pore Pressure Ratio (DPPR) parameter log block as the basis for our new log block. Go to REPORT DESIGN | Logs then call the command Blocks > Edit Log Blocks. Select DG CPT DPPR from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT QE in the Page names to copy to and click OK.
At this stage, your screen should look similar to this:
A-7
The references to the new field and User System Data, and User Report Variables will be fixed at a later step. We now need to add a reference to the new block to the Dynamic Log reports. From the current screen (REPORT DESIGN | Logs > Log Blocks), select DG CPT DYNAMIC COLUMNS from the yellow drop down list. Call the command Blocks > Insert Block and enter the following values, then click OK. Main Tab:
Field Name Block Source Page Range Design Mode Colour Offset X Value Int!dg cpt qe All Medium Blue <<Let(Block = "qe")>>_ <<User System Data.DG CPT Dynamic Log Col Offset X>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value 10 <<Let(Block = "qe")>>_ <<User System Data.DG CPT Dynamic Log Col Output Condition>>
A-8
Left click on a vacant space to place the Block reference, then click Save. We now need to add a new User Report Variable to the Dynamic Log reports. Click on the Logs tab to return to the REPORT DESIGN | Logs screen. Select the log report CPT DYNAMIC A4P from the yellow drop down list, and call the command File > Page > Properties. Click on the User Report Variables button, and click on the Add Field button on the bottom left. Enter the following values into the fields and click OK.
Field Name Name Type Value qe Width Memo
Enter <<Let(Block = "qe")>><<User System Data.DG CPT Dynamic Log Col Width>> for the Value in the newly created User Report Variable, and click OK.
Click OK to close the Properties window and save the changes. We now need to copy the new User Report Variable to the other Dynamic Log reports. With the CPT DYNAMIC A4P report currently open, call the command File > Page > Copy Report Variables, select qe Width and click OK.
A-9
Click on the List of pages to copy to button to bring up the selection dialog. Select the Dynamic Log Reports in your library, then click OK. Note you may not have all the reports in your library as shown below.
Click OK to copy to User Report Variables to the selected Reports.
Creating the Fence Block

To create the Fence Block, we will make a copy of an existing derived parameter fence block and modify it to work with the new derived parameter. In this tutorial, we will be using the Differential Pore Pressure Ratio (DPPR) parameter fence block as the basis for our new fence block. Note that there are two blocks that need to be created, left and right. The fence blocks are suffixed by L and R to denote this. Go to REPORT DESIGN | Fences then call the command Blocks > Edit Fence Blocks. Select DG CPT DPPR L from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT QE L in the Page names to copy to and click OK. Now we will create the right block. From the current screen (REPORT DESIGN | Fences > Fence Blocks), select CPT DPPR R from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT QE R in the Page names to copy to and click OK. We now need to add a reference to the new fence block to the Fence reports. From the current screen (REPORT DESIGN | Fences > Fence Blocks), select DG CPT STICK from the yellow drop down list.
A-10
Call the command Blocks > Insert Block and enter the following values for the left fence block, then click OK. Main Tab:
Field Name Block Source Page Range Design Mode Colour Offset X Value Int!dg cpt qe l All Very Light Blue <<Let(Block = "qe")>>_ <<User System Data.DG CPT Fence Col Offset X L>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value -11.75 <<Let(Block = "qe")>>_ <<User System Data.DG CPT Fence Col Output Cond L>>
Left click on a vacant space to place the Block reference, then click Save. Repeat the above steps, and enter the following for the right fence block. Main Tab:
Field Name Block Source Page Range Design Mode Colour Offset X Value Int!dg cpt qe r All Very Light Red <<Let(Block = "qe")>>_ <<User System Data.DG CPT Fence Col Offset X R>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value 11.75 <<Let(Block = "qe")>>_ <<User System Data.DG CPT Fence Col Output Cond R>>
We now need to add a new User Report Variable to the CPT Fence reports. Click on the Fences tab to return to the REPORT DESIGN | Fences screen. Select the log report CPT FENCE A4P from the yellow drop down list, and call the command File > Page > Properties. Click on the User Report Variables button, and click on the Add Field button on the bottom left. Enter the following values into the fields for the left fence block and click OK.
Field Name Name Type Value qe Width L Memo
Enter <<Let(Block = "qe")>><<User System Data.DG CPT Fence Col Width L>> for the Value in the newly created User Report Variable.
A-11
Click on the Add Field button again, and enter the following values into the fields for the right fence block, and click OK.
Field Name Name Type Value qe Width R Memo
Enter <<Let(Block = "qe")>><<User System Data.DG CPT Fence Col Width R>> for the Value in the newly created User Report Variable.
Click OK to close the Properties window and save the changes. We now need to copy the new User Report Variable to the other CPT Fence reports. With the CPT FENCE A4P report currently open, call the command File > Page > Copy Report Variables, select qe Width L and qe Width R then click OK.
A-12
Click on the List of pages to copy to button to bring up the selection dialog. Select the CPT Fence Reports in your library, then click OK. Note you may not have all the reports in your library as shown below.
Replace Field Names in Log and Fence Blocks

Now we need to replace all references to the original parameter (Differential Pore Pressure Ratio) to the new parameter (Effective Cone Resistance). The quickest and least error-prone way to do this is to use the Replace Field Names command. Go to DATA DESIGN | Project Database, then call the command Tools > Replace Field Names. Click on the Field List button and enter the following values in the table grid.
Find <<CPT_DATA.Differential_Pore_Pressure_Ratio>> <<Report Var.DPPR Width>> <<Report Var.DPPR Width L>> <<Report Var.DPPR Width R>> <<User System Data.DG CPT Param DPPR>> Replace <<CPT_DATA.Effective_Cone_Resistance>> <<Report Var.qe Width>> <<Report Var.qe Width L>> <<Report Var.qe Width R>> <<User System Data.DG CPT Param Effective Cone Resistance>>
Click on the Reports to Scan button. Select the following items in the list then Click OK. LogBlk!DG CPT QE FenceBlk!DG CPT QE L
A-13
FenceBlk!DG CPT QE R
Click OK to run the command. View the report to ensure that replacements were made and click OK.
At this point, you have completed creating the Dynamic Log Block and Fence Block for the Effective Cone Resistance derived parameter. Ensure that you have data in Effective_Cone_Resistance, and test the output of the new derived parameter in your Dynamic Log and Fence reports.
A-14
Appendix B Tutorial: Creating a New Correlation in the Formula Tool
Aim
In this tutorial, we will create a formula titled Undrained Shear Strength 5, which is the same as Undrained Shear Strength 3. For more details on the correlation refer to Undrained Shear Strength 3 section in this user guide. For quick reference, the equation is as below:
Procedure
We will start by creating the fields necessary to support this correlation. Go to the DATA DESIGN | Project Database tab, and then call the command File > Open File > Current Project. Select CPT_DATA from the yellow table drop down list from the top, and then add a new field by clicking on the New button. Fill in the fields with the following values, and click OK when finished.
Field Name Name Caption Type Description Value Undrained_Shear_Strength_5 Su 5 Tutorial Double Undrained shear strength from CSSM (method 5), Su = 0.5 * sin phi' * OCR^lambda * sig vo'; phi' is taken from the first of these fields with data: Effective_Friction_Angle_3 and Effective_Friction_Angle_1; OCR is taken from Overconsolidation_Ratio_1; Lambda stored on CPT_POINT_MATERIAL_PROPERTIES, CPT_POINT_CORRELATION _PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables kPa Field - Calculated
Units Cell Color
Select CPT_PROJECT_CORRELATION_PARAMETERS from the yellow table drop down list from the top, and then add a new field by clicking on the New button. Fill in the fields with the following values, and click OK when finished.
Field Name Name Type Description Value Undrained_Shear_Strength_5_Lambda Double Undrained shear strength from CSSM (method 5), Su = 0.5 * sin phi' * OCR^lambda * sig vo'; phi' is taken from the first of these fields with data: Effective_Friction_Angle_3 and Effective_Friction_Angle_1; OCR is taken from Overconsolidation_Ratio_1; This field represents lambda; Typically low to medium sensitivity clays are 0.7 <= lambda <= 0.8 , and sensitive and structured clays are 0.9 <= lambda <= 1.0 0.85 Field Enter Data
Default Value Cell Color
We will now copy this field into the CPT_POINT_CORRELATION_PARAMETERS table. Select CPT_POINT_ CORRELATION_PARAMETERS from the yellow drop down list from the top.
B-1
Call the command Tables > Merge Fields from Current File. Select CPT_PROJECT_CORRELATION_PARAMETERS and click OK. Then select Undrained_Shear_Strength_Tutorial_5 and click OK. Clear the Default Value. Click Save to save the changes. Go back to the INPUT tab and launch the Formula Tool Configuration Form, by calling the command Add-Ins > Datgel CPT Tool > Formula Tool Configuration.
The Formula Tool Configuration Form should appear.
Change the Location drop down to Project. Click on the new
Icon to create a new blank formula.
We will now use the Table Field Data Tool to insert a table field reference to the configuration. In the Configuration Group, Click on the Write Value To text field so that the cursor is blinking in the text field. Click on the Table drop down list, and select CPT_DATA. Then click on the Field drop down list, and select Undrained_Shear_Strength_5. The Table Field Drop Down list should look like the following:
B-2
Click on the Paste button. <<CPT_DATA.Undrained_Shear_Strength_5>> should have been pasted in the Write Value To field. NOTE: You are free to type the table field references. However, using the Table Field Data Tool eliminates typographical errors which will cause errors and unexpected results further down the track. Hence, you are encouraged to use the Table Field Data Tool to insert table field references, as typographical errors can be difficult to find afterwards. In the Configuration Group, fill in the following values.
Field Name Name Iteration Description Value Undrained Shear Strength 5 1 Undrained shear strength from CSSM (method 5), Su = 0.5 * sin phi' * OCR^lambda * sig vo'; phi' is taken from the first of these fields with data: Effective_Friction_Angle_3 and Effective_Friction_Angle_1; OCR is taken from Overconsolidation_Ratio_1; Lambda stored on CPT_POINT_MATERIAL_PROPERTIES, CPT_POINT_CORRELATION_PARAMETERS and CPT_PROJECT_CORRELATION_PARAMETERS tables Book: NCHRP Synthesis 368 pp39 <<CPT_DATA.Undrained_Shear_Strength_5>> Check this option. Decimal Places 1
Write Value To Enabled Formatting Type Value
We will now enter the variables in the Table/Field References to Variables Grid. Click on the Variable Name column, first row. Type in PhiD1 minding the case of each character. Click on the Expression column, first row. Go to the Table Field Data Tool, and select the CPT_DATA table, Effective_Friction_Angle_1 field. Click on the Paste button, and this should insert <<CPT_DATA.Effective_Friction_Angle_1>> in the cell in the first row of the Expression column. Click on the Validation Value column, first row. Enter 15 in the cell. We have just finished entering one variable, PhiD1 which represents Repeat the last three steps to enter the rest of the variables listed below:
Variable Name PhiD1 PhiD3 OCR SigDV0 PjLambda Expression Unit Validation Value 15 10 3 kPa 100 0.7 Represents Variable in the Equation
from the equation.
<<CPT_DATA.Effective_Friction_Angle_1>> <<CPT_DATA.Effective_Friction_Angle_3>> <<CPT_DATA.Overconsolidation_Ratio_1>> <<CPT_DATA.Effective_Stress>> <<CPT_PROJECT_CORRELATION_PARAMETERS.Undra ined_Shear_Strength_5_Lambda>>
deg deg
B-3
PtLambda SoilType
<<CPT_POINT_CORRELATION_PARAMETERS.Undrain ed_Shear_Strength_5_Lambda>> <<CPT_DATA.Soil_Type_1>>
0.8 Fine
TIP: You can use the up down arrows adjacent to the Variable Grid on the left to change the order the variables appear in the Grid. The order does not affect the formula calculation in any way. We are now ready to write the Formula. Click on the Formula text field so that the cursor is blinking in the text field. Go to the Function Data Tool, select Miscellaneous as the Type, then select the If() function. The Function Data Tool should look like the following:
Click on the Paste the Formula field.
button. if(cond, trueval, falseval) should have been pasted in
NOTE: You are free to type the function names. However, using the Function Data Tool eliminates typographical errors which will cause errors and unexpected results further down the track. Additionally, it helps you to set up the proper function syntax for the formula. Hence you are encouraged to use the Function Data Tool to insert functions, as typographical errors can be difficult to find afterwards. Parameters and Functions are case sensitive. Enter the following text in the formula field, using the Function Data Tool when needed:
if( SoilType == "Fine" || SoilType == "Mixed" || SoilType == "" , 0.5 * sin(first(PhiD3,PhiD1)/180*pi) * OCR^ first(PtLambda,PjLambda) * SigDV0 , "" )
An explanation of the formula is as below:

If( SoilType == "Fine" || SoilType == "Mixed" || SoilType == "" ...
Check to see if the Soil Type is either Fine, Mixed or empty. If it is, then evaluate the equation, otherwise, return empty. || denotes an OR logical operation, and == denotes an EQUAL TO text comparison.
first(PhiD3,PhiD1)
The first() function returns the first non-empty value (from left to right) in the list of parameters. If both PhiD3 and PhiD1 have values, then the first value, PhiD3 is returned.
sin(first(PhiD3,PhiD1)/180*pi)
The parameter for the sine function in the Formula Tool must be in radians. PhiD3 and PhiD1 are in Degrees, so the value is converted to radians by dividing by 180, then multiplying by pi.
B-4
TIP: You can use spaces and carriage returns (new line) to format, and space out your formula for better readability. The formatting method used in this tutorial separates the function name, parameters, parameter delimiters and closing bracket in a new line, and the parameters are indented by two spaces. For example,
FunctionName(Parameter1,Parameter2,FunctionName2(Parameter1,Parameter2))
Becomes
FunctionName( Parameter1 , Parameter2 , FunctionName2( , Parameter1 , Parameter2 ) )
Using a consistent formatting standard throughout your collection of formulas will allow you to quickly read and understand a formula, and enables you to find errors easily. Set the Result Unit as kPa. Your screen should look similar to the following:
B-5
Click the save button to save the formula to your Project. After saving, the formula name should be visible in the Formulas Grid on the left side. Avoid Errors. Divide by zero and null parameter errors slow the calculations noticeably. You should check for the possibility of these situations in the formula code For example, add the code in red
if( (SoilType == "Fine" || SoilType == "Mixed" || SoilType == "") && first(PhiD3,PhiD1) !="" && OCR !="" && SigDV0 !="" , 0.5 * sin(first(PhiD3,PhiD1) / 180 * pi) * OCR^ first(PtLambda,PjLambda) * SigDV0 , "" )
You can check if formulas are causing errors: 1. Call Add-Ins > Datgel CPT Tool > Settings, and set Log Formula Exceptions to True. 2. Do a batch calculation with 2 or more strokes, and when the calculation is complete click on the Report button. Errors will be listed in the More Information tab. We are now ready to validate the formula. Click on the Validate button. This will substitute variables in the Formula with the corresponding value in the Validation Value column in the Variables Grid, and then evaluate the equation. If everything has been correctly entered, a value of 20.9 will appear in the text field adjacent to the Validate button. Otherwise, an error message will show, detailing why the validation failed. Read the error message carefully and fix your configuration accordingly. Then click the Validate button again to validate the configuration. Repeat until no errors are shown, and the correct value is returned. The details of our formula can be saved to a text file, so that it may be archived, printed or distributed. Click on the Generate Validation Report for Current Formula button. Specify a file name and path for the new text file and click Save. The text file will be created, and will be automatically opened in your default text editor.
B-6
Return to the Formula Tool Configuration form, and click OK to close the form. We are now ready to calculate the Undrained Shear Strength 5 correlation in the CPT_DATA table. Go to INPUT | CPT | CPT Global Parameters tab, and enter 0.7 in the Undrained_Shear_Strength_Tutorial_5_Lambda field. Go to INPUT | CPT | CPT Data tab, and select GEF_01 as the PointID. Click on the bottom half of the screen and change a value to enable the Save button. Click Save. Assuming that you have entered a value in all table fields referenced in the Variables Grid, and there is a value in the Effective_Stress field, and Soil_Type_1 is either Fine, Mixed or empty, you should see a value in the newly created Undrained_Shear_Strength_5 field. Over 50 working correlations in the Formula Tool have been provided to you with the CPT Tool standard gINT Files. A good way to learn how to use the Formula Tool is by learning from example.
B-7
You may use these existing correlations as a basis to create new correlations that suit your requirements. The Copy Formula button on the Formula Configuration form is useful feature to quickly create multiple formulas that have only small differences. You may also copy rows in the parameter grid to other correlations. Now we will add the new correlation to the CPT Symbology tables. Go to DATA DESIGN | Library Data tab and select DG_CPT_SYMBOLOGY from the yellow table drop down list. Correctly assign the Data Template field, and then add a new row at the bottom with the following values, using the Data Tool when appropriate:
Column Name Parameter gINT Field Name SQL Field Name Unit Line Colour Line Type Line Thickness Data Marker Data Marker Height Log Data Marker Height Graph Minimum Scale Maximum Scale Automatic Scale Automatic Scale Round To Show on Report Remark Name Abbreviation Reference Reference Short Undrained Shear Strength S<<SUB>>u<<SUB>> Wroth (1984) True 0 500 Value Undrained Shear Strength 5 <<CPT_DATA.Undrained_Shear_Strength_5>> [CPT_DATA].[Undrained_Shear_Strength_5] kPa Very Light Magenta Solid 0.2 5 0
Go to INPUT | CPT | CPT Project Symbology. Scroll to the bottom, and select Undrained Shear Strength 5 from the drop down list in the Parameter column. For the Undrained Shear Strength 3 parameter, Set the Show on Report column value to false. Values entered in this table will take precedence over the values in the DG_CPT_SYMBOLOGY library table. Therefore, The Undrained Shear Strength 3 parameter will not be shown on reports generated with this project file. We will now output a dynamic report showing the calculated values in our newly created field.
Go to OUTPUT | Logs tab, and select the CPT DYNAMIC A4P log report from the yellow drop down list. Select GEF_01 in PointID field.
B-8
Click on the Print or Preview button, and the User Report Variables window will show. Fill in the following values and click OK.
Name Column 1 Column 2 Column 3 Column 4 Column 5 Column 6 Column 7 Column 8 Column 9 Column 10 Width 1 (mm) Width 2 (mm) Width 3 (mm) Width 4 (mm) Width 5 (mm) Width 6 (mm) Width 7 (mm) Width 8 (mm) Width 9 (mm) Width 10 (mm) Show qc qt Average Legend Show Dissipation Legend Show Design Line Legend Legend 1 Legend 2 Check this option. Check this option. Check this option. UNDRAINED SHEAR STRENGTH 45 45 Value QT QC FT FS WITH MINOR RF SLOPE INDICATOR UNDRAINED SHEAR STRENGTH
Below is an output of the report, exported as a png file.
B-9
B-10
Appendix C Tutorial: Creating a Log and Fence Report Column for a new Correlation
Aim
In this tutorial, we will be creating a dynamic log column and fence column for the correlation Undrained Shear Strength, . This tutorial will assume that the relevant fields and formula calculations have been created for Undrained Shear Strength as specified in the Error! Reference source not found.Appendix B tutorial.
Creating the User System Data

Go to DATA DESIGN | User System Data and call the command File > New. Enter DG CPT Param Undrained Shear Strength in the Name, optionally enter a description and click OK.
Enter the following code in the Data or Expression field then click Save.
<<Let(Param = <<ListBuildSepTrim(" ","Undrained Shear Strength",<<Get(ParamIndex)>>)>>)>>
C-1
Adding the Configuration to the Library Table

This step requires adding new records into the CPT Tool Library configuration tables, namely DG_DPT_SYMBOLOGY, DG_CPT_SYMBOLOGY_SCALES_UNITS, DG_CPT_LOG_BLOCK and DG_CPT_FENCE_BLOCK. The correlation log/fence reports can display up to 6 variations/interpretations of a correlation, and each variation must be configured in these tables. Each variation is denoted by an index number, starting from 1 to 6 inclusive. The naming convention that the log and fence blocks utilise is as below: [Correlation Name] [Index Number] Therefore, the names of the Undrained Shear Strength correlation are as below: Undrained Shear Strength 1 Undrained Shear Strength 2 Undrained Shear Strength 3 Undrained Shear Strength 4 Undrained Shear Strength 5 Undrained Shear Strength 6 The field names also follow this naming convention, except that spaces are replaced with underscores. Therefore, the CPT_DATA field names for Undrained Shear Strength are as below: Undrained_Shear_Strength_1 Undrained_Shear_Strength_2 Undrained_Shear_Strength_3 Undrained_Shear_Strength_4 Undrained_Shear_Strength_5 Undrained_Shear_Strength_6 Go to DATA DESIGN | Library Data, and select DG_DPT_SYMBOLOGY from the yellow drop down list. Enter 6 new records in DG_DPT_SYMBOLOGY with the following values, replacing the # with the index number starting from 1 to 6, then click Save.
Column Name Parameter gINT Field Name SQL Field Name SQL Table Name Line Type Line Thickness Data Marker Height Log Show on Report Value Undrained Shear Strength # <<CPT_DATA.Undrained_Shear_Strength_#>> [CPT_DATA].[Undrained_Shear_Strength_#] [CPT_DATA] Solid 0.2 0 True
C-2
Column Name Name Abbreviation
Value Undrained Shear Strength s<<SUB>>u<<SUB>>
Set the following values for each parameter, then click Save.
Parameter Name Undrained Shear Strength 1 Undrained Shear Strength 2 Undrained Shear Strength 3 Undrained Shear Strength 4 Undrained Shear Strength 5 Undrained Shear Strength 6 Line Colour Very Light Blue Very Light Brown Very Light Red Very Light Green Very Light Yellow Very Light Magenta Comparison Line Type Dash Dash-Dot Dash-Dot-Dot Dash2 Dash-Dash-Dot Dot2 Data Marker 1 2 3 4 5 6
Select DG_CPT_SYMBOLOGY_SCALES_UNITS from the yellow drop down list and enter two sets of 6 records following values, replacing the # with the index number starting from 1 to 6, then click Save. 1st Set:
Column Name Unit System Parameter Unit Minimum Scale Maximum Scale Value SI Undrained Shear Strength # kPa 0 500
C-3
Column Name Number of Divisions
Value 4
2nd Set:
Column Name Unit System Parameter Unit Minimum Scale Maximum Scale Number of Divisions Value English Undrained Shear Strength # tsf 0 4 4
Select DG_CPT_LOG_BLOCK from the yellow drop down list and enter a new record with the following values, then click Save. You may right-click and drag the row header to change the position of the record appears on the table.
Column Name Name Description Log Width Parameter Value Undrained Shear Strength Undrained Shear Strength, su 30 Undrained Shear Strength
C-4
Select DG_CPT_FENCE_BLOCK from the yellow drop down list and enter a new record with the following values, then click Save.
Column Name Name Description Width Parameter Value Undrained Shear Strength Undrained Shear Strength, su 10 Undrained Shear Strength
Creating the Dynamic Log Block

To create the Dynamic Log Block, we will make a copy of an existing correlation Dynamic Log Block and modify it to work with the new correlation parameter. In this tutorial, we will be using the Effective Friction Angle correlation parameter log block as the basis for our new log block. Go to REPORT DESIGN | Logs then call the command Blocks > Edit Log Blocks. Select DG CPT EFFECTIVE FRICTION ANGLE from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT UNDRAINED SHEAR STRENGTH in the Page names to copy to and click OK.
C-5
At this stage, your screen should look similar to this:
The references to the table fields and User System Data, and User Report Variables will be fixed at a later step. We now need to add a reference to the new block to the Dynamic Log reports. From the current screen (REPORT DESIGN | Logs > Log Blocks), select DG CPT DYNAMIC COLUMNS from the yellow drop down list. Call the command Blocks > Insert Block and enter the following values, then click OK. Main Tab:
Field Name Block Source Page Range Value Int!dg cpt undrained shear strength All
C-6
Field Name Design Mode Colour Offset X
Value Medium Blue <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Dynamic Log Col Offset X>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value 10 <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Dynamic Log Col Output Condition>>
Left click on a vacant space to place the Block reference, then click Save. We now need to add a new User Report Variable to the Dynamic Log reports. Click on the Logs tab to return to the REPORT DESIGN | Logs screen. Select the log report CPT DYNAMIC A4P from the yellow drop down list, and call the command File > Page > Properties. Click on the User Report Variables button, and click on the Add Field button on the bottom left. Enter the following values into the fields and click OK.
Field Name Name Type Value Undrained Shear Strength Width Memo
Enter <<Let(Block = "Undrained Shear Strength")>><<User System Data.DG CPT Dynamic Log Col Width>> for the Value in the newly created User Report Variable, and click OK.
Click OK to close the Properties window and save the changes.
C-7
We now need to copy the new User Report Variable to the other Dynamic Log reports. With the CPT DYNAMIC A4P report currently open, call the command File > Page > Copy Report Variables, select qe Width and click OK.
Click on the List of pages to copy to button to bring up the selection dialog. Select the Dynamic Log Reports in your library, then click OK. Note you may not have all the reports in your library as shown below.
Creating the Fence Block

To create the Fence Block, we will make a copy of an existing correlation parameter fence block and modify it to work with the new correlation parameter. In this tutorial, we will be using the Effective Friction Angle correlation parameter fence block as the basis for our new fence block. Note that there are two blocks that need to be created, left and right. The fence blocks are suffixed by L and R to denote this. Go to REPORT DESIGN | Fences then call the command Blocks > Edit Fence Blocks. Select DG CPT EFFECTIVE FRICTION ANGLE L from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT UNDRAINED SHEAR STRENGTH L in the Page names to copy to and click OK.
C-8
Now we will create the right block. From the current screen (REPORT DESIGN | Fences > Fence Blocks), select CPT EFFECTIVE FRICTION ANGLE R from the yellow drop down list. Call the command File > Copy Page. Enter DG CPT UNDRAINED SHEAR STRENGTH R in the Page names to copy to and click OK. We now need to add a reference to the new fence block to the Fence reports. From the current screen (REPORT DESIGN | Fences > Fence Blocks), select DG CPT STICK from the yellow drop down list. Call the command Blocks > Insert Block and enter the following values for the left fence block, then click OK. Main Tab:
Field Name Block Source Page Range Design Mode Colour Offset X Value Int!dg cpt undrained shear strength l All Very Light Blue <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Fence Col Offset X L>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value -11.75 <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Fence Col Output Cond L>>
Left click on a vacant space to place the Block reference, then click Save. Repeat the above steps, and enter the following for the right fence block. Main Tab:
Field Name Block Source Page Range Design Mode Colour Offset X Value Int!dg cpt undrained shear strength r All Very Light Red <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Fence Col Offset X R>>
Configuration Tab:
Field Name Design Mode Offset X Output Condition Value 11.75 <<Let(Block = "Undrained Shear Strength")>>_ <<User System Data.DG CPT Fence Col Output Cond R>>
We now need to add a new User Report Variable to the CPT Fence reports. Click on the Fences tab to return to the REPORT DESIGN | Fences screen. Select the log report CPT FENCE A4P from the yellow drop down list, and call the command File > Page > Properties.
C-9
Click on the User Report Variables button, and click on the Add Field button on the bottom left. Enter the following values into the fields for the left fence block and click OK.
Field Name Name Type Value Undrained Shear Strength Width L Memo
Enter <<Let(Block = "Undrained Shear Strength")>><<User System Data.DG CPT Fence Col Width L>> for the Value in the newly created User Report Variable. Click on the Add Field button again, and enter the following values into the fields for the right fence block, and click OK.
Field Name Name Type Value Undrained Shear Strength Width R Memo
Enter <<Let(Block = "Undrained Shear Strength")>><<User System Data.DG CPT Fence Col Width R>> for the Value in the newly created User Report Variable.
Click OK to close the Properties window and save the changes. We now need to copy the new User Report Variable to the other CPT Fence reports. With the CPT FENCE A4P report currently open, call the command File > Page > Copy Report Variables, select Undrained Shear Strength Width L and Undrained Shear Strength Width R then click OK.
C-10
Click on the List of pages to copy to button to bring up the selection dialog. Select the CPT Fence Reports in your library, then click OK. Note you may not have all the reports in your library as shown below.
Replace Field Names in Log and Fence Blocks

Now we need to replace all references to the original parameter (Effective Friction Angle) to the new parameter (Undrained Shear Strength). The quickest and least error-prone way to do this is to use the Replace Field Names command. Go to DATA DESIGN | Project Database, then call the command Tools > Replace Field Names. Click on the Field List button and enter the following values in the table grid.
Find <<CPT_DATA.Effective_Friction_Angle_1>> <<CPT_DATA.Effective_Friction_Angle_2>> <<CPT_DATA.Effective_Friction_Angle_3>> <<CPT_DATA.Effective_Friction_Angle_4>> <<CPT_DATA.Effective_Friction_Angle_5>> <<CPT_DATA.Effective_Friction_Angle_6>> Replace <<CPT_DATA.Undrained_Shear_Strength_1>> <<CPT_DATA.Undrained_Shear_Strength_2>> <<CPT_DATA.Undrained_Shear_Strength_3>> <<CPT_DATA.Undrained_Shear_Strength_4>> <<CPT_DATA.Undrained_Shear_Strength_5>> <<CPT_DATA.Undrained_Shear_Strength_6>>
C-11
Find <<Report Var.Effective Friction Angle Width>> <<Report Var.Effective Friction Angle Width L>> <<Report Var.Effective Friction Angle Width R>> <<User System Data.DG CPT Param Effective Friction Angle>>
Replace <<Report Var.Undrained Shear Strength Width>> <<Report Var.Undrained Shear Strength Width L>> <<Report Var.Undrained Shear Strength Width R>> <<User System Data.DG CPT Param Undrained Shear Strength>>
Click on the Reports to Scan button. Select the following items in the list then Click OK.

LogBlk!DG CPT UNDRAINED SHEAR STRENGTH FenceBlk!DG CPT UNDRAINED SHEAR STRENGTH L FenceBlk!DG CPT UNDRAINED SHEAR STRENGTH R
Click OK to run the command. View the report to ensure that replacements were made and click OK.
At this point, you have completed creating the Dynamic Log Block and Fence Block for the Undrained Shear Strength correlation parameter. Ensure that you have data in Undrained_Shear_Strength_#, and test the output of the new correlation in your Dynamic Log and Fence reports.
C-12
Appendix D Tutorial: Creating a New Unit System
Aim
In this tutorial, we will be creating a new unit system called SI_MPa, and apply the new system to our project database. This unit system is based on the units defined in AGS4.
Adding a new Unit System to the Lookup List

Go to DATA DESIGN | Lookup Lists tab, and select DG_COM_UNIT_SYSTEM from the yellow drop down list. Enter a new record at the bottom of the list.
Column Name Text Description Value SI_MPa SI MPa
SI_MPa is the name of the new unit system, and all unit conversion configuration fields will be prefixed with this name.
Creating the new Configuration Fields

Go to DATA DESIGN | Library Tables tab, and open the DG_CPT_FIELD_MAP table from the yellow drop down list. Add a field for each row in the following table, by clicking on the New button near the bottom left of the window, and filling out the text fields.
Name SI_MPa Type Text Caption Description
D-1
Name SI_MPa_FR_Minimum SI_MPa_FR_Maximum SI_MPa_FR_Decimals_Displayed SI_MPa_FR_Round_To_Nearest SI_MPa_FR_Format_Type SI_MPa_Default
Type Double Double Integer Double Text Text
Caption Minimum (SI_MPa) Maximum (SI_MPa) Decimals Displayed (SI_MPa) Round to Nearest (SI_MPa) Format Type (SI_MPa) Default (SI_MPa)
Description Minimum field rules property value Maximum field rules property value Decimals Displayed field rules property value Round to nearest field rules property value Format type field rules property value Default field property value
Set the Cell Colour to Field Enter Data for all the fields created. Select the SI_MPa field, set the Lookup to Libtbl!field units, check the Must use Lookup and Allow additions in Input options. Select the SI_MPa_FR_Format_Type field, set the Lookup to Lookup!dg_com_fr_format_type and check the Must use Lookup option. Your screen should appear similar to the following:
D-2
Populating the Configuration Fields

Go to DATA DESIGN | Library Data tab, and select DG_CPT_FIELD_MAP from the yellow drop down list. We will be using the units in the SI unit system as a basis to the SI_MPa unit system. Highlight all the cells in the SI field, and press Ctrl + C to copy the values to the Clipboard. Select the first cell in the SI_MPa column, and press Ctrl + P to paste the values to the column. Change the value in the SI_MPa column for the following records:
Table Name CPT_CONE_CALIBRATIONS CPT_DATA CPT_DATA CPT_DATA CPT_DATA CPT_DATA CPT_DATA CPT_DATA CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_GENERAL CPT_DISSIPATION_TEST_READINGS CPT_DISSIPATION_TEST_READINGS CPT_DISSIPATION_TEST_READINGS CPT_DISSIPATION_TEST_READINGS Field Name Area_Cone Excess_pore_pressure Filtered_Sleeve_Friction_Resistance In_Situ_Pore_Pressure Porewater_Pressure_1 Porewater_Pressure_2 Porewater_Pressure_3 Sleeve_Friction_Resistance Corrected_Initial_Pore_Pressure In_Situ_Pore_Pressure Initial_Pore_Pressure Maximum_Pore_Pressure Minimum_Pore_Pressure Pore_Pressure_Degree_Dissipation Friction_Resistance Porewater_Pressure_1 Porewater_Pressure_2 Porewater_Pressure_3 SI MPa cm2 MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa MPa Decimals Displayed (SI_MPa) 0 4 4 4 4 4 4 4 3 3 3 3 3 3 3 4 4 4
Validating the Configuration and Executing the Unit Conversion

Go to the INPUT tab, then call the command Add-Ins > Datgel CPT Tool > Unit Conversion. The following form will show:
Select SI_MPa from the Convert To pick list, then click Validate. If there are no problems with the configuration, you should see the following message form. Otherwise, a log report will display with a list
D-3
of problems with the configuration. If there are problems, close the Unit Conversion form, correct the problems and return to the Unit Conversion form and repeat this step.
Click on Execute to run the unit conversion. If you are running the unit conversion against a gINT project file (*.gpj), a backup file with the extension of (*.dbk) would have been made of the project file before the unit conversion is performed. You may rename this file to *.gpj if you wish to revert the unit conversion process. The following screen should appear if the unit conversion process has been successful. Note that some of the field units will appear to have not updated. Close the gINT Project file and reopen the file, and the units will show correctly.
Close and reopen gINT. You should be able to see the changes to the field units, the values and the decimals displayed.
D-4
D-5
Appendix E Tutorial: Entering a New Unit Quantity
Aim
In this tutorial, we will be entering the unit conversion factors for the quantity acceleration.
Procedure
We will be using m/s2 (meters per second squared) as the SI base unit, and entering the conversion factors to convert all acceleration units to the SI base unit. With this information, the CPT Tool can convert a value in any acceleration unit to another by multiplying the value by the conversion factor to m/s2, then converting the result to the desired unit by multiplying the value by the inverse of the conversion factor of the desired unit to the m/s2. Go to DATA DESIGN | Lookup Lists, and select DG_COM_UNIT_QUANTITY. Enter Acceleration for the text column in a new row, and click Save.
Go to DATA DESIGN | Library Data, and select Field units from the yellow drop down list. Enter the following values in the table and click Save.
Name cm/s2 in/s2 ft/s2 g0 m/s2 Description centimetres per second squared inches per second squared feet per second squared free fall (gravity) metres per second squared
E-1
Name mm/s2
Description Millimetres per second squared
Go to DATA DESIGN | Library Data, and select DG_COM_UNIT_CONVERSION from the yellow drop down list. Enter the following values in the table and click Save.
Source Unit cm/s2 in/s2 ft/s2 g0 m/s2 mm/s2 Formatted Source Unit cm/s<<SUP>>2<<SUP>> in/s<<SUP>>2<<SUP>> ft/s<<SUP>>2<<SUP>> g<<SUP>>0<<SUP>> m/s<<SUP>>2<<SUP>> mm/s<<SUP>>2<<SUP>> Source Unit Description centimetres per second squared inches per second squared feet per second squared free fall (gravity) metres per second squared millimetres per second squared Source to SI Conversion Factor 0.01 0.0254 0.3047987 9.80665 1 0.001 SI Unit m/s2 m/s2 m/s2 m/s2 m/s2 m/s2
For each of the newly added rows above, enter metres per second squared in the SI_Unit_Description column and Acceleration in the Quantity column. Your screen should look similar to the following:
Click Save.
E-2
Appendix F Tutorial: How to change a field unit and make it work with reports
Aim
This example will change the unit for Porewater_Pressure_2, u2, from kPa to MPa.
Step 1 - Change the field unit

Open the field properties for u2 and change the unit to MPa.
Step 2 - Use the Data Correction Tool to convert the data from kPa to MPa
1. Configure a new formula
2. 3.
Run the correction u2 kPa to MPa against all strokes in the project. Adjust library table DG_CPT_SYMBOLOGY_SCALES_UNITS
F-1
4.
Preview a dynamic log report to see the outcome Before After
5.
Do the same for u0, so that the data can plot on the same graph.
All the calculations refer to the unit property of the field, and convert units within the calculations as needed. That is why you must define units for each parameter in the formula tool.
F-2
Appendix G Tutorial: How create and configure a new CPT Data table
Aim
In this tutorial, we will create a new CPT data related table in the gINT project database, and add configuration to allow the table to work with the CPT Tool.
Creating a New Table

Go to the DATA DESIGN | Project Database tab in gINT to create a new table. The 3 types of CPT Data Tables are explained below. A screenshot of example CPT Data table Properties window is provided as a reference. After creating the new table, create new fields for the table before proceeding to the next step.
One to One child of CPT_DATA

Each row in this table has a corresponding row in the CPT_DATA table. Data can be written to or read from these tables for CPT custom formula calculations. To create a One to One Child of CPT_DATA table, set Key Sets to PointID,ItemKey,Depth, Parent table to CPT_DATA and check the One to One Relation check box.
Point Level
Values stored on a Point Level table are applicable to a specific PointID, noting that a PointID can have one or more CPT Tests. Values can be referenced from these tables for CPT custom formula calculations. Point Level tables can optionally have a split-screen child table, for which values also can be read for use in CPT Calculations.
G-1
To create a Point Level table, set Key Sets to PointID, Parent table to POINT.
Project Level
Values stored on a Project Level table are applicable to the current project, which encompasses all PointIDs and CPT Tests. Values can be referenced from these tables for CPT custom formula calculations. To create a Project Level table, set the Key Set to Project.
G-2
Adding the gINT Rules Table Procedures

Go to the Properties of the new table, and go to the gINT Rules tab. Add the gINT Rules procedures as per the table below.
Field gINT Rules Procedure on Empty Dataset gINT Rules Procedure After Updating Grid gINT Rules Procedure on Save gINT Rules Procedure on Deletion (non-Project level tables only) gINT Rules Procedure After Save gINT Rules Procedure Leaving Tab Value DATGEL DGD!OnEmpty DATGEL DGD!UpdatingGrid DATGEL DGD!OnSave DATGEL DGD!OnDelete DATGEL DGD!AfterSave DATGEL DGD!LeavingTable
Note that the gINT Rules Procedure on Deletion does not apply to Project level tables.
G-3
Adding New Records to the CPT_FIELD_MAP Library Table

Configuring this table will allow the CPT Tool to automatically run the calculation on the new table when changed, and the Unit Conversion to convert values in the fields of the new table from one unit to another. Browse to DATA DESIGN | Library Data tab in gINT. Select DG_CPT_FIELD_MAP from the table drop down list. You will need to enter one record for the new table and a record for each field on the table. The following section will use a table called CPT_DATA_PILE which has a field called Pile_Axial_Capacity_Unit_End_Bearing_1. Records in DG_CPT_FIELD_MAP cannot be ordered alphabetically, and are listed in the order they were created. So to keep the records in alphabetical order by Table Name and Field Name, find the appropriate row position in the table, select the entire row by left-clicking on the row header, then right-click on the row and select Insert Rows. For the table, enter the following values for the specified columns, leaving the other columns empty.
Column Table Name Location Change Initiates Calc Value CPT_DATA_PILE Project Check this option.
G-4
For fields in this table, enter the following values for the specified columns, leaving the other columns empty. See Unit Conversion 26.3.1 for more details on configuring the Unit Conversion related columns.
Column Table Name Field Name Location SI English Decimals Displayed (SI) Format Type (SI) Decimals Displayed (English) Format Type (English) Value CPT_DATA_PILE Pile_Axial_Capacity_Unit_End_Bearing_1 Project MPa tsf 3 Decimal Format 1 Decimal Format
Adding gINT Rules Code to Reference the New Table

Browse to gINT Rules > gINT Rules Code from the top Menu. On the List tab, select Datgel DGD then click on the Code tab.
Add the following Constant for the new table, at the desired row. Note that the constants are ordered in an alphabetical order.
G-5
The example below is for a table named CPT_DATA_PILE. You must repeat these steps for each new table. It is recommended that you keep to the naming convention for naming constants. Naming convention is as below:
Public Const gs_Table_<<Table Name>> as String = "<<Table Name>>"
Applying the convention for the current example, the code should look like this:
Public Const gs_Table_CptDataPile As String = "CPT_DATA_PILE"
Your screen should look something like this:
If the table is a One to One Child, Point Level or Project Level, you must add a reference to the table in the Case statement in the OnSave procedure. From the Proc drop down list, select OnSave. This should jump to the beginning of the OnSave sub. Within the Case statement, add the following code:
Case gs_Table_CptDataPile Cpt
G-6
If the table is a One to One Child, you must add a reference to the table in the Case statement in the AfterSave procedure. From the Proc drop down list, select AfterSave. This should jump to the beginning of the OnSave sub. Within the Case statement, add the following code:
Case gs_Table_CptDataPile Cpt
Click Save. The names of the constants, and the references to the constants in the case statements are listed in alphabetical order. It is recommended that when adding new table entries into the list of constants and case statements, the alphabetical order is maintained so that it is easier to navigate to and find the table constant in the future.
Colouring the Change Initiates Calculation Fields to Pastel Beige

If changing a value in a field on your new table is to initiate the CPT calculation, the colour of the field must be set to Pastel Beige. Go to DATA DESIGN | Project Database tab, and select the table from the drop down list. Select the field from the Fields list, then set the Cell Colour to Field Calculated. Click OK. Set the Cell Colour to Field Calculated for any other fields you wish to initiate the calculation upon the value changing.
G-7

Datgel CPT Tool User Guide

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Datgel CPT Tool User Guide

Diunggah oleh

Hak Cipta:

Format Tersedia

User Guide

CPT Tool gINT Add-In 3

Installation and Licensing ............................................................................................ 1

Quick Start Tutorial ................................................................................................... 11

Project Tables ........................................................................................................... 16

Library Tables ........................................................................................................... 30

CPT Tool gINT Add-In 3 User Guide

4.26 4.27 4.28 4.29

Data Import ................................................................................................................ 35

CPT Filter .................................................................................................................. 41 Groundwater and Overwater Testing ......................................................................... 42

Derived Parameters ................................................................................................... 52

Depth Correction Due to Inclination ........................................................................... 54 Formula Tool ............................................................................................................. 56

Data Correction Tool ................................................................................................. 67

Soil Behaviour Type .................................................................................................. 75

CPT Tool gINT Add-In 3 User Guide

Liquefaction Assessment ........................................................................................ 102

Pile Axial Capacity .................................................................................................. 114

Transfer Description and Consistency Summary .................................................... 117

Lower-Best-Upper Correlations ............................................................................... 120 Correlation Summary .............................................................................................. 121

Symbology .............................................................................................................. 135

Unit Conversion....................................................................................................... 141

Formula Tool and Data Correction Tool Functions.................................................. 147

CPT Tool gINT Add-In 3 User Guide

Reports .................................................................................................................... 161

References .............................................................................................................. 175

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

About Datgel CPT Tool 3

17. Faster, multithread calculation

Versions Used When Writing This Document

Hardware and Operating System

Required Windows Components

Conventions and typography used in this guide

Bold Text Italics Emphasis CAPITALS KEY+KEY

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

File name or path Table_Name Field_Name Command line

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

Installation and Licensing

DLL Program Installation

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

Virtual Memory Configuration

Which Database Structure? DGD SI, DGD EN or AGS RTA

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

Merge gINT Library Objects

Click Execute. The process may take several minutes.

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

Merge gINT Project File Tables and Fields

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

CPT Tool gINT Add-In 3 User Guide

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012

CPT Tool gINT Add-In 3 User Guide

Datgel DCT-UG-001 - 3.02 - August 2012