Professional Documents
Culture Documents
Datgel
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 Datgel Pty Ltd 2006-2014
Datgel Pty Ltd
Suite 8, Level 1, The Hub
89 - 97 Jones Street
Ultimo NSW 2007
Australia
Tel:
Fax:
Email:
Website:
info@datgel.com
www.datgel.com
Contents
About Datgel CPT Tool 3.1 .................................................................................................. v
New in Version 3.1 ............................................................................................................................v
New in Version 3................................................................................................................................ v
Versions Used When Writing This Document .................................................................................. vi
Support ............................................................................................................................................. vi
System Requirements ...................................................................................................................... vi
gINT ............................................................................................................................................................. vi
Hardware and Operating System ................................................................................................................. vi
Required Windows Components .................................................................................................................. vi
Introduction ........................................................................................................................... 10
Preparing .............................................................................................................................. 10
Importing CPT and Dissipation Data .................................................................................... 10
Configuring Parameters and CPT Data Analysis ................................................................. 12
Transfer Summary of Material Description ........................................................................... 13
Output a Log ......................................................................................................................... 14
More Information ................................................................................................................... 14
3.2
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 ...................................................................................... 31
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 ........................................................................................... 32
DG_CPT_SOIL_CLASS_ZONES .............................................................................................. 32
DG_CPT_SOIL_TYPE ............................................................................................................... 33
DG_CPT_SYMBOLOGY ............................................................................................................ 33
DG_CPT_SYMBOLOGY_SCALES_UNITS ............................................................................... 33
Datgel
DCT-UG-001 - 3.11 - September 2014
3.2.23
3.2.24
3.2.25
3.2.26
3.2.27
3.2.28
3.2.29
Processing ................................................................................................................. 35
4.1
4.2
4.3
4.4
5.2
5.3
Introduction................................................................................................................................. 64
Formula Toolbar ......................................................................................................................... 65
Data Tool Toolbar ....................................................................................................................... 66
Formulas Group ......................................................................................................................... 68
Key Set Group ............................................................................................................................ 69
Configuration Group ................................................................................................................... 69
Offset and Correction Group ...................................................................................................... 70
5.5
Introduction................................................................................................................................. 54
Formula Toolbar ......................................................................................................................... 55
Data Tool Toolbar ....................................................................................................................... 56
Formulas Group ......................................................................................................................... 59
Configuration Group ................................................................................................................... 60
Merge/Copy Formulas ................................................................................................................ 62
5.4
Formula Tool..........................................................................................................................54
5.2.1
5.2.2
5.2.3
5.2.4
5.2.5
5.2.6
Functions .................................................................................................................................... 72
Special Functions ....................................................................................................................... 74
CPT Filter...............................................................................................................................45
Groundwater and Overwater Testing ....................................................................................46
4.4.1
4.4.2
4.5
4.6
Tools Menu................................................................................................................................. 35
File Browse Types ...................................................................................................................... 35
File Types ................................................................................................................................... 36
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
DG_CPT_TERMINATION .......................................................................................................... 33
DG_CPT_TEST_METHOD ........................................................................................................ 33
DG_CPT_TRANSFER_SUMMARY_DESC_CONSISTENCY.................................................... 33
DG_CPT_TYPE ......................................................................................................................... 33
DG_CPT_ZERO_LOCATION ..................................................................................................... 33
DG_IMPORT_USER_IMPORT_PARAMETERS ........................................................................ 33
DG_LOG_CONSISTENCY_DENSITY ....................................................................................... 33
Introduction................................................................................................................................. 86
Project Field Units ...................................................................................................................... 86
Library Configuration .................................................................................................................. 87
Unit Conversion of the Current Project ....................................................................................... 90
Analysis ..................................................................................................................... 92
6.1
Derived Parameters...............................................................................................................92
6.1.1
6.1.2
6.2
6.3
Correlations ...........................................................................................................................99
ii
Datgel
DCT-UG-001 - 3.11 - September 2014
6.3.1
6.3.2
6.3.3
6.3.4
6.3.5
6.3.6
6.3.7
6.3.8
6.3.9
6.3.10
6.3.11
6.3.12
6.3.13
6.3.14
6.3.15
6.3.16
6.3.17
6.3.18
6.3.19
6.4
6.5
6.8
6.6
6.7
iii
Datgel
DCT-UG-001 - 3.11 - September 2014
6.11.2
6.11.3
7.2
Adding the CPT Tool fence stick to a non-CPT Tool fence report ............................................ 173
Creating a Log and Fence Report Column for a new Derived Parameter ..........................184
8.1.1
8.1.2
8.1.3
8.1.4
8.1.5
8.1.6
8.1.7
8.2
8.3
How to change a field unit and make it work with reports ...................................................228
8.6.1
8.6.2
8.6.3
8.7
8.6
8.5
8.4
7.4
7.3
Tables
Table 1 - Field Colours ............................................................................................................................. viii
Table 2 - Derived Parameters .................................................................................................................. 92
Table 3 - Log Reports ............................................................................................................................ 169
Table 4 - Dynamic Log Report Variables ............................................................................................... 170
Table 5 - Fence Reports ........................................................................................................................ 171
Table 6 - Fence Report Variables .......................................................................................................... 171
Table 7 - Graph Reports ........................................................................................................................ 173
iv
Datgel
DCT-UG-001 - 3.11 - September 2014
ASCII data files in numerous standard and propriety formats may be imported
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
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.
2.
Begemann Mechanical CPT derivations from raw readings, and pre-population of CPT_DATA
depth data to facilitate data entry
3.
4.
5.
6.
7.
Thin Layer Correction, calculated for reference, not used be other calculations
8.
9.
Earthquake design groundwater depth and fill surcharge, resulting design effective stress
profile
New in Version 3
1.
2.
Datgel
DCT-UG-001 - 3.11 - September 2014
3.
Soil behaviour type correlations by Eslami Fellenius (1997), Ramsey (2002), and
Schmertmann (1978)
4.
5.
6.
7.
8.
Liquefaction factor of safety, residual shear strength, lateral displacement and settlement
9.
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 or +65 6631 9780.
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.
2.
vi
Datgel
DCT-UG-001 - 3.11 - September 2014
Used to indicate a gINT Application Group, Application, Table Group or Table , e.g.
DATA DESIGN | Project Database
Bold Text
Italics Emphasis
CAPITALS
KEY+KEY
Code Snippet
Code sample
Table_Name
Field_Name
Command line
vii
Datgel
DCT-UG-001 - 3.11 - September 2014
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
Read-only
Note: The Datgel CPT Tool is supplied with three 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 DGD SI and AGS-RTA 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
Datgel
DCT-UG-001 - 3.11 - September 2014
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.
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
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:
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.
Datgel
DCT-UG-001 - 3.11- September 2014
1.2
This setting is recommended so that Windows can achieve optimal memory use and speed for batch
calculation.
1.
Start Menu, right click on Computer > Properties > Advanced System Settings >
Advanced tab > Performance section > Settings button > Advanced Tab > Virtual
memory section > Change button
2.
3.
4.
Set Initial size to the same as your installed RAM (e.g. if 8GB RAM, then enter 8192MB)
5.
Set Max size to double your installed RAM (e.g. if 8GB RAM, then enter 16384MB)
1.3
At this point you must decide which CPT Tool database structure to use. The options are:
1.
DGD SI stands for Datgel Database with SI/metric units and long table (e.g.
CPT_POINT_PARAMETERS) and field names.
2.
DGD EN stands for Datgel Database with English/Imperial units and long table (e.g.
CPT_POINT_PARAMETERS) and field names.
3.
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.
Unless youre currently using an AGS RTA style database, we recommend you adopt the DGD
database most relevant for your local practice.
1.4
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 asis.
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.
Make a backup copy of your existing library file. By default this is located at:
C:\Users\Public\Documents\Bentley\gINT\libraries\
2.
Start gINT and open the library and project file you wish to use the Datgel CPT Tool with.
3.
If your library has 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.
4.
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.
Datgel
DCT-UG-001 - 3.11- September 2014
5.
6.
Browse the Source Library File for datgel cpt tool dgd lib #.## <Unit>.glb
7.
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.
8.
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
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 click the toolbar button
, select the tables to delete, click the delete key, and click OK.
Datgel
DCT-UG-001 - 3.11- September 2014
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 tables to import as shown in the following examples, and click OK.
The selected 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
Datgel
DCT-UG-001 - 3.11- September 2014
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. If youre
unsure, we suggest merging them all and reconciling them later.
6.
Merge fields from PROJECT. Follow a similar process to that for POINT.
Datgel
DCT-UG-001 - 3.11- September 2014
7.
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
Initial Configuration
After the library and project merge steps, the following items should be configured:
1.
Move to INPUT and reorder the tables within the CPT table group. Select the Table Group,
and call Tables > Input Sequence
Datgel
DCT-UG-001 - 3.11- September 2014
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 3.2.19 DG_CPT_SOIL_CLASS_ZONES on page
32. Select the most appropriate graphics in your library for each soil type zone.
3.
Datgel
DCT-UG-001 - 3.11- September 2014
4.
Move to INPUT and configure the table and field names for Lithology/Stratigraphy and
Consistency/Density as described in 5.1.3 Configuration of description and consistency
summary transfer on page 54 .
5.
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.
6.
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.
7.
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)
1.7
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
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 including Add-In commands and gINT Rules modules. 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
We recommend you open the relevant file above in DATA DESIGN | Correspondence Files, and do
the following:
Datgel
DCT-UG-001 - 3.11- September 2014
1.
Adjust the Source File and Target File properties to point to your old and new data template /
project file.
2.
3.
4.
Try converting one file using UTILITES | Convert Projects. Note that gINT will automatically
make a backup of the project with an extension *.or#.
5.
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.
Datgel
DCT-UG-001 - 3.11- September 2014
2.1
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.
To learn about more advanced operations of the CPT Tool, refer to 8 Tutorials.
2.2
Preparing
1.
First work your way through sections 1.1 DLL Program Installation and 1.3 Which Database
Structure? DGD SI, DGD EN or AGS RTA.
2.
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.
3.
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.
4.
Now, open the datgel cpt tool dgd lib X.XX SI.glb, using File > Change Library.
5.
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.
2.3
Launch the Data Import Tool, by calling the command Add-Ins > Datgel CPT Tool > Data
Import.
The CPT Tool splash screen should displays, confirming you are now using the CPT Tool
license.
If youre using a trial license then a form displays how many uses you have remaining.
If nothing happens, then confirm you have installed the CPT Tool program by running the
setup.exe file located in the Installation Files folder on the DVD.
10
Datgel
DCT-UG-001 - 3.11- September 2014
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
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.
2.
d) Click Execute. There will be a short pause while the Datgel code translates the data, then
you will see a gINT progress form.
11
Datgel
DCT-UG-001 - 3.11- September 2014
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
The following information must be entered for the basic CPT Calculations to occur:
CPT | CPT Data - Upper: Test Number, Cone ID, and (optionally) Groundwater Depth. Set Groundwater
Depth to 0.
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)
12
Datgel
DCT-UG-001 - 3.11- September 2014
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:
Refer to section 4.4 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 4.2
Initiation of the CPT Data Calculation).
The resulting CPT | CPT Data screen should look like this:
2.5
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.
13
Datgel
DCT-UG-001 - 3.11- September 2014
2.6
Output a Log
2.7
More Information
Refer to section 6.11 Dissipation Test Analysis for a tutorial on that subject.
14
Datgel
DCT-UG-001 - 3.11- September 2014
Almost all of the data and configuration that is created through using CPT can be viewed directly. You
might not ever need to do this as part of your workflow, but gaining familiarity with this data can provide
confidence about the accuracy of CPT calculations. Some power users also find that it provides a better
understanding of the analysis process.
3.1
Project Tables
The test and interpreted data tables are stored in the project database.
A number of constants and assumptions are required in derivations. Many may be set as follows:
Some may be set for each push (on CPT Data Upper).
This provided you with full control over which level in the hierarchy to use.
3.1.1
Main Group
3.1.1.1
POINT
When an Elevation is changed the Tool will calculate. The PointID and HoleDepth fields must be defined.
15
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.2
CPT
3.1.2.1
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.1.2.2
This table stores the actual raw depth related data for each push and derived results related to each
reading.
16
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.2.3
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.1.2.4
This table can be used to record the calibration dates for each cone.
17
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.2.5
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.1.2.6
These tables store the Dissipation Test raw and derived data.
18
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.2.7
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.1.2.8
Spherical Ball Penetrometer Data is stored on these tables. In future versions correlations will be
added.
19
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.2.9
3.1.2.10
This table was added to support AGS 4 Format. Currently users must manually enter summary data in
this table.
20
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.3
CPT-Liquefaction
3.1.3.1
3.1.3.2
21
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.3.3
3.1.4
CPT-Foundation
3.1.4.1
22
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.4.2
3.1.4.3
23
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.4.4
3.1.5
CPT-Configuration
3.1.5.1
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.
24
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.2
3.1.5.3
A bulk unit weight, u0, e, Nk, Nkt, Su LB, Su BE, Su UB, FC 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.1.5.4
Project level constants and parameters related to derived parameter and soil behaviour type
calculations are stored on this table.
25
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.5
Project level correlation parameters and constants are stored on this table.
3.1.5.6
26
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.7
This table stores Point level overrides for the settings on CPT_PROJECT_SYMBOLOGY and
DG_CPT_SYMBOLOGY.
3.1.5.8
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.
CPT Tool gINT Add-In 3.1
User Guide
27
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.9
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.
28
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.10
3.1.5.11
Definition of project specific Soil Behaviour Type zones and polygon data.
29
Datgel
DCT-UG-001 - 3.11- September 2014
3.1.5.12
3.1.5.13
This is a hidden table and stores Project level Data Correction formulas.
3.2
Library Tables
This section lists library tables that are important to calculation of the CPT Tool and reports.
3.2.1
DG_COM_UNIT_CONVERSION
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.
3.2.2
DG_CPT_AUTO_FILTER
3.2.3
DG_CPT_CORRELATION_SUMMARY_CONFIG
This table stores Library level data for the correlation summary function.
3.2.4
DG_CPT_DATA_CORRECTION_FORMULA_CONFIG
3.2.5
DG_CPT_DEPTH_ELEVATION_SCALE
3.2.6
DG_CPT_FENCE_BLOCK
3.2.7
DG_CPT_FIELD_MAP
Stores the table and field name configuration used by the CPT Tool calculation. This allows you 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.
3.2.8
DG_CPT_FORMULA_CONFIGURATION
These table stores Library level formulas for the Formula Tool.
3.2.9
DG_CPT_LOG_BLOCK
3.2.10
DG_CPT_MEASUREMENT_SYSTEM
This table is a simple lookup for the measurement system type options, based on the GEF standard.
30
Datgel
DCT-UG-001 - 3.11- September 2014
3.2.11
DG_CPT_MODIFIED_TIME_FACTOR
3.2.12
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_BEARING
3.2.13
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_FRICTION
3.2.14
DG_CPT_PILE_AXIAL_CAPACITY_LCPC_SOIL
3.2.15
DG_CPT_PORE_PRESSURE_FILTER_POSITION
3.2.16
DG_CPT_SCALE_TYPE
This table is a simple lookup for the soil classification graph type options.
3.2.17
DG_CPT_SOIL_CLASS_DATA
This table stores the soil classification polygon data. Users can add their own classification methods.
31
Datgel
DCT-UG-001 - 3.11- September 2014
3.2.18
DG_CPT_SOIL_CLASS_METHOD
This table stores the names and graphing options for each soil classification method.
3.2.19
DG_CPT_SOIL_CLASS_ZONES
This table stores the descriptions and graphics for each soil classification zone.
32
Datgel
DCT-UG-001 - 3.11- September 2014
3.2.20
DG_CPT_SOIL_TYPE
3.2.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.
3.2.22
DG_CPT_SYMBOLOGY_SCALES_UNITS
3.2.23
DG_CPT_TERMINATION
This table is a simple lookup of reasons for terminating a CPT stroke, based on the GEF standard.
3.2.24
DG_CPT_TEST_METHOD
3.2.25
DG_CPT_TRANSFER_SUMMARY_DESC_CONSISTENCY
This table stores the target table and field names soil description and consistency data summary
transfer.
3.2.26
DG_CPT_TYPE
3.2.27
DG_CPT_ZERO_LOCATION
3.2.28
DG_IMPORT_USER_IMPORT_PARAMETERS
3.2.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
Datgel
DCT-UG-001 - 3.11- September 2014
34
Datgel
DCT-UG-001 - 3.11- September 2014
Processing
This section provides information that is helpful for gaining an understanding of the end-to-end workflow
using the CPT Tool. After completing this section, you can use this information to develop greater
control over processing. This will enable you to achieve accurate, repeatable results. Importing data
enables you to work with data created by many hardware manufacturers, without the effort of manual
data entry or copy-paste. The import feature supports a wide range of standard data formats
You can use processing functions to apply repetitive corrections, e.g. apply calibrations.
4.1
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.
4.1.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.
4.1.2
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.
35
Datgel
DCT-UG-001 - 3.11- September 2014
4.1.3
File Types
AGS (*.ags)
ConeTec (*.cor)
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.
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/
Geo-Explorer (*.csv)
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
4.1.4
Vertek (*.ecp)
Overwrite Option
4.1.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.
4.1.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
Datgel
DCT-UG-001 - 3.11- September 2014
There are two features in the Advanced Options panel, Create Temp Import File and User Import
Parameters.
4.1.6.1
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
Datgel
DCT-UG-001 - 3.11- September 2014
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.
4.1.6.2
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.
This enables you to 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
Datgel
DCT-UG-001 - 3.11- September 2014
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.
4.1.7
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.1
User Guide
39
Datgel
DCT-UG-001 - 3.11- September 2014
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!
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.
4.1.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.
4.2
4.2.1
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
40
Datgel
DCT-UG-001 - 3.11- September 2014
CPT_DATA_ENVIRONMENTAL
CPT_DATA_LIQUEFACTION
CPT_DATA_LOWER_BEST_UPPER
CPT_DATA_FOUNDATION
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.
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 4.2.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
Action Taken
FALSE
FALSE
CPT calculated
TRUE
FALSE
41
Datgel
DCT-UG-001 - 3.11- September 2014
pending calculation
FALSE
TRUE
CPT Calculated
TRUE
TRUE
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.
4.2.2
Batch Calculation
The Batch Calculation feature allows you to make changes to the 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
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.
42
Datgel
DCT-UG-001 - 3.11- September 2014
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.
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.
4.2.3
Order of Calculation
Derived parameters
2.
3.
4.
4.2.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.
43
Datgel
DCT-UG-001 - 3.11- September 2014
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
Maximum Strokes Per Sub-batch: This Setting applies to SQL Server databases only. If a
batch contains a large number of short Strokes, then the length of the resulting queue of
Strokes waiting to be processed will grow large. This may have a detrimental effect on the
speed of the batch calculation. On SQL Server it may cause connection dropouts and failure to
update a Stroke with the newly calculated values. Setting this value may help stop these kinds
of issues. 30 is the default and recommended value. When set to 0, this setting is not applied.
Threading
Maximum Threads Per Processor: Each CPT calculation is performed in a separate multitasking process called a "Thread". This specifies 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 between zero and one. 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
44
Datgel
DCT-UG-001 - 3.11- September 2014
concurrent Threads ("Maximum Threads per Processor" x "Number of Processors"). The default
factor is 3. Only values between 3 and 6 are recommended.
These settings are included in order to change the way a computer organizes and manages memory
and processor (CPU) resources while performing a CPT batch calculation. Different brands and models
of PCs use memory and CPU resources in different ways. Therefore a batch calculation may run
without errors on your desktop PC, but may run very slowly or run out of memory on another computer,
such as your laptop. Due to the variety of brands and models of Windows PCs available, it is impossible
to predict which computers will experience problems.
If, when using the default Calculation Settings, you experience slow performance, error messages
referring to OutOfMemoryExceptions or failure of a number of calculations, you may need to adjust
these Calculation Settings to suit your computer.
The first thing to try is to double the Batch Size Denominator value and run the calculation again. If
you still experience errors after this step, then you should call Datgel for technical support and provide
details of the problems encountered. One of our team will provide you with the configuration of these
Settings that is most likely to address your specific problem.
If you have written any of your own Formula Tool formulae and included them in the batch calculation,
you may find the speed of the calculations decreases dramatically. This is most likely because the
formula is attempting many calculations on fields without values, or is attempting to divide by zero or
other operations resulting in mathematical errors. You can set the Log Formula Exceptions setting to
true to include additional information in the batch calculation Report. This will help you identify
problematic formulas and the conditions causing the errors. Ensuring that you check for fields with no
(null) values and zero denominators will generally avoid these kinds of problems.
4.2.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.
4.3
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 filtering to take place, the Cone_Sleeve_Offset on the CPT_CONE_INFORMATION table must
be defined.
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.
45
Datgel
DCT-UG-001 - 3.11- September 2014
4.4
4.4.1
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.
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.Offshore_Water_Depth: Nothing
In situ pore pressure is calculated relative to the atmospheric pressure using the following formula:
< = 0
= ( )
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)
4.4.2
Overwater Testing
The critical fields related to pore pressure calculation for over water testing are:
CPT_GENERAL.Offshore_Water_Depth or CPT_POINT_PARAMETERS.Offshore_Water_Depth
CPT_GENERAL.Zero_Location
CPT_GENERAL.Pre_Drilled_Depth
CPT_GENERAL.Groundwater_Depth
46
Datgel
DCT-UG-001 - 3.11- September 2014
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.
4.4.2.1
In this case the transducers, including depth, are zeroed on deck (at atmospheric pressure). Measured
parameters dont require zero corrections.
Define
CPT_GENERAL.Zero_Location: S - Surface
In situ pore pressure is calculated relative to the atmospheric pressure using the following formula:
< = 0
= ( )
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.
4.4.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.Zero_Location: SB - Seabed
CPT_GENERAL.Groundwater_Depth: Nothing
The in situ pore pressure, total stress and effective stress are calculated relative to the seabed, hence:
CPT Tool gINT Add-In 3.1
User Guide
47
Datgel
DCT-UG-001 - 3.11- September 2014
=
=
=
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
4.4.2.3
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.Groundwater_Depth: Nothing
In this scenario the and 2 will be corrected using the following formulas before they are used by the
calculation code:
= +
2 = 2 +
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)
Where:
is the cone resistance corrected
is the cone resistance measured
CPT Tool gINT Add-In 3.1
User Guide
48
Datgel
DCT-UG-001 - 3.11- September 2014
4.5
Unit Weight and Void Ratio may be defined in two locations and are used in the order listed:
1.
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.
4.6
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:
=
0
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.
49
Datgel
DCT-UG-001 - 3.11- September 2014
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.
4.6.1
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:
50
Datgel
DCT-UG-001 - 3.11- September 2014
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.
51
Datgel
DCT-UG-001 - 3.11- September 2014
This section explains features of CPT Tool that are available to extend its functionality. These features
provide a powerful means of improving the efficiency of your work, such as when you need to repeat a
set of corrections. It also enables you to create new formula to support calculations nor available in the
standard configuration.
These features are most suitable for use by engineers and scientists who are able to harness the
extended capabilities of the CPT Tool. This can be done without exposure to complex programming:
CPT Takes care of converting expressions into working code.
5.1
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.
52
Datgel
DCT-UG-001 - 3.11- September 2014
Prompt on overwrite Prompts you to select 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.
The CPT Description data is processed and consolidated before it is transferred to the Description
table. The order of operation is:
1.
2.
3.
5.1.1
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.
If the layer above is the same coarse or fine type, then the Bottom will be set to the Bottom of the
removed layer.
2.
If the layer below is the same coarse or fine type, then the Depth will be set to the Depth of the
removed layer.
3.
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.
5.1.2
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.
53
Datgel
DCT-UG-001 - 3.11- September 2014
5.1.3
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:
2.
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.
Click OK.
5.2
Formula Tool
5.2.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.
54
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.2
Formula Toolbar
Hovering the mouse cursor over each item will show a tooltip with a short description of the item.
Name
Icon/Image
Keyboard Shortcut
Description
New Formula
Ctrl + N
Save Formula
Ctrl + S
Delete Formula
Ctrl + D
Undo Changes
Ctrl + U
Copy Current
Formula
Ctrl + Shift + C
55
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Icon/Image
Keyboard Shortcut
Description
Enable all
Formulas
Disable all
Formulas
Location
Generate
Validation
Report for
Current
Formula
Generate
Validation
Report for All
Formulas
Merge/Copy
Formulas
5.2.3
Hovering the mouse cursor over each item will show a tooltip with a short description of the item.
Name
Icon/Image
Keyboard Description
Shortcut
Refresh Data
Tool
Ctrl + R
Table Field
Data Tool
Function Data
Tool
56
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.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:
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.
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
Formula
Write Value To
57
Datgel
DCT-UG-001 - 3.11- September 2014
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.
5.2.3.2
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.
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 ... .
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
Formula
Write Value To
Refer to section 5.4 Formula Tool and Data Correction Tool Functions for detailed information about the
functions.
58
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.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 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.
59
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.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.
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
60
Datgel
DCT-UG-001 - 3.11- September 2014
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 5.4 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 of the table.
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
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.
61
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.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 .
5.2.6.1
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
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.
62
Datgel
DCT-UG-001 - 3.11- September 2014
5.2.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
Description
OK (Library, Version 2)
Valid CPT Tool gINT Library (*.glb) version 2.17 and older, CPT Tool DLL version
2.2.0 and older
OK (Library, Version 3)
Valid CPT Tool gINT Library (*.glb) version 2.18 and newer, CPT Tool DLL version
2.2.1 and newer
OK (Project, Version 2)
Valid CPT Tool gINT Project (*.gpj) version 2.17 and older, CPT Tool DLL version
2.2.0 and older
OK (Project, Version 3)
Valid CPT Tool gINT Project (*.gpj) version 2.18 and newer, CPT Tool DLL version
2.2.1 and newer
Error
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.
5.2.6.3
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.
5.2.6.4
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.
63
Datgel
DCT-UG-001 - 3.11- September 2014
Source and Target files have not been validated, or validation has failed for either of the files
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
5.2.6.5
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.
5.3
5.3.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).
CPT Tool gINT Add-In 3.1
User Guide
64
Datgel
DCT-UG-001 - 3.11- September 2014
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.
5.3.2
Formula Toolbar
Hovering the mouse cursor over each item will show a tooltip with a short description of the item.
Name
Icon/Image
Keyboard Shortcut
Description
New Formula
Ctrl + N
Save Formula
Ctrl + S
Delete Formula
Ctrl + D
Undo Changes
Ctrl + U
Copy Current
Formula
Ctrl + Shift + C
Paste Formula
Ctrl + Shift + V
65
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Icon/Image
Keyboard Shortcut
Description
Enable all
Formulas
Ctrl + Shift + E
Disable all
Formulas
Ctrl + Shift + D
5.3.3
Hovering the mouse cursor over each item will show a tooltip with a short description of the item.
Name
Icon/Image
Refresh Data
Tool
Keyboard
Shortcut
Description
Ctrl + R
Table Field
Data Tool
Function Data
Tool
5.3.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.
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:
Caption The caption text as configured in the Caption field in the gINT Table or Field
Properties
66
Datgel
DCT-UG-001 - 3.11- September 2014
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
Formula
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.
5.3.3.2
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.
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 [,...])
67
Datgel
DCT-UG-001 - 3.11- September 2014
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 ... .
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
Formula
Name
Refer to section 5.4 Formula Tool and Data Correction Tool Functions.
for detailed information about the functions.
5.3.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
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 Down Moves the currently selected formula down by one row
Move to Bottom moves the currently selected formula to the bottom of the grid
68
Datgel
DCT-UG-001 - 3.11- September 2014
5.3.5
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:
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.
5.3.6
Configuration Group
69
Datgel
DCT-UG-001 - 3.11- September 2014
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
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.
5.3.7
The Offset and Correction group defines the formula type and options related to the for the currently
selected formula.
70
Datgel
DCT-UG-001 - 3.11- September 2014
5.3.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.
5.3.7.2
Correction
This formula type allows for the alteration in value of data for a column based on a Formula. For
example:
1.
Re-zero the Depth column, to correct for an incorrect start depth applied during acquisition.
2.
71
Datgel
DCT-UG-001 - 3.11- September 2014
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 5.4 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.
5.4
5.4.1
Functions
Type
Description
Function Name
Constants
, 3.14159
Pi
Constants
Constants
true
Constants
false
Natural Logarithm
ln(x)
Logarithm base 10
log(x)
Logarithm base 2
lg(x)
Exponential (e^x)
exp(x)
Power
pow(x)
Miscellaneous
If
Miscellaneous
abs(x)
Miscellaneous
Binomial coefficients
binom(n, i)
Miscellaneous
first(x1,x2,x3,...)
Miscellaneous
LookupIntervalRangeWithUnit("<<Current
Interval Table.Field>>","<<Lookup Value
72
Datgel
DCT-UG-001 - 3.11- September 2014
Type
Description
Function Name
Table.Field>>","<<Top Interval
Table.Field>>","<<Bottom Interval
Table.Field>>",Return Unit)
Miscellaneous
FixedIntervalAverage("<<Current Interval
Table.Field>>","<<Values to Average
Table.Field>>",Top Boundary, Bottom
Boundary, Interval Unit, Return Unit)
Miscellaneous
Modulus
mod(x,y)
Miscellaneous
Modulus
x%y
Miscellaneous
Moving Average
MovingAverage("<<Current Interval
Table.Field>>","<<Values to Average
Table.Field>>",Thickness)
Miscellaneous
rand()
Stepped Average
SteppedAverage("<<Current Interval
Table.Field>>","<<Values to Average
Table.Field>>",Thickness)
Miscellaneous
Stepped Extrapolation
SteppedExtrapolation("<<Current Interval
Table.Field>>","<<Values to Extrapolate
Table.Field>>")
Miscellaneous
Square Root
sqrt(x)
Miscellaneous
Sum
sum(x,y,...)
Miscellaneous
str(x)
Miscellaneous
TableIntervalAverage("<<Current Interval
Table.Field>>","<<Values to Average
Table.Field>>","<<Top Interval
Table.Field>>","<<Bottom Interval
Table.Field>>")
Operators
Addition
Operators
Subtraction
Operators
Division
Operators
Multiplication
Operators
Unary Plus
+x
Operators
Unary Minus
-x
Operators
Power
Operators
Modulus
Operators
Boolean Not
Operators
Boolean And
&&
Operators
Boolean Or
||
Operators
Equal
==
Operators
Not Equal
!=
Operators
Less Than
<
Operators
>
Operators
Less or Equal
<=
Operators
>=
Rounding
Round
round(x)
Rounding
Round
round(x, p)
Rounding
Floor
floor(x)
Miscellaneous
73
Datgel
DCT-UG-001 - 3.11- September 2014
Type
Description
Function Name
Rounding
Ceiling
ceil(x)
Statistical
Average
avg(x1,x2,x3,...)
Statistical
Minimum
min(x1,x2,x3,...)
Statistical
Maximum
max(x1,x2,x3,...)
Trigonometric
sin(x)
Trigonometric
cos(x)
Trigonometric
tan(x)
Trigonometric
asin(x)
Trigonometric
acos(x)
Trigonometric
atan(x)
Trigonometric
atan2(y, x)
Trigonometric
sinh(x)
Trigonometric
cosh(x)
Trigonometric
tanh(x)
Trigonometric
asinh(x)
Trigonometric
acosh(x)
Trigonometric
atanh(x)
5.4.2
Special Functions
Functions that require explanation in greater detail are listed in this section.
5.4.2.1
LookupWithUnit
The LookupWithUnit 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 LookupWithUnit function is only available in the Formula Tool.
"<<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
74
Datgel
DCT-UG-001 - 3.11- September 2014
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 LookupWithUnit 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 LookupWithUnit function.
LookupWithUnit(
"<<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
)
5.4.2.2
LookupIntervalRangeWithUnit
The Lookup Interval Range With Unit function returns the 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 LookupIntervalRangeWithUnit function is only available in the Formula Tool.
"<<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
"<<Return Unit>>" Unit the returned value must be in. If the Return Unit does not match the
unit of the <<Lookup Table.Field>>, then it will be converted to the Return Unit.
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 LookupIntervalRangeWithUnit function cannot be evaluated via the Validate button or in Validation
Reports from the Formula Tool Configuration Form.
The LookupIntervalRangeWithUnit 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.
CPT Tool gINT Add-In 3.1
User Guide
75
Datgel
DCT-UG-001 - 3.11- September 2014
5.4.2.3
FixedIntervalAverage
The Fixed Interval Average function returns an arithmetic mean of values where the current interval
value lies between the Top and Bottom boundaries.
The FixedIntervalAverage function is only available in the Formula Tool.
"<<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 values to average. 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>>" The table field reference for the values to average.
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 Values to Average table field references must refer to fields from the same table.
The FixedIntervalAverage 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 Fixed Interval Average function that calculates the arithmetic mean of
the Effective Stress value (in kPa) from the Effective_Stress field in the CPT_DATA_FOUNDATION table,
where the current CPT_DATA depth lies between the top (=1 m) and bottom (= 2 m) depths.
FixedIntervalAverage(
"<<CPT_DATA.Depth>>"
,
"<<CPT_DATA_FOUNDATION.Effective_Stress>>"
,
1
,
2
CPT Tool gINT Add-In 3.1
User Guide
76
Datgel
DCT-UG-001 - 3.11- September 2014
,
"m"
,
"kPa"
)
5.4.2.4
MaxMinValueOutOfRange
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.
"<<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
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.
5.4.2.5
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.
77
Datgel
DCT-UG-001 - 3.11- September 2014
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:
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 values are taken from 0.5 m from the
given depth.
5.4.2.6
MovingAverageConstrainedLCPC
MovingAverageConstrainedLCPC(
"<<Current Interval Table.Field>>",
Current Interval Required Unit,
"<<Values to Average Table.Field>>",
Values to Average Required Unit,
DistanceLesserDepth,
DistanceGreaterDepth,
ConstrainingMinimumFactor,
ConstrainingMaximumfactor)
CPT Tool gINT Add-In 3.1
User Guide
78
Datgel
DCT-UG-001 - 3.11- September 2014
The Moving Average Constrained LCPC function calculates a type of moving average known as the
LCPC method as specified in the paper written by Bustamante and Gianeselli (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
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.
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:
79
Datgel
DCT-UG-001 - 3.11- September 2014
5.4.2.7
NextValue
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.
80
Datgel
DCT-UG-001 - 3.11- September 2014
"<<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.
5.4.2.8
PreviousValue
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.
5.4.2.9
SteppedAverage
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>>.
CPT Tool gINT Add-In 3.1
User Guide
81
Datgel
DCT-UG-001 - 3.11- September 2014
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.
5.4.2.10
SteppedExtrapolation
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.
82
Datgel
DCT-UG-001 - 3.11- September 2014
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:
83
Datgel
DCT-UG-001 - 3.11- September 2014
5.4.2.11
TableIntervalAverage
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.
"<<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:
84
Datgel
DCT-UG-001 - 3.11- September 2014
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.
5.4.2.12
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.
Boundary Value is 27
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:
85
Datgel
DCT-UG-001 - 3.11- September 2014
"<<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
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.
5.5
Unit Conversion
5.5.1
Introduction
The unit conversion feature of the CPT Tool allows you 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.
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.
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.
Section 8.6 - How to change a field unit and make it work with reports
5.5.2
The unit of a field in the project database is determined by the value in the Units field property.
86
Datgel
DCT-UG-001 - 3.11- September 2014
5.5.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.
5.5.3.1
DG_COM_UNIT_CONVERSION
All units, conversion factors and equations are listed in this table.
Column Name
Description
Source_Unit
Unit to be converted to base SI unit. The unit must exist in the gINT Field
Units Library table.
87
Datgel
DCT-UG-001 - 3.11- September 2014
Column Name
Description
Formatted_Source_Unit
Source_To_SI_Conversion_Factor
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.
Source_To_SI_Conversion_Equation
SI_Unit
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.
5.5.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
Description
Table Name
Table Name
Field Name
Field Name
88
Datgel
DCT-UG-001 - 3.11- September 2014
Column Name
Description
Location
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.
English
SI
<<Unit System>>
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.
English_FR_Minimum
SI_FR_Minimum
<<Unit System>>_FR_Minimum
English_FR_Maximum
SI_FR_Maximum
<<Unit System>>_FR_Maximum
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
89
Datgel
DCT-UG-001 - 3.11- September 2014
5.5.3.3
DG_CPT_SYMBOLOGY_SCALES_UNITS
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
Description
Unit System
Unit System
Parameter
Parameter name
Unit
5.5.4
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.
90
Datgel
DCT-UG-001 - 3.11- September 2014
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.
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.
91
Datgel
DCT-UG-001 - 3.11- September 2014
Analysis
This section contains information about predefined parameter and correlation calculations, and analysis
related features included in the CPT Tool.
Analysis can be performed using published interpretation methods, or other methods that you define.
6.1
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
AGS RTA
Field Name
Caption
Symbol
Unit
Description
Penetration_Rate
Bulk_Unit_Weight
STCT_BUW
In_Situ_Pore_Pressure
STCT_PWPI
In Situ u
Excess_Pore_Pressur
e
STCT_PWPE
Delta u
Normalised_Excess_P
ore_Pressure
Normalised Delta
u
Normalis
ed
Total_Stress
STCT_TOTS
Total Stress
Effective_Stress
STCT_EFFS
Effective Stress
Total_Cone_Resistanc
e
STCT_QT
qt
Total_Cone_Resistanc
e_Moving_Average
Moving Average
qt
Total_Cone_Resistanc
e_Moving_Average_In
c
Moving Average
qt Included
Net_Cone_Resistance
STCT_QNET
qn
Corrected_Sleeve_Fric
tion
STCT_FT
ft
Friction_Ratio
STCT_FRR
Rf
(2 3 )
Friction ratio,
= 100,
100, or
100
92
Datgel
DCT-UG-001 - 3.11- September 2014
AGS RTA
Field Name
Caption
Normalised_Friction_R
atio
STCT_FR
Fr
Symbol
Unit
Description
Normalised friction ratio,
=
( )
STCT_QNOR
Qt
( )
Stress_Normal
ised_Cone_Re
sistance
qt1
2001), 1 =
Pore_Pressure_Ratio
STCT_BQ
Bq
Differential_Pore_Pres
sure_Ratio
STCT_DPPR
DPPR
Dimensionless_Penetr
ation_Resistance
6.1.1
Qt(1-Bq)+1
(1 )+1 -
Dimensionless penetration
resistance
In case of using a mechanical cone, the corrected values for and are calculated from input data
cone readings 1 and 2 as:
= 1
+ 1 + 2
Or if one of 1 , , , 1 2 is NULL: = 1
= (2 1 )
Where:
1 is the mechanical cone reading 1 and is taken from Mechanical_Reading_1 field
2 is the mechanical cone reading 2 and is taken from Mechanical_Reading_2 field
is the area of plunger and is taken from Area_Plunger field on CPT_CONE_INFORMATION
is the projected area of the cone and is taken from Area_Cone field on CPT_CONE_INFORMATION
1 is the mass of cone and is taken from Mass_Cone field on CPT_CONE_INFORMATION
93
Datgel
DCT-UG-001 - 3.11- September 2014
2 is the mass of one inner rod and is taken from Mass_Inner_Rod field on
CPT_CONE_INFORMATION
is the number of rods used, calculated from dividing Depth by Length_Inner_Rod on
CPT_CONE_INFORMATION, rounded up to nearest whole number plus one if the top of the rod is at
the ground surface
is the area of sleeve and is taken from Area_Friction_Casing field on CPT_CONE_INFORMATION
The Cumulative Sum of the Sleeve Friction Resistance aka Total Sleeve Friction Resistance (TF) is
calculated by the Formula Tool and written to CPT_DATA.Cumulative_Sleeve_Friction_Resistance.
6.1.2
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
6.2
Seven 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.
CPT_POINT_PARAMTERS.Project_Soil_Class_Method_#
2.
CPT_POINT_PARAMTERS.Soil_Class_Method_#
3.
CPT_PROJECT_PARAMTERS.Project_Soil_Class _Method_#
4.
CPT_PROJECT_PARAMTERS.Soil_Class_Method_#
6.2.1
Preconfigured in Library
The CPT Tool is supplied with nine material type interpretation methods:
Begemann 1965
Ramsey 2002
Robertson 1990
Schmertmann 1978
Additional methods may be defined by users in the DG_CPT* library tables. See section 6.2.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.
CPT Tool gINT Add-In 3.1
User Guide
94
Datgel
DCT-UG-001 - 3.11- September 2014
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
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.
6.2.2
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.
95
Datgel
DCT-UG-001 - 3.11- September 2014
2.
DG_CPT_SOIL_CLASS_METHOD
3.
Graph 2 is optional
4.
DG_CPT_SOIL_CLASS_ZONES
5.
DG_CPT_SOIL_CLASS_DATA
96
Datgel
DCT-UG-001 - 3.11- September 2014
6.
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.
7.
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.
8.
Now open the report properties and make the following changes
Property
New Value
General Tab
Description
Soil behaviour type classification graph - GEO, total cone resistance (qt) versus
friction ratio (Rf)
Report Variable
Soil Class Method
<<Let(A="GEO")>><<Get(A)>>
Report Variable
Graph Number
<<Calc(1)>>
Report Variable
Default Title
Report Variable Y
Axis Unit
Conversion Factor
<<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>>
Dependent Tab
Data Expression 1
Minimum Value
Maximum Value
97
Datgel
DCT-UG-001 - 3.11- September 2014
Property
New Value
<<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]_
)>>
Number of Points
10
Line Type
Solid
Line Thickness
0.2
Line Colour
Light Blue
When you update the User Report Variable in the GENERAL tab, ensure that you entered
correct Soil Class Method name (e.g. GEO). This will make sure all the user system data are
referring to the right method.
The unit conversion feature will (section 22 Unit Conversion), has been applied to expressions
Data Expression, Minimum Value and Maximum Value.
9.
6.2.3
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
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
type field, and it needs data that will order correctly as text, hence enter numbers padded with a zero
e.g. 01.
98
Datgel
DCT-UG-001 - 3.11- September 2014
6.3
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.
CPT_POINT_MATERIAL_PROPERTIES
2.
CPT_POINT_PARAMETERS or CPT_POINT_CORRELATION_PARAMETERS
3.
CPT_PROJECT_CORRELATION_PARAMETERS or CPT_PROJECT_PARAMETERS
6.3.1
6.3.1.1
( )
( )
Otherwise,
99
Datgel
DCT-UG-001 - 3.11- September 2014
Description
Undrained_Shear_Strength_1_Nk_qc_BP
Undrained_Shear_Strength_1_Nk_qc_LT_BP
Undrained_Shear_Strength_1_Nk_qc_GTE_BP
Undrained_Shear_Strength_1_Nkt_qt_BP
Undrained_Shear_Strength_1_Nkt_qt_LT_BP
Undrained_Shear_Strength_1_Nkt_qt_GTE_BP
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.
6.3.1.2
6.3.1.3
(q t )
Nkt
(q c )
Nk
Otherwise,
Where:
is stored in the Undrained_Shear_Strength_2_Nkt field.
is stored in the Undrained_Shear_Strength_2_Nk field.
CPT Tool gINT Add-In 3.1
User Guide
100
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.1.4
6.3.1.5
6.3.1.6
6.3.1.7
101
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.1.8
6.3.1.9
u
Nu
6.3.1.10
6.3.2
6.3.2.1
Relative Density 1
1
(
) 100
2
0 ( ) 1
Baldi et al. (1986) and Al-Homoud and Wehr (2006), CPT in Geotechnical Practice p 83
Where:
and are in kPa
0 is stored in the Relative_Density_1_C0 field. Published value for normally consolidated 157,
over consolidated 181
1 is stored in the Relative_Density_1_C1 field. Published value is 0.55
2 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.
102
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.2.2
6.3.2.3
Relative Density 2
6.3.2.4
6.3.2.5
Relative Density 3
1 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.
103
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.2.6
6.3.3
6.3.3.1
0
=
( )
( ) 1.7
0
=
100%
0
is calculated using = 1, if > , then its been accepted, otherwise its calculated using =
0.5. If < then its accepted, otherwise its calculated using = 0.7.
Robertson and Wride (1998)
Where:
1 is 3.47 in the published formula, and is stored in the Soil_Behaviour_Type_Index_1_C1 field.
2 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.
6.3.3.2
104
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.3.3
( )
2
= ((1 (
)) + (( ) + 2 ) )
6.3.3.4
6.3.4
6.3.4.1
1 (1 )
2
105
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
1 is 8.5 in the published formula, and is stored in the SPT_N60_1_C1 field.
2 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.
The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and
CPT_PROJECT_CORRELATION_PARAMETERS tables.
6.3.4.2
1 (1
)
2
6.3.5
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.
6.3.6
6.3.6.1
106
Datgel
DCT-UG-001 - 3.11- September 2014
is in kPa
1 is 118.8 in the published formula, and is stored in the Shear_Wave_Velocity_1_C1 field.
2 is 18.5 in the published formula, and is stored in the Shear_Wave_Velocity_1_C2 field.
The constants are stored on CPT_POINT_CORRELATION_PARAMETERS and
CPT_PROJECT_CORRELATION_PARAMETERS tables.
6.3.6.2
= (1 ( ) 2
)3
( 100)
6.3.6.3
107
Datgel
DCT-UG-001 - 3.11- September 2014
This correlation of is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Fine or
Mixed for that row.
6.3.6.4
6.3.7
Unit Weight
6.3.7.1
6.3.7.2
108
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.7.3
6.3.8
6.3.8.1
0 = 1 (
)
0
109
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
, 0 and 0 are in kPa
1 is 1634 in the published formula, and is stored in the Small_Strain_Shear_Modulus_1_C1 field
2 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 0 is calculated only when the Soil_Type_1 field value on the CPT_DATA table is Coarse
or Mixed for that row.
6.3.8.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 0 is applicable to all soil types.
6.3.9
Youngs Modulus
6.3.9.1
Youngs Modulus 1
6.3.9.2
Youngs Modulus 2
110
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
is calculated from degree of loading, , effective stress and reduction factor as given in the
following plot.
6.3.10
Constrained Modulus
6.3.10.1
Constrained Modulus 1
111
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.10.2
Constrained Modulus 2
6.3.11
6.3.12
Compression Index
2.3(1 + )
6.3.13
6.3.13.1
112
Datgel
DCT-UG-001 - 3.11- September 2014
= 1 ( )
Mayne (1995), Demers and Leroueil (2002), NCHRP Synthesis 368 p 34
Where:
1 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:
=
6.3.13.2
6.3.13.3
113
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.13.4
= 1 2
Robertson (2009), Guide to CPT p 31
Where:
1 is 0.25 in the published formula, and is stored in the Preconsolidation_Stress_4_C1 field
2 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:
=
6.3.13.5
1
)
4
114
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.13.6
6.3.14
Angle of Friction
6.3.14.1
Angle of Friction 1
115
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.14.2
Angle of Friction 2
= 1 (1 + 2 ( ))
0
6.3.14.3
Angle of Friction 3
6.3.15
Effective Cohesion
6.3.15.1
Effective Cohesion 1
116
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.16
Sensitivity
6.3.16.1
Sensitivity 1
6.3.16.2
Sensitivity 2
1 ( )
6.3.17
6.3.17.1
Coefficient of Lateral Earth Pressure 1 (0 ) for uncemented sands and well behaved clays in
Coefficient_Lateral_Earth_Pressure_1 is defined as:
0 = (1 )
0 = =
(1 + )
(1 )
117
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.17.2
2 3
) (
) 4
6.3.17.3
6.3.18
Rigidity Index
6.3.18.1
Rigidity Index 1
Rigidity index 1 ( ) for fine material is recorded in the Rigidity_Index_1 is defined as:
1
= [( + 2 ) (
) 3 ]
2
Mayne (2001), NCHRP Synthesis 368 p 46
Where:
118
Datgel
DCT-UG-001 - 3.11- September 2014
6
3
for the calculation of the Cam clay constant is taken from the Friction_Angle_1 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.
6.3.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:
=
[1 (2 )]
[1 + {1 + 3 ( 1)4 }]5
119
Datgel
DCT-UG-001 - 3.11- September 2014
6.3.19
Hydraulic Conductivity
6.3.19.1
Hydraulic Conductivity 1
3x10-9 to 3x10-8
Organic soils
1x10-8 to 1x10-6
Clay
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
Sand
1x10-4 to 1x10-3
10
1x10-3 to 1
11
1x10-8 to 1x10-6
12
3x10-7 to 3x10-4
6.3.19.2
Hydraulic Conductivity 2
3x10-9 to 3x10-8
Organic soils
1x10-8 to 1x10-6
Clay
1x10-10 to 1x10-9
Silt mixtures
3x10-9 to 1x10-7
Sand mixtures
1x10-7 to 1x10-5
Sands
1x10-5 to 1x10-3
1x10-3 to 1
1x10-8 to 1x10-6
1x10-8 to 1x10-6
120
Datgel
DCT-UG-001 - 3.11- September 2014
6.4
Liquefaction Assessment
6.4.1
0
( )
( ) 1.7
0
=
100%
0
The stress exponent in Stress_Exponent calculated from , so iterations are done to find the final value.
6.4.2
Stress Exponent
Stress exponent is calculated from either method by Robertson (2009) or NCEER 2001 method
based on the method selected on point/parameters table:
Robertson (2009):
= 0.381 + 0.05
0
0.15 1
6.4.3
Layer Thickness
The adjacent layers with similar value compared to reference value ( < : fine
grained, < : Coarse grained) are grouped to either fine or coarse layer and the thickness of
the overall layer is calculated.
6.4.4
Thin layer correction factor is calculated for thin stiff layers lying within softer strata based on lower
bound of the field curve suggested by NCEER 2001:
2
= 0.25 (
1.77) + 1
17
The soft and stiff layers are recognised based on the value compared to reference value .
1000 , and is calculated and stored in Transitional_Layer_Thickness on
CPT_DATA_LIQUEFACTION
CPT Tool gINT Add-In 3.1
User Guide
121
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.5
6.4.6
State Parameter
6.4.6.1
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:
(
=
6.4.6.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:
CPT Tool gINT Add-In 3.1
User Guide
122
Datgel
DCT-UG-001 - 3.11- September 2014
3
= (
)
1 + 20
1.45
6.4.6.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:
0.5
= 100 ( )
0
0
is effective vertical overburden stress in Effective_Stress on CPT_DATA Table
6.4.6.4
State parameter 4
The state parameter 4, Y4, in State_Parameter_4 is defined based on the method by Plewes (1992) as:
(1 )
)
123
Datgel
DCT-UG-001 - 3.11- September 2014
= (3 +
0.85
)
= 11.9 13.3
=
10
6.4.6.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:
(1 )
)
0.85
)
= 11.9 13.3
=
1
34 10
124
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.7
Correlations calculated values may be overridden by a user defined profile defined in Fines_Content on
CPT_POINT_MATERIAL_PROPERTIES.
6.4.7.1
Fines Content 1
Fines content 1, in Fines_Content_1 is based on the method by Robertson and Wride 1998:
< 1.26 = 0
1.26 3.5 (%) = 1.75 3.25 3.7
3.5 < = 100%
is soil behaviour type index 1, NCEER, and is stored in the Soil_Behaviour_Type_Index_1_NCEER
on CPT_DATA_LIQUEFACTION.
6.4.7.2
Fines Content 2
6.4.8
Unit Weight may be defined in two locations and are used in the order listed:
1.
2.
6.4.9
In-Situ Pore Pressure may be defined in two methods and are used in the order listed:
1.
2.
The in-situ pore pressure for earthquake is calculated based on the position of design
groundwater table for earthquake from CPT_LIQ_PROJECT_PARAMETERS or
CPT_LIQ_POINT_PARAMETERS.
6.4.10
The total stress for earthquake is calculated using bulk unit weight (earthquake). In case of a fill
existence, the weight of the fill has been considered in calculation of the total stress. The total stress
(earthquake) is used for calculation of cyclic stress ratio.
125
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.11
The effective stress for earthquake is calculated from total stress (earthquake) and pore pressure
(earthquake). The effective stress (earthquake) is used for calculation of cyclic stress ratio.
6.4.12
6.4.12.1
Cyclic stress ratio 1, in Cyclic_Stress_Ratio_1 is defined based on the relation proposed by Seed and Idriss
(1971) as:
0
= ( ) = 0.65 ( )
0
0
NCEER 2001, p818
Where:
is peak horizontal acceleration at the ground surface generated by earthquake, and is
stored in Peak_Ground_Acceleration
0 is total vertical overburden stress in Total_Stress on CPT_DATA_LIQUEFACTION
0
is effective vertical overburden stress calculated from design groundwater depth for
earthquake, bulk and saturated unit weights, and stored in Effective_Stress on
CPT_DATA_LIQUEFACTION Table
is the stress reduction coefficient. T. F. Blake (1996) approximated the mean values of as:
=
6.4.12.2
Cyclic stress ratio method 2, in Cyclic_Stress_Ratio_2 is defined based on the relation proposed by Idriss
and Boulanger (2008) as:
0
= ( ) = 0.65 ( )
0
0
= ( + )
= 1.012 1.126 (
= 0.106 + 0.118 (
+ 5.133)
11.73
+ 5.142)
11.28
126
Datgel
DCT-UG-001 - 3.11- September 2014
0
is effective vertical overburden stress calculated from design groundwater depth for
earthquake, bulk and saturated unit weights, and stored in Effective_Stress on
CPT_DATA_LIQUEFACTION Table
6.4.12.3
Cyclic stress ratio method 3 is calculated from normalised shear wave velocity as
0
= 0.65 ( )
0
1+
=
1+
=
< 20
20
Moss et al (2013)
6.4.12.4
Cyclic stress ratio method 4 is calculated from normalised shear wave velocity as
0
= 0.65 ( )
0
1+
=
1+
,12
is the average shear wave velocity in the upper 12.2m (40 ft) of the soil column
6.4.13
6.4.13.1
Overburden correction factor 1 is calculated from method by Robertson and Wride (1998)/NCEER
(2001) as:
= ( )
0
1.7
127
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.13.2
Overburden correction factor 2 is calculated from method by Idriss and Boulanger (2008) as:
1.3380.2491 0.264
= ( )
0
1.7
21 1 254
Four iterations are carried out. The first iteration assumes = ( ) and m is taken as 0.5.
0
6.4.13.3
Overburden correction factor 3 is calculated from method by Moss et al. (2006) as:
= ( ) 1.7
0
2
= 1 ( )
3
1 = 0.78 0.33
2 = 0.32 0.35 0.49
3 = ((10 + ))1.21
is normalised tip resistance 1 = . Three iterations are carried out.
6.4.13.4
Overburden correction factor 4 is calculated from method by Kayen et al. (2013) as:
0.25
=( )
0
1.5
6.4.14
6.4.14.1
1 is calculated as:
1 =
6.4.14.2
128
Datgel
DCT-UG-001 - 3.11- September 2014
Four Iterations has been carried out between 1 and to find final solution.
Soil liquefaction during earthquakes, p. 85, 88
6.4.14.3
1 is calculated as:
1 =
Moss et al. (2006)
6.4.15
Normalised shear wave velocity method 1 is calculated from shear wave velocity as
1 =
Kayen et al. (2013), p. 411
is referenced from CPT_DATA.Shear_Wave_Velocity_Extrapolated
6.4.16
6.4.16.1
The clean-sand equivalent normalised cone resistance 1, in qc1N_cs_1 is calculated by the following
equation:
(1 ) = 1
Robertson and Wride (1998), NCEER 2001 pp. 822-823
Where,
For 1.64
= 1.0
6.4.16.2
The clean-sand equivalent normalised cone resistance 2, in qc1N_cs_2 based on method by Idriss and
Boulanger (2008) is defined as:
(1 ) = 1 + 1
1 = (5.4 +
2
1
9.7
15.7
(
) )
) . (1.63 +
16
+ 0.01
+ 0.01
129
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.16.3
6.4.16.4
The clean-sand equivalent normalised cone resistance 4, in qc1N_cs_4, based on method by Idriss and
Boulanger (2008), using the corrections recommended by Seed 1987, is defined as:
(1 ) = 1 + 1
The Corrections due to fines content are as per below table:
FC
qc1N_cs
10
10
25
25
50
45
75
55
6.4.17
Modified normalised CPT tip resistance for the frictoinal effects of apparent fines, (method by Moss et
al., 2006),
1 = 1 +
= (0.38 0.19) ln() + 1.46 0.73
0.5 (%) 5.0
6.4.18
6.4.18.1
The clean-sand based cyclic resistance ratio method 1, in Cyclic_Resistance_Ratio_1 method by Robertson
and Wride (1998), for sand-like behaviour ( ) for standard earthquake of magnitude 7.5 is
calculated by:
(1 ) < 50:
7.5 = 0.833
(1 )
+ 0.05
1000
3
(1 )
50 (1 ) 160: 7.5 = 0.833 (
) + 0.08
100
= 0.18 0.8
130
>
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.18.2
Cyclic resistance ratio 2, in Cyclic_Resistance_Ratio_2 for standard earthquake of magnitude 7.5, is based
on critical state approach for sand-like behaviour ( ) and calculated from:
=
= 0.18 0.8
>
Jefferies & Been 2006, Soil liquefaction, a critical state approach, p 395
Idriss & Boulanger 2008, Soil liquefaction during earthquakes, pp. 199
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
is soil behaviour type index 1, NCEER, and is stored in the Soil_Behaviour_Type_Index_1_NCEER
on CPT_DATA_LIQUEFACTION.
is soil behaviour type index break point that separates sand-like behaviour from clay-like
behaviour, and is stored in the Ic_Break_Point on CPT_LIQ_PROJECT_PARAMETERS and/or
CPT_LIQ_POINT_PARAMETERS.
6.4.18.3
The cyclic resistance ratio method 3, in Cyclic_Resistance_Ratio_3 for standard earthquake of magnitude
7.5 is calculated by:
2
(1 )
(1 )
(1 )
(1 )
= (
+(
) (
) +(
) 3) 1000
540
67
80
114
= 0.18 0.8
>
Idriss & Boulanger 2008, Soil liquefaction during earthquakes, pp. 95, 100 and 199
131
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
(1 ) is the clean-sand equivalent normalised cone resistance 2 and is stored in qc1N_cs_2 on
CPT_DATA_LIQUEFACTION.
is taken from Overconsolidation_Ratio_1 or Overconsolidation_Ratio_5
is soil behaviour type index 1, NCEER, and is stored in the Soil_Behaviour_Type_Index_1_NCEER
on CPT_DATA_LIQUEFACTION.
is soil behaviour type index break point that separates sand-like behaviour from clay-like
behaviour, and is stored in the Ic_Break_Point on CPT_LIQ_PROJECT_PARAMETERS and/or
CPT_LIQ_POINT_PARAMETERS.
6.4.18.4
The cyclic resistance ratio method 4 in Cyclic_Resistance_Ratio_4 is similar to cyclic resistance ratio
method 3 with (1 ) from qc1N_cs_3 on CPT_DATA_LIQUEFACTION.
6.4.18.5
Cyclic resistance ratio method 5 is calculated from normalised shear wave velocity as
)
11.045 + 1 (0.110 ) + 0.001 + (1 + 0.85 ) 8.48 ( ) 0.002 (0
20.923 1.632 1 ( )
= (
)
7.177
6.4.18.6
Cyclic resistance ratio method 6 is calculated from normalised shear wave velocity as
)
(0.0073 1 )2.8011 2.6168 ( ) 0.0099 (0
+ 0.0028 0.4809 1( )
= (
)
1.946
132
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.19
6.4.19.1
Factor of Safety 1
The factor of safety method 1, in Factor_of_Safety_1 for depths greater than design ground water depth is
defined as:
For sand like behaviour ( )
= (
)
0
= ( )
102.24
M 2.56
= (
)
= 1.12 (
) + 0.828 1.13
4
0
is the effective vertical overburden stress in Effective_Stress on CPT_DATA
6.4.19.2
Factor of Safety 2
The factor of safety method 2, in Factor_of_Safety_2 for depths greater than design ground water depth is
defined as:
For sand like behaviour ( )
133
Datgel
DCT-UG-001 - 3.11- September 2014
= (
)
0
= ( )
102.24
M 2.56
= (
)
= 1.12 (
) + 0.828 1.13
4
0
is the effective vertical overburden stress in Effective_Stress on CPT_DATA
6.4.19.3
Factor of Safety 3
= (
)
= 6.9 (
) 0.058 1.8
4
0
= 1 ( ) 1.1
134
Datgel
DCT-UG-001 - 3.11- September 2014
1
0.264 0.3 1 211
37.3 8.271
= (
)
= 1.12 (
) + 0.828 1.13
4
0
is effective vertical overburden stress in Effective_Stress on CPT_DATA
For thin fine/coarse layers, layers with thickness less than Minimum_Layer_Thickness on CPT_Liq_ Point
_Parameters/CPT_Liq_ Project _Parameter table, the FOS of first upper thick layer is used.
6.4.19.4
Factor of Safety 4
The factor of safety method 4, in Factor_of_Safety_4 is similar to factor of safety method 3 with CRR from
Cyclic_Resistance_Ratio_4. 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).
6.4.19.5
Factor of Safety 5
= 17.84 1.43
Moss et al. (2006)
For thin fine/coarse layers, layers with thickness less than Minimum_Layer_Thickness on CPT_Liq_ Point
_Parameters/CPT_Liq_ Project _Parameter table, the FOS of first upper thick layer is used.
6.4.19.6
Factor of Safety 6
Factor of safety method 6 is calculated from CRR 6 and CSR 4 based on shear wave velocity
assessment as
= (
CPT Tool gINT Add-In 3.1
User Guide
135
Datgel
DCT-UG-001 - 3.11- September 2014
= 15 1.342
Kayen et al. (2013), p. 414
For thin fine/coarse layers, layers with thickness less than Minimum_Layer_Thickness on CPT_Liq_ Point
_Parameters/CPT_Liq_ Project _Parameter table, the FOS of first upper thick layer is used.
6.4.20
6.4.20.1
Liquefaction potential index method 1 which predicts the potential of liquefaction to cause foundation
damage at a site is calculated from factor of safety 1 as:
20
()
= 1
=0
1
> 1
() = 10 0.5
Toprak and Holzer (2003).
6.4.20.2
6.4.21
6.4.21.1
=+
0
1.45
0
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
136
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.21.2
Residual shear strength 2 in Residual_Shear_Stregth_2, for negligible void redistribution effects, is defined
as:
1
1 2
1 3
1
=
+
9.82))
(
)
(
) 4.42) (1 + (
0
24.5
61.7
106
11.1
Soil liquefaction during earthquakes, p. 131
Where:
1 is the clean-sand equivalent normalised cone resistance 4, in qc1N_cs_4 on
CPT_DATA_LIQUEFACTION
0
is effective vertical overburden stress in Effective_Stress on CPT_DATA
6.4.21.3
Residual shear strength 3 in Residual_Shear_Stregth_3, for significant void redistribution effects, is defined
as:
1
1 2
1 3
(
) +(
) 4.42)
= (
0
24.5
61.7
106
Soil liquefaction during earthquakes, p. 132
Where:
1 is the clean-sand equivalent normalised cone resistance 4, in qc1N_cs_4 on
CPT_DATA_LIQUEFACTION
0
is effective vertical overburden stress in Effective_Stress on CPT_DATA
6.4.21.4
Residual shear strength 4 in Residual_Shear_Stregth_4, method by Olson and Stark (2002) is defined as:
= 0.03 + 0.01431
0
1 = =
= (
1 6.5
1.8
0.8 + 0
0.5
1.7
)
0
Where:
CPT Tool gINT Add-In 3.1
User Guide
137
Datgel
DCT-UG-001 - 3.11- September 2014
0
is effective vertical overburden stress in Effective_Stress on CPT_DATA
6.4.22
Relative Density, ( )
Relative density method by Tatsouka et al. (1990) to calculate maximum shear strain 2 is calculated as:
= 85 + 76 (1 )
1 200
6.4.23
6.4.23.1
Maximum shear strain method 1 in Maximum_Shear_Strain_1, is calculated based on the method by Idriss
and Boulanger (2008):
2 = 0
2 > >
1
= [ , 0.035(2 ) (
)]
6.4.23.2
Maximum shear strain method 2 in Maximum_Shear_Strain_2, is calculated based on the method by Zhang
et al. (2004):
= 90%,
= 3.26 1.80
= 90%,
= 80%,
= 3.22 2.08
= 80%,
= 70%,
CPT Tool gINT Add-In 3.1
User Guide
= 6.2
= 10
= 3.20 2.89
138
0.7 2.0
0.7
0.56 2.0
0.56
0.59 2.0
Datgel
DCT-UG-001 - 3.11- September 2014
= 70%,
0.59
= 3.58 4.42
= 60%,
= 60%,
= 22.7
0.66 2.0
0.66
= 4.22 6.39
= 50%,
= 50%,
= 40%,
= 40%,
= 14.5
= 34.1
0.72 2.0
0.72
= 3.31 7.97
1.0 2.0
= 250(1.0 ) + 3.5
= 40%,
= 51.2
0.81 1.0
0.81
6.4.24
Lateral displacement index (LDI), is calculated by integrating maximum shear strains versus depth,
6.4.25
6.4.25.1
Lateral Displacement 1
The lateral displacement 1, in Lateral_Displacement_1, method by Youd et al (2002), for gently sloping
ground conditions, is defined as,
= 16.213 + 1.532 1.406 0.012 + 0.338 + 0.540 15
+ 3.413 (100 15 ) 0.795 (5015 + 0.1 )
= + 0
0 = 100.895.64
Where:
is the earthquake magnitude (6 < < 8) and is stored in Earthquake_Magnitude
is the nearest horizontal or map distance from the site to the seismic energy source, in
kilometres, and is stored in Hor_Dist_To_Earthquake_Source
is the ground slope, in percent, (0.1 < (%) < 6) and is stored in Ground_Slope
15 is the cumulative thickness of saturated granular layers with corrected blow counts, (1 )60,
less than 15, (1 < 15 () < 15), and is stored in Cumulative_Thickness_SPTN_15
CPT Tool gINT Add-In 3.1
User Guide
139
Datgel
DCT-UG-001 - 3.11- September 2014
15 is the average fines content for granular materials included within 15 and is stored in
Average_Fines_Content_SPTN_15
5015 is the average mean grain size for granular materials within 15 and is stored in
Average_Mean_Grain_Size
6.4.25.2
Lateral Displacement 2
The lateral displacement 2, in Lateral_Displacement_2, method by Youd et al (2002), for free face
conditions, is defined as,
= 16.713 + 1.532 1.406 0.012 + 0.592 + 0.540 15
+ 3.413 (100 15 ) 0.795 (5015 + 0.1 )
= + 0
0 = 100.895.64
Where:
is the earthquake magnitude (6 < < 8) and is stored in Earthquake_Magnitude
is the nearest horizontal or map distance from the site to the seismic energy source, in
kilometres, and is stored in Hor_Dist_To_Earthquake_Source
is the free-face ratio defined as the height of the free face devided by the distance (1 <
(%) < 20) and is stored in Free_Face_Ratio
15 is the cumulative thickness of saturated granular layers with corrected blow counts, (1 )60,
less than 15, (1 < 15 () < 15) and is stored in Cumulative_Thickness_SPTN_15
15 is the average fines content for granular materials included within 15 and is stored in
Average_Fines_Content_SPTN_15
5015 is the average mean grain size for granular materials within 15 and is stored in
Average_Mean_Grain_Size
6.4.25.3
Lateral Displacement 3
The lateral displacement 3, in Lateral_Displacement_3, method by Zhang et al (2004), for gently sloping
ground conditions, is defined as,
= ( + 0.2)
Where:
is ground slope in Ground_Slope on CPT_LIQ_PROJECT_PARAMETERS or
CPT_LIQ_POINT_PARAMETERS
6.4.25.4
Lateral Displacement 4
The lateral displacement 4, in Lateral_Displacement_4, method by Zhang et al (2004), for free face
conditions, is defined as,
= 6 0.8 2.5% < < 25%
140
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
is the free-face ratio defined as the height of the free face devided by the distance and is
stored in Free_Face_Ratio on CPT_LIQ_PROJECT_PARAMETERS or CPT_LIQ_POINT_PARAMETERS
6.4.26
6.4.26.1
with 1 21
141
Datgel
DCT-UG-001 - 3.11- September 2014
1 1.2 ( 4)2.17
( )
(
)
20
15
0.45
0.45
= 215 ( )
15
= ( 4)2.17
1 1.2
15 = ( )
20
= 0.0389 ( ) + 0.124
0
1 + 20
=(
) 0
3
= 447 0 (1 )1/3
0
= 0.65
1
2
1 + ( )
0
0 = 95.76
447 0 (1 )1/3
0.6
= 6400 ( )
0
1 + 2
( 3 0 ) 0
1 + 0.0389 (
) + 0.124
1 + 20
( 3 ) 0
0
2
1 + ( )
0.65
0.6
1+20
)0
3
)
0
0 = 30.48
= 2
(
1 + 2
6400(
( 3 0 ) 0
1 + (0.0389 (
) + 0.124)
0
1+
1 +
142
Datgel
DCT-UG-001 - 3.11- September 2014
Where:
0 is the coefficient of lateral earth pressure, and is stored in Coefficient_Lateral_Earth_Pressure_1 on
CPT_DATA_LIQUEFACTION
1 is the clean-sand equivalent normalised cone resistance 2, in qc1N_cs_2 on
CPT_DATA_LIQUEFACTION
1 is the corrected SPT N value normalised to an effective overburden of 100 kPa and to an
effective energy of 60% of the free-fall energy, in SPT_N60_1 on CPT_DATA
6.4.26.2
Post liquefaction volumetric strain 2, in Post_Liq_Volumetric_Strain_2, for saturated sands method by Zhang
et al. (2002), is calculated as,
0.5,
= 1021 0.82
33 1 200
= 0.6,
= 1021 0.82
33 1 147
= 0.6,
= 0.7,
= 0.7,
= 0.8,
= 0.8,
= 0.9,
= 0.9,
= 24111 1.45
= 1021 0.82
= 17011 1.42
= 1021 0.82
= 16901 1.46
= 1021 0.82
= 14301 1.48
147 1 200
33 1 110
110 1 200
33 1 80
80 1 200
33 1 60
60 1 200
= 1.0,
= 641 0.93
33 1 200
= 1.1,
= 111 0.65
33 1 200
= 1.2,
= 9.71 0.69
33 1 200
= 1.3,
= 7.61 0.71
33 1 200
= 2.0,
= 0
33 1 200
143
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.26.3
To comply with the requirements of NZ DBH (Department of Building and Housing) the post liquefaction
volumetric strain 3, in Post_Liq_Volumetric_Strain_3, for saturated sands is calculated using the method by
Zhang et al. (2002) with factor of safety from Factor_of_Safety_4.
6.4.27
6.4.27.1
1 =
Where:
is the post liquefaction volumetric strain 1, and is stored in Post_Liq_Volumetric_Strain_1 on
CPT_DATA_LIQUEFACTION
6.4.27.2
2 =
Where:
is the post liquefaction volumetric strain 2, and is stored in Post_Liq_Volumetric_Strain_2 on
CPT_DATA_LIQUEFACTION
6.4.27.3
6.4.28
6.4.28.1
144
Datgel
DCT-UG-001 - 3.11- September 2014
6.4.28.2
6.5
Foundation Correlations
6.5.1
6.5.1.1
Soil Description
(MPa)
<1
1 to 5
>5
Soft chalk
5 to 12
>5
> 12
6.5.1.2
145
Datgel
DCT-UG-001 - 3.11- September 2014
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.
Factor
(MPa)
Group I
Group II
<1
0.4
0.5
1 to 5
0.35
0.45
0.4
0.5
>5
0.45
0.55
Soft chalk
0.2
0.3
5 to 12
0.4
0.5
>5
0.2
0.4
> 12
0.3
0.4
Nature of soil
Soft clay and mud
Moderately compact clay
Group I: plain bored piles, mud bored piles, micro piles (grouted under low pressure), cased
bored piles, hollow auger bored piles, piers, barrettes.
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.
6.5.1.3
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 and maximum limit of are given in the following table (CPT in geotechnical practice,
table 6.5).
Coefficient
Nature of soil
(MPa)
II
II
III
<1
30
90
90
30
0.015
0.015
0.015
0.015
0.035
1 to 5
40
80
40
80
0.035
(0.08)
0.035
(0.08)
0.035
(0.08)
0.035
0.08
0.12
60
150
60
120
0.035
0.035
0.035
0.035
0.08
>5
60
120
60
120
0.035
(0.08)
0.035
(0.08)
0.035
(0.08)
0.035
0.08
0.20
Soft chalk
100
120
100
120
0.035
0.035
0.035
0.035
0.08
146
Datgel
DCT-UG-001 - 3.11- September 2014
5 to 12
100
200
100
200
0.08
(0.12)
0.035
(0.08)
0.08
(0.12)
0.08
0.12
0.20
Weathered to fragmented
chalk
>5
60
80
60
80
0.12
(0.15)
0.08
(0.12)
0.12
(0.15)
0.12
0.15
0.20
> 12
150
300
150
200
0.12
(0.15)
0.08
(0.12)
0.12
(0.15)
0.12
0.15
0.20
Note: maximum limit unit skin friction, : bracket values apply to careful execution and minimum
disturbance of soil due to construction.
Category
IA: plain bored piles, mud bored piles, hollow auger bored piles, micro piles (grouted under low
pressure), cast screwed piles, piers, barretes.
IB: cased bored piles, driven cast piles (concrete or metal shaft).
IIA: driven precast piles, prestress tubular piles, jacket concrete piles. IIB: driven metal piles,
jacked metal piles
IIIB: high pressure grouted piles of large diameter >250mm, micropiles (grouted under high
pressure).
6.5.1.4
6.5.1.5
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
6.5.1.6
The ultimate pile axial capacity, , in Pile_Axial_Capacity_Ultimate_1 consists of two components: side
friction capacity, , and end bearing capacity, , as:
= +
CPT in geotechnical practice, pp. 152-154
6.5.1.7
147
Datgel
DCT-UG-001 - 3.11- September 2014
Where
is read from Pile_End_Bearing_Factor_of_Safety in foundation project parameters table. Default
value for factor of safety is 3.
CPT in geotechnical practice, p. 155
6.5.1.8
6.5.1.9
= +
6.5.1.10
6.5.2
Bulk Unit Weight may be defined in two locations and are used in the order listed:
1.
2.
6.5.3
In-Situ Pore Pressure may be defined in two methods and are used in the order listed:
CPT Tool gINT Add-In 3.1
User Guide
148
Datgel
DCT-UG-001 - 3.11- September 2014
1.
2.
The in-situ pore pressure for foundation is calculated based on the position of design
groundwater table for foundation from CPT_FOUNDATION_PROJECT_PARAMETERS or CPT_
FOUNDATION _POINT_PARAMETERS.
6.5.4
The total stress for foundation is calculated using bulk unit weight (foundation). The total stress
(foundation) is used for shallow foundation settlement.
6.5.5
The effective stress for foundation is calculated from total stress (foundation) and pore pressure
(foundation). The effective stress (foundation) is used for calculation of shallow foundation settlement.
6.5.6
6.5.7
Youngs Modulus, E
6.5.8
6.5.8.1
Foundation settlement method 1 for shallow foundations is based on the strain influence approach,
method by Schmertmann (1978) for square footing (L/B=1). This is applicable to coarse soils.
= 12
1
1 = 1 0.5
2 = 1 0.2 log10 10
3 = 1.25
CPT in Geotechnical Practice, pp. 158-160
Where
149
Datgel
DCT-UG-001 - 3.11- September 2014
0,
0.5
0,
is the effective overburden pressure at the level of peak (see figure below). Effective
stresses are calculated using the design groundwater depth on
CPT_FOUNDATION_POINT_PARAMETERS and/or CPT_FOUNDATION_PROJECT_PARAMETERS
6.5.8.2
Foundation settlement method 2 for shallow foundations based on the strain influence approach,
method by Schmertmann (1978) for strip footing (L/B >10). This is applicable to coarse soils.
= 12
1
150
3
Datgel
DCT-UG-001 - 3.11- September 2014
1 = 1 0.5
0,1
0.5
2 = 1 0.2 log10 10
3 = 1.75
Where
is net foundation pressure which is foundation pressure (q) in Foundation_Pressure on
CPT_FOUNDATION_POINT_PARAMETERS and/or CPT_FOUNDATION_PROJECT_PARAMETERS tables,
0,
0.5
foundation level.
is thickness of sub-layer
is the Youngs modulus and stored in Young_Modulus on CPT_DATA_FOUNDATION
0,
is the effective overburden pressure at the level of peak . Effective stresses are
calculated using the design groundwater depth on CPT_FOUNDATION_POINT_PARAMETERS and/or
CPT_FOUNDATION_PROJECT_PARAMETERS
6.5.8.3
Foundation settlement method 3 for shallow foundations based on the strain influence approach,
method by Schmertmann (1978) for footing with 1 < L/B < 10 is interpolated between foundation
settlement 1 and 2. This is applicable to coarse soils.
6.6
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,
CPT_POINT_MATERIAL_PROPERTIES (only for undrained shear strength parameter Nkt) and
CPT_PROJECT_CORRELATION_PARAMETERS tables. Users should configure the parameters to suit site
conditions.
151
Datgel
DCT-UG-001 - 3.11- September 2014
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.
6.7
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 be userdefinable, allowing you to configure source table/fields, and provides the option for to manually define
the depth ranges.
6.7.1
Default Configuration
152
Datgel
DCT-UG-001 - 3.11- September 2014
6.7.2
Custom Configuration
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.
CPT Tool gINT Add-In 3.1
User Guide
153
Datgel
DCT-UG-001 - 3.11- September 2014
6.7.2.1
Interval Calculation
Multiple fields may be used to define the intervals. Each set of parameters is to be suffixed with a
number (#).
6.7.2.1.1 Parameters
Parameter names and their definitions are defined below.
IntervalSourceField#: gINT field reference for field used for interval definition
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.
2.
Then a distinct list of all interval top and bottom depths is made from all interval source sets.
6.7.2.2
Average Calculation
6.7.2.2.1 Parameters
Parameter names and their definitions are defined below.
AverageSourceField#: Field reference for source data. All AverageSourceField# must be from
the same table
154
Datgel
DCT-UG-001 - 3.11- September 2014
6.8
qc and qt Averaging
6.8.1
Moving Average
6.8.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.
6.8.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.
6.9
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
CPT_POINT_PARAMETERS table,
CPT_PROJECT_PARAMETERS table
6.10
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,
CPT Tool gINT Add-In 3.1
User Guide
155
Datgel
DCT-UG-001 - 3.11- September 2014
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:
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.
CPT Tool gINT Add-In 3.1
User Guide
156
Datgel
DCT-UG-001 - 3.11- September 2014
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.
6.11
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 is calculated using the method proposed by Houlsby and
Teh (1988):
=
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 50)
Vertical coefficient of consolidation in is calculated by dividing the by Ratio_ch_to_cv.
6.11.1
1.
2.
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.
157
Datgel
DCT-UG-001 - 3.11- September 2014
3.
Ensure the ground water depth is defined, see section 4.4 Groundwater. Set
CPT_GENERAL.Groundwater_Depth to 1.50.
4.
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.
6.
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.
7.
8.
9.
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.
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.
158
Datgel
DCT-UG-001 - 3.11- September 2014
159
Datgel
DCT-UG-001 - 3.11- September 2014
6.11.2
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.
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.
2.
You may also like to use the minimum and maximum scale fields to control the graph report
scale extents.
3.
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.
160
Datgel
DCT-UG-001 - 3.11- September 2014
161
Datgel
DCT-UG-001 - 3.11- September 2014
6.11.3
The forward extrapolation option allows you 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.
162
Datgel
DCT-UG-001 - 3.11- September 2014
163
Datgel
DCT-UG-001 - 3.11- September 2014
Reports
CPT Tool provides hundreds of reports, covering a wide range of presentation options. In addition to
the built-in reports, you can adapt or edit reports using gINTs report designer. If you intend to
customise the reports we suggest you first work through the relevant tutorials.
7.1
Report Symbology
The Symbology feature in the CPT Tool provides a way to dynamically configure the output and
presentation of derived parameter and correlation plots and text entities in the CPT gINT 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.
7.1.1
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.
7.1.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.
CPT Tool gINT Add-In 3.1
User Guide
164
Datgel
DCT-UG-001 - 3.11- September 2014
7.1.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.
165
Datgel
DCT-UG-001 - 3.11- September 2014
7.1.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.
166
Datgel
DCT-UG-001 - 3.11- September 2014
7.1.2
Configurable Options
7.1.2.1
CPT_SYMBOLOGY
Field Name
Description
Configured In
Parameter
Library, Project,
Point
Library
Library
Library
Line Colour
Library, Project,
Point
Line Type
Library, Project,
Point
Library, Project,
Point
Line Thickness
Library, Project,
Point
Data Marker
Library, Project,
Point
Library, Project,
Point
Library, Project,
Point
Show on Report
Enter True to show the parameter in the CPT log/fence report plot
entities, False to hide.
Library, Project,
Point
Name
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.
Library
Abbreviation
Library
167
Datgel
DCT-UG-001 - 3.11- September 2014
Field Name
Description
Configured In
Reference
Library
Reference Short
Library
Library, Project,
Point
Library
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]
Library
7.1.2.2
DG_CPT_SYMBOLOGY_SCALES_UNITS
Field Name
Description
Unit System
Parameter
Unit
Unit of the parameter, value will be displayed in the header section of the log/fence
column.
Minimum Scale
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 Scale
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.
Automatic Scale
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.
168
Datgel
DCT-UG-001 - 3.11- September 2014
Field Name
Description
Number of Divisions
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.
7.2
Log Reports
Description
CPT A4P
CPT LETP
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.
CPTU A4P
CPTU COMPARISON A4
CPTU / Piezocone derived report with qt, Rf, Bq and material description.
CPTU / Piezocone derived report with qt, Rf, Bq and material description.
CPTU LETP
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.
169
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
CPTU NL A4P
CPTU / Piezocone report to Dutch Standard in English with qc, fs, u, Rf.
CPTU NL EN A4P
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,
Phi', material description and consistency.
CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type,
Phi', material description and consistency.
CPTU SU 11X17L
CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type,
su, material description and consistency.
CPTU SU A3L
CPTU / Piezocone report with qt, fs or ft, uo, u2, Rf, Bq, interpreted soil type,
su, material description and consistency.
CPTU SU A4P
CPTU SU DR 11X17L
CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, interpreted soil
type, Dr, su, material description and consistency.
CPTU SU DR A3L
CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, interpreted soil
type, Dr, su, material description and consistency.
CPTU SU DR CC 11X17L
CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, Dr, su, Cc,
material description and consistency.
CPTU SU DR CC A3L
CPTU / Piezocone report with qc, qt, fs or ft, uo, u2, Rf, Bq, Dr, su, Cc,
material description and consistency.
CPTU SU LETP
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).
7.2.1
Dynamic Logs
Value
Comparison
False to show one PointID, True to two PointIDs on the page, one in red and the
other in blue.
Defines the type of depth or elevation scale that will display on the left side of the
log.
Column 1
.
CPT Tool gINT Add-In 3.1
User Guide
170
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Value
Column 10
Width 1
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.
Width 10
Show qt qc Average Legend
Select up to 5 parameters that will display reference legends in the footer of the
page.
Legend 5
Header Legend Type
7.3
Defines if numbers or the reference names will display in the column header.
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
Default Value
Notes
Title
Drawn
Persons initials/name
Drawn Date
Enter date
Checked
Persons initials/name
Checked Date
Enter date
Figure Number
Revision
Enter Revision
Sheet
Enter Sheet
Override Sitemap
Scale
Stick CPT
171
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Default Value
Notes
L C = Legend/ Soil classification method colour
S = Stick/line
Default Title
Column R3
Width R3 (mm)
Column R2
Width R2 (mm)
Column R1
Width R1 (mm)
Column L1
Width L1 (mm)
Column L2
Width L2 (mm)
Column L3
Width L3 (mm)
Legend 1
Legend 2
Legend 3
Legend 4
172
Datgel
DCT-UG-001 - 3.11- September 2014
7.3.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>>)>>)>>
7.4
Graph Reports
Description
Soil behaviour type classification graph - Begemann 1965, cone resistance (qc)
versus sleeve friction ratio (fs).
Soil behaviour type classification graph - Begemann 1965, cone resistance (qc)
versus sleeve friction ratio (fs).
Soil behaviour type classification graph - Multiple PointIDs per page - Begemann
1965, cone resistance (qc) versus sleeve friction ratio (fs).
Soil behaviour type classification graph - Multiple PointIDs per page - Begemann
1965, cone resistance (qc) versus sleeve friction ratio (fs).
173
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
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.
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 normalised excess pore pressure versus linear time,
grouped by PointID.
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,
grouped by PointID.
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, grouped by PointID.
174
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
DEPTH LETP
CPT EFFECTIVE COHESION RL
A4P
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).
Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998).
Soil Behaviour Type Index (Ic) 1 versus Depth. Robertson and Wride (1998).
CPT IC 1 RL A4P
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).
CPT IC 1 RL LETP
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).
CPT IC 2 RL A4P
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).
175
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
CPT IC 2 RL LETP
Soil Behaviour Type Index (Ic) 2 versus Elevation. Jefferies and Davies (1993).
CPT IC 3 RL A4P
CPT IC 3 RL LETP
Soil Behaviour Type Index (Ic) 4 versus Depth. Been and Jefferies (1992).
Soil Behaviour Type Index (Ic) 4 versus Depth. Been and Jefferies (1992).
CPT IC 4 RL A4P
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.
Soil Behaviour Type Index (Ic) 4 versus Elevation with differing colours for each
PointID. Been and Jefferies (1992).
CPT IC 4 RL LETP
Soil Behaviour Type Index (Ic) 4 versus Elevation. Been and Jefferies (1992).
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
176
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
Ratio (Fr).
Soil behaviour type index classification graph - Been and Jefferies (1992),
Dimensionless Penetration Resistance (Qt(1-BQ)+1) versus Normalised Friction
Ratio (Fr).
177
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
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).
CPT PRECONSOLIDATION
STRESS DEPTH A4P
CPT PRECONSOLIDATION
STRESS DEPTH LETP
CPT PRECONSOLIDATION
STRESS RL A4P
CPT PRECONSOLIDATION
STRESS RL LETP
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
178
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
qt is found, the graph will plot qt. Otherwise, qc is plotted.
CPT QC QT VS ELEVATION
COLOUR A4P
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.
CPT QC QT VS ELEVATION
COLOUR LETP
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 - 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 - Multiple PointIDs per page - 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).
Friction ratio (Rf) vs elevation with differing colours for each PointID.
Friction ratio (Rf) vs elevation with differing colours for each PointID.
179
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
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 - 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 - 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
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).
180
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
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 - 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 - 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 - 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 - 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.
181
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
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.
CPT SU LB BE UB RL A4P
CPT SU LB BE UB RL LETP
CPT SU RL A4P
CPT SU RL LETP
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
182
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
LETP
183
Datgel
DCT-UG-001 - 3.11- September 2014
Tutorials
Use the tutorials in this section to develop more skills with some of the CPT Tools advanced features.
Data needed for these tutorials is provided with the installation files.
8.1
8.1.1
Aim
In this tutorial, we will be creating a dynamic log column and fence column for the derived parameter
Effective Cone Resistance, .
8.1.2
We will start by creating the field that will store the data for this parameter on the CPT_DATA table.
1.
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.
2.
Fill in the fields with the following values, and click OK when finished.
Field Name
Value
Name
Effective_Cone_Resistance
Caption
qe
Type
Double
Description
Units
kPa
Cell Color
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.
8.1.3
1.
184
Datgel
DCT-UG-001 - 3.11- September 2014
2.
Enter the following code in the Data or Expression then click Save.
8.1.4
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.
1.
Go to DATA DESIGN | Library Data, and select DG_DPT_SYMBOLOGY from the yellow drop
down list.
2.
Enter a new record in DG_DPT_SYMBOLOGY with the following values, then click Save.
185
Datgel
DCT-UG-001 - 3.11- September 2014
Column Name
Value
Parameter
<<CPT_DATA.Effective_Cone_Resistance>>
[CPT_DATA].[Effective_Cone_Resistance]
[CPT_DATA]
Line Colour
Line Type
Solid
Solid
Line Thickness
0.2
Show on Report
True
Name
Abbreviation
q<<SUB>>e<<SUB>>
3.
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
Value
Unit System
SI
Parameter
186
Datgel
DCT-UG-001 - 3.11- September 2014
Column Name
Value
Unit
MPa
Minimum Scale
Maximum Scale
40
Number of Divisions
2nd Record:
Column Name
Value
Unit System
English
Parameter
Unit
tsf
Minimum Scale
Maximum Scale
Number of Divisions
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
Value
Name
qe
Description
187
Datgel
DCT-UG-001 - 3.11- September 2014
Column Name
Value
Log Width
40
Parameter
5.
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
Value
Name
qe
Description
Width
10
Parameter
188
Datgel
DCT-UG-001 - 3.11- September 2014
6.
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
Value
Table Name
CPT_DATA
Field Name
Effective_Cone_Resistance
Location
Project
Parameter Name
CptDataEffectiveConeResistanceField
SI
MPa
English
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.
189
Datgel
DCT-UG-001 - 3.11- September 2014
8.1.5
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.
1.
Go to REPORT DESIGN | Logs then call the command Blocks > Edit Log Blocks. Select
DG CPT DPPR from the yellow drop down list.
2.
Call the command File > Copy Page. Enter DG CPT QE in the Page names to copy to and
click OK.
190
Datgel
DCT-UG-001 - 3.11- September 2014
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.
3.
From the current screen (REPORT DESIGN | Logs > Log Blocks), select DG CPT DYNAMIC
COLUMNS from the yellow drop down list.
4.
Call the command Blocks > Insert Block and enter the following values, then click OK.
Main Tab:
Field Name
Value
Block Source
Int!dg cpt qe
Page Range
All
Medium Blue
Offset X
<<Let(Block = "qe")>>_
<<User System Data.DG CPT Dynamic Log Col Offset X>>
Configuration Tab:
Field Name
Value
10
Output Condition
<<Let(Block = "qe")>>_
<<User System Data.DG CPT Dynamic Log Col Output Condition>>
5.
Left click on a vacant space to place the Block reference, then click Save.
191
Datgel
DCT-UG-001 - 3.11- September 2014
We now need to add a new User Report Variable to the Dynamic Log reports.
6.
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.
7.
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
Value
Name
qe Width
Type
Memo
8.
9.
We now need to copy the new User Report Variable to the other Dynamic Log reports.
10. With the CPT DYNAMIC A4P report currently open, call the command File > Page > Copy
Report Variables, select qe Width and click OK.
192
Datgel
DCT-UG-001 - 3.11- September 2014
11. 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.
8.1.6
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.
1.
Go to REPORT DESIGN | Fences then call the command Blocks > Edit Fence Blocks.
Select DG CPT DPPR L from the yellow drop down list.
2.
Call the command File > Copy Page. Enter DG CPT QE L in the Page names to copy to
and click OK.
From the current screen (REPORT DESIGN | Fences > Fence Blocks), select CPT DPPR R
from the yellow drop down list.
4.
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.
5.
From the current screen (REPORT DESIGN | Fences > Fence Blocks), select DG CPT
STICK from the yellow drop down list.
193
Datgel
DCT-UG-001 - 3.11- September 2014
6.
Call the command Blocks > Insert Block and enter the following values for the left fence
block, then click OK.
Main Tab:
Field Name
Value
Block Source
Int!dg cpt qe l
Page Range
All
Offset X
<<Let(Block = "qe")>>_
<<User System Data.DG CPT Fence Col Offset X L>>
Configuration Tab:
Field Name
Value
-11.75
Output Condition
<<Let(Block = "qe")>>_
<<User System Data.DG CPT Fence Col Output Cond L>>
7.
Left click on a vacant space to place the Block reference, then click Save.
8.
Repeat the above steps, and enter the following for the right fence block.
Main Tab:
Field Name
Value
Block Source
Int!dg cpt qe r
Page Range
All
Offset X
<<Let(Block = "qe")>>_
<<User System Data.DG CPT Fence Col Offset X R>>
Configuration Tab:
Field Name
Value
11.75
Output Condition
<<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.
9.
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.
10. 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
Value
Name
qe Width L
Type
Memo
194
Datgel
DCT-UG-001 - 3.11- September 2014
11. Enter <<Let(Block = "qe")>><<User System Data.DG CPT Fence Col Width
L>> for the Value in the newly created User Report Variable.
12. 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
Value
Name
qe Width R
Type
Memo
13. Enter <<Let(Block = "qe")>><<User System Data.DG CPT Fence Col Width
R>> for the Value in the newly created User Report Variable.
14. 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.
15. 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.
195
Datgel
DCT-UG-001 - 3.11- September 2014
16. 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.
8.1.7
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.
1.
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
Replace
<<CPT_DATA.Differential_Pore_Pressure_Ratio>>
<<CPT_DATA.Effective_Cone_Resistance>>
2.
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
FenceBlk!DG CPT QE R
196
Datgel
DCT-UG-001 - 3.11- September 2014
3.
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.
197
Datgel
DCT-UG-001 - 3.11- September 2014
8.2
8.2.1
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:
su = 0.5 sin OCR vo
8.2.2
Procedure
Go to the DATA DESIGN | Project Database tab, and then call the command File > Open
File > Current Project.
2.
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.
3.
Fill in the fields with the following values, and click OK when finished.
Field Name
Value
Name
Undrained_Shear_Strength_5
Caption
Su 5 Tutorial
Type
Double
Description
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:
Friction_Angle_3 and 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
Units
kPa
Cell Color
Field - Calculated
4.
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.
5.
Fill in the fields with the following values, and click OK when finished.
Field Name
Value
Name
Undrained_Shear_Strength_5_Lambda
Type
Double
Description
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:
Friction_Angle_3 and 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
Default Value
0.85
Cell Color
Select CPT_POINT_ CORRELATION_PARAMETERS from the yellow drop down list from the top.
198
Datgel
DCT-UG-001 - 3.11- September 2014
7.
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.
8.
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.
9.
We will now use the Table Field Data Tool to insert a table field reference to the configuration.
10. 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:
199
Datgel
DCT-UG-001 - 3.11- September 2014
Value
Name
Iteration
Description
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: Friction_Angle_3 and
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
Write Value To
<<CPT_DATA.Undrained_Shear_Strength_5>>
Enabled
Formatting Type
Decimal Places
Value
We will now enter the variables in the Table/Field References to Variables Grid.
12. Click on the Variable Name column, first row. Type in PhiD1 minding the case of each
character.
13. Click on the Expression column, first row. Go to the Table Field Data Tool, and select the
CPT_DATA table, Friction_Angle_1 field. Click on the Paste button, and this should insert
<<CPT_DATA.Friction_Angle_1>> in the cell in the first row of the Expression column.
14. Click on the Validation Value column, first row. Enter 15 in the cell.
We have just finished entering one variable, PhiD1 which represents from the equation.
Repeat the last three steps to enter the rest of the variables listed below:
Variable
Name
Expression
Unit
Validation
Value
PhiD1
<<CPT_DATA.Friction_Angle_1>>
deg
15
PhiD3
<<CPT_DATA.Friction_Angle_3>>
deg
10
OCR
<<CPT_DATA.Overconsolidation_Ratio_1>>
OCR
SigDV0
<<CPT_DATA.Effective_Stress>>
100
vo
PjLambda
<<CPT_PROJECT_CORRELATION_PARAMETERS.Undra
ined_Shear_Strength_5_Lambda>>
0.7
PtLambda
<<CPT_POINT_CORRELATION_PARAMETERS.Undrain
ed_Shear_Strength_5_Lambda>>
0.8
SoilType
<<CPT_DATA.Soil_Type_1>>
Fine
kPa
200
Represents
Variable in the
Equation
Datgel
DCT-UG-001 - 3.11- September 2014
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.
15. 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:
17. 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
,
""
)
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.
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(
CPT Tool gINT Add-In 3.1
User Guide
201
Datgel
DCT-UG-001 - 3.11- September 2014
,
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.
19. 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
202
Datgel
DCT-UG-001 - 3.11- September 2014
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.
203
Datgel
DCT-UG-001 - 3.11- September 2014
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.
20. Go to INPUT | CPT | CPT Global Parameters tab, and enter 0.7 in the
Undrained_Shear_Strength_Tutorial_5_Lambda field.
21. 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.
22. 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. You may use
these existing correlations as a basis to create new correlations that suit your requirements. The Copy
CPT Tool gINT Add-In 3.1
User Guide
204
Datgel
DCT-UG-001 - 3.11- September 2014
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.
23. Go to DATA DESIGN | Library Data tab and select DG_CPT_SYMBOLOGY from the yellow table
drop down list.
24. 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
Value
Parameter
<<CPT_DATA.Undrained_Shear_Strength_5>>
[CPT_DATA].[Undrained_Shear_Strength_5]
Unit
kPa
Line Colour
Line Type
Solid
Line Thickness
0.2
Data Marker
Maximum Scale
500
Automatic Scale
Automatic Scale Round To
Show on Report
True
Remark
Name
Abbreviation
S<<SUB>>u<<SUB>>
Reference
Wroth (1984)
Reference Short
25. 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.
26. 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.
27. Click on the Print or Preview button, and the User Report Variables window will show. Fill in
the following values and click OK.
CPT Tool gINT Add-In 3.1
User Guide
205
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Value
Column 1
QT QC FT FS WITH MINOR
Column 2
RF SLOPE INDICATOR
Column 3
Column 4
Column 5
Column 6
Column 7
Column 8
Column 9
Column 10
Width 1 (mm)
Width 2 (mm)
45
Width 3 (mm)
45
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
Legend 1
Legend 2
206
Datgel
DCT-UG-001 - 3.11- September 2014
207
Datgel
DCT-UG-001 - 3.11- September 2014
8.3
8.3.1
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.
8.3.2
1.
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.
2.
Enter the following code in the Data or Expression field then click Save.
208
Datgel
DCT-UG-001 - 3.11- September 2014
8.3.3
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:
209
Datgel
DCT-UG-001 - 3.11- September 2014
Undrained_Shear_Strength_1
Undrained_Shear_Strength_2
Undrained_Shear_Strength_3
Undrained_Shear_Strength_4
Undrained_Shear_Strength_5
Undrained_Shear_Strength_6
3.
Go to DATA DESIGN | Library Data, and select DG_DPT_SYMBOLOGY from the yellow drop
down list.
4.
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
Value
Parameter
<<CPT_DATA.Undrained_Shear_Strength_#>>
[CPT_DATA].[Undrained_Shear_Strength_#]
[CPT_DATA]
Line Type
Solid
Line Thickness
0.2
Show on Report
True
Name
Abbreviation
s<<SUB>>u<<SUB>>
5.
Set the following values for each parameter, then click Save.
Parameter Name
Line Colour
Data Marker
Dash
Dash-Dot
Dash-Dot-Dot
Dash2
Dash-Dash-Dot
Dot2
210
Datgel
DCT-UG-001 - 3.11- September 2014
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
Value
Unit System
SI
Parameter
Unit
kPa
Minimum Scale
Maximum Scale
500
Number of Divisions
2nd Set:
Column Name
Value
Unit System
English
Parameter
Unit
tsf
Minimum Scale
Maximum Scale
Number of Divisions
211
Datgel
DCT-UG-001 - 3.11- September 2014
7.
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
Value
Name
Description
Log Width
30
Parameter
212
Datgel
DCT-UG-001 - 3.11- September 2014
8.
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
Value
Name
Description
Width
10
Parameter
8.3.4
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 Friction
Angle correlation parameter log block as the basis for our new log block.
1.
Go to REPORT DESIGN | Logs then call the command Blocks > Edit Log Blocks. Select
DG CPT FRICTION ANGLE from the yellow drop down list.
2.
Call the command File > Copy Page. Enter DG CPT UNDRAINED SHEAR STRENGTH in the
Page names to copy to and click OK.
213
Datgel
DCT-UG-001 - 3.11- September 2014
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.
3.
Call the command Blocks > Insert Block and enter the following values, then click OK.
Main Tab:
Field Name
Value
Block Source
Page Range
All
Medium Blue
214
Datgel
DCT-UG-001 - 3.11- September 2014
Field Name
Value
Offset X
Configuration Tab:
Field Name
Value
10
Output Condition
4.
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.
5.
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.
6.
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
Value
Name
Type
Memo
7.
8.
We now need to copy the new User Report Variable to the other Dynamic Log reports.
CPT Tool gINT Add-In 3.1
User Guide
215
Datgel
DCT-UG-001 - 3.11- September 2014
9.
With the CPT DYNAMIC A4P report currently open, call the command File > Page > Copy
Report Variables, select qe Width and click OK.
10. 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.
8.3.5
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 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.
1.
Go to REPORT DESIGN | Fences then call the command Blocks > Edit Fence Blocks.
Select DG CPT FRICTION ANGLE L from the yellow drop down list.
2.
Call the command File > Copy Page. Enter DG CPT UNDRAINED SHEAR STRENGTH L in
the Page names to copy to and click OK.
From the current screen (REPORT DESIGN | Fences > Fence Blocks), select CPT
FRICTION ANGLE R from the yellow drop down list.
216
Datgel
DCT-UG-001 - 3.11- September 2014
4.
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.
5.
From the current screen (REPORT DESIGN | Fences > Fence Blocks), select DG CPT
STICK from the yellow drop down list.
6.
Call the command Blocks > Insert Block and enter the following values for the left fence
block, then click OK.
Main Tab:
Field Name
Value
Block Source
Page Range
All
Offset X
Configuration Tab:
Field Name
Value
-11.75
Output Condition
7.
Left click on a vacant space to place the Block reference, then click Save.
8.
Repeat the above steps, and enter the following for the right fence block.
Main Tab:
Field Name
Value
Block Source
Page Range
All
Offset X
Configuration Tab:
Field Name
Value
11.75
Output Condition
We now need to add a new User Report Variable to the CPT Fence reports.
9.
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.
10. 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.
217
Datgel
DCT-UG-001 - 3.11- September 2014
Field Name
Value
Name
Type
Memo
Value
Name
Type
Memo
14. 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.
15. 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.
218
Datgel
DCT-UG-001 - 3.11- September 2014
16. 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.
8.3.6
Now we need to replace all references to the original parameter (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
Replace
<<CPT_DATA.Friction_Angle_1>>
<<CPT_DATA.Undrained_Shear_Strength_1>>
<<CPT_DATA.Friction_Angle_2>>
<<CPT_DATA.Undrained_Shear_Strength_2>>
<<CPT_DATA.Friction_Angle_3>>
<<CPT_DATA.Undrained_Shear_Strength_3>>
<<CPT_DATA.Friction_Angle_4>>
<<CPT_DATA.Undrained_Shear_Strength_4>>
<<CPT_DATA.Friction_Angle_5>>
<<CPT_DATA.Undrained_Shear_Strength_5>>
<<CPT_DATA.Friction_Angle_6>>
<<CPT_DATA.Undrained_Shear_Strength_6>>
219
Datgel
DCT-UG-001 - 3.11- September 2014
Find
Replace
1.
Click on the Reports to Scan button. Select the following items in the list then Click OK.
2.
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.
220
Datgel
DCT-UG-001 - 3.11- September 2014
8.4
8.4.1
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.
8.4.2
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
Value
Text
SI_MPa
Description
SI MPa
SI_MPa is the name of the new unit system, and all unit conversion configuration fields will be prefixed
with this name.
8.4.3
1.
Go to DATA DESIGN | Library Tables tab, and open the DG_CPT_FIELD_MAP table from the
yellow drop down list.
2.
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.
221
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Type
Caption
Description
SI_MPa
Text
SI_MPa_FR_Minimum
Double
Minimum (SI_MPa)
SI_MPa_FR_Maximum
Double
Maximum (SI_MPa)
SI_MPa_FR_Decimals_Displayed
Integer
SI_MPa_FR_Round_To_Nearest
Double
SI_MPa_FR_Format_Type
Text
SI_MPa_Default
Text
Default (SI_MPa)
3.
Set the Cell Colour to Field Enter Data for all the fields created.
4.
Select the SI_MPa field, set the Lookup to Libtbl!field units, check the Must use Lookup and
Allow additions in Input options.
5.
8.4.4
Go to DATA DESIGN | Library Data tab, and select DG_CPT_FIELD_MAP from the yellow drop down list.
CPT Tool gINT Add-In 3.1
User Guide
222
Datgel
DCT-UG-001 - 3.11- September 2014
We will be using the units in the SI unit system as a basis to the SI_MPa unit system.
1.
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.
2.
Change the value in the SI_MPa column for the following records:
Table Name
Field Name
SI MPa
Decimals Displayed
(SI_MPa)
CPT_CONE_CALIBRATIONS
Area_Cone
cm2
CPT_DATA
Excess_pore_pressure
MPa
CPT_DATA
Filtered_Sleeve_Friction_Resistance
MPa
CPT_DATA
In_Situ_Pore_Pressure
MPa
CPT_DATA
Porewater_Pressure_1
MPa
CPT_DATA
Porewater_Pressure_2
MPa
CPT_DATA
Porewater_Pressure_3
MPa
CPT_DATA
Sleeve_Friction_Resistance
MPa
CPT_DISSIPATION_TEST_GENERAL
Corrected_Initial_Pore_Pressure
MPa
CPT_DISSIPATION_TEST_GENERAL
In_Situ_Pore_Pressure
MPa
CPT_DISSIPATION_TEST_GENERAL
Initial_Pore_Pressure
MPa
CPT_DISSIPATION_TEST_GENERAL
Maximum_Pore_Pressure
MPa
CPT_DISSIPATION_TEST_GENERAL
Minimum_Pore_Pressure
MPa
CPT_DISSIPATION_TEST_GENERAL
Pore_Pressure_Degree_Dissipation
MPa
CPT_DISSIPATION_TEST_READINGS
Friction_Resistance
MPa
CPT_DISSIPATION_TEST_READINGS
Porewater_Pressure_1
MPa
CPT_DISSIPATION_TEST_READINGS
Porewater_Pressure_2
MPa
CPT_DISSIPATION_TEST_READINGS
Porewater_Pressure_3
MPa
8.4.5
1.
Go to the INPUT tab, then call the command Add-Ins > Datgel CPT Tool > Unit Conversion.
The following form will show:
2.
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 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.
223
Datgel
DCT-UG-001 - 3.11- September 2014
3.
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.
224
Datgel
DCT-UG-001 - 3.11- September 2014
225
Datgel
DCT-UG-001 - 3.11- September 2014
8.5
8.5.1
Aim
In this tutorial, we will be entering the unit conversion factors for the quantity acceleration.
8.5.2
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.
1.
2.
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
Description
cm/s2
in/s2
ft/s2
g0
226
Datgel
DCT-UG-001 - 3.11- September 2014
Name
Description
m/s2
mm/s2
3.
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
Source to SI Conversion
Factor
SI Unit
cm/s2
cm/s<<SUP>>2<<SUP>>
0.01
m/s2
in/s2
in/s<<SUP>>2<<SUP>>
0.0254
m/s2
ft/s2
ft/s<<SUP>>2<<SUP>>
0.3047987
m/s2
g0
g<<SUP>>0<<SUP>>
9.80665
m/s2
m/s2
m/s<<SUP>>2<<SUP>>
m/s2
mm/s2
mm/s<<SUP>>2<<SUP>>
0.001
m/s2
4.
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:
5.
Click Save.
227
Datgel
DCT-UG-001 - 3.11- September 2014
8.6
8.6.1
Aim
This example will change the unit for Porewater_Pressure_2, u2, from kPa to MPa.
8.6.2
Open the field properties for u2 and change the unit to MPa.
8.6.3
Step 2 - Use the Data Correction Tool to convert the data from kPa to
MPa
1.
2.
Run the correction u2 kPa to MPa against all strokes in the project.
3.
228
Datgel
DCT-UG-001 - 3.11- September 2014
4.
5.
After
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.
229
Datgel
DCT-UG-001 - 3.11- September 2014
8.7
8.7.1
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.
8.7.2
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.
8.7.2.1
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.
8.7.2.2
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
CPT Tool gINT Add-In 3.1
User Guide
230
Datgel
DCT-UG-001 - 3.11- September 2014
calculations. Point Level tables can optionally have a split-screen child table, for which values also can
be read for use in CPT Calculations.
To create a Point Level table, set Key Sets to PointID, Parent table to POINT.
8.7.2.3
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.
231
Datgel
DCT-UG-001 - 3.11- September 2014
8.7.3
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
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.
232
Datgel
DCT-UG-001 - 3.11- September 2014
8.7.4
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_FOUNDATION 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
Value
Table Name
CPT_DATA_FOUNDATION
Location
Project
233
Datgel
DCT-UG-001 - 3.11- September 2014
For fields in this table, enter the following values for the specified columns, leaving the other columns
empty. See Unit Conversion section 5.5.3.2 for more details on configuring the Unit Conversion related
columns.
Column
Value
Table Name
CPT_DATA_FOUNDATION
Field Name
Pile_Axial_Capacity_Unit_End_Bearing_1
Location
Project
SI
MPa
English
tsf
Decimal Format
Decimal Format
8.7.5
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.
234
Datgel
DCT-UG-001 - 3.11- September 2014
The example below is for a table named CPT_DATA_FOUNDATION. 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_FOUNDATION"
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
235
Datgel
DCT-UG-001 - 3.11- September 2014
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.
8.7.6
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.
236
Datgel
DCT-UG-001 - 3.11- September 2014
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, pp. 601-610.
Been, K. and Jefferies, M.G. (1992); Towards Systematic CPT Interpretation. Proceedings Wroth
Memorial Symposium, Thomas Telford, London, pp. 121134
Begemann, H. K. S. (1965). The friction jacket cone as an aid in determining the soil profile.
Proceedings of the 6th International Conference on Soil Mechanics and Foundation Engineering,
ICSMFE, Montreal, September 8 - 15, Vol. 2, pp. 17-20.
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
237
Datgel
DCT-UG-001 - 3.11- September 2014
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
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.
238
Datgel
DCT-UG-001 - 3.11- September 2014
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
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.
Tonkin & Taylor (2013), Liquefaction Vulnerability Study, T&T Ref: 52020.0200/v1.0
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.
239
Datgel
DCT-UG-001 - 3.11- September 2014
Youd, T. Leslie; Hansen, Corbett M.; Bartlett, Steven F. (2002). "Revised Multilinear Regression
Equations for Prediction of Lateral Spread Displacement". Journal of Geotechnical and
Geoenvironmental Engineering 128 (12): 10071017.
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.
240
Datgel
DCT-UG-001 - 3.11- September 2014