LOG A GNGN04.TXT
(formerly LAGNGN04)
General Purpose gINT version 6 and later Log Reports:
"A" size paper (8.5x11")
Predominately geotechnical data presentation
No well column
With graph (CPT)
No legend
English (Imperial) units input and output
Portrait Orientation
================
Revision History
================
23 January 2006:
1. Converted to version 7 format.
2. Made use of column entities.
3. Took advantage of new features that are available since the
initial upload.
01 December 2002:
1. Converted to version 5 format.
2. Renamed from LAGNGN04 to LOG A GNGN04.
3. Altered form and database structure to take advantage of the many enhancements to the program since the initial upload.
4. Made the data scales variable on a borehole basis (see Special Notes below).
22 February 1998:
1. Initial Upload
*************************************************
INCLUDED FILES:
LOG A GNGN04.GLB
gINT library file containing:
Logs : LOG A GNGN04
User System Data : LOG A GNGN04 Log Scale Inc Major
LOG A GNGN04 Log Scale Inc Minor
LOG A GNGN04.GDT
gINT project data template. You will clone this file to create new project files.
LOG A GNGN04.GPJ
gINT project file containing one borehole of example data. You can use this file to clarify any input procedure questions by looking at the way the data was entered in the Input application. You can also output this data using the report template to see what the final output looks like.
*************************************************
INSTALLATION PROCEDURE:
1. Copy LOG A GNGN04.GDT to your gINT data template directory (usually C:\Program Files\GINT\DATATMPL).
2. Copy LOG A GNGN04.GPJ to your gINT projects directory (usually C:\Program Files\GINT\PROJECTS).
3. Merge LOG A GNGN04.GLB:
a) Bring up gINT.
b) Move to the Utilities application group and then to the Lib Merge/Copy application.
c) Mark "Merge From".
d) Specify the source library file as LOG A GNGN04.GLB. Remember to specify the path or use the launch button (...) to select the file with a file dialog.
e) Check the selection and query options to best meet your needs. If you wish to merge all of the above, mark Select All and Never Query.
f) Move all of the tables from the Available Source Table column to the Tables to Merge/Copy column by clicking the >> button.
g) Click the Execute button.
*************************************************
SPECIAL NOTES:
1. The company information at the lower left is taken from the Help:Company Information dialog. Remove the "Logo" text and replace with your company logo (Draw:Discrete Graphics or Draw:Bitmap Symbol).
2. The report requires the friction and cone resistance data and calculates the friction ratio.
3. The scale at the right of the report is elevation if there is a numeric elevation value in the BOREHOLE (POINT) table for the borehole, otherwise, it automatically switches to a second depth scale.
4. The increment of the vertical scales is determined by the log vertical scale in feet per inch. This is done in Data Design:User System Data:
LOG A GNGN04 Log Scale Inc Major:
<<Case(<<LogVS>>,_
< 1,1,_
< 2.5,2.5,_
< 7,5,_
Else,10_
)>>
That is, if the log vertical scale is less than 1 foot/inch, the major ticks and scale numbers are shown every foot, else if the scale is less than 2.5 feet/inch, each 2.5 feet, else if the log scale is less than 7 feet/inch, each 5 feet, else each 10 feet.
LOG A GNGN04 Log Scale Inc Minor:
<<Calc(<<User System Data.LOG A GNGN04 Log Scale Inc Major>> / 5)>>
That is, one fifth the major increment.
5. The three scale maximum values are determined on a borehole by borehole basis by calculating the maximum for each of the three plot columns. These calculations are made in the page properties of the report under the "User Report Variables" property (under the "Main" tab). Following are the three variables:
Max Friction:
<<Let(Max = _
<<Sql(Select Max([CPT].[Friction]) _
From [CPT] _
Where [CPT].[PointID] = '<<PointID>>'_
)>>_
)>>_
_
<<Case(<<Get(Max)>>,_
<= 0.4,0.4,_
<= 0.8,0.8,_
<= 2,2,_
<= 4,4,_
Else,8_
)>>
----------------------------------
Max Cone:
<<Let(Max = _
<<Sql(Select Max([CPT].[Cone Resistance]) _
From [CPT] _
Where [CPT].[PointID] = '<<PointID>>'_
)>>_
)>>_
_
<<Case(<<Get(Max)>>,_
<= 40,40,_
<= 80,80,_
<= 160,160,_
Else,400_
)>>
----------------------------------
Max Friction Ratio:
<<Let(Max = _
<<Sql(Select Max(100 * [CPT].[Friction] / [CPT].[Cone Resistance]) _
From [CPT] _
Where [CPT].[PointID] = '<<PointID>>'_
)>>_
)>>_
_
<<Case(<<Get(Max)>>,_
<= 0.4,0.4,_
<= 0.8,0.8,_
<= 2,2,_
<= 4,4,_
Else,8_
)>>
Note that the maximums are even multiples of 4 for the friction and friction ratio and 8 for the cone resistance. These correspond to the number of divisions in each of the columns.
If you wish to have scales that are consistant for all CPTs in a project, simply remove the "Where" clause in each of the Sql function expressions. For example:
<<Let(Max = _
<<Sql(Select Max(100 * [CPT].[Friction] / [CPT].[Cone Resistance]) _
From [CPT] _
Where [CPT].[PointID] = '<<PointID>>'_
)>>_
)>>_
.
.
becomes:
<<Let(Max = _
<<Sql(Select Max(100 * [CPT].[Friction] / [CPT].[Cone Resistance]) _
From [CPT] _
)>>_
)>>_
.
.
This will then determine the maximum from all CPTs in the current project.
*************************************************