CODA-GeoKit User Manual

Project: CODA-GeoKit
Document Type: User Manual
Coda Part Number: KM001-016
CODA-GeoKit User Manual
Document ID: Manuals on ‘Sister’ (J:)\GeoKit\Version 2.01\GeoKit.pdf
Confidentiality: General Distribution
Distribution: MASTER
Author Date Summary Manual
Version
DKR 29.04.97 Document Created 1.00
DKR 14.09.98 Updated 2.00
IMM 22.01.99 Updated for software version 1.34.xx 2.01
DKR 29.02.00 Updated for software version 1.40 2.02
Approved for Release: Date: 5 Mar 2000
Approved for Release: Date: 5 Mar 2000
Document is For Information Only unless it has original signatures above.

ii February 2000 for version 1.40
GeoKit User Manual
Copyright © Coda Technologies Ltd, 2000
All Rights Reserved
Printed in UK
No part of this publication may be reproduced or transmitted in any form or by any means –
graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in
any medium, taping by any computer or information storage and retrieval system, etc. without
prior permissions in writing from Coda Technologies Ltd.
Coda Technologies Ltd, Admiral House, 29-30 Maritime Street, Edinburgh, EH6 6SE, UK
February 2000
Important Note to Users
While every effort has been made to ensure the accuracy and completeness of all information in
this document, Coda Technologies Ltd assumes no liability to any party for any loss or damage
caused by errors or omissions, or by statements of any kind in this document, its updates, supplements,
or special editions, whether such errors, omissions or statements result from negligence,
accident or any other cause. Coda Technologies further assumes no liability arising out of the
application or use of any product or system described herein; nor any liability for incidental or
consequential damages arising from the use of this document. Coda Technologies disclaims all
warranties regarding the information contained herein, whether expressed, implied or statutory,
including implied warranties of merchantability or fitness for a particular purpose. Coda
Technologies makes no representation that the interconnection of products in the manner
described herein will not infringe on existing or future patent rights, nor do the descriptions
contained herein imply the granting of any licence to make, use or sell equipment constructed in
accordance with this description.
Coda Technologies reserves the right to make changes to any products herein without further
notice.
Trademarks
Coda Technologies has made every effort to supply trademark information about company
names, products and services mentioned in this manual. Trademarks indicated below were
derived from various sources.
UNIX is a registered trademark
UnixWare is a trademark of The SantaCruz Operation Inc.
Novell is a registered trademark of Novell Inc.
Ethernet is a trademark of Xerox Corporation
MS-DOS and Windows are registered trademarks of Microsoft Corporation
Postscript is a registered trademark of Adobe Systems Inc.
Q-MIPS is a registered trademark of Triton Elics International
Maxoptix and T5-2600 are registered trademarks of Maxoptix Corporation
The SAS and FAS asynchronous I/O packages were developed by Uwe Doring and Jim Murray.
Coda Technologies Ltd did not develop and do not hold the copyright to these packages. The
original SAS package in its entirety is held in /home/PKG of the DA system.
xvertext 5.0, Copyright (c) 1993 Alan Richardson (mppa3@uk.ac.sussex.syma)
Permission to use, copy, modify, and distribute the xvertext software and its documentation for
any purpose and without fee is hereby granted, provided that the above copyright notice appears
in all copies and that both the copyright notice and this permission notice appear in supporting
documentation. All work developed as a consequence of the use of this program should duly
acknowledge such use. No representations are made about the suitability of this software for any
purpose. It is provided ‘as is’ without express or implied warranty.

GeoKit User Manual
Read This First!
Coda systems are fitted with either a DAT or an Exabyte tape IO sub-system or an optical disk
IO sub-system. Both of the sub-systems are covered in this manual. The sets of instructions and
descriptions of the sub-systems are grouped together by task (Operating GeoKit) and by menu
item (Reference Guide).
You should read the following information before using the system.
DAT Tapes
• Coda systems which are fitted with DAT drives use Digital Data Storage (DDS) certified
Digital Audio Tapes (DAT). Do not use audio DAT tapes: they will not function correctly.
• Use only DAT tapes with one of the following markings:
• We recommend that you use DAT tapes by the following manufacturers: TDK, HP, Verbatim
and Fujifilm.
Optical Disks
• We recommend that you use Maxoptix ISO 14517, rewritable, 2.6 GB polycarbonate disks
with 1024 bytes per sector – Maxoptix part no. 3015385 R/W – for systems fitted with optical
disk drives, though other major manufacturers’ rewritable disks can be used, provided that
they comply with ISO/IEC 14517.
Security Devices
• The Coda system uses a hardware security device (dongle) to prevent illicit copying of the
system’s software. (The security device is enclosed within the Coda system and under normal
circumstances you should be unaware of its presence.) Notwithstanding any other agreements,
the security device is the only proof Coda Technologies will accept of legal software
ownership. Under no circumstances will a replacement security device be issued unless the
original is returned.
Loss of the dongle means loss of the software!
February 2000 for version 1.40 iii

iv February 2000 for version 1.40
GeoKit User Manual

Contents
Read This First! iii
I Introduction
1 Welcome 3
1.1 CODA-GeoKit 3
1.1.1 Site Survey Toolkit 4
1.1.2 Target Detection Toolkit 4
1.2 About this Manual 4
1.2.1 Conventions Used in this Manual 4
II The Basics
2 The Basics 9
2.1 The Main Display 9
2.1.1 The Menu Bar 9
2.1.1.1 Tear-off Menus 9
2.1.2 The Data Control Area 10
2.2 Menu Features 10
2.2.1 One-of Selection Switch 10
2.2.2 On/Off Switch 10
2.2.3 Option Selection Button 10
2.2.4 Pop-up Selector 10
2.2.5 Pop-up Action Buttons 11
2.2.5.1 Load Settings 11
2.2.5.2 Save Settings 12
2.2.6 Spin Box 13
2.2.7 Scrolling Option List 13
2.2.8 File Selection Area 13
2.2.9 Tool Bar 14
2.2.10 Message Window 14
2.2.11 Scroll Bar 14
2.2.12 Tab Forms 15
2.3 Pointer Types 15
2.4 Terminology 16
III Quick Reference
3 Quick Reference 21
3.1 Quick-Start Procedure 21
3.2 Shortcuts 21
3.2.1 Key Shortcuts 22
IV Operating GeoKit
4 Using GeoKit 25
4.1 Overview of Using GeoKit 25
4.2 Interactive Tagging with GeoKit 25
4.2.1 Overview 25
4.2.2 Creating Tags in GeoKit 26
4.2.2.1 Summary 26
4.2.3 Selecting and Deselecting Tags 27
4.2.4 Deleting Tags 27
4.2.5 Annotating Tags 27
4.2.6 Measuring Tag Dimensions 28
4.2.7 Moving Tags 28
4.3 Customising the Tag Setup 28
4.3.1 Setting up Tag Lists 28
4.3.2 Setting up Fast Tags 29
4.4 Reporting Tagged Events 29
4.5 Customising the Report Setup 30
v
Contents

Contents
V Reference Guide
Contents
5 Menu Reference 33
5.1 Tagging 33
5.1.1 Tag Types 33
5.1.1.1 Single Tags 33
5.1.1.2 Linear Tags 34
5.1.1.3 Boundary Tags 34
5.1.1.4 Expanding Box Tags 35
5.1.2 Tagging Modes 35
5.1.2.1 Add Mode 35
5.1.2.2 Select Mode 35
5.1.3 Selecting and Deselecting Tag Nodes 35
5.1.3.1 Selecting Tag Nodes 36
5.1.3.2 Deselecting Tag Nodes 36
5.1.4 Replaying Tags 36
5.2 The Tagging Menu 36
5.2.1 Add Tag Node(s) 37
5.2.2 Delete Tag Node(s) 37
5.2.3 Move Tag Node(s) 37
5.2.4 Insert/Append Tag Node 38
5.2.4.1 Append Tag Node 38
5.2.4.2 Insert Tag Node 38
5.2.5 Complete Multi-Node Tag 38
5.2.6 Annotate Tag Node(s) 38
5.2.6.1 Node Identity Tab Form 39
5.2.6.2 Node Position Tab Form 40
5.2.6.3 Node Dimensions Tab Form 40
5.2.6.4 Node Text Tab Form 41
5.2.7 Manage Tag Files (tape system) 42
5.2.7.1 Tape Load/Save 42
5.2.7.2 Delete 44
5.2.7.3 Rescan 44
5.2.8 Manage Tag Files (optical disk system) 45
5.2.8.1 Copy Tag Files 45
5.2.8.2 Delete 46
5.2.8.3 Rescan 46
5.2.8.4 Unmount 46
5.2.9 Setup Tags 46
5.2.10 Tag Activation 47
5.2.10.1 Tag Active 47
5.2.10.2 Tag Name and Incident Code 47
5.2.11 System Tag Setup 48
5.2.12 Right Mouse Tag 48
5.2.13 Fast Tag Setup 49
5.2.13.1 Fast Tag Colour 49
5.2.13.2 Add Tag 50
5.2.13.3 Delete Tag 50
5.2.13.4 Delete All Tags 50
5.3 The Reporting Menu 50
5.3.1 Report Setup 51
5.3.1.1 Report Setup Format 51
5.3.1.2 Report Setup Options 52
5.3.1.3 Report Setup Contents 53
5.3.2 Report Generation 54
5.3.2.1 Printer Setup Window 55
5.4 The Applications Menu 56
5.5 The Application Specific Area 56
5.5.1 Fast Tagging 56
5.5.1.1 Summary 58
5.5.2 The Position Area 58
VI Appendices
vi

Contents
A GeoKit Report Contents 61
A.1 Table of Tag Properties 61
B Calculations for Tag Node Measurements 67
B.1 Measurement Methods 67
C Corrected Nav Report Mnemonics 69
C.1 Measure Mnemonics 69
C.2 Sonar Mnemonics 69
C.3 Node Mnemonics 69
VII Checklists
D Mobilisation Checklists 73
D.1 GeoKit/PI100 Mobilisation Checklist 73
D.2 PI100 Mobilisation Checklist 75
E On-Line Checklists 77
E.1 Saving Tag Files to Tape/Disk Checklist 77
E.2 Loading Tag Files to System Hard Disk Checklist 77
VIII Glossary & Conversions
Conversion Table 81
Glossary 85
Software Defect Report Form 99
Product Feedback 101
Manual Feedback 103
vii
Contents

Contents
Contents
viii

Part I: Introduction
Introduction

Introduction
2 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual 1.1 CODA-GeoKit
1 Welcome
Congratulations on buying or hiring the CODA-GeoKit software package. Your investment in
GeoKit will make working with your sonar data easier and faster.
GeoKit provides automated interpretation tools and a suite of interactive enhancement and eventmarking
tools, all of which are designed to improve data interpretation and report generation.
Whether you are new to digital sonar acquisition, an experienced data processor or a professional
geophysicist, you will find GeoKit a reliable and versatile tool for interpreting sonar data.
GeoKit has been developed by:
Coda Technologies Ltd
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
tel: +44 131 553 1380
fax: +44 131 554 7143
e-mail: coda@coda-technologies.com
www: http://www.coda-technologies.com
Coda’s Technical Support service is available 24 hours a day:
USA – tel: 1 888 340 CODA
Rest of the World – tel: +44 131 553 7003.
See ‘Technical Support’ on the inside front cover for full details.
Coda’s American subsidiary is:
Coda Technologies Inc.
9800 Richmond Avenue
Suite 480
Houston
Texas 77042
USA
tel: 1 713 780 3223
fax: 1 713 780 3280
e-mail: coda@coda-technologies.com
http://www.coda-technologies.com
1.1 CODA-GeoKit
GeoKit forms the geophysicist’s on-line interpretation toolkit module for the CODA-DA
System. It provides the interpretation and reporting tools for all sidescan and shallow seismic
survey applications. On-line, on-screen interpretation and user-configurable reporting results in
a complete sonar interpretation workstation.
February 2000 for version 1.40 3
Introduction

Introduction
1.2 About this Manual GeoKit User Manual
1.1.1 Site Survey Toolkit
GeoKit has been designed for site survey applications; it offers on-screen event-marking tools
which allow you to interactively mark seabed features and their boundaries on the display screen
in real time or during data replay. All interpreted features are automatically logged to Coda’s
event database for reporting and charting. GeoKit can be used for interpretation, databasing and
reporting of both sidescan and shallow seismic data.
The high-resolution display can be used to highlight and mark the seabed features and bottom
types of interest. These marked areas are colour coded, according to your own configuration, to
allow different seabed types and features to be distinguished immediately. The results can be
seen on the display screen in colour-coded form or a full report, including locations and seabed
type, can be displayed on screen or sent directly to a printer.
1.1.2 Target Detection Toolkit
GeoKit includes tools specifically designed for target detection. Some of the basic targetmarking
tools of the DA System have been extended and modified to make target detection and
interpretation more efficient and give better results. Whereas the basic target-marking tools of
the DA System allow a single target type to be marked on screen, GeoKit allows a number of
different target types to be marked, measured, annotated and reported. This allows you to colourcode,
name, and perform automatic calculations on marked targets.
Report files can be generated in ASCII format for importing to spreadsheets, report documents,
GIS or MCM systems.
1.2 About this Manual
This manual is designed to help you get the most out of the GeoKit package, whatever your level
of experience.
• Part II: The Basics – contains basic information about Coda systems’ display features and
types of pointers, as well as the terminology used in Coda manuals. If you are new to GeoKit,
we recommend that you read this section before using the package.
• Part III: Quick Reference – includes a quick-start procedure, which summarises the instructions
for operating GeoKit. It also contains a list of tips and shortcuts to speed up using the
software package. If you are an experienced data processor, you can use this section to
refresh your memory about the operating procedures.
• Part IV: Operating GeoKit – contains operating instructions for GeoKit. They explain HOW
TO DO SOMETHING (for example, annotate tags), through step-by-step instructions, and give
hints on how to get the best out of the package. These sections are intended for users at any
level of experience.
• Part V: Reference Guide – describes in detail the areas of the GeoKit display and the various
menus and menu items available with the package. It explains WHAT CAN BE DONE (for
example, the range of tag types available for event marking). Reading through these sections
reveals the true power and flexibility of the system.
• Part VI: Appendices – contains detailed information about the contents of GeoKit reports, the
calculations for tag node measurements, as well as corrected nav report mnemonics.
• Part VII: Checklists – contains checklists for mobilising GeoKit, saving tag files, loading tag
files, and using tag and reporting setups during data interpretation.
• Part VIII: Glossary & Conversions – contains a table of useful conversions; a full list of the
terminology used in this manual; and a software defect report form, product feedback form
and manual feedback form.
1.2.1 Conventions Used in this Manual
As you read this manual, bear in mind the following conventions:
• Italics indicates words or phrases that are explained in the Glossary and modes of operation.
4 February 2000 for version 1.40

GeoKit User Manual 1.2 About this Manual
• This font identifies menu items and data control buttons. When two or three menu items are
joined by an arrow you must select the first item and then the second or third; for example,
File→Open Acquisition means that you must click on File on the Menu Bar and then, in the
pull-down menu that appears, click on Open Acquisition.
• Keyboard keys appear within greater and lesser symbols. When key names are joined by a
hyphen (-) you must hold down the first key, press the other key and then release both keys.
For example, means you must hold down and press .
• British English spelling is used throughout this manual.
• To keep instructions brief, we refer to clicking or pressing a MOUSE button, rather than a
MOUSE OR TRACKBALL button. If your system comes with the optional trackball, click or
press the appropriate button. If no button is specified, use the left button.
February 2000 for version 1.40 5
Introduction

Introduction
1.2 About this Manual GeoKit User Manual
6 February 2000 for version 1.40

Part II: The Basics
The Basics

The Basics
8 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual 2.1 The Main Display
2 The Basics
Coda’s systems use menus, pop-up windows, text-entry boxes, key shortcuts and so on in a
similar way to other windows applications. If you are familiar with Microsoft Windows®, or the
X Windows system, you will immediately find the operation of Coda’s systems familiar. If you
are not familiar with other windows applications, you will find the main features and terms
explained below.
2.1 The Main Display
The main display has six areas, as shown in Figure 2-1, this page. Five of the areas – Title Bar,
Menu Bar, Tool Bar, Data Display Area, General Information Area, Message Bar and Data
Control Area – are identical for all Coda systems and software modules; their functions are
explained in Section 5 of the DA System User Manual. The Application Specific Area, however,
changes according to the application being used; its functions in GeoKit are explained in Section
5.5 of this manual.
Tool Bar
Figure 2-1 The Main Display in Data Acquisition Mode
2.1.1 The Menu Bar
Menu Bar
Data Display Area
Title Bar
General Information Area Application Specific Area
Data Control Area
Message Bar
The Menu Bar lies across the top of the screen throughout operation of GeoKit. It displays eight
menu options: File, Display, Settings, Tagging, Reporting, Applications, Processing and
Help. When you click on any of these options (that is, you move the pointer over an option and
then click the left mouse button), a pull-down menu appears. The functions of the various menu
options are explained in Part II of the DA User Manual.
2.1.1.1 Tear-off Menus
The pull-down menus can be detached from the Menu Bar and moved around the screen; they
remain on screen until dismissed. To detach a pull-down menu, select the dotted tear-off strip at
the top of the menu; this changes the menu to a pop-up window. To move the window, press and
drag it to another part of the screen (that is, move the pointer over the window’s titlebar, press
the left mouse button and hold it down while you drag the pointer to the desired position, then
release the mouse button). To dismiss the window, double-click on the button in the top left
corner of the window, or position the pointer over the window and press .
February 2000 for version 1.40 9
The Basics

The Basics
2.2 Menu Features GeoKit User Manual
2.1.2 The Data Control Area
Figure 2-2 The Data Control Buttons
The seven data control buttons, which are located at the bottom of the main display, are on/off
switches. A button appears recessed or ‘pressed’ when it is enabled (or on). To toggle a button
on or off, simply click on it. The functions of the various data control buttons are explained in
Section 5 of the DA System User Manual.
2.2 Menu Features
2.2.1 One-of Selection Switch
Figure 2-3 One-of Selection Switches
The diamond button (or toggle) is a one-of selection switch for a group of options, only one of
which can be selected at a time. To change the selection, click on another diamond button. In the
example above, from the Report Setup Options menu, the green diamond indicates that the Tab
option has been selected; the Space and Comma options are automatically deselected.
2.2.2 On/Off Switch
Figure 2-4 On/Off Switches
The square button is an on/off switch. When the square is grey the option is disabled (or off);
when the square is green the option is enabled (or on). More than one on/off switch can be
enabled. To toggle from one setting to another, click on the square button. In the example above,
also from the Report Setup Options menu, Enclose text in double quotes has been selected.
2.2.3 Option Selection Button
Figure 2-5 An Option Selection Button
The option button displays a currently held value and indicates that other values can be selected.
In Figure 2-5, this page, from the Processing→Fish Height/Bottom Tracking menu, the fish
height calculation function is set to copy data from data channel 2 as its source. Click on the
option button to display a list of other options (in this case, active channels) and then drag the
pointer to another channel to select that channel as the data source for fish height calculations.
2.2.4 Pop-up Selector
Figure 2-6 Pop-up Window Selectors
The three-point ellipsis (...) is appended to some menu items and indicates that selection of the
item will cause a pop-up window to appear; the window will contain further selections associated
with the menu item. This hierarchical structure enables the comprehensive functions of GeoKit
10 February 2000 for version 1.40

GeoKit User Manual 2.2 Menu Features
to be accessed in a way that is logical and easy to understand. In the example above, from the
Settings menu, selecting Playback Speed will open a pop-up which contains three possible
settings for the speed at which data can be replayed.
2.2.5 Pop-up Action Buttons
Figure 2-7 Pop-up Action Buttons
Action buttons are positioned at the bottom of pop-ups; they are used either to confirm changes
made within the pop-up or to cancel those changes. Click on the OK button to confirm the
changes and dismiss the pop-up from the screen; click on the Apply button to confirm the
changes but retain the pop-up on screen. Click on the Cancel button to cancel the changes and
leave the previous settings as the current definition.
Additional action buttons are displayed on some pop-ups:
Figure 2-8 Store and Factory Action Buttons
Click on the Store button to store the settings of the current pop-up as the default setting. Click
on the Factory button to reset the settings to Coda Technologies’ original settings. To revert to
the Factory settings as the default setting after the default setting has been changed, click on the
Factory button and then the Store button.
Figure 2-9 Load and Save Action Buttons
Click on the Load button to load previously saved settings for the current pop-up. Click on the
Save button to save the current pop-up settings to file for reloading at a later date.
2.2.5.1 Load Settings
Figure 2-10, this page, shows an example of a Load Settings pop-up; this pop-up appears when
you click on the Load button in the Format tab form of the Reporting→Report Setup menu.
Figure 2-10 A Load Settings Pop-up Window
February 2000 for version 1.40 11
The Basics

The Basics
2.2 Menu Features GeoKit User Manual
Click on the Select Default button to make the default file the selected file; the name of the
default file appears beside the Default Filename label. Click on the Select Factory Default
button to reset the pop-up to Coda Technologies’ original setting; the string ‘FACTORY
DEFAULT SELECTED’ appears in the File Name text-entry box at the bottom of the pop-up.
Click on the Drive option button to select the drive from which to load the settings file; only Hard
Disk is currently available.
Use the Files window to search and view particular settings files. Enter the desired search pattern
in the File Type Filter text-entry box and then press the Filter button. All the files that pass the
search pattern appear in the Files list. To select a settings file from the list, click on the file name;
the File Name text-entry box is updated to display the selected file. Alternatively, if you know
the file name, move the pointer into the File Name text-entry box and type the file name.
Click on the Delete button to remove the currently selected file from the hard disk. In the window
that appears asking for confirmation, click on the Yes button to delete the file or the No button
to abort the delete. If the file to be deleted is the default file, a window appears asking for confirmation.
•Note: All settings files have a ‘.set’ ending. Files cannot be loaded if the directory is not shown.
Trying to do so results in an error.
Click on the Apply button or the OK button to load the settings stored in the file shown in the
File Name window. If no file has been selected, a warning window appears. Click on the Done
button to cancel any changes made to the settings and dismiss the Load Settings pop-up.
2.2.5.2 Save Settings
Figure 2-11, this page, shows an example of a Save Settings pop-up; this pop-up appears when
you click on the Save button in the Format tab form of the Reporting→Report Setup menu.
Figure 2-11 A Save Settings Pop-up Window
Click on the Make Default button to make the selected file the default file; the name of the file
appears beside the Default Filename label. If no file is selected, the settings are saved to a file
called ‘unnamed.default.set’.
Click on the Drive option button to select the drive to which to save the setting file; only Hard
Disk is currently available.
12 February 2000 for version 1.40

GeoKit User Manual 2.2 Menu Features
Use the Files window to search and view particular settings files. Enter the desired search pattern
in the File Type Filter text-entry box and then press the Filter button. All the files that pass the
search pattern appear in the Files list. To select a settings file from the list, click on the file name;
the File Name text-entry box is updated to display the selected file. Alternatively, if you know
the file name, move the pointer into the File Name text-entry box and type the file name.
Click on the Delete button to remove the currently selected file from the hard disk. In the window
that appears asking for confirmation, click on the Yes button to delete the file or the No button
to abort the delete. If the file to be deleted is the default file, a window appears asking for confirmation.
•Note: All settings files have a ‘.set’ ending. Files cannot be saved if the directory is not shown.
Trying to do so results in an error.
Click on the Apply button or the OK button to save the current settings to the file shown in the
File Name window. If no file has been selected, a warning window appears. Click on the Done
button to cancel changes made to the settings and dismiss the Save Settings pop-up window.
2.2.6 Spin Box
Figure 2-12 A Spin Box
Spin boxes appear in pop-ups where you are required to specify a numerical setting. You can
either click in the box and type the required numbers or use the up and down arrows to change
to the correct setting. Pressing and dragging on the horizontal bar between the up and down
arrows allows you to alter the value, too – if you drag upwards, the value will increase, and if
you drag downwards the value will decrease.
2.2.7 Scrolling Option List
Figure 2-13 A Scrolling Option List
Scrolling option lists consist of a text area and a down arrow. They provide a flexible method of
choosing from a list of available options. Click on the down arrow to display the list of options.
You can then move through the list by typing the first letters of your chosen option or by using
the up and down arrows on your keyboard. Each option will be highlighted as you scroll onto it.
To select the highlighted option, either press the space bar or , or click on it with the
mouse. To reset your selection, use either the left or right arrow on your keyboard. You can then
begin making our selection again. To scroll directly to your chosen option, click in the text box
and use the keyboard arrows to move to your choice. To dismiss the list, either press or
click outside the list area.
2.2.8 File Selection Area
Figure 2-14 A File Selection Area
February 2000 for version 1.40 13
The Basics

The Basics
2.2 Menu Features GeoKit User Manual
The file selection area appears in pop-ups where you can load or save files. In this area you can
choose the file type using the File Type Filter text entry box, change the filter using the Filter
button, scroll through a list of the available files and enter the name of the file you require in the
File Name text entry box, or double-click on the list. You may delete files from the list (and the
disk) using the Delete button.
2.2.9 Tool Bar
Figure 2-15 A Tool Bar
Directly below the Menu Bar of each window in the display is a Tool Bar. The icons included
in the Tool Bar allow you to perform a number of operations within the window without opening
the relevant menus (see Section 5.3).
2.2.10 Message Window
Figure 2-16 The Message Window
A Message Window appears at the bottom of each of the windows of TrackPlot/Mosaic. This
gives time-stamped Coda system information. As they appear, messages are colour coded, red
for errors, blue for warnings and black for information. Once a new message appears, the older
one disappears and is stored in black in the list of messages created since your system was started
up. You can scroll through this list by clicking on the down arrow at the side of the window.
2.2.11 Scroll Bar
Figure 2-17 A Scroll Bar
The scroll bar appears at the bottom or on the side of some pop-ups and indicates that only part
of a list of items is currently being displayed. To view other items in the list, click on the arrows
in the scroll bar or press and drag the scroll box in the scroll bar up or down, or to the left or right.
14 February 2000 for version 1.40

GeoKit User Manual 2.3 Pointer Types
2.2.12 Tab Forms
Figure 2-18 A Tab Form
Some pop-ups have several tab forms; for example, the Tag Setup pop-up from the Tagging
menu has eight tab forms (see Figure 2-18, this page). A tab form contains a number of related
items of information or selections and has a labelled tab at the top; they are arranged so that they
overlap each other. To select a tab form, click on its tab. This brings the form to the front of the
pile; the information can then be read and changes made to it. When a tab label is greyed out it
cannot be accessed.
2.3 Pointer Types
Eight mouse pointers are used in GeoKit.
The arrow pointer is the pointer type most commonly used in GeoKit.
The pencil pointer is used to create tags.
Keyboard shortcuts: to
The crosshair pointer is used to make on-screen measurements and appears when
GeoKit is in measure mode.
Keyboard shortcut:
The zoom pointer appears when GeoKit is in zoom mode.
Keyboard shortcut:
The move pointer is used to move tags.
Keyboard shortcut:
The watch pointer appears when the system is waiting for an operation to complete.
The automatic tracking pointer is used to reset the bottom tracking position.
Keyboard shortcut:
The text-entry pointer appears when the pointer is placed in a text-entry box and is
used to enter text in the selected field of a pop-up.
When the pointer is in a particular mode – for example, for moving or deleting tags – you must
complete the operation, or deselect the mode, before selecting another pointer mode. If you fail
to do so, a warning pop-up appears on screen, reminding you that a pointer operation is already
February 2000 for version 1.40 15
The Basics

The Basics
2.4 Terminology GeoKit User Manual
in progress. Click on the OK button to dismiss the pop-up and then complete the pointer
operation, or deselect the mode, before continuing to the next pointer operation. Deselecting a
mode usually involves repeating the action for selecting the mode.
2.4 Terminology
The most common computer terms used in this manual are defined below. A more complete list
of terms can be found in the Glossary at the end of this manual.
Apply this button applies the settings or options selected and retains the pop-up
window on screen.
Cancel this button cancels any items or options selected and dismisses the pop-up
window; the previous settings are retained.
click press down and release the appropriate mouse button. If no button is
specified, use the left button.
double-click press and release the appropriate mouse button twice in rapid succession. If
no button is specified, use the left button.
information
window
16 February 2000 for version 1.40
a window that provides information during acquisition or playback; this
information cannot be edited. It can be displayed for any length of time, and
is dismissed by clicking on the OK or Done button.
Menu Bar the area at the top of the main display in which eight menu options are
permanently displayed: File, Display, Settings, Tagging, Reporting,
Applications, Processing and Help. Selecting any of the options causes
a pull-down menu to appear.
OK this button selects and applies the settings or options selected and dismisses
the pop-up window from the screen.
pop-up menu an option selection menu with a specific user-alterable value or parameter.
pop-up
window
press and
drag
pull-down
menu
a general term applied to a window that automatically appears when a menu
item or control function is selected; it may be a text-entry box (in which you
type your requirement), or an area of information (which requires no action
on your part). In this manual this phrase is abbreviated to pop-up.
position the pointer over an object, press the left mouse button and hold it
down while you drag the object to the desired position, then release the
mouse button. If no button is specified, the left button should be used.
a pop-up that appears directly beneath an option in the Menu Bar when that
option is selected.
scroll bar the means by which all the items in a list appearing in a menu or pop-up
window may be examined.
select click the left mouse button on the appropriate item (such as a menu item,
toggle or value selection).
select a
menu item
click the left mouse button on a Menu Bar option, and then release the
mouse button over an item in the pull-down menu that appears below the
Menu Bar option.
tab form a form that contains a number of related items of information or selections
and has a labelled tab at the top. As tab forms overlap, the required tab form
may have to be brought to the front of the pile by clicking on its tab.
tear-off
menu
a pull-down menu that can be detached from the Menu Bar for permanent
display.

GeoKit User Manual 2.4 Terminology
text-entry
box
an area in a window for entering text or numerical values. Click within the
rectangular area and type text or edit the text using the keyboard.
toggle switch from one setting to another, usually between on and off. A toggle
switch is a switch that has just two positions.
toolkit a pop-up that contains various tools for processing the data, for example
TVG and Image Enhancement. Each pop-up contains an interactive graph
and several smart icons.
February 2000 for version 1.40 17
The Basics

The Basics
2.4 Terminology GeoKit User Manual
18 February 2000 for version 1.40

Part III: Quick Reference
Quick
Reference

Quick
Reference
20 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual 3.1 Quick-Start Procedure
3 Quick Reference
This section includes a quick-start procedure, which summarises the basic instructions for
operating GeoKit. It also contains a list of tips and shortcuts to help you work more quickly and
efficiently.
The quick-start procedure is intended for those of you who are already familiar with GeoKit; for
a more detailed guide to using GeoKit, refer to Section 5.5 which describes the functions of the
Application Specific Area.
3.1 Quick-Start Procedure
1. Set up the DA System for playback or data acquisition, as outlined in Section 5 and Section
6 of the DA System User Manual.
2. Select Applications→GeoKit to switch to GeoKit software.
3. Select Tagging→Setup Tags and either define tag types and their placement rules or load a
previously saved file of tag setups to use in the current survey.
The system always starts with the current default setups.
4. Select Tagging→Fast Tag Setup and assign the fast tag keys in the Application Specific
Area.
To mark and annotate events:
1. Switch on the Message Window in the Display menu.
2. Select the appropriate tag type from the fast tag keys in the Application Specific Area to
activate add mode.
3. Mark the required event within the sonar data on the screen.
Single tag events require one click operation to mark the event, whereas multi-node tag
events require a separate click operation for each node. Expanding box tags require a press
and drag action to expand the tag node to the required size.
• Perform any measurements required as part of the tag setup.
• Use Tagging→Complete Multi-Node Tag to complete any unclosed boundary tags.
4. If you want to manipulate the recently marked event, switch to select mode by clicking again
on the pending fast tag button.
5. Annotate events either by selecting Tagging→Annotate Tag Node(s) and clicking on the
appropriate on-screen tag, or by using the key shortcut .
6. Ensure that all information is stored to the database.
To save tag files:
1. When you have finished event marking during playback or data acquisition, save the tag file
to a new, blank tape or optical disk using Tagging→Manage Tag Files.
2. Label all tapes or optical disks correctly.
To generate a report:
1. Set up the report contents and layout using the Report Setup options in the Reporting menu.
2. Generate a report to the screen, to floppy disk or directly to a printer using the Report Generation
options in the Reporting menu.
3. Label all reports correctly.
3.2 Shortcuts
Various shortcuts are supported by the program to enable you to work more quickly and
efficiently with your data.
February 2000 for version 1.40 21
Quick
Reference

Quick
Reference
3.2 Shortcuts GeoKit User Manual
3.2.1 Key Shortcuts
Many of the common commands can be carried out using key shortcuts. A key shortcut is a single
keystroke or a combination of keystrokes that executes a command.
The key can be used to activate pull-down menus. To do this, press and hold down the
key and then press the key of the underlined letter in the required option in the Menu Bar.
For example, pressing causes the File menu to appear. An item from the pull-down menu
can be selected by pressing the key for the underlined letter of the required menu item’s name.
A list of other key shortcuts can be displayed on screen by selecting Help→Key Shortcuts. The
number of shortcut keys available, however, depends on the software module being used with
the DA System. A few of the most common shortcuts are listed below.
Key To Do This
Annotate currently selected tag node
Reset automatic bottom tracking position using mouse
Make on-screen measurements
Zoom
Toggle pause button. (Pauses scrolling screen)
Dismiss status pop-up window
Some key shortcuts are also listed in the pop-ups; for example, appears in more than
one pop-up. However, note that these shortcuts are only available when the pointer is in the Data
Display Area.
22 February 2000 for version 1.40

Part IV: Operating GeoKit
Operating
GeoKit

Operating
GeoKit
24 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual 4.1 Overview of Using GeoKit
4 Using GeoKit
4.1 Overview of Using GeoKit
See also: Appendix D
We recommend that inexperienced operators spend some time using GeoKit in playback mode
to become familiar with the look and feel of the interface. A sample tape or disk of data acquired
using GeoKit is provided to enable you to become familiar with the system. You should also
refer to Section 4.2 of this manual and Section 6 and Section 7 of the DA System User Manual.
o Switch to GeoKit in the Applications menu.
o Ensure that the data is displayed to the screen. If you are recording data, ensure that it is being
recorded to the correct drive by clicking on the Record button and checking that the appropriate
LED is on. If you are replaying or recording data, the data should be displayed on the
Data Display Area of the screen.
o An event is a feature of interest in the data. It is marked with a tag. In GeoKit, an event can
be a single point (and is therefore marked with a single tag) or can consist of a number of
points (and is therefore marked with a multi-node tag with multiple nodes).
o Use the Setup Tags item in the Tagging menu to define tag types and their placement rules
(that is, measurements which you will be forced to make when placing tags – known as
forced measures). Alternatively, use the same menu item to load a previously saved file of
tag setups to use in the current survey, or to save the current setup for future use. The Tag
Setup pop-up also allows you to assign feature codes to each event which will be logged
automatically to the database when events are marked to the screen.
o Assign the fast tag keys in the Application Specific Area by using the Fast Tag Setup option
in the Tagging menu. Up to 12 fast tags may be allocated to the function keys at the top of
the keyboard, as can the colour they appear on the screen. The tag types which can be added
are those already activated using Tagging→SetupTags. Alternatively, save the current setup
for future use or load a previously saved file of fast tag setups.
o To mark an event, click on the appropriate button in the Fast Tag Area and then tag the event
in the Data Display Area by clicking on it with the left mouse button (see Section 4.2.2), or
if no appropriate fast tag exists, mark it as Unknown (for example, using the R. Mouse Tag
if this is set to Unknown).
o All tagged events are logged to a tag database, allowing the tags to be displayed on data
replay. Once created, tags can be selected and then manipulated, for instance by annotation,
measurement or movement. Any modification to a tag automatically updates its entry in the
tag database. Annotation is a particularly powerful tool, as it allows the tag type to be
changed, dimensions to be measured and text to be associated with the tag.
o The contents of a tag database can also be reported in the form of a body of text (see Section
4.4). The format and contents of the report can be specified by you (see Section 4.5).
4.2 Interactive Tagging with GeoKit
4.2.1 Overview
See also: Section 5.2; Section 4.2.2; Section 4.1; Section 5.5; as well as Sections 10 of the
DA System User Manual
Whereas the DA System is restricted to single tags, allowing events to be marked by a single
point, events covering an area of interest can be marked using the multi-node tags available in
GeoKit. Event reports can also be generated using GeoKit’s additional tagging facilities: principally
tag annotation, movement and measurement. Using the Setup Tags option in the Tagging
menu, you can define a large number of tag types to suit the anomalies in the survey and specify
additional information to be logged to the database for each of those tag types. Once set up, such
February 2000 for version 1.40 25
Operating
GeoKit

Operating
GeoKit
4.2 Interactive Tagging with GeoKit GeoKit User Manual
a file can be saved and used on further surveys. Colour-coded fast tag keys, which can be used
to mark single and multi-node events, are available in the Application Specific Area of the
display screen. The Fast Tag Setup may be customised either by loading a file of previously
saved fast tag definitions, or by changing the definitions of each fast tag key (see Section 5.2.13).
The right mouse button may also have a specific single tag assigned to it via the R. Mouse tab
in the Setup Tags option of the Tagging menu.
The full navigational and position information of the associated ping is stored with each tag node.
Additional information about individual tags can be stored by using the Annotate Tag Node(s)
option in the Tagging menu (see Section 5.2).
4.2.2 Creating Tags in GeoKit
See also: Section 5.5
A suite of specific event markers (fast tags) can be selected from the Application Specific Area
of the GeoKit display. These enhanced tagging features are colour coded for easy identification
on the screen. Select (and deselect) the tag required by clicking the left mouse button on the
appropriate fast tag button, or by pressing the appropriate keyboard function key, and then
moving the mouse pointer (now shaped like a pencil) to the area of interest. Clicking with the
left mouse button will then mark and tag the event with the desired tag type.
When a tag button or label is clicked on in the Fast Tag Area, prior to adding a tag, the appropriate
fast tag button remains depressed and the label is outlined in black. This indicates that this
tag is the pending fast tag. For features where there is a single specific localised area of interest
on the screen (for example mattress, localised debris), a colour-coded square appears on the
screen centred on the point where the left mouse button is released; these are known as single
tags. Tag information, including type and location, is automatically logged to the event database.
Single tags are denoted in the Fast Tag Area by the letter ‘S’ on the fast tag button.
For features which cover an area of screen, multi-node tags are available to allow you to mark
the extent of the feature. These are: boundary tags, which allow you to mark the boundary of the
feature; linear tags, which allow you to mark a linear feature with start and end nodes with internodes
between them. Begin the tag by selecting the fast tag with the mouse or from the keyboard,
and clicking on the Data Display Area to define the position of the first tag node. A tag node will
appear on the screen. The button in the Application Specific Area will stay depressed and its
label will be coloured green to show that the tag is incomplete. You can then click in the Data
Display Area to define additional tag nodes. Complete the multi-node tag either by clicking on
the middle mouse button or by selecting Complete Multi-Node Tag from the Tagging menu. If
the start tag node has not scrolled off the bottom of the screen, the tag will be redrawn with all
the nodes joined together.
In addition there are expanding box tags which allow you to define features in the data by using
a press and drag action to expand the single tag node to the required size.
In Tagging→Setup Tags it is possible to define a set of placement rules that force measurements
to be carried out when tags are placed. In this instance, the crosshair measure pointer will then
appear on the screen and you must make the required measurements before any further tag nodes
can be placed.
When all the required measurements have been made, the pointer will revert to the add mode
pencil pointer, allowing you to place another node of the same type. To cancel the add mode (to
enable other tagging operations) you must deselect the pending fast tag by clicking on its corresponding
button in the Application Specific Area.
When a tag is created, tag information, including event type, location of the start and end nodes
and any required measurements, is automatically logged to the event database. Further
annotation, using the Tagging→Annotate Tag Node(s) menu is outlined in Section 4.2.5.
4.2.2.1 Summary
1. Switch on the Message Window in the Display menu.
2. Select the appropriate fast tag in the Application Specific Area, using either the mouse or the
assigned function key.
26 February 2000 for version 1.40

GeoKit User Manual 4.2 Interactive Tagging with GeoKit
3. Mark the screen (Data Display Area) with this tag by clicking on the location of the event,
and make the required measurements. Single point events (single tags) will require one click,
whereas larger events will require multiple tag selections and clicks to define the location.
4. Make any required measurements to complete the tag.
4.2.3 Selecting and Deselecting Tags
See also: Section 5.1.3
When you wish to manipulate a tag or one of its nodes, you must first put GeoKit in select mode.
You do this by clicking once on a node to select it or by double-clicking on one of the nodes of
a multi-node tag to select the entire tag. The selected node (or nodes) will flash blue and the
pointer in the Data Display Area will change from a PENCIL to an ARROW. The selected node (or
nodes) can then be manipulated (for example, moved, annotated, deleted).
To deselect a node, simply click on it again. The node will cease to flash, indicating that it has
been deselected. To deselect all of the nodes in a selected tag either double-click on any of the
selected nodes or click on a node of a different tag.
4.2.4 Deleting Tags
See also: Section 5.1.3; Section 5.2.2
Key shortcut: or
To delete a tag node, first select the node by clicking on it in the Data Display Area (the selected
node will flash blue), then either select the Delete Tag Node(s) item in the Tagging menu, or
press (for ‘kill’) or on the keyboard. This is not possible when in add mode (see
Section 5.2.2). When the tag has been successfully deleted, the node will disappear from the
display and will be removed from the database. To delete an entire multi-node tag, double-click
over the tag in the display so that all nodes are flashing. Delete the nodes as described above.
When the start node of a multi-node tag is deleted, the next node will automatically be redrawn
as a start node.
4.2.5 Annotating Tags
See also: Section 4.2.3; Section 5.2.6
Key shortcut:
Annotation allows you to add more detailed information to the database entry for a given tag or
selected nodes within the tag. Only a selected node can be annotated (see Section 4.2.3). To
annotate, either select the Annotate Tag Node(s) item from the Tagging menu, or use the
keyboard shortcut , having first ensured that the pointer is in the Data Display Area.
In addition to the information that GeoKit automatically stores about each user-defined tag (tag
type, position, system ID and any previously made measurements), you can use the Dimensions
tab form to include a variety of additional measurements, and the Identity tab form to change the
tag’s name and give the anomaly its own identification number. A description of the feature and
notes about comparison/action may also be added in the Text tab form. In this tab form the tag
may also be marked in the database for further inspection and information can be added about
the geophysicist and quality controller associated with annotating the tag nodes.
You can change this information at any time during acquisition or playback and save the changes
by selecting Update Selected Node to make changes to the selected node alone, or Update All
Tag Nodes to make changes to the entire tag. In addition, the tag name may be changed by
clicking on the Tag Name button and selecting another option from the list which appears. (It
should be noted, however, that tags can only be changed from one single tag to another or from
one multi-node tag type to another of the same type.) Updating the tag file using the Annotate
Tag Node(s) tab form is described in further detail in Section 5.2.6.
February 2000 for version 1.40 27
Operating
GeoKit

Operating
GeoKit
4.3 Customising the Tag Setup GeoKit User Manual
4.2.6 Measuring Tag Dimensions
See also: Section 5.2.6.3; Appendix B; as well as Section 10 of the DA System User Manual
Key shortcuts: , , , , , ,
The following dimensions can be measured with GeoKit:
• length
• width
• height
• depth
• span height
• offset to feature
• true range to fish
Once a tag node is selected, measurements can be performed by pressing the appropriate key
shortcut or clicking on the corresponding button in the Dimensions tab of the Annotation popup
(see Section 5.2.6.3). In addition, the Annotation pop-up allows dimensions to be entered by
hand.
Dimension measures are carried out in the same manner as Processing→Measure (see
Appendix B and also Section 10 of the DA System User Manual). When the crosshair pointer
appears, move to the position defining the start of the measure and press the left mouse button.
Then drag the pointer to the end of the measure and release the button. The measure can be
aborted by re-clicking the appropriate key shortcut. Once a measure is completed, the tag
database is immediately updated.
4.2.7 Moving Tags
See also: Section 5.2.3
Key shortcut:
Tag nodes which have already been placed may be moved using the Tagging→Move Tag
Node(s) menu option. Pressing cuts the selected nodes from the screen. A click with the
left mouse button pastes the nodes back in, the last selected node being positioned at the point of
clicking with the rest of the selected nodes undergoing the same displacement. Prior to pasting,
the move operation can be cancelled by pressing the key shortcut again.
4.3 Customising the Tag Setup
See also: Section 5.2.9; Section 5.2.13; Section 5.5; Section 5.5.1; Appendix D
4.3.1 Setting up Tag Lists
See also: Appendix D
To give GeoKit users a high degree of flexibility, the names, codes and properties (that is tag
identity) can be customised for each survey. For each tag type available, there is a tab in the
Tagging→Setup Tags pop-up defining a list of all possible tag identities.
•Note: The tag setup should be defined during mobilisation and before commencing data interpretation,
since making modifications during interpretation may lead to inconsistencies in data
storage and reporting.
To make a tag available (for example, for fast tagging and reporting purposes), the tag should be
activated via the Tag Active button (up to 255 separate active tag identities are possible per tag
type). Tags other than System tags can also be activated by double-clicking on the tag name in
the list of Tag Names or by hitting in one of the text fields when the tag is selected in
the list. You can also assign a unique Tag Name and tag Incident Code.
Within the tab form, you can also define the Tag Properties for a tag (for example, Forced User
Measures) which are followed when the tag is placed. The Message Window (selected from the
Display menu) will indicate which measurements, if any, must be made when tag nodes are
placed in the data.
28 February 2000 for version 1.40

GeoKit User Manual 4.4 Reporting Tagged Events
The Tag Setup pop-up also has two further tabs, for System tag setup and R. Mouse tag setup.
In the System tab, you can set up the incident codes and system tag colours. Within the GeoKit
application, the only system tag that will have an effect is the Fix Line tag. In the R. Mouse tag
tab, you can pick from the full list of active single tags in order to assign a tag identity to the right
mouse button click.
To use a previously saved file of tag setups, for example to ensure consistency with previous
reports, click on the Load button at the bottom of the Tag Setup pop-up. This will produce a
Load Settings pop-up listing all of the available tag setups which may be loaded, together with
a button for loading the Default tag setup. To load a file, click on the file name and confirm by
clicking on OK.
Changes made to the Tag Setup may be saved for future use by clicking the Save option. This
will produce a Save Settings pop-up, allowing you to specify the name of the file in the File
Name text-entry box. Alternatively, an existing tag setup can be overwritten by selecting one
from the current list. This pop-up also allows you to allocate the current tag setup as the default
by clicking on the Make Default button.
Once all modifications have been made to the Tag Setup, click on OK. Any changes which were
made to the Tag Setup will be applied to the Report Setup and will therefore affect subsequent
report generation. In addition, the labels will change on the appropriate fast tag keys in the Application
Specific Area.
•Note: Tag setups are not stored to the tag database. Thus if the tagging and reporting options
are to contain the correct tag names and incident codes, the correct Tag Setup file should always
be loaded.
4.3.2 Setting up Fast Tags
See also: Appendix D
The Fast Tag Area is provided to allow you to quickly place tags in the Data Display Area. The
Fast Tag Setup can be customised, to specify a setup for each survey. Typically, tags chosen to
be fast tags are those most likely to be accessed during the survey. Up to 12 fast tags may be
assigned.
Clicking on Tagging→Fast Tag Setup produces the Fast Tag Setup pop-up. This pop-up
displays a list of all the current fast tags, plus their fast tag colour. To change the fast tag colour,
click on the coloured option button and drag the pointer over the new colour. To add a new fast
tag, click on the Add Tag button and select a tag from the list of all active tags. To delete a fast
tag, select the fast tag by clicking on it and then click on the Delete Tag button.
As with the Tag Setup, fast tag setups can be both saved and loaded. Once all modifications have
been made to the Fast Tag Setup, you should click on OK.
4.4 Reporting Tagged Events
See also: Section 5.3.2
Tag database files are in binary, machine-readable format to allow them to be read and interpreted
rapidly by GeoKit. To generate an on-screen, floppy disk or hardcopy tag database report
in ASCII format (as defined by the Report Setup):
1. Open the Reporting→Report Generation pop-up.
2. Select the tag file for which you wish to generate a report.
3. Choose between Text Window, Printer and Floppy Disk output.
Selection of the Text Window option will cause the completed report to be displayed in a
window on GeoKit screen, allowing you to browse through it. The Printer option causes the
report to be output to the printer defined by the Printer Setup pop-up. Floppy output of the
report requires a blank DOS-formatted floppy disk to be present in the floppy disk drive, and
saves the report to the disk, allowing it to be imported by database, spreadsheet or word
processing packages.
4. Click on the Generate Report button to produce the report.
February 2000 for version 1.40 29
Operating
GeoKit

Operating
GeoKit
4.5 Customising the Report Setup GeoKit User Manual
5. Exit the pop-up by clicking on Done.
•Note: The length of file which can be displayed in a Text Window report is limited to 2000 entries.
•Note: Copying the report file to floppy disk will take much longer if the system is being used for
playback or acquisition at the same time. To complete the report generation on floppy disk as
quickly as possible, pause the screen until the report output to floppy has been completed.
4.5 Customising the Report Setup
See also: Section 5.3.1; Appendix D
By using the Report Setup option of the Reporting menu, you can define the information to be
included in subsequent reports and how the data will be presented. Within the Report Setup, the
Format can be defined by adding and deleting columns and specifying their contents, including
the Label for the columns, the column Width, and the Precision with which the data will be
reported (that is the number of decimal places to be included). Scrolling down the pop-up allows
the details of each column of the report to be checked.
The Options tab form allows you to define details of labelling and separating columns, how
multi-node tags will be reported, the presentation of text strings and how the report will be sorted.
In the Contents tab form, you can specify which tags should be included in the report.
To use a previously saved file of report format setups, thus ensuring consistent reporting between
surveys, use the Load button. Clicking on this button will produce a list of files which may be
selected from the appropriate directory. To select a default file, click on either the Select Default
(your default) or Select Factory Default button. To select a file, click on the file name and
confirm by clicking on OK.
Changes made to the Report Setup may be saved for future use by using the Save button.
Clicking on the Save button will produce a pop-up showing the appropriate directory and file
extension for saving the file. To name the file, place the pointer in the File Name text-entry box
and type the file name and extension after the pathway provided by GeoKit. To make the report
setup the default setup, click on the Make Default button.
When all the changes to the Report Setup have been made, click on OK.
30 February 2000 for version 1.40

Part V: Reference Guide
Reference
Guide

Reference
Guide
32 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual 5.1 Tagging
5 Menu Reference
5.1 Tagging
See also: Section 4.2; Section 4.3; Section 5.2; Section 5.2.9; as well as Section 10 of the DA
System User Manual
A tag is an entity used to mark events which occur in the data. Each tag may consist of a single
point (used, for example, to mark a small target on the seabed) or may be composed of multiple
points (used, for example, to mark a linear feature). One tag may be used to mark an event that
crosses from one data channel to the other. Individual points within a tag are known as tag nodes;
a tag which consists of more than one node is known as a multi-node tag. The first node placed
in the tag is known as the creator node.
Tag nodes appear as small, coloured symbols overlying the point in the data where the event was
marked. Different types of tags have different symbols, (see Figure 5-1, this page). You can
define up to 255 different tag identities for each of the available tag types (see Section 5.2.9).
Tagging can be performed during either acquisition or data playback. Once tags have been
created for a data set, they are saved to the database and can be replayed as required (see Section
10 of the DA System User Manual).
5.1.1 Tag Types
Single, linear, boundary and expanded box tags are available in GeoKit, as well as system and
right mouse tags; dual tags are NOT available. Figure 5-1, this page, shows the symbols which
are used to create the various types of tags.
Single Tag Node Start Node End Node
Inter Node Expanding Tag Node Creator Node
Figure 5-1 Symbols of Tag Types Available in GeoKit
5.1.1.1 Single Tags
See also: Section 5.2.12
Figure 5-2 Single Tag
Single tags are markers for single point events which can be represented by a one-node tag; for
example, anodes and pock marks on the seabed. Single tags are the only type of tag which can
be set as the right mouse button tag (see Section 5.2.12).
February 2000 for version 1.40 33
Reference
Guide

Reference
Guide
5.1 Tagging GeoKit User Manual
5.1.1.2 Linear Tags
Figure 5-3 Linear Tag
Linear tags consist of a start node and an end node, between which there may be any number of
inter-nodes; links are drawn by GeoKit to connect the tag nodes. Linear tags can be used for long
events, such as seismic horizons and pipe crossings.
5.1.1.3 Boundary Tags
See also: Section 5.2.5
Figure 5-4 Boundary Tag
Boundary tags allow you to define events which form areas within the data, such as visibly
distinct areas of differing seafloor sediment. They are multi-node tags consisting entirely of
inter-nodes. When first placed, boundary tags are unclosed. However, once at least three tag
nodes have been placed, the boundary may be closed by linking the first node to the last (see
Section 5.2.5).
The contents of an area surrounded by a boundary tag may be defined by creating single tags
inside the boundary.
34 February 2000 for version 1.40

GeoKit User Manual 5.1 Tagging
5.1.1.4 Expanding Box Tags
Figure 5-5 Expanding Box Tag
Like single tags, expanding box tags have a single node. However, the press and drag action used
to place them allows you to expand a box which defines the extent of the tag. The tag node is
indicated by a cross symbol in the drawing area. Expanding box tags can be used to mark and
define the extent of targets in the data.
5.1.2 Tagging Modes
GeoKit has two distinct tagging modes, each of which is detailed below.
5.1.2.1 Add Mode
This mode allows you to place tag nodes of the desired type. Add mode is indicated by the pointer
in the Data Display Area changing from the usual ARROW to a PENCIL. You can change from
select mode to add mode by clicking on one of the fast tag buttons in the Fast Tag Area, or by
pressing the appropriate function key. A tag node with this identity can then be placed in the Data
Display Area. Once the tag node is placed, the system remains in add mode, allowing you to add
more nodes of the same identity by clicking with the left mouse button. To cancel add mode,
deselect the pending tag placement by clicking on the appropriate fast tag button, or by pressing
the appropriate function key.
Note that, whilst the last node placed in add mode is always made the selected node, this
selection cannot be changed until select mode is active.
5.1.2.2 Select Mode
See also: Section 5.2.12
Select mode allows nodes to be marked for subsequent tag operations and manipulation, for
example annotation, deletion, and moving. It also prevents the addition of tag nodes other than
right mouse tag nodes (see Section 5.2.12).
You can change from add mode to select mode in one of two ways. You can select
Tagging→Add Tag Node(s), or you can select the pending tag – as displayed by a black
rectangle in the Fast Tag Area – either by clicking on the fast tag button or by pressing the appropriate
function key.
Select mode is indicated by an arrow pointer in the Data Display Area. A tag node may be
selected by clicking on the node with the left mouse button. Multi-node tags may have any
number of their nodes selected. Selected tag nodes flash between their normal colour and light
blue.
5.1.3 Selecting and Deselecting Tag Nodes
See also: Section 5.1.2.2; Section 5.2.2; Section 5.2.3; Section 5.2.6
Once a tag node has been placed, you may wish to manipulate it. For instance, a node may need
to be moved or deleted (see Section 5.2.3, Section 5.2.2). Alternatively, you may wish to update
some of a node’s parameters and therefore will need to use the Annotate Tag Node(s) pop-up
(see Section 5.2.6).
February 2000 for version 1.40 35
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
Nodes can only be manipulated if they are selected. They cannot be selected when GeoKit is in
add mode; GeoKit must be in select mode (see Section 5.1.2.2).
5.1.3.1 Selecting Tag Nodes
See also: Section 5.2.2; Section 5.2.3; Section 5.2.6
Once GeoKit is in select mode, any node in a tag may be selected. Position the arrow pointer over
the desired node in the Data Display Area and click with the left mouse button. A selected node
will flash between its usual tag colour and light blue. If the tag is a multi-node tag, additional
nodes may also be selected within the same tag. Multiple node selections are not possible when
the nodes come from different tags.
If all the nodes in a multi-node tag are required for selection, a shortcut is provided: double-click
over an unselected node. The entire tag will be selected, including any nodes off screen at the
time of selection.
Once all the required nodes have been selected, you can perform tag manipulations, such as
moving or deleting the tag or nodes. If you wish to annotate nodes, each node must be selected
separately, as it is not possible to annotate more than one node at a time.
5.1.3.2 Deselecting Tag Nodes
A selected node can be deselected simply by clicking on it. The node will cease to flash,
indicating that it has been deselected. All of the nodes in a tag can be deselected either by doubleclicking
on any of the tag’s selected nodes or by selecting a node in a different tag.
•Note: When selected nodes scroll off the display they remain selected, but will be deselected
automatically once the last selected node in the tag scrolls off screen.
5.1.4 Replaying Tags
See also: Section 5.2.7; Section 5.2.8; Appendix E; as well as Section 10 of the DA System
User Manual
GeoKit automatically labels each sonar data file on a Coda format data tape or optical disk with
the file name of its associated tag file. If the selected tag file is in the tag file directory of the
system hard disk or optical disk, the tags in the file will automatically be replayed along with the
data from the tape or optical disk during playback. Loading tag files from tape, saving tag files
to tape, and copying tag files to and from optical disk are described in Section 10 of the DA
System User Manual.
If the Overlay Data toggle in the Display menu is on, then the tags will be overlaid on the sonar
data. If this toggle is off, the tags are still read from the file but are not displayed to the screen.
5.2 The Tagging Menu
This menu contains the facilities for creating and deleting tags, and for manipulating tag files.
Figure 5-6 The Tagging Menu
36 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
5.2.1 Add Tag Node(s)
See also: Section 2.3; Section 4.2.2; Section 5.2.12
Selecting this menu item causes the mouse pointer to change from an arrow to a pencil (see
Section 2.3); if the pencil is placed on the display area and the left mouse button pressed, a tag
node will be marked. The tag type will always be that of the right mouse tag. If the menu item
has been selected but no tagging is required, or if no further tags are to be added, reselection of
the Add Tag Node(s) menu item will cause the pencil pointer to be replaced by the usual mouse
pointer; the tagging operation will be abandoned.
Single tags can also be added without the use of the Tagging menu, by positioning the mouse
pointer as required in the display area and pressing the right mouse button. However, performing
tagging in this way does not leave the system in add mode. The tag type added can be set up via
the R. Mouse tab of the Tag Setup pop-up (see Section 5.2.12).
•Note: It is only possible to add tags if the data is recorded in Coda format.
5.2.2 Delete Tag Node(s)
See also: Section 4.2.4; Section 5.1.2.1
Key shortcut: or
Selection of this menu item, or the letter (for kill) or the key on the keyboard,
deletes all the selected nodes from both the Data Display Area and the tag database. You can
therefore decide whether to delete an entire tag or just one of its nodes. After deleting the selected
node or nodes, there will be no tag nodes selected.
If Delete Tag Node(s) is selected but no tag nodes are selected, a warning will appear in the
message bar: ‘No nodes currently selected’.
It is not possible to delete a tag or nodes when GeoKit is in add mode, even though the last tag
node added is a selected node (see Section 5.1.2.1).
5.2.3 Move Tag Node(s)
See also: Section 2.3; Section 4.2.7; Section 5.1.3.1
Key shortcut:
Move Tag Node(s) allows you to move one or more tag nodes to a different position in the
display. The function may be selected from the Tagging menu, or by using the keyboard shortcut
key .
Tag nodes must be selected before they can be moved (see Section 5.1.3.1). If Move Tag
Node(s) is selected but no tag nodes are selected, a warning will appear in the display area: ‘No
nodes currently selected’.
The move operation consists of two stages. First, the selected nodes are removed from the
display area and the tag database. The pointer changes to the move pointer (see Section 2.3).
Then the selected nodes are pasted back into the display area. This is done by moving the pointer
to the required point and clicking with the left mouse button. If a single node has been moved, it
will be repositioned at this point. If multiple nodes have been moved, this will be the point of
reinsertion of the last node selected prior to the move. The other nodes selected are moved with
the same relative displacement as this node. (Nodes selected by double-clicking will be moved
relative to the node which was double-clicked on.)
•Note: If an entire tag is to be moved, it is moved relative to the pointer position of the last node
selected or the last node double-clicked on. If a further move is attempted without reselecting the
nodes, the system will automatically reselect all the nodes from the original move. After the move,
the node placed at the pointer position will be the end node of the tag.
Once the move has been completed, the last selection will remain active to allow further actions
(for example, measurements) to be taken.
Currently tag nodes may only be moved within the same data channel; if the new position for any
of the tag node(s) is outwith the valid area of the display, you will hear a warning beep. The move
pointer will remain until the tag node(s) are repositioned correctly. Similarly, a move which
February 2000 for version 1.40 37
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
would result in any of the selected tag nodes being placed off screen is not permitted and you
will be warned that the move is not possible. The move pointer will remain until the nodes are
repositioned correctly.
A move may be cancelled and the selected nodes returned to their original positions by selecting
Move Tag Node(s) or by pressing the shortcut key again.
5.2.4 Insert/Append Tag Node
See also: Section 5.5.1
Key shortcut:
This menu item allows additional nodes to be appended to linear or incomplete boundary tags. It
also allows a new node to be created between two adjacent nodes in a linear or boundary tag.
5.2.4.1 Append Tag Node
To append nodes, the system must be in select mode, with either the start or end node of the linear
or incomplete boundary tag selected. Selecting the Insert/Append Tag Node option switches the
system into one of two add modes, depending on whether the selected tag is a fast tag or not.
• fast tag add mode: for an incomplete fast tag with the end node selected, clicking the left
mouse button appends a tag and the system remains in add mode.
• append add mode: for non-fast tags, clicking the left mouse button appends a node and the
system reverts to select mode.
An append operation may be cancelled by pressing the shortcut key in append add mode, or
by clicking on the appropriate fast tag button if in fast tag add mode.
5.2.4.2 Insert Tag Node
To insert nodes in a multi-node tag, the system must be in select mode, with two adjacent nodes
selected. Selecting the Insert/Append Tag Node option will put the system in add mode. After
clicking the left mouse button at the required position for the inserted node, the system will return
to select mode. The newly inserted node will remain selected.
An insert operation my be cancelled by pressing the shortcut key in add mode.
5.2.5 Complete Multi-Node Tag
See also: Section 5.5
When in select mode, this menu item allows the selected boundary tag to be closed, provided that
the tag consists of at least three nodes. The entire tag does not have to be visible on the display
to be closed, nor are there any restrictions as to which node in the boundary tag must be selected
to allow the tag to be closed.
In add mode, if the current tag is a boundary tag, it may be closed by clicking with the middle
mouse button. This will complete the tag without adding a node beneath the pointer on the
display. The status of the pending fast tag label in the Application Specific Area will change from
green to black, indicating that the tag has been completed (see Section 5.5).
5.2.6 Annotate Tag Node(s)
See also: Section 5.1.3.1
Key shortcut:
This option allows you to update the data associated with the selected tag node. To access the
option, you must first have selected a node within a tag (see Section 5.1.3.1).
The tab form displayed when the Annotate Tag Node(s) window is popped up contains four
tabs, allowing different fields of information to be updated.
When all the required annotation has been completed, the changes can be accepted in one of two
ways. Clicking on Update Selected Node will apply all changes to the selected tag node alone
and will dismiss the Annotate Tag Node(s) pop-up. (The exception to this rule is the case where
38 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
the Tag Name is changed, and is therefore given a new tag identity, when all nodes in the tag are
given the new tag name.) Alternatively, clicking on Update All Tag Nodes applies the changes
made to all the nodes within the tag, including nodes off screen and also dismisses the Annotate
Tag Node(s) window.
•Note: Changes are always made to both the database and the screen representations of tag
nodes.
If the Annotate Tag Node(s) window is on screen when a selected node is about to scroll off
screen, the display will pause automatically to allow you to complete the annotation. If pause is
released and the tag node scrolls off screen, the Annotate Tag Node(s) pop-up is dismissed,
losing any unsaved annotation.
It is possible to display more than one annotate pop-up on screen at a time by selecting another
tag node and then clicking on Annotate Tag Node(s) before dismissing the previous Annotate
Tag Node(s) pop-up.
5.2.6.1 Node Identity Tab Form
Figure 5-7 The Node Identity Tab Form
The node identity tab form of the Annotate Tag Node(s) pop-up allows you to change the Tag
Name and the tag node Anomaly Number. It lists further information associated with the tag
node, namely Incident Code, System ID and Tag File name.
To change the Tag Name (and therefore the tag identity), click on the button displaying the
current Tag Name. A list of the available options will appear. This list will always contain all the
active tags of this tag type. (For this reason it is not possible to change tag types.) The new name
may then be selected by clicking on the chosen Tag Name. When the Update All Tag Nodes
button is pressed, the change will be applied to all nodes within that tag and, if visible in the
display, the tag will be redrawn in the new tag colour.
Where the Anomaly Number is to be changed, the changes should be typed in the text field. The
Anomaly Number field is provided to let you associate a unique identifier with each tag node.
February 2000 for version 1.40 39
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
5.2.6.2 Node Position Tab Form
See also: Section 5.2.3
Figure 5-8 : The Node Position Tab Form
The node position tab form details the positional parameters associated with the tag node. It is
provided solely for information and QC purposes, since the position of nodes can only be altered
using the Move Tag Nodes(s) option of the Tagging menu (see Section 5.2.3).
Raw nav position data is displayed on the left of the tab form, while corrected nav data (if
available) is displayed on the right.
5.2.6.3 Node Dimensions Tab Form
See also: Section 2.3; Section 4.2.6; Appendix A; Appendix B; Appendix C; as well as
Section 8.6 of the DA System User Manual
Key shortcuts: ; ; ; ; ; ;
The Dimensions tab form allows you to update the dimensions of the tag for the node. It contains
five frames, each with a button allowing you to make the relevant measurement. The top, right
frame button allows you to choose whether to measure the Height, Depth or Span of the object.
The default is Height, but the type of measurement selected will remain until changed by you.
(When sub-bottom data is being annotated, the Height field becomes a Depth to Horizon field,
making the Height and Span options unavailable.) Each of the five frames also contains a text
field which allows you to enter a value manually.
Figure 5-9 The Node Dimensions Tab Form
40 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
Measure
Clicking on the Measure button beside any of the dimensions on the form will indent the button
and cause the pointer in the Data Display Area to change from an arrow to the crosshair pointer
(see Section 2.3). You can then measure the dimension in the display area in the same manner as
a Processing→Measure operation (see Appendix B, and Section 8.6 of the DA System User
Manual), using the mouse button to press and drag. Once the measurement is completed, the
measurement is displayed in the text field and the Measure button is no longer indented. (The
start and end positions of the measure will be saved to the tag database immediately, regardless
of whether one of the Update buttons is pressed.) This allows corrected nav to be applied to the
dimensions at a later date.
To cancel a measure operation, press the indented Measure button, or press the Measure button
in another area of the form. The latter will cancel the first measure and initiate the measure in the
second area of the form.
Using the dimension shortcut keys will also affect the status of a Measure button (see Section
4.2.6). For example, if a Length measure is under way, with the Measure button indented in the
usual way, and the key is pressed, the measure will be cancelled and the Measure button will
revert to its unselected state. Similarly if no measurements are selected and a shortcut key is used,
the appropriate Measure button will indent as if the button had been pressed. You should
continue to measure in the usual way.
Measurements made in this manner are stored internally as two end points and automatically get
distance values recalculated whenever the value is displayed in the system or output to a report.
This means that changing any navigation parameters via corrected nav will cause the distance
values to be updated (see Section 6.6 of the DA System User Manual). This implies that measurements
can be placed on raw data, and then prior to generating a report, a corrected nav file can
be loaded to obtain the most accurate measurement values. When a report is generated, those nav
parameters that have been corrected and used to calculate a measurement value can be indicated
in the report. This allows the integrity of measurement values to be monitored (see Appendix A
and Appendix C).
Dimensions Using Text Entry
The node’s dimensions may also be changed by typing an entry in the appropriate text field.
However, such a value will not have the necessary associated positional information to allow
navigation correction to be applied in the future.
5.2.6.4 Node Text Tab Form
Figure 5-10 The Node Text Tab Form
This form contains text fields allowing you to add comments about the feature being annotated.
For the Description and Comparison/Action fields, the text entry can be scrolled through using
the scroll bar at the side of each of the text entry boxes. Also included are an on/off toggle to
allow you to indicate where Further Inspection is required; and two single line text fields for
entering the names of the Geo and QC.
February 2000 for version 1.40 41
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
5.2.7 Manage Tag Files (tape system)
See also: Appendix E
The Manage Tag Files menu item allows you to organise the many tag files which are created
during a survey. If you are using a tape system, selecting this menu item produces the Tag
Database Management pop-up shown in Figure 5-11, this page. If you are using an optical disk
system, see Section 5.2.8.
Figure 5-11 Tag Database Management Pop-up Window
GeoKit automatically names tag files according to the date and time when recording data began
(that is ddmmyy.hhmmss). The file structure of the Coda system is explained in Section 14.5 of
the DA System User Manual.
The Database Location option button allows you to select the drive on which to locate the tag
files you wish to save, load or delete.
When the Tag Database Management pop-up is opened, the default tag file selection is the
current tag file and this is the file highlighted on the list. The scroll bar can be used to move up
or down the list of Tag Files. A tag file can be selected by clicking on it with the left mouse
button. To make a multiple selection, either press and drag the pointer to highlight adjacent files
or hold down while clicking on specific file names.
The pop-up also displays the amount of space available on the hard disk. Each tag database entry
uses about 2KB of file space.
The Store and Factory buttons currently have no function in the tape system.
5.2.7.1 Tape Load/Save
Figure 5-12 The Load/Save Tags to Tape Pop-up Window
This pop-up allows you to load tag files from tape to hard disk, save tag files to tape and also to
list tag files which have been saved to tape previously. For single tape systems, tag files cannot
be accessed on tape while the tape drive is being used for any other purpose (that is data acquisition
or playback).
•Note: Tag files and sonar data should be saved to different tapes to prevent data being accidentally
overwritten.
42 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
Saving Batches
When tag files are saved, each separate save writes a batch of tag files to the tape. The batch
contains the highlighted tag files in the Tag Database Management pop-up and can therefore
contain one or more tag files. Batches can be saved to the tape one after another, but tag files can
be loaded only one batch at a time. Thus, if three tag files were saved as three separate batches,
all three files would have to be loaded individually, whereas if they were saved as a batch
consisting of the three files, they could be loaded together using the Load Batch option. There
is no limit to the number of tag files which can be saved as a single batch.
Tag files are selected for Save by clicking the left mouse button on the tag file name in the list
of tag files. If more than one tag file is to be saved, either press and drag the left mouse button to
highlight a group of tags, or hold down while clicking on the tag file names to add
more tag files to a group.
Listing Batches
Figure 5-13 : The Batch File List Pop-up Window
Batches are read and written to tape sequentially; after a batch has been saved, the tape is
therefore positioned at the end of that batch. To verify that a batch of newly saved tag files
contains the appropriate files, the List Prev Batch option should be used. All the batches on a
tape can be listed by clicking on the List All Batches button. This is useful for determining which
batch on a tape contains the required tag file.
•Note: Listing a batch causes the batch to be read but not loaded. The tape is therefore left at the
end of a batch after a list request.
Tape Movement
The Tape Movement commands in the pop-up can be used to move backwards or forwards
through successive batches.
Loading Batches
See also: Section 5.3.2
A batch of tag files can be loaded from tape using the Load Batch option. If this is selected, a
pop-up appears with the message ‘Insert tape in tape drive 1 and press OK’ (or tape drive 2,
depending on which tape drive is available). GeoKit then loads a batch of tag files from the tape
drive into the tag file directory on the system hard disk, and indicates that this is taking place.
•Note: If any of the tag files on the tape have the same name as those already in the GeoKit tag
file directory, they will overwrite the files on the hard disk.
The tag database files are saved in binary, machine-readable format using this command. To
access the database in an ASCII format suitable for import into spreadsheets, databases and word
processing packages, use the Report Generation option (see Section 5.3.2).
February 2000 for version 1.40 43
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
Load/Save Command Summary
• Load Batch loads the batch file recorded at the current tape position.
• Load Remote allows a tag file to be loaded from another GeoKit system on the same
Ethernet network. Contact Coda Technologies for further information.
Figure 5-14 : The Load Remote Tag File Pop-up Window
• List Batch lists the batches on a tape before loading. Before using this option, the tape must
be rewound. When the tag file details have been checked, the pop-up is dismissed by clicking
on the Dismiss button at the bottom of the Batch File List pop-up.
• List Previous Batch displays details of the previous batch of tag files on the tape, relative to
the current tape position.
• List All Batches displays details of all the batches of tag files on the tape.
• Save Batch Overwrite saves a batch file, overwriting any data already on the tape. The tape
is automatically rewound to the beginning before saving the batch.
• Save Batch Append saves a batch file to the end of existing data on the tape. The tape is
wound forward automatically to the end of any data on the tape before the batch is saved.
• Rewind rewinds the tag file tape to the beginning.
• Next Batch moves the tape forward by one batch to the start of the next batch.
• Previous Batch moves the tape backward by one batch to the start of the previous batch.
5.2.7.2 Delete
See also: Section 5.2.7.1; Appendix E
If tag files are no longer required, or if they have been saved to tape, they may be deleted from
the tag file directory on the hard disk of the DA System. The selection process is as outlined in
Save (see Section 5.2.7.1).
Make single selections by clicking the left mouse button, and multiple selections by either
clicking and dragging or by clicking with held down. Once the selection process has
been completed, click on the Delete menu item. A pop-up will appear, to ask ‘Are you sure?’; if
you click on Yes, the highlighted tag files will be deleted. Any tags currently on the screen which
were in the deleted tag files will be automatically removed from the screen.
5.2.7.3 Rescan
See also: Section 5.2.7
Rescan causes the directory entries of the tag file directory on the system hard disk to be re-read,
updating the list of tag files in the Tag Database Management window (see Section 5.2.7). This
should be carried out after loading or deleting tag files, as described above.
44 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
5.2.8 Manage Tag Files (optical disk system)
See also: Appendix E
Figure 5-15 Tag Database Management Pop-up Window
If you are using an optical disk system, selecting the Manage Tag Files menu item produces the
Tag Database Management pop-up shown in Figure 5-15, this page. It allows you to organise
the many tag files which are created during a survey.
GeoKit automatically names tag files according to the date and time when recording data began
(that is ddmmyy.hhmmss). The file structure of the Coda system is explained in Section 14.5 of
the DA System User Manual.
The Database Location option selection button displays the drive on which the tag files will be
created. (A list of files on that drive is displayed in the Tag Files window.) It is also the drive
from which files will be deleted and the source for files to be copied. In Figure 5-15, this page,
Database Location is set to Optical 1. Clicking on the option button displays the other options
available: Optical 2 (in a dual drive system) and Hard Disk.
The Tag Files window displays all the tag files that appear on the selected database location. A
tag file can be selected by clicking on it with the left mouse button. To make a multiple selection,
either press and drag the pointer to highlight adjacent files or hold down while
clicking on specific file name. The scroll bar can be used to move up or down the list.
The pop-up also displays the amount of space available on the hard disk. Each tag database entry
uses about 2KB of file space.
The Store action button at the bottom of the pop-up gives you the option of storing the currently
selected database location as the default location. Clicking on the Factory button will restore the
database location to Hard Disk.
5.2.8.1 Copy Tag Files
Figure 5-16 Copy Tag Files Pop-up Window
The Copy Tag Files pop-up lets you select the target drive for the tag files that you wish to copy
and to direct the system to copy those files from the source database location to the target drive.
To copy tag files, you must first have selected the source drive (Database Location) of the tag
files that you wish to copy and have highlighted the relevant tag files from the list in the Tag
Files window. Clicking on the Copy Tag Files button produces the Copy Tag Files pop-up. The
target drive for the tag files can be selected using the Copy selected files to: option selection
February 2000 for version 1.40 45
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
button; the options available are Hard Disk, Optical 1, and Optical 2 (in a dual drive system).
When you click on the OK button, the system automatically copies the files from the source
database location to the target drive. To check that the tag files have been copied to the new
location, you can select the new database location and see that the tag files appear in the Tag
Files window.
5.2.8.2 Delete
The procedure for deleting tag files is similar to that of copying tag files. First, the source of the
tag files must be selected in the Tag Database Management pop-up, using the Database
Location option selection button. Then, the files that you want to delete must be selected from
the list that appears in the Tag Files window. Clicking on the Delete button then deletes the files
from the database.
5.2.8.3 Rescan
This button updates the list of files in the Tag Files window and the disk space available either
on the hard disk or on the selected optical disk. This can be carried out after copying or deleting
tag files, as described above.
5.2.8.4 Unmount
This button directs the optical disk drive to unmount the disk. It must be selected before the
optical disk can be ejected from the optical disk drive.
5.2.9 Setup Tags
See also: Section 5.2.13; Section 5.3.1.3; Appendix D
•Note: The tag setup should be defined before commencing data interpretation, since making
modifications during interpretation may lead to inconsistencies in data storage and reporting.
Figure 5-17 The Setup Tags Pop-up Window
The Tag Setup pop-up allows you to define lists of tags for each of the tag types available in
GeoKit, including System tags, User Defined tags, and the Right Mouse tag. Dual tags are not
available in GeoKit; they are available only in the CODA-PI100 Pipeline Inspection module.
As shown in Figure 5-17, page 46, clicking on the tab for a tag type produces a form which allows
you to activate or deactivate tags (except for System tags). The Tag Name and Tag Code
(incident code) lists are dual scrolling lists (see Section 2.2.11). This ensures that a tag name and
code always follow one another when either item is selected. In addition, for user tags there is a
set of definable properties. Where certain properties are not applicable to a particular tag type,
46 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
the property is greyed out. Changes made to a tag setup within this pop-up will also, where applicable,
be applied to the setups for fast tags (see Section 5.2.13) or report contents (see Section
5.3.1.3).
The pop-up action buttons (for example OK, Apply) function in the usual way (see Section
2.2.5), but it is important to realise that the entire Tag Setup will be affected by their action, not
just the tab form visible on the screen at the time. This allows you to create a single composite
tag setup for the survey rather than a number of individual setups.
5.2.10 Tag Activation
See also: Appendix D
5.2.10.1 Tag Active
See also: Section 5.2.9; Section 5.2.13; Section 5.3.1.3
This on/off toggle allows you to switch each tag type on or off for the current survey. Active tags,
indicated in bold text in the list of tag names (see Section 5.2.9) are those which are available for
use in the survey. This also makes them available in the Fast Tag Setup and Report Contents
pop-up windows (see Section 5.2.13, and Section 5.3.1.3).
Tags (other than System tags) may also be activated or deactivated by double-clicking on the
tag name in the list of Tag Names appearing in the Tag Setup pop-up; or by hitting
in one of the text fields when the tag is selected in the list.
•Note: If a tag is not activated in the tag setup, it will be named ‘Unknown’.
5.2.10.2 Tag Name and Incident Code
When a tag is selected from the scrolling list in this area of the pop-up, the name and associated
code will appear in the text fields below the lists. You may change either or both by entering text
in place of the labels provided in the text-entry boxes. The text in a box is confirmed by hitting
, although the appropriate pop-up action button must be pressed to apply or save the
Tag Setup. Selecting a new item in the list will update the previous item with the value in the
Tag Name and Tag Code text fields.
Each tag name and code for a particular tag type must be unique, as GeoKit will not accept duplicates,
nor will it accept blank fields. It is possible to give two tags the same name, but only if
these are different tag types (for example, the tag name ‘Support’ could be allocated to tags
where one was a single tag and the other a linear tag).
February 2000 for version 1.40 47
Reference
Guide

Reference
Guide
5.2 The Tagging Menu GeoKit User Manual
5.2.11 System Tag Setup
See also: Section 5.2.9
Figure 5-18 The System Tag Tab Form
System Tags are tags automatically generated by the system and cannot be added manually. They
are set up in the same way as User Defined tags (see Section 5.2.9). The tag types available in
the dual scrolling list may be from any of the tag types available with GeoKit, each of these
having specific functions within the system. A Fix Line, for example, is an example of a special
system single tag. It is important to realise that if you change the name of a system tag, this may
disguise the nature of its function within the system. For this reason changes to system tag names
and codes cannot be saved.
An additional feature in the System Tag tab is the Tag Colour option button. Pressing and
dragging on this button allows you to select the colours for each system tag type. In GeoKit, only
alterations to the Fix Line System Tag will have an effect; all other system tags are used in the
CODA-PI100.
5.2.12 Right Mouse Tag
Figure 5-19 : The Right Mouse Tag Tab Form
48 February 2000 for version 1.40

GeoKit User Manual 5.2 The Tagging Menu
The right mouse tag is the tag node placed by clicking the right mouse button over the data area
of the display. By default this is an ‘Unknown’ single tag type, but you may instead select one
of the previously activated single tags.
The Right Mouse Tag form always displays a scrolling list of tag names and incident codes
corresponding to each of the active single tags set up using the Setup Tags pop-up, plus one
‘Unknown’ tag. There can only be one active right mouse tag, as activating a new tag will
deactivate the previous right mouse tag. It does not alter any other Tag Setup settings. If the tag
selected as the right mouse tag is subsequently deactivated via the Single tag tab form, the right
mouse tag reverts to the default ‘Unknown’ type.
5.2.13 Fast Tag Setup
See also: Section 5.2.9
Figure 5-20 The Fast Tag Setup Pop-up Window
Fast Tag Setup allows you to specify which of the active tags previously set up using the
Tagging→Setup Tags options are to be used as fast tags (see Section 5.2.9). Alongside each of
the 12 fast tag buttons is the tag name assigned by you to the button and an abbreviation
indicating the tag type. This pop-up also allows you to define the colour in which these tags will
appear on the screen. The Fast Tag Setup pop-up always displays the current fast tag selections
(see Figure 5-20, this page). Changes to the Fast Tag Setup may be made as detailed below.
At the bottom of the pop-up, you are given the option to Load a previous fast tag setup, or Save
the current setup for future use, in addition to Cancel, Apply, and OK.
5.2.13.1 Fast Tag Colour
The colour of each item on the fast tag list may be changed by pressing the Colour button
opposite the fast tag name and clicking on the new choice from the colour options that appear on
the screen. The same colour may be used for more than one fast tag.
February 2000 for version 1.40 49
Reference
Guide

Reference
Guide
5.3 The Reporting Menu GeoKit User Manual
5.2.13.2 Add Tag
See also: Section 5.2.9; Section 5.5.1
Figure 5-21 Add Tag Pop-up Window
This button allows you to increase the number of user-allocated Buttons (function keys F1 to
F12 along the top of the DA System keyboard) specified for fast tagging up to a maximum of 12
tag identities. (If you have not defined a fast tag button, it is allocated as an ‘Unknown’ tag.)
To allocate a tag to a particular Button, first click on the list in the Fast Tag Setup pop-up on
the button number at which the tag is to be added Before or After. Clicking on the Add Tag
button pops up the full list of tags which were previously defined as active using the Setup Tags
option of the Tagging menu (see Section 5.2.9). From this scrolling list, you can select the
required tag to be added by clicking on the appropriate tag name. The abbreviation before the tag
name in the list indicates the tag type. Multiple selections may be made by using a point and drag
action on the required items, or by pressing at the same time as pressing with the left
mouse button.
If the new fast tag is to be placed in the fast tag list after the marked button, you should select the
After current selection option, otherwise the fast tag will be added before the current selection.
The same tag cannot be added to the list twice. All the fast tag button numbers subsequent to the
newly added tag button are increased by one. If 12 fast tag buttons have already been allocated,
you must delete one from the list before another item can be added to the list.
5.2.13.3 Delete Tag
Clicking on this button removes the button currently selected from the list of fast tag buttons. To
alter the selection, click over the row containing the relevant button.
5.2.13.4 Delete All Tags
This deletes all of the current fast tags from the tag setup.
5.3 The Reporting Menu
See also: Appendix D
Figure 5-22 The Reporting Menu
This menu allows you to generate text reports in ASCII format from the contents of tag database
files; this is necessary because the tag database files are stored in binary, machine-readable – but
not human-readable – format. The report files generated can then be saved to floppy disk or
output to the screen or a printer.
50 February 2000 for version 1.40

GeoKit User Manual 5.3 The Reporting Menu
5.3.1 Report Setup
The Report Setup pop-up provides the options for defining the contents and style of the report.
Each of the aspects of the Report Setup has its own list of options, contained on the appropriate
tab form pop-up: Format, Options, Contents.
At the bottom of the pop-up, you have the option to Load a previous report setup, or Save the
current setup for future use, in addition to Cancel, Apply, and OK. These buttons apply to all
three tab forms in the Report Setup pop-up window, resulting in a single combined report setup.
Section 2.2.5.1 and Section 2.2.5.2 describe how to load and save settings.
5.3.1.1 Report Setup Format
See also: Appendix A
Figure 5-23 The Report Setup Format Tab Form
Clicking on the Format tab of the Report Setup pop-up allows you to alter the number of
columns reported and the order in which they are printed. Report column entries may be added
or deleted. To do so, select one of the report columns from the scrolling form by clicking on a
column number. The Add Item or Delete Item button should then be selected.
You may define some or all of the following parameters for each column in the report.
• Label allows you to define the label for each column in the report.
• Width allows you to specify the width of each column.
• Precision allows you to define the number of figures after the decimal point for non-integer
numbers in the report.
Add Item
Clicking on the Add Item button opens a pop-up window (see Figure 5-24, page 52). This
produces an alphabetically sorted list of the report column types.
February 2000 for version 1.40 51
Reference
Guide

Reference
Guide
5.3 The Reporting Menu GeoKit User Manual
Figure 5-24 The Add Item Pop-up Window
In the Add Item pop-up you can select items from the scrolling list by clicking on the names in
the list and you can specify their position in the report by clicking on either the Before current
selection button or the After current selection button. For a brief description of each of the
reportable items, see Appendix A.
The appropriate action button at the bottom of the pop-up (Add or Done) should be clicked on
when all items have been added. Alternatively, double-click on the item to add it to the report.
Multiple selections may be made by using a press and drag action over the required item in the
list.
Delete Item and Delete All Items
The two delete buttons under the horizontal scroll bar allow you to delete either the selected
column (Delete Item) or all the columns in the report (Delete All Items).
5.3.1.2 Report Setup Options
Figure 5-25 The Report Setup Options Tab Form
52 February 2000 for version 1.40

GeoKit User Manual 5.3 The Reporting Menu
Report Separator
The options within this section of the pop-up allow you to select the type of separator for the
columns of the report from the one-of option: Tab, Space, and Comma. Tab inserts a single tab
character between columns, Space inserts a single space, and Comma inserts a single comma
with no additional spaces.
Report Headings
This allows you to toggle on or off the labels at the top of the report columns.
Dual Tags
This option is only applicable to the CODA-PI100 Pipeline Inspection module. See the PI100
manual for further details.
Multi-Node Tags
The options within the Multi-Node Tags frame also have an effect on the output of reports in
GeoKit. If Report nodes by sort order is selected, all nodes will appear in the report in their
sort order. If Report nodes grouped by tag is selected, when the first node of a multi-node tag
is found, the remaining nodes will be reported immediately afterwards, irrespective of sort order.
If Report start nodes only is selected, only the start event of a multi-node tag will be reported.
Sort Order
This option allows you to sort the data by Time or by Kp, and by increasing or decreasing order
in the report. This can affect the reporting of start and end events.
Text Strings
You can select either to Enclose text in double quotes, or to Replace spaces with underscores.
This can be used to ensure that columns whose output contains spaces are not created as
several columns when input to another computer package. You should choose the output best
suited to the software the report will be used with.
5.3.1.3 Report Setup Contents
See also: Section 5.2.9; Section 5.2.13
This pop-up allows you to define which tag types should be included in the report and the order
in which they should appear. For example, you may wish to exclude Fix Lines from the report.
Figure 5-26 The Report Setup Contents Tab Form
February 2000 for version 1.40 53
Reference
Guide

Reference
Guide
5.3 The Reporting Menu GeoKit User Manual
This form comprises a scrolling list containing the user-defined sub-set of all the active System
and User tags which are to appear in the report (defined in Section 5.2.9). At the bottom of the
form are the Add Tag, Delete Tag, and Delete All Tags buttons. These buttons function in
exactly the same way as those described in Fast Tag Setup (Section 5.2.13). In addition, the Add
All Tags button gives the option of including all the currently active tag types to the report.
Before individual tags may be added or deleted using these buttons, they must be selected from
the scrolling list. The report contents list only shows each tag name once. However the tag name
in this menu may refer to more than one tag type. Selecting the tag name on the contents menu
will report all tag types under this name. For example, Boulder can be both single and expanding.
This only needs to appear in the conents list once to report both boulder tag types.
Changes made in this form are confirmed or cancelled when one of the action buttons is pressed.
5.3.2 Report Generation
See also: Section 5.3.1; as well as Section 4.1.2, Section 4.2.2 and Section10.10 and
Appendix J of the DA System User Manual
Figure 5-27 The Report Generation Pop-up Window
The Report Generation pop-up allows you to generate one or more ASCII text reports in the
style defined by the Report Setup (see Section 5.3.1). To select a report for output, click on the
appropriate entry in the scrolling list. (The current tag database will always be selected when the
window first pops up.) You can select more than one tag file by pressing and dragging over the
required files or by holding down while clicking on the tag file names. To generate
the report, click on the Generate Report button. The watch pointer will appear while the report
is being generated.
The buttons in the Output Report To frame allow you to select the destination for the report file.
If Text Window is selected from the above options, a report file is generated by the system and
displayed in a text window which is overlaid on the screen. You can scroll through this window
to view its contents (Figure 5-28, this page).
54 February 2000 for version 1.40

GeoKit User Manual 5.3 The Reporting Menu
Figure 5-28 Report File Displayed in Text Window
If output to Printer is selected, the report file is sent to the printer, according to the options
selected in the Printer Setup menu (see Section 5.3.2.1). The Printer option is available only if
a suitable hardcopy device is connected to the Coda system (see Section 4.1.2, Section 4.2.2 and
Appendix J in the DA System User Manual). The printing process can be stopped at any point
by pressing the Cancel button.
If the output is to be saved to a floppy disk, Floppy Disk should be selected, and a blank DOSformatted
floppy disk inserted in the floppy disk drive. After Generate Report is clicked, a
further window will appear asking for the name under which the report file should be saved to
the floppy disk. Once the name has been entered, press OK to start copying the report file to disk.
The report file saved to disk will be an ASCII dump of the database contents, in exactly the same
format as the report sent to a printer, or to the screen. All files are saved with the extension ‘.rep’.
Note that the size of ASCII file which can be copied to a floppy disk is limited to the formatted
capacity of the floppy disk – normally 1.44 MB.
•Note: If the system is being used for data acquisition or playback, the process of saving a report
file to floppy disk will take longer to complete. To speed up the process, pause the display until
the report file has been saved to the floppy disk.
5.3.2.1 Printer Setup Window
See also: Section 4.2 and Appendix J of the DA System User Manual
Figure 5-29 The Printer Setup Pop-up Window
Selection of the appropriate printer port is made by clicking on the port to which the printer is
connected. If the port is a serial port (one of the Com ports), the Serial Setup button should be
clicked to set up the serial line parameters.
Either Portrait or Landscape Format may be selected for PostScript® printers by clicking on
the appropriate toggle. Where a printout is being saved in ASCII format, this selection does not
apply and will therefore be ignored. Type allows a choice of ASCII or PostScript® printer.
February 2000 for version 1.40 55
Reference
Guide

Reference
Guide
5.4 The Applications Menu GeoKit User Manual
Once the required selections have been made, the appropriate action button at the bottom of the
pop-up should be clicked on.
•Note: The printer should be connected to the required port of GeoKit before OK or Apply is
clicked (see Section 4.1.2 and 4.2.2 in the DA System User Manual).
5.4 The Applications Menu
Figure 5-30 The Applications Menu
This menu allows you to select which Coda application you wish to run. The Application
Specific Area of the main display will change according to the application being used.
With the standard DA System you can select Data Acquisition, which allows you to record and
replay data. With other modules, you can record and play back data as well as using the survey
tools specific to the module. Further information about the capabilities of the additional software
modules is available from Coda Technologies.
When an application is running (for example, automated pipeline inspection), the letter ‘R’ is
appended to the Application menu item. This lets you switch between application modules while
remaining aware of which application is currently running.
Pipeline Inspection: The PI100 Pipeline Inspection module is designed as a tool for surveying
sub-sea pipelines. It carries out automated pipeline tracking and span and burial detection, as
well as offering a comprehensive set of database annotation tools. This allows pipeline surveys
to be conducted without using thermal paper printouts of the survey.
5.5 The Application Specific Area
See also: Section 5.1.1.4; Section 5.1.2; Section 5.2.6; Section 5.2.13
The Application Specific Area of the display shows various pieces of information which change
according to the application being used. When GeoKit is selected under the Applications menu,
the Application Specific Area is updated as in Figure 5-31, this page. As shown in the figure, two
areas are displayed: Fast Tag Area (labelled Key) and Position.
Figure 5-31 : The Application Specific Area of GeoKit
5.5.1 Fast Tagging
See also: Section 5.1.1.4; Section 5.1.2; Section 5.2.6; Section 5.2.13
This area consists of 12 specific colour-coded fast tag keys for accelerated event tagging. To
customise these, use the Fast Tag Setup option of the Tagging menu (see Section 5.2.13). Each
button is labelled to indicate the assigned function key ( to along the top of the
keyboard); the tag name; and the tag type. The different events can either be marked by clicking
on the appropriate button (or by pressing one of the function keys when the pointer is in the Data
Display Area) and then clicking in the display area to mark the required position of the feature.
56 February 2000 for version 1.40

GeoKit User Manual 5.5 The Application Specific Area
Tag type will be one of S (single tag), L (linear tag), B (boundary tag), or E (expanding box tag).
If a tag is not assigned to a Fast Tag Button in the Fast Tag Setup, the button in the Fast Tag
Area will be labelled Unknown.
The Fast Tag Buttons may be used as a quick method of adding tags; clicking on the button, or
the label beside it, will toggle between add mode and select mode (see Section 5.1.2). If GeoKit
is in select mode, clicking on the button will indent the button and change the system to add mode
and vice versa to switch from add mode to select mode.
Figure 5-31, this page, shows a fast tag setup defined by the user using Fast Tag Setup (see
Section 5.2.13). The tag name labels are black and no buttons are depressed, indicating that the
system is not in add mode. Accessing one of these fast tags makes this tag the pending fast tag.
Figure 5-32 Fast Tag Area showing a Pending Fast Tag
Pending fast tags are indicated by the indentation of the fast tag button and the black border
around the fast tag label. In addition, the pointer in the Data Display Area changes from an
ARROW to a PENCIL (see Section 2.3). Once a fast tag is pending, a node may be added by moving
the pointer over the event to be marked and clicking with the left mouse button. The exception
is where the tag type being placed is an expanding box tag (see Section 5.1.1.4). A tag node of
the appropriate type will be drawn and will flash in the Data Display Area, indicating it has been
automatically selected (see Section 5.1.2.2). An entry will also be created for the tag in the
database, allowing the tag’s position, nav information and other relevant information to be
stored.
Figure 5-33 The Fast Tag Area showing an Incomplete Multi-Node Tag
If the tag node placed is one from a multi-node tag (linear or boundary tags), the tag will be
incomplete. An incomplete tag is indicated by a green fast tag label. Figure 5-33, this page illustrates
the Fast Tag Area after the start node of a multi-node tag has been placed. The green label
indicates that the tag is incomplete (lacking its end node).
You may continue to add nodes to the current multi-node tag until the tag is completed. Each
additional node will always be linked to the previously added node. The node last added is
automatically made the selected node, and this node flashes on the screen until it is deselected or
another node is placed.
If you want to add a tag with a different identity, the corresponding fast tag should be clicked on
(or function key pressed). The selected fast tag will then be the pending tag. If the previous tag
was a multi-node tag which was not completed before changing to a new pending tag, it will
remain incomplete (fast text label shown in green). To complete the previous tag, the fast tag
should be selected and the Complete Multi-Node Tag should be selected.
February 2000 for version 1.40 57
Reference
Guide

Reference
Guide
5.5 The Application Specific Area GeoKit User Manual
Multi-node tags can be completed in two ways: by pressing the middle mouse button; or by
selecting Tagging→Complete Multi-Node Tag. After a multi-node tag has been completed, the
last node added will be selected and the system will remain in add mode. The tag label in the Fast
Tag Area will change from green to black.
Once a tag has been completed, you may wish to manipulate it in one of a number of ways. For
this to be possible the system must be in select mode. This can be achieved by re-clicking on the
pending fast tag. The pointer in the Display Area will change to a pencil and the pending fast tag
will be cancelled.
Once the tag has been placed the fast tag remains selected until another fast tag is selected or the
current one is deselected. A selected fast tag is shown by: description is black, outlined in black
with the tag button indented. Information such as tag type, location and length of linear tags (start
and end nodes) is automatically logged to the database. Additional annotation information can
be added to the database via the Tagging→Annotate Tag Node(s) menu option or by using the
appropriate keyboard shortcut, as outlined in Section 5.2.6
Fast tag selection may be altered simply by clicking on the new choice (or by using the appropriate
function key). The black bordered rectangle will then move to the new choice. If the
previous choice was a multi-node tag, its state will revert to that before the previous selection
was made, so if the multi-node tag was not completed the Fast Tag Area will reflect this. To
cancel a selection, simply click again on the same selection and the pointer in the Data Display
Area will revert to an arrow.
5.5.1.1 Summary
• Selecting a Fast Tag: A fast tag can be selected by pressing the appropriate button in the Fast
Tag Area, or by pressing the appropriate function key (F1–F12) as displayed in the Fast Tag
Area. Selecting a tag causes it to become a pending tag. Selecting a tag which is the pending
tag causes the tag to become deselected.
• Deselecting a Fast Tag: A fast tag can be deselected by pressing the pending tag button or the
appropriate function key.
• Pending Tag: The pending tag is the tag that will be added to the Data Display Area when the
left mouse button is pressed. The pending tag is shown in the Fast Tag Area with the button
depressed and the label surrounded by a black border. There is only one pending tag.
• Incomplete Multi-Node Tags: Incomplete multi-node tags are indicated by the label being
displayed in green. There may be more than one incomplete multi-node tag.
• Completing a Multi-Node Tag: An incomplete multi-node tag (label displayed in green) can
be completed by first selecting it and making sure that it is the pending tag. By selecting
Tagging→Complete Multi-Node Tag, or by pressing the middle mouse button, the tag will
become complete. The label will then change from green to black.
5.5.2 The Position Area
This section of the window displays the UTM or lat/long co-ordinates of the ship or towfish for
the most recent line of data displayed at the top of the data display area. When the waterfall
display is scrolling these co-ordinates are continuously updated.
58 February 2000 for version 1.40

Part VI: Appendices
Appendices

Appendices
60 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual A.1 Table of Tag Properties
A GeoKit Report Contents
The table below lists the possible contents of the report. For full details of how to define the
columns in the report, see Section 5.3.1.
A.1 Table of Tag Properties
Field name Applicable
to...
Description
Anomaly Number Node A user defined identifier that can be associated
with a tag node (entered via Annotate pop-up)
Anti-alias Filter Freq Sonar Anti-aliasing filter frequency (Hz)
Channel Sync With Sonar Bitfield indicating which channel the nodes
associated channel is synched with
Channel Type Sonar The type of data channel the node is marked in,
(e.g. Port, Starboard, Seismic)
Comparison Node Any extra comparative details about the tag
node (text entered via the Annotate pop-up)
Course Sonar The actual course of the vessel/towfish in
degrees
Creator Tag ID Node The database ID of the tag’s creator node
DCC Sonar The distance cross course of the ping in metres
(Starboard is positive)
Date Node &
Sonar
The date of the node’s associated ping
Depth From Horizon Node The depth in metres from node to horizon, SBP
only, (entered via Measure)
Depth From Seabed Node The depth in metres from the tag node to the
seabed, SBP only
Depth From Surface Node The depth in metres from the tag node to the
sea surface, SBP only
Description Node Any extra descriptive details about the tag node
(text entered via the Annotate pop-up)
Easting Node The (corrected) nav data easting position
Easting End Node The (corrected) nav data end event easting
position
Feature Offset Node The offset to feature from the node in metres
Fish Height Sonar The height of the towfish above the seabed in
metres
Fish Offset Sonar The (corrected) distance cross-track in metres
from the ship position to the fish position;
Starboard is positive
Fix Number Sonar The previous navigation fix number to the node
Fractional Fix Node The fractional value between the fix lines
where the node lies
February 2000 for version 1.40 61
Appendices

Appendices
A.1 Table of Tag Properties GeoKit User Manual
Field name Applicable
to...
Fractional Fix End Node The fractional value between fix lines where
the end of the event lies
Further Inspection Node Indicating whether the node is marked for
further inspection. User input via the Annotate
pop-up
GDOP Sonar Geometric dilution of precision (as entered via
the nav string) of associated sonar message
Geo Node Details of the Geophysicist that marked the tag
node (text entered via the Annotate pop-up)
HDOP Sonar Horizontal dilution of precision (as entered via
the nav string) of associated sonar message
Heading Sonar The ship’s heading (degrees)
Heave Source Sonar The source of Heave on the ship. Currently
always set to none – for future expansion
Heave Value Sonar The magnitude of Heave on the ship. Currently
always set to zero – for future expansion
Heave Velocity Sonar The velocity of Heave on the ship (m/s). Currently
always set to null – for future expansion
Height Node The measured height value of the node in
metres
Height CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
height (see Appendix B)
Height CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node height
(see Appendix B)
Incident Code Node The (start) incident code of the node
Incident Code End Node The end incident code of the node
Note: This is not necessarily the incident code
of the end node
Input Channel Node &
Sonar
62 February 2000 for version 1.40
The number of the channel the node was placed
in (from acquisition setup)
Input Gain Sonar The gain of the input sonar signal in decibels
(from the nav string)
Kp Node &
Sonar
Kp End Node &
Sonar
Description
The (corrected) nav data Kp position
The (corrected) nav data end event Kp position
Layback Sonar The (corrected) distance in metres from the
ship position to the fish position
Length Node The Length of the tag (as automatically
generated or measured by the user) in metres

GeoKit User Manual A.1 Table of Tag Properties
Field name Applicable
to...
Length CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
length (see Appendix B)
Length CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node length
(see Appendix B)
Line Name Sonar The Line name that is entered in the Navigation
Parameter Settings pop-up or via the nav string
allowing the user to mark a specific part of the
survey
Nav Basis Sonar The nav basis of the survey (e.g. UTM or
Lat/Long)
Node CorrNav Off Node A mnemonic indicating which of the node’s
nav parameters are uncorrected (see Appendix
C)
Node CorrNav On Node A mnemonic indicating which of the node’s
nav parameters are corrected (see Appendix C)
Node Type Node The type of (multi) node, e.g. start node (S),
intermediate node (I) or end node (E). Single
tags are reported as start nodes.
Northing Node The (corrected) nav data northing position
Northing End Node The (corrected) nav data end event northing
position
No. Rec. Chans Sonar The number of data channels recorded
Offset CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
offset (see Appendix B)
Offset CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node offset
(see Appendix B)
PDOP Sonar Position dilution of precision (as entered via
the nav string) of associated sonar message
Ping Number Sonar The ping number
Description
Ping Rate Sonar The number of pings per second – calculated
during acquisition
Pitch Sonar The instantaneous pitch of the vessel/towfish
(degrees); forward pitch is positive
QC Node The name of the quality controller – text
entered via the Annotate pop-up
Range Node The corrected true range to fish in metres
Raw DCC Sonar The raw value of distance cross course of the
sonar message
Raw Easting Node The raw nav data easting position
February 2000 for version 1.40 63
Appendices

Appendices
A.1 Table of Tag Properties GeoKit User Manual
Field name Applicable
to...
Raw Easting End Node The raw nav data end easting position
Raw Fish Height Sonar The raw nav data fish height above the seabed
in metres
Raw Fish Offset Sonar The raw nav data distance cross-track in metres
from the ship position to the fish position;
Starboard is positive
Raw Heading Node &
Sonar
Raw Kp Node &
Sonar
Raw Kp End Node &
Sonar
64 February 2000 for version 1.40
The raw nav data heading (degrees)
The raw nav data Kp position
The raw nav data end Kp position
Raw Layback Sonar The raw distance in metres from the ship
position to the fish position
Raw Northing Node The raw nav data northing position
Raw Northing End Node The raw nav data end northing position
Raw Water Depth Sonar The raw nav data water depth in metres
Roll Sonar The instantaneous roll of the vessel/towfish
(degrees); starboard roll is positive
Sample Interval Sonar The time in seconds between each data sample
Sidescan Flags Sonar Sonar message bitfield
Description
Slant Feature Offset Node The slant corrected fish offset to feature of the
tag in metres
Slant Height Node The slant corrected height of the tag in metres
Slant Range Node The slant corrected range to fish of the tag in
metres
Slant Width Node The slant corrected width of the tag in metres
Sonar CorrNav Off Sonar A mnemonic indicating which nav parameters
are uncorrected in the associated sonar message
(see Appendix C)
Sonar CorrNav On Sonar A mnemonic indicating which nav parameters
are corrected in the associated sonar message
(see Appendix C)
Sonar Frequency Sonar The frequency of the sonar (Hz) – unused
Speed of Sound Sonar The speed of sound through the water (m/s)
Speed Over Ground Sonar The speed over the ground that the fish is
travelling (m/s)
Start Delay Sonar The start delay in milliseconds (set in the
acquisition parameters)
Swell High Freq Sonar The High cut off frequency for the swell
filtering (Hz), SBP only

GeoKit User Manual A.1 Table of Tag Properties
Field name Applicable
to...
Swell Low Freq Sonar The Low cut off Frequency for the swell
filtering (Hz), SBP only
Swell Source Sonar The source of swell filtering used (i.e. Manual,
Automatic etc), SBP only
Swell Value Sonar The value of swell in metres, SBP only
TDOP Sonar The time dilution of precision (as entered via
the nav string) of associated sonar message
TagID Node The Tag Database Identification Number
Tag-Name Node The name of the Tag (as assigned in the Setup
Tags pop-up)
Tag Source Node An indication of whether the tag node was
automatically (A) or manually (M) marked
Temperature Sonar The water temperature (degrees C)
Time Node &
Sonar
Description
The Nav time of the sonar message at which
the tag was placed on the data
Time Basis Sonar Whether the time zone is local or UTC (GMT)
Transmitted Power Sonar The transmission power of the sonar message
in decibels (from nav input)
Trigger Number Sonar The trigger number of the sonar message (e.g.
A, B, C)
UTM Zone Sonar The UTM zone number of the survey
VDOP Sonar Vertical dilution of precision (as entered via the
nav string) of associated sonar message
Voltage Range Sonar The associated sonar data voltage range as is
set in the Acquisition Parameters (volts)
Water Depth Sonar The corrected water depth in metres (via nav)
of associated sonar message
Width Node The Width of the Tag in metres – Normally
taken from a tag measurement in metres
Width CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
width (see Appendix B)
Width CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node width
(see Appendix B)
Yaw Sonar The yaw of the vessel/towfish (degrees);
Starboard is positive (from nav input string)
Zero Offset Sonar The DC level of data samples. This number is
the sample value for 0V
February 2000 for version 1.40 65
Appendices

Appendices
A.1 Table of Tag Properties GeoKit User Manual
66 February 2000 for version 1.40

GeoKit User Manual B.1 Measurement Methods
B Calculations for Tag Node Measurements
Measurements are calculated using the start and end points of the user-placed measure line, as
shown in Figure B-1, this page.
End
heading
End Ping
E,N
Start
heading
Start Ping
E,N
Track
End range
Start range
Figure B-1 Difference in E,N
Measure
Start point
B.1 Measurement Methods
Measure
End point
Measure line
When the measurement method in the Settings menu is set to Difference in E,N pair, both the
start and end points have their E, N (Easting and Northing) calculated from their associated ping
E, N. The ping E, N is first corrected and then, using the heading, fish height and range, a true
range distance and bearing is calculated, to compute the measurement point E, N. The heading
and fish height values will also be corrected if available. The measurement distance is then calculated
from the difference in the Easting and Northing pairs.
The most accurate measurements therefore require corrected values for the start and end points’
E, N, heading and fish height. When the measurement is associated with a tag node (as either
length, width, height or offset) a report may be output that indicates which of the measurement
values have been corrected (or alternatively, which have not been corrected). These are displayed
as letters as follows:
• e = Easting
• n = Northing
• h = heading
• f = fish height
These letters are preceded by either an ‘S’ for start point values or ‘E’ for end point values. For
example, Senhf Eenhf indicates that the Easting, Northing, heading and fish height have been
corrected for both the start and end point. If any letter had been missing, a less accurate
measurement would result.
When the measurement method is set to Speed x Time, only the start point has its position calculated.
The end point is then calculated based on the along-track and across-track distance differences
(see Figure B-2, page 68).
February 2000 for version 1.40 67
Appendices

Appendices
B.1 Measurement Methods GeoKit User Manual
Start
heading
Start Ping
E,N
Track
Start range
Figure B-2 Speed x Time
Along-track
Measure
Start point
The distances are calculated as follows:
This measurement method is less accurate than Difference in E,N pair if corrected nav is
available, but may give more accurate results when only raw nav is available. Typically the
accuracy of this method is determined by the ship speed values input via the nav string. If these
values are inaccurate, the along-track distance will also be inaccurate. Across-track distances are
generally very accurate, provided that the speed of sound is approximately correct.
If the nav positions are given as Lat/Long rather than E,N, then the Lat/Long pairs are first
converted to E,N and then the above calculations performed to get the required position. This
position is then reconverted back to Lat/Long.
68 February 2000 for version 1.40
Across-track
Measure
End point
Measure line
StartPointShipSpeed + EndPointShipSpeed
AlongTrack = ------------------------------------------------------------------------------------------------------------------- × Time
2
AcrossTrack = SpeedOfSound × Time
Distance ( AlongTrack ) 2 ( AcrossTrack)
2
=
+

GeoKit User Manual C.1 Measure Mnemonics
C Corrected Nav Report Mnemonics
See also: Appendix B
C.1 Measure Mnemonics
• S = Start point of measure
• E = End point of measure
These are prefixes to the following letters:
• e = Easting
• n = Northing
• h = heading
• f = fish height
For example
SenEnh = Start point Easting and Northing, End point Northing and heading.
C.2 Sonar Mnemonics
These represent values for the sonar ping, as follows:
• e = Easting
• n = Northing
• h = heading
• k = Kp
• d = dcc
• l = layback
• o = fish offset
• f = fish height
• w = water depth
C.3 Node Mnemonics
These represent values stored for each tag node. Nav fields not mentioned here are taken from
the tag’s associated ping information (see Appendix B):
• e = Easting
• n = Northing
• k = Kp
• d = dcc
February 2000 for version 1.40 69
Appendices

Appendices
C.3 Node Mnemonics GeoKit User Manual
70 February 2000 for version 1.40

Part VII: Checklists
Checklists

Checklists
72 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual D.1 GeoKit/PI100 Mobilisation Checklist
D Mobilisation Checklists
Before starting a survey with GeoKit, you should check that the equipment is mobilised
correctly. Correct mobilisation procedures ensure that, at the time of sailing, the system is
functioning correctly and is receiving all the data it needs in a form that it understands.
We recommend that the mobilisation procedures are observed every time a vessel sails, and that
they form the basis of any ISO9000 definition of readiness for use before sailing.
If any of the items in the list below are unclear, feel free to consult our Technical Support staff
at any time. Details are given on the inside front cover of this manual.
Our Technical Support staff may ask about the mobilisation checklist items if technical support
is required during a survey.
D.1 GeoKit/PI100 Mobilisation Checklist
1 Tag Setup Files
GeoKit/PI100 Mobilisation Comments Initials
1.1 Are the correct tag types set up? Have you
included all the tag types required by the
client?
1.2 Are the start/end codes correct?
1.3 Are the correct tags active?
1.4 Are the forced measures set for the
appropriate tags?
1.5 Is the Tag Setup saved on the system hard
disk/optical disk?
1.6 Has the Tag Setup been saved to
tape/optical disk, using Maintenance
Menu→Backup Setup Files?
1.7 Has the Tag Setup file name changed on
the system hard disk/optical disk?
1.8 Has the Tag Setup been reloaded onto the
system hard disk from tape/optical disk,
using Maintenance Menu→Restore
Setup Files?
1.9 Is the tape/optical disk labelled and writeprotected?
2 Fast Tag Files
2.1 Are the Fast Tag Setup files correct for
the job?
2.2 Is the Fast Tag Setup saved on the
system hard disk/optical disk?
2.3 Has the Fast Tag Setup saved to
tape/optical disk, using Maintenance
Menu→Backup Setup Files?
February 2000 for version 1.40 73
Checklists

Checklists
D.1 GeoKit/PI100 Mobilisation Checklist GeoKit User Manual
2.4 Has the Fast Tag Setup file name changed
on the system hard disk/optical disk?
2.5 Has the Fast Tag Setup been reloaded
onto the system hard disk from
tape/optical disk, using Maintenance
Menu→Restore Setup Files?
2.6 Is the tape/optical disk labelled and writeprotected?
2.7 Has the right mouse button been set up for
maximum efficiency?
3 System Hard Disk
3.1 Have all previous interpretations and tag
files been stored to tape/optical disk and
labelled correctly?
3.3 Have all unwanted tag files on the system
hard disk/optical disk been deleted?
4 Report Files
4.1 Are the Report Setup files correct for the
job?
4.2 Can the Report ASCII output on floppy
be read by the system the report is
intended for?
4.3 Is the report format as required and
meaningful?
4.4 Is the Report Setup file saved onto the
system hard disk/optical disk?
4.5 Have the Report Setup files been
saved to tape/optical disk, using Maintenance
Menu→Backup Setup Files?
4.6 Has the Report Setup file name changed
on the system hard disk/optical disk?
4.7 Has the Report Setup been reloaded onto
the system hard disk from tape/optical
disk, using Maintenance Menu→Restore
Setup Files?
4.8 Is the tape/optical disk write-protected
and labelled?
74 February 2000 for version 1.40
GeoKit/PI100 Mobilisation Comments Initials
CODA system mobilised for Tagging
& Reporting
Signed Date

GeoKit User Manual D.2 PI100 Mobilisation Checklist
D.2 PI100 Mobilisation Checklist
1 Tagging & Reporting
PI100 Mobilisation Comments Initials
1.1 Have all the checks in the GeoKit/Pipeline
Inspection Mobilisation Checklist
(above) been carried out successfully?
2 Pipeline Inspection
2.1 Is the pipeline external diameter known
for all the pipelines to be surveyed?
2.2 Is the client spec for touchdown known
for all the pipelines to be surveyed?
2.3 Is the minimum span length to report
known for all the pipelines to be
surveyed?
CODA system mobilised for Pipeline Inspection
Signed Date
February 2000 for version 1.40 75
Checklists

Checklists
D.2 PI100 Mobilisation Checklist GeoKit User Manual
76 February 2000 for version 1.40

GeoKit User Manual E.1 Saving Tag Files to Tape/Disk Checklist
E On-Line Checklists
The purpose of these checklists is to ensure that the system operator is carrying out all the
required steps when tagging or generating reports with the Coda system.
E.1 Saving Tag Files to Tape/Disk Checklist
Tape System:
Blank tape loaded into drive 1 q
Files saved using Tagging→ManageTag Files→TapeLoad/Save.
(Save Batch Overwrite to overwrite existing data on tape; Save Batch Append
to write to the first blank section of the tape)
Tag files saved correctly (List Previous Batch showed the appropriate tag files) q
Optical Disk System:
Blank optical disk loaded into drive. q
Tag files located and selected using Tagging→Manage Tag Files→Database
Location
Tag files copied to target location using Copy Tag Files q
Tag files saved correctly (Database Location showed the appropriate tag files) q
Tape/Disk Systems:
Tag file tape labelled correctly: q
Date and time of recording q
Data Source q
Client q
Kp (start and end) q
Tag file name q
Tag file tape/optical disk write protected q
Tag file stored with data file tape/optical disk q
E.2 Loading Tag Files to System Hard Disk Checklist
Tag file tape/disk loaded into correct drive q
Tag file tape rewound (tape system only) q
Tag file copied correctly. Tag filename appears in Tagging→Manage Tag Files
window following Rescan
q
q
q
February 2000 for version 1.40 77
Checklists

Checklists
E.2 Loading Tag Files to System Hard Disk Checklist GeoKit User Manual
78 February 2000 for version 1.40

Part VIII: Glossary &
Conversions
Glossary &
Conversions

Glossary &
Conversions
80 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual
Conversion Table
The following tables may be used for conversion from one unit of measurement to another. The
units are grouped under the headings: angle, area, length/distance, temperature, time, velocity/
speed, weight.
An Example of Use of the Tables
To convert a measurement from a unit in the first column (Unit A) to a unit in the fourth column
(Unit B), you multiply the measurement by the multiplier/conversion factor in the second
column (Unit A to Unit B multiplier/conversion). For example, to convert 10 knots to metres per
second: 10 x 0.5145 = 5.145 metres per second.
To convert a measurement from a unit in the fourth column (Unit B) to a unit in the first column
(Unit A), you multiply the measurement by the multiplier/conversion factor in the third column
(Unit B to Unit A multiplier/conversion). For example, to convert 10 metres per second to knots:
10 x 1.944 = 19.44 knots.
Angle
Area
Unit A Unit A→Unit B
multiplier/conversion
Length/Distance
Unit B→Unit A
multiplier/conversion
degrees (angle) 1.745 10 57.3 radians
2 – ×
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
Unit B
acres 4.356 10 square feet
4 × 2.296 10 5 – ×
acres 4047 2.471 10 square metres
4 – ×
square feet 9.290 10 10.76 square metres
2 – ×
square miles 3.098 10 square yards
6 × 3.228 10 7 – ×
square miles 640 1.562 10 acres
3 – ×
square miles 2.59 0.3861 square kilometres
square millimetres 1973 5.067 10 circular mils
4 – ×
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
chain (surveyors’) 66 1.515 10 feet
2 – ×
fathoms 6 0.1667 feet
Unit B
feet 30.48 3.281 10 centimetres
2 – ×
feet 0.3048 3.281 metres
February 2000 for version 1.40 81
Glossary &
Conversions

Glossary &
Conversions
Temperature
Time
Unit A Unit A→Unit B
multiplier/conversion
82 February 2000 for version 1.40
GeoKit User Manual
inches 2.54 0.3937 centimetres
inches 8.333 10 12 feet
2 – ×
inches 1.578 10 miles
5 – × 6.336 104 ×
inches 1000 0.001 mils
inches 2.778 10 36 yards
2 – ×
kilometres 3281 3.048 10 feet
4 – ×
leagues 3 0.33 miles (approximately)
metres 1.094 0.9144 yards
miles (nautical)* 6076.1 1.646 10 feet
4 – ×
miles (nautical)* 1852 5.400 10 metres
4 – ×
miles (nautical)* 1.1508 0.869 miles (statute)
miles (statute) 1.609 0.6214 kilometres
miles (statute) 5280 1.894 10 feet
4 – ×
yards 3 0.3333 feet
* Conversion factors for the nautical mile and, hence, for the knot, are based on the International
Nautical Mile
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Centigrade (Celsius) Fahrenheit
⎛ 9
C° × --⎞
5
+ 32 ( F° – 32)
×
--
⎝ 5⎠
9
Unit A Unit A→Unit B
multiplier/conversion
GMT date & time see Appendix F
of the DA100 or
DA200 User Manual
UTC seconds see Appendix F
of the DA100 or
DA200 User Manual
Unit B→Unit A
multiplier/conversion
Unit B→Unit A
multiplier/conversion
see Appendix F
of the DA100 or
DA200 User Manual
see Appendix F
of the DA100 or
DA200 User Manual
Unit B
Unit B
Unit B
UTC seconds
GMT date & time

GeoKit User Manual
Velocity/Speed
Weight
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
knots** 1.688 0.5925 feet per second
knots** 30.87 0.0324 metres per minute
knots** 0.5145 1.944 metres per second
knots** 1.1508 0.869 miles (stat) per hour
metres per minute 3.281 0.3048 feet per minute
metres per minute 0.06 16.67 kilometres per hour
miles per hour 0.4469 2.2374 metres per second
miles per hour 88 1.136 10 feet per minute
2 – ×
miles per hour 1.609 0.6214 kilometres per hour
** Nautical miles per hour
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
kilograms 2.205 0.4536 pounds (avoirdupois)
February 2000 for version 1.40 83
Glossary &
Conversions

Glossary &
Conversions
84 February 2000 for version 1.40
GeoKit User Manual

GeoKit User Manual
Glossary
A/D conversion the process of converting an analogue signal to a digital one
absolute using a predefined frame of reference (0 Kp, or 0:00 on 1st January,
1970); see also relative
AC Alternating Current; mains supply
acquisition see data acquisition
acquisition mode see data acquisition mode
acquisition parameters the settings used within the acquisition sub-system to determine
the quality and volume of the digital data obtained
acquisition sub-system the parts of the DA100/DA200 concerned with obtaining a digital
form of the analogue sonar inputs
across-track at 90° to the towfish or vessel track
across-track resolution the distance across-track covered by each sample of sonar data
active channel a data channel which is currently being digitised
aliasing distortion of the input signal caused by carrying out digitisation
at too low a sampling frequency
along-track along the line of the towfish or vessel track
along-track resolution the distance along-track covered by each sample of sonar data
altitude (of towfish) the distance above the seabed
ambient temperature the temperature of the surrounding air
analogue conveying information by changes in signal amplitude and phase;
see also digital
annotation (of sonar records) the practice of using an external device to overlay
the analogue sonar data with navigation information
Application Specific
Area
the part of the DA100/DA200 display (in the bottom right of the
screen) whose functions change in playback and acquisition
modes
Apply A button which applies the settings or options selected and
retains the pop-up window on the screen.
ASCII American Standard Code for Information Interchange; the worldwide
standard means of sending alphanumeric characters in a
7-bit format
auto pause release (of the DA100/DA200) a feature which prevents the freezing of
the screen display by the Pause button if further pausing would
cause loss of data to the screen
automatic position
pointer
the pointer type used for resetting the position of automatically
tracked features during PI100 operation
automatic sub-sample (of the DA100/DA200) the default sub-sample mode; this automatically
derives a sub-sample rate which allows the full swathe
width to be displayed on the screen
batch a group of tag files saved in the same save operation
February 2000 for version 1.40 85
Glossary &
Conversions

Glossary &
Conversions
86 February 2000 for version 1.40
GeoKit User Manual
baud rate (of RS-232 interfaces) the rate at which raw data bits are sent;
roughly equivalent to bits/second
bit binary digit; the smallest information unit in a digital system
BNC connector industry-standard bayonet connector for analogue and digital
signals
bottom tracking (of the DA100/DA200) automated location of the seabed first
return to allow the towfish altitude to be calculated
byte 8 bits
Cancel this button cancels any items or options selected and dismisses a
pop-up window, retaining the previous settings
case sensitive recognising the difference between lower and upper case letters
(for example, ‘a’ and ‘A’)
Centronics industry-standard parallel interface for connecting devices such
as printers and plotters to computer equipment
cleaning cartridge the means of carrying out head cleaning for DAT or Exabyte tape
drive units; a tape cartridge which holds cleaning tape rather than
recording tape
click press down and release the appropriate mouse button; if no button
is specified, the left button should be used
clipped (of analogue input signals) not converting the whole of the input
range, thus losing some of the signal (for example, the outgoing
pulse in sonar data); this should only be allowed to happen if the
information being discarded will NEVER need to be recovered
Coda format Coda Technologies’ format for storing data to a recording media;
retains more information about the recorded data than other
proprietary data formats
COM1 the name commonly used in DOS systems for the first serial port
COM2 the name commonly used in DOS systems for the second serial
port
compression (of tape drives) the practice of eliminating redundancy in the data
being recorded, allowing a larger amount of data to be stored in a
given space
continuous record (of the DA100/DA200) a facility which allows recording of
incoming data to carry on continuously, without the need to stop
recording when changing data tapes or optical disks
contrast the variation in shades of grey or hue within the display
corrected navigation
data
navigation information which has been smoothed to remove
spikes or jitter from the positional information
creator node the first node in a multi-node tag
critical length (PI100) the length in metres that an automatically detected span
must be before it is deemed to be a critical span (user-defined)
cross track at ninety degrees to the direction of travel of the towing vessel
cross-track offset the straight line cross-track distance from the vessel datum point
to the point where the tow cable passes over the stern of the
vessel

GeoKit User Manual
cross-track slant
distance
the distance measured between two points solely in the crosstrack
direction. It is a non-slant corrected measure (i.e. it is
dependent on fish height)
cross-track smoothing (of sidescan sonar data) low pass filtering of the sonar signal
from the nearest to the farthest end of the swathe, using a filter of
fixed frequency response
current tag (of the DA100/DA200) the event marker selected to be active by
clicking on the appropriate area of the Data Display Area. The
selected tag flashes between its normal colour and light blue
cursor symbol that shows the position on the display where any typed
text will be entered
DA100 Coda Technologies’ system for acquiring, processing and
replaying sidescan sonar or sub-bottom data, with single trigger
capability
DA200 Coda Technologies’ system for acquiring, processing and
replaying data from two independently firing sonars, e.g.
sidescan sonar and boomer
DAT Digital Audio Tape; an international standard for the recording of
analogue data to digital tape; see also DDS and DDS2
data acquisition the process of obtaining data (usually in digital form)
data acquisition mode (of the DA100/DA200) the operation mode in which the DA100/
DA200 is digitising and records data; see also data playback
mode
data bits the number of bits used to hold the information from each
sample; usually an integer number of bytes (8, 16 or 32 bits)
data channel a flow of data (for example, sonar data) into or within the DA100/
DA200; see also display channel
Data Control Area (of the DA100/DA200) that part of the DA100/DA200 interface
which controls the operation of the tape or optical disk drive unit
or units
Data Display Area (of the DA100/DA200) that part of the screen given over to the
display of data from the acquisition sub-system or from tape or
optical disk; the upper portion of the screen
data format (of tapes or optical disks) the scheme used to record the digital
data onto the tape or optical disk. Different formats can result in
different amounts of data being stored; see also Coda format,
Q-MIPS format, SDEF format, SEG-Y format
data playback mode (of the DA100/DA200) the operation mode in which the DA100/
DA200 reads previously recorded data from tape or optical disk
and displays it on the screen
database a structured means for storing and retrieving data in digital form,
allowing rapid random access to individual data entries
datum point the point on the towing vessel from which all measurements are
referenced
DCC Distance Cross Course; the across-track distance of a point from
the survey line
DDS Digital Data Storage; the standard format for storing computer
data to DAT tapes
February 2000 for version 1.40 87
Glossary &
Conversions

Glossary &
Conversions
88 February 2000 for version 1.40
GeoKit User Manual
DDS2 an improvement to the DDS standard, allowing a higher recording
density to be used, hence obtaining more storage capacity
from a given length of magnetic tape
dead time (in digitisation) the time allowed between the end of sampling for
a given data line (or ping), and the arrival of the next trigger
pulse
DGPS Differential GPS. A form of GPS which uses a base station to
send corrections to the satellite derived positions, allowing more
accurate fixes to be obtained
digital representing information by a sequence of bits, rather than using
the signal amplitude and phase; see also analogue
digital signal processing
using numerical techniques to carry out signal filtering or amplification
in the digital domain, rather than the analogue domain
digitisation the process of converting an analogue signal’s amplitude and
phase information into digital form
display channel a data channel which is displayed on the DA100 screen
DOS see MS-DOS
DOS formatted (of floppy disks) formatted on the MS-DOS operating system
double-click press and release the specified mouse button twice in rapid
succession; if no button is specified, the left button should be
used
dual tape (of DA100/DA200) a system having two tape drive units, rather
than one
dynamic range that portion of an analogue signal which actually conveys
information; that is, the range of values between the highest and
lowest encountered
Eastings distance East or West in metres of a given position from the UTM
or lat/long origin
edge sensitive (of TTL input) reacts to the change in voltage level, rather than to
the steady-state voltage level
Encapsulated Postscript®
EOT End Of Tape
a form of Postscript® which is suitable for incorporating into
documents on word processing packages, spreadsheets, and so on
Ethernet Local Area Network using a coaxial cable with BNC connectors,
capable of up to 1.25MB/second transfer rate
event (DA100/DA200) a point in the data which the user wishes to mark
using a database entry
Exabyte 8mm magnetic tape drive unit (based on 8mm video tape technology)
used for storage of digital computer data
external trigger (DA100/DA200) a TTL trigger which originates outwith the
DA100/DA200, used by the system to initiate the acquisition for
each ping
fast tag (PI100/GeoKit) colour-coded keys for accelerated marking of
events during pipeline inspection

GeoKit User Manual
file a set of data which exists as a distinct entity; on tape, file extents
are defined by end of file markers; on disk, they are defined by
the operating system
filtering the alteration of the frequency content of a signal; usually the
removal of unwanted (noise) frequencies
first return (in sonar data) the first echo which rises above the noise level of
the water column; the first point of contact of the outgoing pulse
with the seabed
fish abbreviation for towfish
fish height (PI100) the true height of the sonar transducer (fish) above the
seabed
fix a reference point (in time and space) for navigation purposes
fix tag the database entry for a given fix; see also tag
floppy disk portable magnetic media. Usually refers to 3½ inch double-sided,
high density disks with a capacity of 1.44MB (formatted)
flow chart method of breaking down a task into a sequence of actions and
decisions in diagrammatic form
flow control also known as handshaking
forced measure (following tag operation in PI100/GeoKit mode) a sequence of
measurements of the tag’s features which may have to be carried
out manually, rather than automatically by the system. The Tag
Placement Rules define which measurements are required for a
given tag
full resolution (zoom) using all the available samples for display; no subsampling
of any sort is carried out
gamma (colour mapping) the exponential function used to map incoming
intensities to greyscale values
gamma correction the process of redisplaying the image data displayed on screen
using a new gamma value
GB Gigabyte, approximately 1 000 000 000 bytes
General Information
Area
(DA100/DA200) that area of the screen which holds the current
ping number, time and cursor position; situated above the Data
Control Area
GeoKit Coda Technologies’ software module for geophysical interpretation,
which allows the user to tag events and generate ASCII
report output
goto (DA100/DA200) a command allowing random access to sonar
data stored on magnetic tape or optical disk
GPS Global Positioning System – a satellite-based navigation system
graphical user interface the means of interaction of the computer user with the programs
running on the computer; uses the display, the keyboard and the
mouse/trackball
greyed out (DA100/DA200) menu items which cannot be selected are greyed
out, written in lighter, grey text
greyscale the range of shades from black to white
February 2000 for version 1.40 89
Glossary &
Conversions

Glossary &
Conversions
grip see grip point
90 February 2000 for version 1.40
GeoKit User Manual
grip point (DA100/DA200) a point on an interactive graph, signified by a
small square, which can be moved by users (using the mouse/
trackball) to alter the shape of the graph
GUI Graphical User Interface
half-wave rectify remove those portions of an incoming analogue signal which are
below some threshold value (usually 0 volts)
handshaking (of RS-232 interfaces) the means by which the starting and
stopping of data transfers is effected; this can be carried out in
hardware or software
hard disk the magnetic disk which is permanently attached to a computer
system
hardcopy printed output; the generation of printed output
hardware electronic components
hardware handshaking handshaking carried out by electronic components, without the
intervention of any computer program
heave compensation
unit
a piece of equipment external to the sonar which monitors the
vessel’s heave, and varies the timing of the trigger pulse sent to
recording equipment (for example, the DA100/DA200), so that
the effect of vessel heave is largely eliminated; used for subbottom
profiling
height trigger (PI100) the minimum height of the bottom of the pipe above the
seabed that will trigger the pipe span condition (user-defined)
high contrast a large proportion of the available grey is used to display the
regions of the image the user is interested in
high pass filtering removing the low frequency component of a signal
high resolution (of digital storage) retaining a large proportion of the original
information content of the signal
hue the shade or tint of a colour
Hz Hertz; the SI equivalent of cycles/second
icon small symbol on the computer screen which represents some
entity or function within the computer system
image enhancement performing image processing in order to improve the quality of
an image (for example, the display of sonar data on a screen)
image processing performing manipulations to an incoming digital signal on the
assumption that the data contained therein has some meaning as
an image
indented (DA100/DA200) the buttons used to control the functions of the
DA100/DA200 (for example the data control buttons) have a
three-dimensional look; when a button has been activated, the
shading changes and the button appears to have sunk into the
interface – to have been indented
information window a window which supplies the user with information, but does not
accept any input from the user (for example, the Survey Data
window)

GeoKit User Manual
input voltage range the range of voltages which can be digitised by the DA100/
DA200
intensity strength, brightness, magnitude or amplitude of a signal
interface a means of transferring information from one piece of computer
equipment to another
internal trigger (DA100/DA200) a TTL trigger pulse which is generated by the
DA100/DA200, allowing it to trigger other equipment (for
example, to trigger the sonar ping)
interpolation the practice of estimating the value of a variable at a point by
setting it between the values of later and earlier samples
invert causing the range of shades (for example, from black to white) to
be reversed, so that items which were coloured black become
white, and vice versa
IO Input/Output
ISA Industry Standard Architecture; a type of signal bus used inside
PCs
jitter the noise present on a signal, causing observations which should
be identical to differ
KB Kilobytes (1 024 bytes)
Kp Kilometre post (distance along the survey line or pipeline, in kilometres)
Landscape mode (Postscript®) printed so that the bottom of the Postscript®
document is aligned with the long edge of the sheet of paper
layback the along-track distance from the datum point on the vessel to the
towfish
LED Light Emitting Diode: small coloured light attached to electronic
equipment
line of data all the data arising from a given sonar ping; for sidescan this
implies both port and starboard channels
local area network the cabling and interfacing standards which allow a collection of
computers to be connected to each other to share data and
resources (for example, Ethernet, Token Ring)
lookup table the rule used to translate incoming digital signals into grey levels
or colours for display; also known as palette
loopback testing a piece of equipment by using its own output as an input
signal, thus testing both the input and output functionality
low contrast a comparatively small range of grey levels is used to display all
the parts of the image the viewer is interested in; see also
contrast, high contrast
low pass filtering removing the high frequency component of a signal
LPT1 the name commonly used on DOS systems for the first parallel
port
LUT Lookup Table
master trigger a trigger used to start a number of pieces of electrical equipment,
to ensure their synchronisation
February 2000 for version 1.40 91
Glossary &
Conversions

Glossary &
Conversions
MB Megabyte; roughly 1 000 000 bytes
Media Recognition
System
92 February 2000 for version 1.40
GeoKit User Manual
second-generation DDS standard tapes, which have markings
which allow the length of tape to be determined by the tape drive
unit
megabyte approximately 1 000 000 bytes; see also MB
menu an area of the display (either a Menu Bar or a window) which
allows users to choose from a number of options, using either the
keyboard or the mouse/trackball
Menu Bar an area (at the top of the display in the DA100/DA200) in which a
number of menu items are permanently displayed
merge length (PI100) the minimum length (or separation) between separate
pipe events (e.g. spans) that will prevent the events from being
merged as one single event (user-defined)
Microsoft Windows a windowing operating system for IBM-PC compatibles
minimum length (PI100) the minimum length a pipe event (e.g. span) can be
without it being discarded as being too short (user-defined)
Mosaic Coda’s software module for Mosaicing sidescan sonar records
mosaicing the process of geopositioning sidescan sonar records such that an
image of a large area of the seafloor is built up line by line
Motif a library of software routines used for building user interfaces,
giving a characteristic ‘look and feel’
mouse a pointing device for use with computers. Movement of the
mouse moves the screen pointer; see also trackball
MS-DOS Microsoft Disk Operating System; see also DOS
multi-node tag an event marker which has several user-positioned points (or
nodes), used to define a boundary or a layer
multi-resolution capable of displaying or processing data at a number of scales
multi-tasking (of operating systems) able to run several programs simultaneously
nav string abbreviation for navigation string
navigation data any form of navigation information within the DA100/DA200
navigation input any form of navigation input to the DA100/DA200 system
navigation library (DA100/DA200) the reference table which allows the DA100/
DA200 to interpret incoming navigation strings
navigation string an ASCII string holding navigation data
node see tag node
non-interlaced (of computer monitors) displaying all the pixels within the
display in a single pass; interlaced displays take two passes, each
displaying every second line of pixel data
northings distance North or South in metres of a given position from the
UTM or lat/long origin
off-line processing which does not take place as data is being acquired, or
at the rate of acquisition

GeoKit User Manual
offset (DA100/DA200) the distance of a given sample from a datum
point; usually the distance of the start of the raw data line to the
start of the displayed line
OK a button which selects and applies the settings or options selected
and dismisses the pop-up window from the screen
on-line processing which takes place as the data is being acquired, and at
the rate of acquisition
on/off toggle a switch on the DA100/DA200 display which turns a system function
on or off; each selection of the switch changes the state of the
function (if it is ‘on’, selection turns it ‘off’; subsequent selection
turns it ‘on’ again)
one-of selection a form of switch on the DA100/DA200 display which selects one
from a number of possible options, where all the possible options
are displayed
operating system the program which ‘manages’ a computer, allowing the user’s
programs to run (e.g. Unix, Windows, DOS)
option selection a form of switch on the DA100/DA200 which selects one from a
number of possible options, where all the options except the one
selected are hidden
outgoing pulse the pulse of sound energy which is reflected to form sonar
images; visible on recorded sonar data as the bright stripe at the
beginning of each line
overlay plane additional coloured graphics which can be displayed on top of
sonar data; these may be switched on and off without affecting
the displayed data
overwrite record another set of data over the first, making the first data set
unrecoverable
palette equivalent to lookup table
parallel port a form of interface which allows a computer to interchange data
with the outside world in parallel form (that is, passing all 8 bits
of a byte simultaneously)
parity a form of error checking for each byte of data transferred (for
example, through a serial or parallel port)
password a collection of letters and numbers which uniquely allows access
to a computer or a set of programs on a computer
PCI Peripheral Component Interconnect: an advanced, high-speed bus
system used by PC-compatible computers
PI100 Coda Technologies’ Pipeline Inspection system, which allows
complete pipeline surveys to be undertaken without the use of
thermal recorders
ping a single sonar scan, resulting in a line of data being acquired
pipe distance (PI100) the slant distance from the sonar transducer (fish) to the
front of the pipe
pipe grazing angle (PI100) the angle made between the ensonified pipe, the transducer
and the seabed directly below the transducer
pipe height (PI100) the true height of the bottom of the pipe above the seabed
February 2000 for version 1.40 93
Glossary &
Conversions

Glossary &
Conversions
pipe striking angle see pipe grazing angle
94 February 2000 for version 1.40
GeoKit User Manual
pixel picture element; the dots on the screen from which an image or
GUI is built
playback mode see data playback mode
playback speed the rate at which sonar lines are displayed on the screen
pointer the icon which reflects changes in the mouse position, or movements
of the trackball. Usually an arrow, but may take other
forms
pop-up menu a menu which appears as the result of a selection in a previous
menu
pop-up window any form of window which appears as the result of a mouse/
trackball, or keyboard selection from a menu in the interface
port equivalent to interface; also left – see also starboard
Portrait mode (of Postscript® documents) printed so that the bottom edge of the
document is aligned with the shorter edge of the paper
positive edge (of TTL inputs) a signal which changes from 0 to 5V
Postscript® a language for describing printed matter (text, diagrams and
images)
power down the procedure to be observed when turning off the mains power to
an item of electrical equipment
power up the procedure to be observed when turning on the mains voltage
to an item of electrical equipment
pre-emptive scheduling allowing one program running in a multi-tasking operating
system to cause other programs to be suspended and only
restarted once the pre-empting program has completed its tasks
press and drag press down the appropriate mouse button, and without releasing
it, move the mouse so that the pointer is in the desired position on
the screen; then release the mouse button
processed navigation
data
see corrected navigation data
PSU Power Supply Unit: converts mains (AC) voltage to the lower
voltages required by computer equipment
pull-down menu a menu which appears when a Menu Bar option is selected; items
within a pull-down menu are selected by pressing and dragging
to the required menu item
Q-MIPS format a format for the storage of sonar data to tape
random access obtaining data from a file or memory in an order which is not the
same as the order the data was stored in
real-time occurring at the speed of data acquisition, or faster
reboot cause a computer system to completely re-initialise itself, as
though the power had been turned off, then on again
recording session the time from the start of recording data to the cessation of
recording

GeoKit User Manual
relative using a local frame of reference (for example, time or distance
measurements as an offset from the current time or distance); see
also absolute
resolution the level of detail which may be extracted from a set of data
ROTV Remotely Operated Towed Vehicle. Subsea vehicle on which a
sidescan sonar or sub-bottom profiler may be mounted
RS-232 an international standard for the interchange of serial data
between computers
sampling to convert analogue data to digital form, it is necessary to
measure its amplitude at regular intervals; this is known as
sampling the signal
sampling frequency the frequency at which an analogue waveform is sampled to
allow it to be converted to digital form
saturation (of colours) the depth of a given tint or shade
screen dump producing an image of the screen display, and either printing it or
saving it to disk
scroll bar the means by which all the items in a list appearing in a menu or
pop-up window may be examined
scrolling moving gradually up or down the display; one line of data must
move out of the bottom of the display for every new line which
appears at the top
SCSI-2 Small Computer Systems Interface, version 2; an improved
version of the SCSI standard for connection of peripheral devices
(such as tape drives, disks and scanners) to computers
SDEF format Sonar Data Exchange Format: sonar interchange format developed
by Meridian Sciences and US Geological Survey
SEG-Y format Society of Exploration Geophysicists ‘Y’ format; obsolescent
standard for seismic and sonar data storage
seismic using vibrations to obtain an understanding of the underlying
geological structure
select click the left mouse button on the appropriate item
serial port a form of interface which allows a computer to interchange data
with the outside world in serial form (that is, one bit at a time)
shortcut key a single typed character or sequence of keyboard inputs which
allows the user to carry out interaction with the DA100/DA200
interface without using the mouse
sidescan sonar a form of sonar which uses twin sideways looking transducers to
obtain an image of the seabed as it is towed through the water
signal processing see digital signal processing
single tape (of DA100/DA200) a version of the DA100/DA200 which has
only one tape drive unit
slant range the distance across-track to a point on the seabed from the
towfish position; this is directly proportional to the time from the
outgoing pulse transmission
February 2000 for version 1.40 95
Glossary &
Conversions

Glossary &
Conversions
96 February 2000 for version 1.40
GeoKit User Manual
slant-range correction a geometric correction to the incoming sonar signal which
converts the across-track scale of the sonar data so that it is
directly proportional to distance across-track, rather than to time
slave trigger the incoming TTL trigger pulse which causes a piece of electronic
equipment to start a sequence of operations (for example,
the digitisation of sonar data)
smart icon an icon which if selected causes a sequence of operations to take
place on the interface (for example, the inversion of the display)
smoothed navigation
data
see corrected navigation data
software computer programs
sonar sound navigation and ranging; the use of sound underwater to
detect objects or make measurements
sonar input the analogue signal output by a sonar processing and control unit
(for example, EG&G 260) which can be accepted as an analogue
input by the DA100/DA200
span (PI100) section of pipe that is unsupported by the seabed
spline a function which smoothes the line of a graph through a number
of points
stacking see trace mixing
starboard right; see also port
stop bits (of RS-232 interfaces) the number of bits following the data bits,
before the start of the next byte transmission
string (of ASCII data) a collection of valid ASCII alphanumerical
characters
sub-bottom profiler a low-frequency sonar device for obtaining seismic information
about the geology under the seabed
sub-sampling the practice of missing out data samples at regular intervals,
allowing a signal to be represented by fewer samples
substrate the material which makes up the seabed or sub-bottom
swathe the area of the seabed covered by a sidescan sonar trace
tab form a form which contains a number of related items of information
or selections and has a labelled tab at the top. As tab forms
overlap, the required tab form may have to be brought to the front
of the pile by clicking on its tab
tag (of the DA100/DA200) a group of one or more interconnected tag
nodes
tag node (of the DA100/DA200) a unique database entry defining a point
within the data, or the screen graphic associated with it
tape cartridge the plastic cartridge containing the magnetic tape medium
tape drive see tape unit
tape head that part of the tape drive which is in contact with the tape
medium, and causes the data to be written to the tape

GeoKit User Manual
tape unit (or tape drive unit) that part of the DA100/DA200 mechanism
which contains the tape head, and into which the tape cartridge is
loaded
TCP/IP Transmission Control Protocol/Internet Protocol; an interface
standard for local area networks
tear-off menu a pull-down menu which can be detached from the Menu Bar to
allow it to be displayed permanently on the interface
telemetry measurements carried out at a distance (for example of the
towfish altitude)
text-entry box an area in a window which allows the user to type input using the
keyboard, thus changing system parameters
thresholding the act of setting a level (for example, a greyscale intensity level,
or a voltage), above and below which different actions are taken
on the incoming signal
TIFF Tag Image File Format – a common, industry standard format for
storing and exchanging binary image data
time varying gain see TVG
titlebar (of the DA100/DA200) the area at the top of the DA100/DA200
screen which holds copyright information
toggle a form of switch which if pressed once is on, and if pressed again
is off
Token Ring the IBM Token Ring protocol for local area networking
toolkit a set of tools or functions accessed through a single pop-up
window
topology the shape of a surface
towfish the vehicle towed by a surface vessel in which the sonar transducers
are mounted
trace mixing adding (or subtracting) the data from succeeding sonar pings to
remove along-track noise; also known as stacking
track the path of the vessel or towfish over the seabed
trackball a pointing device for use with computers; movement of the trackball
moves the screen pointer; see also mouse
TrackPlot Coda’s software module for displaying vessel and towfish track
information
transducer a mechanism which transforms energy from one form into
another (for example, a sonar transducer converts electrical
energy to sound energy)
Transverse Mercator a geographical projection, similar to UTM, in which the user can
define the origin of the projection, by defining the footpoint latitude
and central meridan
trigger either an input which causes a piece of electronic equipment to
start a sequence of operations, or an output generated by one
piece of equipment, which others will use in this way; see also
slave trigger and master trigger
trigger source the piece of electronic equipment from which the trigger pulse
originated
February 2000 for version 1.40 97
Glossary &
Conversions

Glossary &
Conversions
98 February 2000 for version 1.40
GeoKit User Manual
TTL Transistor-Transistor Logic; an electrical interfacing standard for
digital signals
TVG Time Varying Gain: an amplification applied to sidescan sonar
signals which compensates for the spreading loss of the signal,
which is roughly proportional to the log of the range in metres
TVG enhancement (of the DA100/DA200) a set of facilities which allow users to
alter the time varying gain applied to the incoming sonar signal
undersampling sampling at too low a sampling frequency, so that aliasing occurs
Unix a multi-user, timesharing operating system, with real-time
facilities; uses the X Window graphical user interface
update a revision to the DA100/DA200 software, incorporating new
features and/or bug fixes
user-specific (of files) the files in the DA100/DA200 system which are placed
there by users (for example, database files, smoothed navigation
data files)
UTC Coordinated Universal Time; the world time standard; equivalent
to GMT
UTM Universal Transverse Mercator; a form of geographical projection
which allows positions to be measured relative to each other
in metres, over a restricted area
watch pointer the pointer which appears on the display screen when the DA100/
DA200 is waiting for an operation to complete
water depth the depth of water input into the system; the user may define this
relative to a datum on the vessel, as the depth under the keel, or as
the depth under the echo-sounder transducer
waterfall display a scrolling display of image data
window an area of the graphical user interface set aside for a specific
operation, often disappearing when that operation has been
completed
Windows see Microsoft Windows, X Window
write protect (of disk or tape cartridge) set so that it cannot be written to, only
read from
X Window a graphical user interface standard for the Unix operating system
zoom the process of selecting an area of the display to be redisplayed in
greater detail
zoom mode defining the type of zoom operation to be carried out (for example,
full resolution, fixed magnification)

GeoKit User Manual
Software Defect Report Form
Coda Technologies has made every effort to ensure that its software is reliable and performs
satisfactorily at all times. However, as with any software-based product, some defects may still
be present. If you encounter unexpected, undocumented or illogical behaviour by the system,
please complete this form and fax or mail it to:
Coda Technologies Ltd
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
Tel: +44 131 553 1380
Fax: +44 131 554 7143
User
Company
Unit Type
(rental/sale)
Date
Time
System Type
(e.g. DA100/PI100)
Software Version
Number
Serial Number
Mode in which fault
occurred (playback/
acquisition)
Description of Fault
(please be as specific as
possible)
Was recovery possible?
How?
On receipt of this form, Coda Technologies will contact you and issue a reference number for
this report and describe the remedial action to be taken.
For Coda office use only: Reference Number:
February 2000 for version 1.40 99
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
100 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
GeoKit User Manual
Fourth
Fold -
tuck
into
flap

GeoKit User Manual
Product Feedback
We at Coda value your opinion. Please give us your opinion of our products, in each of the
following areas. We’ll send you a free mousemat on receipt of your form.
Product Name
Excellent Good Fair Poor
Ease of Use: is the product easy to use? r r r r
Hardware: is the hardware reliable? r r r r
Software: is the software reliable? r r r r
Range of Facilities: are there enough tools? r r r r
Appearance: Do you like the format of the display?
Physical: Is the product ergonomically
designed?
Suitability: Is the system suited to your application?
Automation: Do you rely on automated interpretation?
Does the product meet your need? Why, or why not?
r r r r
r r r r
r r r r
r r r r
What’s the single most important improvement we could make to the product?
Please complete the following information:
Name (optional):
Job Title or Function
Organisation
Address
Phone
If we need more information, may we contact you? Yes r No r Thank You
February 2000 for version 1.40 101
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
102 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
GeoKit User Manual
Fourth
Fold -
tuck
into
flap

GeoKit User Manual
Manual Feedback
We at Coda value your opinion. Please give us your opinion of this manual, in each of the
following areas. We’ll send you a free mousemat on receipt of your form.
Manual Title
Please complete the following information:
Excellent Good Fair Poor
Accuracy: Is the information correct? r r r r
Completeness: Is information missing? r r r r
Organisation: Is the information easy to find? r r r r
Clarity: Do you understand the information? r r r r
Examples: Are there enough? r r r r
Illustrations: Are there enough? r r r r
Appearance: Do you like the page format? r r r r
Physical Binding: Do you like the cover and binding?
Does the manual meet your need? Why, or why not?
r r r r
What’s the single most important improvement we could make to the manual?
Name (optional):
Job Title or Function
Organisation
Address
Phone
If we need more information, may we contact you? Yes r No r Thank You
February 2000 for version 1.40 103
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
104 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
GeoKit User Manual
Fourth
Fold -
tuck
into
flap

A
add mode 35
Add Tag Node(s) 37
Annotate Tag Node(s) 38–41
Application Specific Area
Coda systems 9
GeoKit 56–58
Applications menu 56
Apply button 11
B
boundary tag, described 34
Buttons (Fast Tag Setup pop-up),
assigning tags to 50
buttons. See particular buttons
C
Cancel button 11
checklists
for mobilising GeoKit/PI100
73–75
for saving/loading tag files
77
Coda systems
main display 9–10
menu features 10–15
pointer types 15–16
security device iii
Complete Multi-Node Tag 38
conversion table 81–83
corrected nav report mnemonics
69
D
Data Control Area 10
Data Display Area 9
Delete Tag Node(s) 37
deleting
tag files 44, 46
tag nodes 27, 37
tags from fast tag list 50
deselecting tag nodes 27, 36
E
event marking. See tagging
event, described 25
expanding box tag, described 35
F
Factory button 11
Fast Tag Area, Application
Specific Area 56–58
fast tag button, Fast Tag Area 56
fast tag keys, Fast Tag Area 56
Fast Tag Setup 49–50
fast tag setup
adding tags to list 50
changing fast tag colour 49
customising 29
deleting tags from list 50
loading a previous setup 29,
49
Index
pop-up, described 49
saving the current setup 29,
49
fast tag, pending 57
fast tagging
adding tags 57
creating tags 26
summary 58
Filter button 12, 13
forced measures 26
G
General Information Area 9
GeoKit
applications
site surveys 4
target detection 4
starting 21
using, an overview 25
glossary 85–98
I
Insert/Append Tag Node 38
interactive tagging. See tagging
K
key shortcuts 22
L
linear tag, described 34
Load button 11
Load Remote button 44
loading
fast tag setups 29, 49
pop-up settings 11–12
report setups 30, 51
tag files 43
tag setups 29
M
main display, Coda systems 9–10
Make Default button 12
Manage Tag Files
optical disk system 45–46
tape system 42–44
Measure button 41
measurement methods 67–68
Menu Bar 9
menu features 10–15
menus
See also particular menus
detaching from Menu Bar 9
Message Window 14
mobilisation checklists
for GeoKit/PI100 73–74
for the PI100 75
Move Tag Node(s) 37–38
O
OK button 11
on/off switch 10
one-of selection switch 10
105
on-line checklists
loading tag files 77
saving tag files 77
optical disks, recommended
brand iii
option selection button 10
P
placement rules. See forced
measures
pointer types 15–16
pop-up action buttons 11–13
pop-up selector 10
Position Area, Application
Specific Area 58
printer setup 55
printing, text reports 55–56
Q
quick-start procedure 21
R
Report Generation 54–56
Report Setup 51–54
report setup
adding columns 51–52
adding tag types 54
customising 30
deleting columns 51–52
deleting tag types 54
loading a previous setup 30,
51
multi-node tags 53
report headings 53
report separators 53
reportable items 52, 61–65
saving the current setup 30,
51
setting column parameters 51
sort order 53
text strings 53
Reporting menu 50–56
reports, generating
displaying in text window 54
instructions for 29
printing hardcopy 55
saving to floppy disk 55
Rescan button 44, 46
right mouse tag, setting up 48
S
Save button 11
saving
fast tag setups 29, 49
pop-up settings 12–13
report setups 30, 51
tag files 42
tag setups 29
scroll bar 14
Scrolling Option List 13
Select Default button 12
Select Factory Default button 12
Index

Index
select mode 35
selecting tag nodes 27, 35–36
settings, pop-up
loading 11–12
resetting to factory default 11
saving 12–13
storing as the default 11
Setup Tags 46–49
shortcuts 21
single tag, described 33
Spin Box 13
Spin Boxes 13
Store button 11
switches. See particular switches
system tags, changing settings 48
T
tab forms 15
tag database. See tag files
tag files
managing, optical system
copying to/from disk 45–
46
database location 45
deleting files 46
rescanning directory 46
selecting files 45
unmounting disks 46
managing, tape system
database location 42
deleting files 44
listing batches 43
loading batches 43
rescanning directory 44
saving batches to tape 43
selecting files 42
tag node measurements,
calculations for 67–68
tag nodes 33
See also tag types, tagging
tag properties, table of 61–65
tag setup
activating/deactivating tag
types 47
changing system tag settings
48
changing tag name/incident
code 47
customising 28–29
loading a previous setup 29
pop-up, described 46–47
saving the current setup 29
setting up right mouse tag 48
tag types
described 26, 33–35
initials in fast tag keys 57
symbols of 33
tagging
See also fast tagging
adding tag nodes 37
annotating tag nodes (see
Index
tags, annotating)
appending tag nodes 38
completing multi-node tags
38
creating tags 26–27
deleting tag nodes 27, 37
deselecting tag nodes 27, 36
inserting tag nodes 38
measuring tag dimensions 28
moving tag nodes 28, 37–38
overview 25, 33
selecting tag nodes 27, 35–36
Tagging menu 36–50
tagging modes
add mode 35
select mode 35
tags
See also tag types
described 33
replaying 36
tags, annotating
adding comments 41
changing tag name/anomaly
number 39
overview 27
updating tag data 38
updating tag dimensions 40–
41
viewing positional data 40
tapes, recommended brands iii
tear-off menus 9
terminology
commonly used terms 16–17
Text Window option, reports 54
Title Bar 9
Tool Bar 14
U
Unknown tag 49, 50, 57
Unmount button 46
Update All Tag Nodes button 39
Update Selected Node button 38
using GeoKit, an overview 25
106

Project: CODA-PI
Document Type: User Manual
Coda Part Number: KM001-015
CODA-PI User Manual
Document ID: Manuals on ‘Sister’ (J:)\CODA-PI\Version 2.02\CODA-PI.pdf
Confidentiality: General Distribution
Distribution: MASTER
Author Date Summary Manual
Version
DKR 26.09.95 Document Created 1.00
DKR 05.10.95 Updated 1.01
DKR 09.10.95 Updated 1.02
DKR 27.10.95 Updated 1.03
DKR 19.12.95 Updated 1.04
DKR 19.04.96 Updated 1.05
DKR 18.09.96 Updated 1.06
DKR 14.09.98 Updated 2.00
IMM 28.01.99 Updated for Software version 1.34.xx 2.01
DKR 29.02.00 Updated for Software version 1.40 2.02
Approved for Release: Date: 5 Mar 2000
Approved for Release: Date: 5 Mar 2000
Document is For Information Only unless it has original signatures above.

ii February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual
Read This First!
Coda systems are fitted with either a DAT or an Exabyte tape IO sub-system or an optical disk
IO sub-system. Both of the sub-systems are covered in this manual. The sets of instructions and
descriptions of the sub-systems are grouped together by task (Operating CODA-PI) and by menu
item (Reference Guide).
You should read the following information before using the system.
DAT Tapes
• Coda systems which are fitted with DAT drives use Digital Data Storage (DDS) certified
Digital Audio Tapes (DAT). Do not use audio DAT tapes: they will not function correctly.
• Use only DAT tapes with one of the following markings:
• We recommend that you use DAT tapes by the following manufacturers: TDK, HP, Verbatim
and Fujifilm.
Optical Disks
• We recommend that you use Maxoptix ISO 14517, rewritable, 2.6 GB polycarbonate disks
with 1024 bytes per sector – Maxoptix part no. 3015385 R/W – for systems fitted with optical
disk drives, though other major manufacturers’ rewritable disks can be used, provided that
they comply with ISO/IEC 14517.
Security Devices
• The Coda system uses a hardware security device (dongle) to prevent illicit copying of the
system’s software. (The security device is enclosed within the Coda system and under normal
circumstances you should be unaware of its presence.) Notwithstanding any other agreements,
the security device is the only proof Coda Technologies will accept of legal software
ownership. Under no circumstances will a replacement security device be issued unless the
original is returned.
Loss of the dongle means loss of the software!
February 2000 for version 1.40 iii

iv February 2000 for version 1.40
CODA-PI User Manual
Copyright © Coda Technologies Ltd, 2000
All Rights Reserved
Printed in UK
No part of this publication may be reproduced or transmitted in any form or by any means –
graphic, electronic, electrical, mechanical, or chemical, including photocopying, recording in
any medium, taping by any computer or information storage and retrieval system, etc. without
prior permissions in writing from Coda Technologies Ltd.
Coda Technologies Ltd, Admiral House, 29-30 Maritime Street, Edinburgh, EH6 6SE, UK
February 2000
Important Note to Users
While every effort has been made to ensure the accuracy and completeness of all information in
this document, Coda Technologies Ltd assumes no liability to any party for any loss or damage
caused by errors or omissions, or by statements of any kind in this document, its updates, supplements,
or special editions, whether such errors, omissions or statements result from negligence,
accident or any other cause. Coda Technologies further assumes no liability arising out of the
application or use of any product or system described herein; nor any liability for incidental or
consequential damages arising from the use of this document. Coda Technologies disclaims all
warranties regarding the information contained herein, whether expressed, implied or statutory,
including implied warranties of merchantability or fitness for a particular purpose. Coda
Technologies makes no representation that the interconnection of products in the manner
described herein will not infringe on existing or future patent rights, nor do the descriptions
contained herein imply the granting of any licence to make, use or sell equipment constructed in
accordance with this description.
Coda Technologies reserves the right to make changes to any products herein without further
notice.
Trademarks
Coda Technologies has made every effort to supply trademark information about company
names, products and services mentioned in this manual. Trademarks indicated below were
derived from various sources.
UNIX is a registered trademark
UnixWare is a trademark of The SantaCruz Operation Inc.
Novell is a registered trademark of Novell Inc.
Ethernet is a trademark of Xerox Corporation
MS-DOS and Windows are registered trademarks of Microsoft Corporation
Postscript is a registered trademark of Adobe Systems Inc.
Q-MIPS is a registered trademark of Triton Elics International
Maxoptix and T5-2600 are registered trademarks of Maxoptix Corporation
The SAS and FAS asynchronous I/O packages were developed by Uwe Doring and Jim Murray.
Coda Technologies Ltd did not develop and do not hold the copyright to these packages. The
original SAS package in its entirety is held in /home/PKG of the DA system.
xvertext 5.0, Copyright (c) 1993 Alan Richardson (mppa3@uk.ac.sussex.syma)
Permission to use, copy, modify, and distribute the xvertext software and its documentation for
any purpose and without fee is hereby granted, provided that the above copyright notice appears
in all copies and that both the copyright notice and this permission notice appear in supporting
documentation. All work developed as a consequence of the use of this program should duly
acknowledge such use. No representations are made about the suitability of this software for any
purpose. It is provided ‘as is’ without express or implied warranty.

Contents
Read This First! iii
I Introduction
1 Welcome 3
1.1 The CODA-PI Module 3
1.2 About this Manual 4
1.2.1 Conventions Used in this Manual 4
II The Basics
2 The Basics 7
2.1 The Main Display 7
2.1.1 The Menu Bar 7
2.1.1.1 Tear-off Menus 7
2.1.2 The Data Control Area 8
2.2 Menu Features 8
2.2.1 One-of Selection Switch 8
2.2.2 On/Off Switch 8
2.2.3 Option Selection Button 8
2.2.4 Pop-up Selector 8
2.2.5 Pop-up Action Buttons 9
2.2.5.1 Load Settings 9
2.2.5.2 Save Settings 10
2.2.6 Spin Box 11
2.2.7 Scrolling Option List 11
2.2.8 File Selection Area 11
2.2.9 Tool Bar 12
2.2.10 Message Window 12
2.2.11 Scroll Bar 12
2.2.12 Tab Forms 13
2.3 Pointer Types 13
2.4 Terminology 14
III Quick Start
3 Quick Reference 19
3.1 Quick-Start Procedure 19
3.2 Shortcuts 19
3.2.1 Key Shortcuts 19
IV Operating CODA-PI
4 Using CODA-PI 23
4.1 Overview of CODA-PI Usage 23
4.2 Interactive Tagging with CODA-PI 24
4.2.1 Overview of Interactive Tagging 24
4.2.2 Creating Tags in CODA-PI 24
4.2.2.1 Summary 25
4.2.3 Selecting and Deselecting Tags 25
4.2.4 Deleting Tags 25
4.2.5 Annotating Tags 25
4.2.6 Measuring Tag Dimensions 26
4.2.7 Moving Tags 26
4.3 Automatic Tagging with CODA-PI 27
4.3.1 Overview 27
4.3.2 Setting the Analysis Parameters 27
4.3.3 Displaying Pipeline Survey Data 28
4.3.4 Starting CODA-PI Automated Analysis 28
4.3.5 Displaying Pipeline Information 29
4.3.6 Editing Automatically Generated Pipe Events 29
v
Contents

Contents
4.3.7
Contents
Selecting Manually the Pipe Position 29
4.3.8 CODA-PI Analysis Limitations 29
4.3.9 Pausing and Stopping Automated Pipeline Analysis 30
4.3.10 ROTV Steering 30
4.3.11 Troubleshooting Automated Pipeline Inspection 30
4.4 Customising the Tag Setup 31
4.4.1 Setting up Tag Lists 31
4.4.2 Setting up Fast Tags 31
4.5 Reporting Tagged Events 32
4.6 Customising the Report Setup 32
V Reference Guide
5 Menu Reference 35
5.1 Tagging 35
5.1.1 Tag Types 35
5.1.1.1 Single Tags 35
5.1.1.2 Dual Tags 36
5.1.2 Tagging Modes 36
5.1.2.1 Add Mode 36
5.1.2.2 Select Mode 36
5.1.3 Selecting and Deselecting Tag Nodes 36
5.1.3.1 Selecting Tag Nodes 37
5.1.3.2 Deselecting Tag Nodes 37
5.1.4 Replaying Tags 37
5.2 The Tagging Menu 37
5.2.1 Add Tag Node(s) 38
5.2.2 Delete Tag Node(s) 38
5.2.3 Move Tag Node(s) 38
5.2.4 Insert/Append Tag Node 39
5.2.5 Complete Multi-Node Tag 39
5.2.6 Annotate Tag Node(s) 39
5.2.6.1 Node Identity Tab Form 40
5.2.6.2 Node Position Tab Form 41
5.2.6.3 Node Dimensions Tab Form 41
5.2.6.4 Node Text Tab Form 42
5.2.7 Manage Tag Files (tape system) 43
5.2.7.1 Tape Load/Save 43
5.2.7.2 Delete 45
5.2.7.3 Rescan 46
5.2.8 Manage Tag Files (optical disk system) 46
5.2.8.1 Copy Tag Files 46
5.2.8.2 Delete 47
5.2.8.3 Rescan 47
5.2.8.4 Unmount 47
5.2.9 Setup Tags 47
5.2.10 Tag Activation 48
5.2.10.1 Tag Active 48
5.2.10.2 Tag Name and Incident Code 48
5.2.11 System Tag Setup 49
5.2.12 Right Mouse Tag 50
5.2.13 Fast Tag Setup 51
5.2.13.1 Fast Tag Colour 51
5.2.13.2 Add Tag 51
5.2.13.3 Delete Tag 52
5.2.13.4 Delete All Tags 52
5.3 The Reporting Menu 52
5.3.1 Report Setup 52
5.3.1.1 Report Setup Format 53
5.3.1.2 Report Setup Options 54
5.3.1.3 Report Setup Contents 55
5.3.2 Report Generation 56
5.3.2.1 Printer Setup Window 57
vi

Contents
5.4 The Applications Menu 58
5.5 The Application Specific Area 58
5.5.1 Pipeline Inspection Mode 58
5.5.1.1 Fast Tagging 59
5.5.2 The Analysis Control Area 61
5.5.2.1 Start Analysis 61
5.5.2.2 Stop Analysis 61
5.5.2.3 Pause Analysis 61
5.5.2.4 Analysis Parameters 61
5.5.2.5 Pipe Data 62
5.5.2.6 Reset Pipe Position 63
5.5.2.7 Position Information Area 63
VI Appendices
A Span Height Estimation 67
A.1 Initial Span Height Estimation 67
A.2 Comparison with Formula in Alan Cameron’s Paper 68
A.3 Tracking Angle and Beam Width 69
B CODA-PI Report Contents 71
B.1 Table of Tag Properties 71
C Calculations for Tag Node Measurements 77
C.1 Measurement Methods 77
D Corrected Nav Report Mnemonics 79
D.1 Measure Mnemonics 79
D.2 Sonar Mnemonics 79
D.3 Node Mnemonics 79
VII Checklists
E Mobilisation Checklists 83
E.1 GeoKit/CODA-PI Mobilisation Checklist 83
E.2 CODA-PI Mobilisation Checklist 85
F On-Line Checklists 87
F.1 Saving Tag Files to Tape/Disk Checklist 87
F.2 Loading Tag Files to System Hard Disk Checklist 87
VIII Glossary & Conversions
Conversion Table 91
Glossary 95
Software Defect Report Form 109
Product Feedback 111
Manual Feedback 113
vii
Contents

Contents
Contents
viii

Part I: Introduction
Introduction

Introduction
2 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual 1.1 The CODA-PI Module
1 Welcome
Congratulations on buying or hiring the CODA-PI system. Your investment in the CODA-PI
will make working with your sonar data easier and faster.
The CODA-PI provides automated interpretation tools and a suite of interactive enhancement
and event-marking tools, all of which are designed to improve data interpretation and report
generation. Whether you are new to digital sonar acquisition, an experienced data processor or a
professional geophysicist, you will find the CODA-PI a reliable and versatile system for
acquiring (with a CODA-DA System), displaying, processing and interpreting sonar data.
The CODA-PI has been developed by:
Coda Technologies Ltd
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
tel: +44 131 553 1380
fax: +44 131 554 7143
e-mail: coda@coda-technologies.com
www: http://www.coda-technologies.com
Coda’s Technical Support service is available 24 hours a day:
USA – tel: 1 888 340 CODA
Rest of the World – tel: +44 131 553 7003.
See ‘Technical Support’ on the inside front cover for full details.
Coda’s American subsidiary is:
Coda Technologies Inc.
9800 Richmond Avenue
Suite 480
Houston
Texas 77042
USA
tel: 1 713 780 3223
fax: 1 713 780 3280
e-mail: coda@coda-technologies.com
http://www.coda-technologies.com
1.1 The CODA-PI Module
CODA-PI provides extensive processing and interpretation tools for sidescan sonar pipeline
inspection. Automated interpretation tools are available to automatically detect spans, partial
burial, and regions of exposure. In addition, interpretation and reporting tools are provided to
allow an event list to be compiled, annotated and stored to a database for ultimately generating
a pipeline event report.
February 2000 for version 1.40 3
Introduction

Introduction
1.2 About this Manual CODA-PI User Manual
1.2 About this Manual
This manual is designed to help you get the most out of the CODA-PI software, whatever your
level of experience.
• Part II: The Basics – contains basic information about Coda systems’ display features and
types of pointers, as well as the terminology used in Coda manuals. If you are new to CODA-
PI, we recommend that you read this section before using the system.
• Part III: Quick Reference – includes a quick-start procedure, which summarises the instructions
for operating CODA-PI. It also contains a list o f tips and shortcuts to speed up using
the system. If you are an experienced data processor, you can use this section to refresh your
memory about the operating procedures.
• Part IV: Operating CODA-PI – contains operating instructions for CODA-PI. They explain
HOW TO DO SOMETHING (for example, annotate tags), through step-by-step instructions, and
give hints on how to get the best out of the system. These sections are intended for users at
any level of experience.
• Part V: Reference Guide – describes in detail the areas of the CODA-PI display and the
various menus and menu items available with the system. It explains WHAT CAN BE DONE (for
example, the range of tag types available for event marking). Reading through these sections
reveals the true power and flexibility of the system.
• Part VI: Appendices – explains the calculations used in estimating span height and in
measuring distances, and describes the contents of CODA-PI reports and corrected nav report
mnemonics.
• Part VII: Checklists – contains checklists for mobilising CODA-PI, saving tag files, loading
tag files, and using tag and reporting setups during data interpretation.
• Part VIII: Glossary & Conversions – contains a table of useful conversions; a full list of the
terminology used in this manual; and a software defect report form, product feedback form
and manual feedback form.
1.2.1 Conventions Used in this Manual
As you read this manual, bear in mind the following conventions:
• Italics indicates words or phrases that are explained in the Glossary and modes of operation.
• This font identifies menu items and data control buttons. When two or three menu items are
joined by an arrow you must select the first item and then the second or third; for example,
File→Open Acquisition means that you must click on File on the Menu Bar and then, in the
pull-down menu that appears, click on Open Acquisition.
• Keyboard keys appear within greater and lesser symbols. When key names are joined by a
hyphen (-) you must hold down the first key, press the other key and then release both keys.
For example, means you must hold down and press .
• British English spelling is used throughout this manual.
• To keep instructions brief, we refer to clicking or pressing a MOUSE button, rather than a
MOUSE OR TRACKBALL button. If your system comes with the optional trackball, click or
press the appropriate button. If no button is specified, use the left button.
4 February 2000 for version 1.40

Part II: The Basics
The Basics

The Basics
6 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual 2.1 The Main Display
2 The Basics
Coda’s systems use menus, pop-up windows, text-entry boxes, key shortcuts and so on in a
similar way to other windows applications. If you are familiar with Microsoft Windows®, or the
X Windows system, you will immediately find the operation of Coda’s systems familiar. If you
are not familiar with other windows applications, you will find the main features and terms
explained below.
2.1 The Main Display
The main display has six areas, as shown in Figure 2-1, this page. Five of the areas – Title Bar,
Menu Bar, Data Display Area, General Information Area and Data Control Area – are identical
for all Coda systems and software modules; their functions are explained in Section 5 of the DA
System User Manual. The Application Specific Area, however, changes according to the application
being used; its functions in CODA-PI are explained in Section 5.5 of this manual.
Tool Bar
Figure 2-1 The Main Display in Data Acquisition Mode
2.1.1 The Menu Bar
Menu Bar
Data Display Area
Title Bar
General Information Area Application Specific Area
Data Control Area
Message Bar
The Menu Bar lies across the top of the screen throughout operation of CODA-PI. It displays
eight menu options: File, Display, Settings, Tagging, Reporting, Applications, Processing
and Help. When you click on any of these options (that is, you move the pointer over an option
and then click the left mouse button), a pull-down menu appears. The functions of the various
menu options are explained in Part II of the DA User Manual.
2.1.1.1 Tear-off Menus
The pull-down menus can be detached from the Menu Bar and moved around the screen; they
remain on screen until dismissed. To detach a pull-down menu, select the dotted tear-off strip at
the top of the menu; this changes the menu to a pop-up window. To move the window, press and
drag it to another part of the screen (that is, move the pointer over the window’s titlebar, press
the left mouse button and hold it down while you drag the pointer to the desired position, then
release the mouse button). To dismiss the window, double-click on the button in the top left
corner of the window, or position the pointer over the window and press .
February 2000 for version 1.40 7
The Basics

The Basics
2.2 Menu Features CODA-PI User Manual
2.1.2 The Data Control Area
Figure 2-2 The Data Control Buttons
The seven data control buttons, which are located at the bottom of the main display, are on/off
switches. A button appears recessed or ‘pressed’ when it is enabled (or on). To toggle a button
on or off, simply click on it. The functions of the various data control buttons are explained in
Section 5 of the DA System User Manual.
2.2 Menu Features
2.2.1 One-of Selection Switch
Figure 2-3 One-of Selection Switches
The diamond button (or toggle) is a one-of selection switch for a group of options, only one of
which can be selected at a time. To change the selection, click on another diamond button. In the
example above, from the Report Setup Options menu, the green diamond indicates that the Tab
option has been selected; the Space and Comma options are automatically deselected.
2.2.2 On/Off Switch
Figure 2-4 On/Off Switches
The square button is an on/off switch. When the square is grey the option is disabled (or off);
when the square is green the option is enabled (or on). More than one on/off switch can be
enabled. To toggle from one setting to another, click on the square button. In the example above,
also from the Report Setup Options menu, Enclose text in double quotes has been selected.
2.2.3 Option Selection Button
Figure 2-5 An Option Selection Button
The option button displays a currently held value and indicates that other values can be selected.
In Figure 2-5, this page, from the Processing→Fish Height/Bottom Tracking menu, the fish
height calculation function is set to copy data from data channel 2 as its source. Click on the
option button to display a list of other options (in this case, active channels) and then drag the
pointer to another channel to select that channel as the data source for fish height calculations.
2.2.4 Pop-up Selector
Figure 2-6 Pop-up Window Selectors
The three-point ellipsis (...) is appended to some menu items and indicates that selection of the
item will cause a pop-up window to appear; the window will contain further selections associated
with the menu item. This hierarchical structure enables the comprehensive functions of CODA-
8 February 2000 for version 1.40

CODA-PI User Manual 2.2 Menu Features
PI to be accessed in a way that is logical and easy to understand. In the example above, from the
Settings menu, selecting Playback Speed will open a pop-up which contains three possible
settings for the speed at which data can be replayed.
2.2.5 Pop-up Action Buttons
Figure 2-7 Pop-up Action Buttons
Action buttons are positioned at the bottom of pop-ups; they are used either to confirm changes
made within the pop-up or to cancel those changes. Click on the OK button to confirm the
changes and dismiss the pop-up from the screen; click on the Apply button to confirm the
changes but retain the pop-up on screen. Click on the Cancel button to cancel the changes and
leave the previous settings as the current definition.
Additional action buttons are displayed on some pop-ups:
Figure 2-8 Store and Factory Action Buttons
Click on the Store button to store the settings of the current pop-up as the default setting. Click
on the Factory button to reset the settings to Coda Technologies’ original settings. To revert to
the Factory settings as the default setting after the default setting has been changed, click on the
Factory button and then the Store button.
Figure 2-9 Load and Save Action Buttons
Click on the Load button to load previously saved settings for the current pop-up. Click on the
Save button to save the current pop-up settings to file for reloading at a later date.
2.2.5.1 Load Settings
Figure 2-10, this page, shows an example of a Load Settings pop-up; this pop-up appears when
you click on the Load button in the Format tab form of the Reporting→Report Setup menu.
Figure 2-10 A Load Settings Pop-up Window
February 2000 for version 1.40 9
The Basics

The Basics
2.2 Menu Features CODA-PI User Manual
Click on the Select Default button to make the default file the selected file; the name of the
default file appears beside the Default Filename label. Click on the Select Factory Default
button to reset the pop-up to Coda Technologies’ original setting; the string ‘FACTORY
DEFAULT SELECTED’ appears in the File Name text-entry box at the bottom of the pop-up.
Click on the Drive option button to select the drive from which to load the settings file; only Hard
Disk is currently available.
Use the Files window to search and view particular settings files. Enter the desired search pattern
in the File Type Filter text-entry box and then press the Filter button. All the files that pass the
search pattern appear in the Files list. To select a settings file from the list, click on the file name;
the File Name text-entry box is updated to display the selected file. Alternatively, if you know
the file name, move the pointer into the File Name text-entry box and type the file name.
Click on the Delete button to remove the currently selected file from the hard disk. In the window
that appears asking for confirmation, click on the Yes button to delete the file or the No button
to abort the delete. If the file to be deleted is the default file, a window appears asking for confirmation.
•Note: All settings files have a ‘.set’ ending. Files cannot be loaded if the directory is not shown.
Trying to do so results in an error.
Click on the Apply button or the OK button to load the settings stored in the file shown in the
File Name window. If no file has been selected, a warning window appears. Click on the Done
button to cancel any changes made to the settings and dismiss the Load Settings pop-up.
2.2.5.2 Save Settings
Figure 2-11, this page, shows an example of a Save Settings pop-up; this pop-up appears when
you click on the Save button in the Format tab form of the Reporting→Report Setup menu.
Figure 2-11 A Save Settings Pop-up Window
Click on the Make Default button to make the selected file the default file; the name of the file
appears beside the Default Filename label. If no file is selected, the settings are saved to a file
called ‘unnamed.default.set’.
Click on the Drive option button to select the drive to which to save the setting file; only Hard
Disk is currently available.
10 February 2000 for version 1.40

CODA-PI User Manual 2.2 Menu Features
Use the Files window to search and view particular settings files. Enter the desired search pattern
in the File Type Filter text-entry box and then press the Filter button. All the files that pass the
search pattern appear in the Files list. To select a settings file from the list, click on the file name;
the File Name text-entry box is updated to display the selected file. Alternatively, if you know
the file name, move the pointer into the File Name text-entry box and type the file name.
Click on the Delete button to remove the currently selected file from the hard disk. In the window
that appears asking for confirmation, click on the Yes button to delete the file or the No button
to abort the delete. If the file to be deleted is the default file, a window appears asking for confirmation.
•Note: All settings files have a ‘.set’ ending. Files cannot be saved if the directory is not shown.
Trying to do so results in an error.
Click on the Apply button or the OK button to save the current settings to the file shown in the
File Name window. If no file has been selected, a warning window appears. Click on the Done
button to cancel changes made to the settings and dismiss the Save Settings pop-up window.
2.2.6 Spin Box
Figure 2-12 A Spin Box
Spin boxes appear in pop-ups where you are required to specify a numerical setting. You can
either click in the box and type the required numbers or use the up and down arrows to change
to the correct setting. Pressing and dragging on the horizontal bar between the up and down
arrows allows you to alter the value, too – if you drag upwards, the value will increase, and if
you drag downwards the value will decrease.
2.2.7 Scrolling Option List
Figure 2-13 A Scrolling Option List
Scrolling option lists consist of a text area and a down arrow. They provide a flexible method of
choosing from a list of available options. Click on the down arrow to display the list of options.
You can then move through the list by typing the first letters of your chosen option or by using
the up and down arrows on your keyboard. Each option will be highlighted as you scroll onto it.
To select the highlighted option, either press the space bar or , or click on it with the
mouse. To reset your selection, use either the left or right arrow on your keyboard. You can then
begin making our selection again. To scroll directly to your chosen option, click in the text box
and use the keyboard arrows to move to your choice. To dismiss the list, either press or
click outside the list area.
2.2.8 File Selection Area
Figure 2-14 A File Selection Area
February 2000 for version 1.40 11
The Basics

The Basics
2.2 Menu Features CODA-PI User Manual
The file selection area appears in pop-ups where you can load or save files. In this area you can
choose the file type using the File Type Filter text entry box, change the filter using the Filter
button, scroll through a list of the available files and enter the name of the file you require in the
File Name text entry box, or double-click on the list. You may delete files from the list (and the
disk) using the Delete button.
2.2.9 Tool Bar
Figure 2-15 A Tool Bar
Directly below the Menu Bar of each window in the display is a Tool Bar. The icons included
in the Tool Bar allow you to perform a number of operations within the window without opening
the relevant menus (see Section 5.3).
2.2.10 Message Window
Figure 2-16 The Message Window
A Message Window appears at the bottom of each of the windows of CODA-PI. This gives
time-stamped CODA system information. As they appear, messages are colour coded, red for
errors, blue for warnings and black for information. Once a new message appears, the older one
disappears and is stored in black in the list of messages created since your system was started up.
You can scroll through this list by clicking on the down arrow at the side of the window.
2.2.11 Scroll Bar
Figure 2-17 A Scroll Bar
The scroll bar appears at the bottom or on the side of some pop-ups and indicates that only part
of a list of items is currently being displayed. To view other items in the list, click on the arrows
in the scroll bar or press and drag the scroll box in the scroll bar up or down, or to the left or right.
12 February 2000 for version 1.40

CODA-PI User Manual 2.3 Pointer Types
2.2.12 Tab Forms
Figure 2-18 A Tab Form
Some pop-ups have several tab forms; for example, the Tag Setup pop-up from the Tagging
menu has eight tab forms (see Figure 2-18, this page). A tab form contains a number of related
items of information or selections and has a labelled tab at the top; they are arranged so that they
overlap each other. To select a tab form, click on its tab. This brings the form to the front of the
pile; the information can then be read and changes made to it. When a tab label is greyed out it
cannot be accessed.
2.3 Pointer Types
Eight mouse pointers are used in the CODA-PI system.
The arrow pointer is the pointer type most commonly used in the CODA-PI.
The pencil pointer is used to create tags.
Keyboard shortcuts: to
The crosshair pointer is used to make on-screen measurements and appears when
the CODA-PI is in measure mode.
Keyboard shortcut:
The zoom pointer appears when the CODA-PI is in zoom mode.
Keyboard shortcut:
The move pointer is used to move tags.
Keyboard shortcut:
The watch pointer appears when the system is waiting for an operation to complete.
The automatic tracking pointer is used to reset the bottom tracking position.
Keyboard shortcut:
The text-entry pointer appears when the pointer is placed in a text-entry box and is
used to enter text in the selected field of a pop-up.
When the pointer is in a particular mode – for example, for moving or deleting tags – you must
complete the operation, or deselect the mode, before selecting another pointer mode. If you fail
to do so, a warning pop-up appears on screen, reminding you that a pointer operation is already
February 2000 for version 1.40 13
The Basics

The Basics
2.4 Terminology CODA-PI User Manual
in progress. Click on the OK button to dismiss the pop-up and then complete the pointer
operation, or deselect the mode, before continuing to the next pointer operation. Deselecting a
mode usually involves repeating the action for selecting the mode.
2.4 Terminology
The most common computer terms used in this manual are defined below. A more complete list
of terms can be found in the Glossary at the end of this manual.
Apply this button applies the settings or options selected and retains the pop-up
window on screen.
Cancel this button cancels any items or options selected and dismisses the pop-up
window; the previous settings are retained.
click press down and release the appropriate mouse button. If no button is
specified, use the left button.
double-click press and release the appropriate mouse button twice in rapid succession. If
no button is specified, use the left button.
information
window
14 February 2000 for version 1.40
a window that provides information during acquisition or playback; this
information cannot be edited. It can be displayed for any length of time, and
is dismissed by clicking on the OK or Done button.
Menu Bar the area at the top of the main display in which eight menu options are
permanently displayed: File, Display, Settings, Tagging, Reporting,
Applications, Processing and Help. Selecting any of the options causes
a pull-down menu to appear.
OK this button selects and applies the settings or options selected and dismisses
the pop-up window from the screen.
pop-up menu an option selection menu with a specific user-alterable value or parameter.
pop-up
window
press and
drag
pull-down
menu
a general term applied to a window that automatically appears when a menu
item or control function is selected; it may be a text-entry box (in which you
type your requirement), or an area of information (which requires no action
on your part). In this manual this phrase is abbreviated to pop-up.
position the pointer over an object, press the left mouse button and hold it
down while you drag the object to the desired position, then release the
mouse button. If no button is specified, the left button should be used.
a pop-up that appears directly beneath an option in the Menu Bar when that
option is selected.
scroll bar the means by which all the items in a list appearing in a menu or pop-up
window may be examined.
select click the left mouse button on the appropriate item (such as a menu item,
toggle or value selection).
select a
menu item
click the left mouse button on a Menu Bar option, and then release the
mouse button over an item in the pull-down menu that appears below the
Menu Bar option.
tab form a form that contains a number of related items of information or selections
and has a labelled tab at the top. As tab forms overlap, the required tab form
may have to be brought to the front of the pile by clicking on its tab.
tear-off
menu
a pull-down menu that can be detached from the Menu Bar for permanent
display.

CODA-PI User Manual 2.4 Terminology
text-entry
box
an area in a window for entering text or numerical values. Click within the
rectangular area and type text or edit the text using the keyboard.
toggle switch from one setting to another, usually between on and off. A toggle
switch is a switch that has just two positions.
toolkit a pop-up that contains various tools for processing the data, for example
TVG and Image Enhancement. Each pop-up contains an interactive graph
and several smart icons.
February 2000 for version 1.40 15
The Basics

The Basics
2.4 Terminology CODA-PI User Manual
16 February 2000 for version 1.40

Part III: Quick Start
Quick Start

Quick Start
18 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual 3.1 Quick-Start Procedure
3 Quick Reference
This section includes a quick-start procedure, which summarises the basic instructions for
operating CODA-PI. It also contains a list of tips and shortcuts to help you work more quickly
and efficiently.
The quick-start procedure is intended for those of you who are already familiar with the system;
for a more detailed guide to using CODA-PI, refer to Section 5.5 which describes the functions
of the Application Specific Area.
3.1 Quick-Start Procedure
1. Set up the DA System for playback or data acquisition, as outlined in Section 5 of the DA
System User Manual.
2. Select Applications→Pipeline Inspection.
3. Select Tagging→Setup Tags and either define tag types and their placement rules or load a
previously saved file of tag setups to use in the current survey.
The system always starts with the current default setups.
4. Select Tagging→Fast Tag Setup and assign the fast tag keys in the Application Specific
Area.
To mark and annotate events:
1. Switch on the Message Window in the Display menu.
2. Select the appropriate tag type from the fast tag keys in the Application Specific Area to
activate add mode.
3. Mark the required event within the sonar data on the screen.
Single tag events require one click operation to mark the event, whereas dual tag events
require two click operations, one to mark the beginning and the other to mark the end of the
event.
4. Perform any measurements required by the tag setup.
5. Annotate events either by selecting Tagging→Annotate Tag Node(s) and clicking again on
the appropriate on-screen tag, or by using the keyboard shortcut .
6. Ensure that all information is stored to the database.
To save tag files:
1. When you have finished event marking during data replay or acquisition, save the tag file to
a new, blank tape or optical disk using Tagging→Manage Tag Files.
2. Label all tapes or optical disks correctly.
To generate a report:
1. Set up the report contents and layout using the Report Setup options in the Reporting menu.
2. Generate a report to the screen, to floppy disk or directly to a printer using Report Generation
options in the Reporting menu.
3. Label all reports correctly.
3.2 Shortcuts
Various shortcuts are supported by the programme to enable you to work more quickly and
efficiently with your data.
3.2.1 Key Shortcuts
Many of the common commands can be carried out using key shortcuts. A key shortcut is a single
keystroke or a combination of keystrokes that executes a command.
February 2000 for version 1.40 19
Quick Start

Quick Start
3.2 Shortcuts CODA-PI User Manual
The key can be used to activate pull-down menus. To do this, press and hold down the
key and then press the key of the underlined letter in the required option in the Menu Bar.
For example, pressing causes the File menu to appear. An item from the pull-down menu
can be selected by pressing the key for the underlined letter of the required menu item’s name.
A list of other keyboard shortcuts can be displayed on screen by selecting Help→Key Shortcuts.
The number of shortcut keys available, however, depends on the module of CODA-PI being
used. A few of the most common shortcuts are listed below.
Key To Do This
Annotate currently selected tag node
Reset automatic bottom tracking position using mouse
Make on-screen measurements
Zoom
Toggle pause button. (Pauses scrolling screen)
Dismiss status pop-up window
Some keyboard shortcuts are also listed in the pop-up menus; for example, appears
in more than one pop-up. However, note that these shortcuts are only available when the pointer
is in the Data Display Area.
20 February 2000 for version 1.40

Part IV: Operating CODA-PI
Operating
CODA-PI

Operating
CODA-PI
22 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual 4.1 Overview of CODA-PI Usage
4 Using CODA-PI
4.1 Overview of CODA-PI Usage
See also: Appendix E
We recommend that inexperienced operators spend some time using CODA-PI in playback
mode to become familiar with the look and feel of the interface. A sample tape or disk of data
acquired using CODA-PI is provided to enable you to become familiar with the system. You
should also refer to Section 4.2 of this manual and to Section 5 of the DA System User Manual.
o Switch to Pipeline Inspection in the Applications menu.
o Ensure that the data is displayed to the screen. If you are recording data, ensure that it is being
recorded to the correct drive by clicking on the Record button and checking that the appropriate
LED is on. If you are replaying or recording data, the data should be displayed on the
Data Display Area of the screen.
o An event is a feature of interest in the data. It is marked with a tag. In CODA-PI, an event
can be a single point (and is therefore marked with a single tag) or it can have start and end
points (and is therefore marked with a dual tag with start and end nodes).
o Use the Setup Tags item in the Tagging menu to define tag types and their placement rules
(that is, measurements which you will be forced to make when placing tags – known as
forced measures). Alternatively, use the same menu item to load a previously saved file of
tag setups to use in the current survey, or to save the current setup for future use. The Tag
Setup pop-up also allows you to assign feature codes to each event which will be logged
automatically to the database when events are marked to the screen.
o Assign the fast tag keys in the Application Specific Area by using the Fast Tag Setup option
in the Tagging menu. Up to 12 fast tags may be allocated to the function keys at the top of
the keyboard, and you can determine the colour they appear on the screen. The tag types
which can be added are those already activated using Tagging→SetupTags. Alternatively,
save the current setup for future use or load a previously saved file of fast tag setups.
o If pipeline events such as spans and exposures are to be tagged automatically, set up CODA-
PI for automated inspection by entering the required values in the Analysis Parameters
window then pressing Start Analysis (see Section 4.3.4).
o If an event appears that cannot be tagged automatically, click on the appropriate button in the
Fast Tag Area and then tag the event in the Data Display Area by clicking on it with the left
mouse button (see Section 4.2.2), or if no appropriate fast tag exists, mark it with an
Unknown tag (for example, using the R. Mouse Tag if this is set to Unknown).
o All tagged events, whether created interactively or automatically, are logged to a tag
database, allowing the tags to be displayed on data replay. Once created, tags can be selected
and then manipulated, for instance by annotation, measurement or movement. Any modification
to a tag automatically updates its entry in the tag database. Annotation is a particularly
powerful tool, as it allows the tag type to be changed, dimensions to be measured and text to
be associated with the tag.
o The contents of a tag database can also be reported in the form of a body of text (see Section
4.5). The format and contents of the report can be specified by you (see Section 4.6).
February 2000 for version 1.40 23
Operating
CODA-PI

Operating
CODA-PI
4.2 Interactive Tagging with CODA-PI CODA-PI User Manual
4.2 Interactive Tagging with CODA-PI
See also: Section 4.1; Section 4.2.2; Section 5.2; Section 5.5; as well as Section 10 of the DA
System User Manual
4.2.1 Overview of Interactive Tagging
Whereas the DA System is restricted to single tags, allowing events to be marked by a single
point, events with start and end points can be marked using the two-ended dual tags available in
CODA-PI. Pipeline inspection reports can also be generated using CODA-PI’s additional
tagging facilities: principally tag annotation, movement and measurement. Using the Setup
Tags option in the Tagging menu, you can define a large number of tag types to suit the
anomalies in the survey and specify additional information to be logged to the database for each
of those tag types (see Section 5.2.9). Once set up, such a file can be saved and used on further
surveys. Colour-coded fast tag keys, which can be used to mark single and dual (start and end)
events, are available in the Application Specific Area of the display screen. The Fast Tag Setup
may be customised either by loading a file of previously saved fast tag definitions, or by
changing the definitions of each fast tag key (see Section 5.2.13). The right mouse button may
also have a specific single tag assigned to it via the R. Mouse tab in the Setup Tags option of
the Tagging menu.
The full navigational and position information of the associated ping is stored with each tag node.
Additional information about individual tags can be stored by using the Annotate Tag Node(s)
option in the Tagging menu (see Section 5.2.6).
4.2.2 Creating Tags in CODA-PI
See also: Section 5.5
A suite of specific event markers (fast tags) can be selected from the Application Specific Area
of the CODA-PI display. These enhanced tagging features are colour coded for easy identification
on the screen. Select (and deselect) the tag required by clicking the left mouse button on
the appropriate fast tag button, or by pressing the appropriate keyboard function key, and then
moving the mouse pointer (now shaped like a pencil) to the area of interest. Clicking with the
left mouse button will mark and tag the event with the desired tag type.
When a tag button or label is clicked on in the Fast Tag Area, prior to adding a tag, the appropriate
fast tag button stays depressed and the label is surrounded by a black border. This indicates
that the tag is the pending fast tag.
For features where there is a single specific localised area of interest on the screen (for example,
mattress or localised debris), a colour-coded square appears on the screen centred on the point
where the left mouse button is released; this is known as a single tag. Tag information, including
type and location, is automatically logged to the event database. Single tags are denoted in the
Fast Tag Area by the letter ‘S’ on the fast tag button.
For features which cover an area of screen (for example, spans, burial, entrenchment) dual tags
are available to denote the start and end of the event. Dual tags are indicated in the Application
Specific Area by a ‘D’ in the fast tag button. Begin the tag by selecting the fast tag with the mouse
or from the keyboard, and clicking on the Data Display Area to define the position of the first tag
node. The start tag node ( ) will appear on the screen. The button in the Application Specific
Area will stay depressed and its label will be coloured green to show that the tag is incomplete
as the other end of the event has still to be tagged. You then click in the Data Display Area to
define the second tag node; the end tag node ( ) will then appear on the screen. If the start
tag node has not scrolled off the bottom of the screen, the start and end tag nodes are joined by
a line.
•Note: Additional tag types, including multi-node linear tags and boundary tags, are available in
the CODA-GeoKit software package.
In Tagging→Setup Tags it is possible to define a set of placement rules that force measurements
to be carried out when tags are placed. In this instance, the crosshair measure pointer will then
appear on the screen and you must make the required measurements before any further tag nodes
can be placed.
24 February 2000 for version 1.40

CODA-PI User Manual 4.2 Interactive Tagging with CODA-PI
When all the required measurements have been made, the pointer will revert to the add mode
pencil pointer, allowing you to place another node of the same type. To cancel add mode (to
enable other tagging operations) you must deselect the pending fast tag by clicking on its corresponding
button in the Application Specific Area.
When a tag is created, tag information, including event type, location of the start and end nodes
and any required measurements, is automatically logged to the event database. Further
annotation, using the Tagging→Annotate Tag Node(s) menu is outlined in Section 5.2.6.
4.2.2.1 Summary
1. Switch on the Message Window in the Display menu.
2. Select the appropriate fast tag in the Application Specific Area, using either the mouse or the
assigned function key.
3. Mark the screen (Data Display Area) with this tag by clicking on the location of the event,
and make the required measurements. Single point events (single tags) will require one click,
whereas start and end type events (dual tags) will require two clicks to mark both locations.
4. Make any required measurements to complete the tag.
4.2.3 Selecting and Deselecting Tags
See also: Section 5.1.3
When you wish to manipulate a tag or one of its nodes, you must first put CODA-PI in select
mode. You do this by clicking once on a node to select it or by double-clicking on one of the
nodes of a dual tag to select the entire tag. The selected node (or nodes) will flash blue and the
pointer in the Data Display Area will change from a PENCIL to an ARROW. The selected node (or
nodes) can then be manipulated (for example, moved, annotated, deleted).
To deselect a node, simply click on it again. The node will cease to flash, indicating that it has
been deselected. To deselect both nodes in a selected dual tag either double-click on either of the
selected nodes or click on a node of a different tag.
4.2.4 Deleting Tags
See also: Section 5.1.3; Section 5.2.2
Key shortcut: or
To delete a tag node, first select the node by clicking on it in the Data Display Area (the selected
node will flash blue), then either select the Delete Tag Node(s) item in the Tagging menu, or
press (for ‘kill’) or on the keyboard. This is not possible when in add mode (see
Section 5.2.2). When the tag has been successfully deleted, the node will disappear from the
display and will be removed from the database. To delete an entire dual tag, double-click over
the tag in the display so that both nodes are flashing. Delete the nodes as described above.
When the start node of a dual tag is deleted, the end node will automatically be redrawn as a start
node. However, if you wish the node to be reported as an end node, this can be changed by
clicking on the appropriate button in the Annotate pop-up (see Section 5.2.6.1).
•Note: It is recommended that dual tags are deleted only after both ends have been displayed on
the Data Display Area. This, particularly during automated analysis, avoids the possibility that a
start node is generated and deleted before its corresponding end tag is generated. The end node
would thus be unable to find its associated start node and would prompt the production of an error
message.
4.2.5 Annotating Tags
See also: Section 4.2.3; Section 5.2.6
Key shortcut:
Annotation allows you to add more detailed information to the database entry for a given tag or
selected nodes within the tag. Only a selected node can be annotated (see Section 4.2.3). To
annotate, either select the Annotate Tag Node(s) item from the Tagging menu, or use the
keyboard shortcut , having first ensured that the pointer is in the Data Display Area.
February 2000 for version 1.40 25
Operating
CODA-PI

Operating
CODA-PI
4.2 Interactive Tagging with CODA-PI CODA-PI User Manual
In addition to the information that CODA-PI automatically stores about each user-defined tag
(tag type, position, system ID, and any previously made measurements), you can use the Dimensions
tab form to include a variety of additional measurements, and the Identity tab form to
change the tag’s name and give the anomaly its own identification number. A description of the
feature and notes about comparison/action may also be added in the Text tab form. In this tab
form the tag may also be marked in the database for further inspection and information can be
added about the geophysicist and quality controller associated with annotating the tag nodes.
You can change this information at any time during acquisition or playback and save the changes
by selecting Update Selected Node to make changes to the selected node alone, or Update All
Tag Nodes to make changes to the entire tag. In addition, the tag name may be changed by
clicking on the Tag Name button and selecting another option from the list which appears. (It
should be noted, however, that tags can only be changed from one single tag to another or from
one dual tag to another.) Updating the tag file using the Annotate Tag Node(s) tab form is
described in further detail in Section 5.2.6.
4.2.6 Measuring Tag Dimensions
See also: Section 5.2.6.3; Appendix C; as well as Section 10 of the DA System User Manual
Key shortcuts: , , , , , ,
The following dimensions can be measured with CODA-PI:
• length
• width
• height
• depth
• span height
• offset to feature
• true range to fish
Once a tag node is selected, measurements can be performed by pressing the appropriate key
shortcut or clicking on the corresponding button in the Dimensions tab of the Annotation popup
(see Section 5.2.6.3). In addition, the Annotation pop-up allows dimensions to be entered by
hand.
Dimension measures are carried out in the same manner as Processing→Measure (see
Appendix C and also Section 10 of the DA System User Manual). When the crosshair pointer
appears, move to the position defining the start of the measure and press the left mouse button.
Then drag the pointer to the end of the measure and release the button. The measure can be
aborted by clicking again on the appropriate key shortcut. Once a measure is completed, the tag
database is immediately updated.
•Note: The span height is calculated using the Pipe Diameter set in the CODA-PI Analysis
Parameters pop-up (see Section 5.5.2.4). If this value does not correspond to the pipeline’s actual
diameter, the span height obtained will be erroneous.
4.2.7 Moving Tags
See also: Section 5.2.3
Key shortcut:
Tag nodes which have already been placed may be moved using the Tagging→Move Tag
Node(s) menu option. Pressing cuts the selected nodes from the screen. A click with the
left mouse button pastes the nodes back in, the last selected node being positioned at the point of
clicking with the rest of the selected nodes undergoing the same displacement. Prior to pasting,
the move operation can be cancelled by pressing the key shortcut again.
26 February 2000 for version 1.40

CODA-PI User Manual 4.3 Automatic Tagging with CODA-PI
4.3 Automatic Tagging with CODA-PI
See also: Section 5.5.1; Appendix E
The automated side of pipeline inspection has been designed to track exposed pipelines and
measure pipeline survey events without the need for continuous manual intervention. The
pipeline events which can be identified automatically are short spans, critical spans, exposures
and burials. These, like manually tagged events, are stored to the event database. The two sets of
tags are easily distinguished in the report phase, however, where the Tag Source column will
contain flags A and M to indicate automatic and manual tags respectively (see Section 5.3.1.1).
4.3.1 Overview
See also: Section 5.4; Section 10 of the DA System User Manual
After Pipeline Inspection has been selected from the Applications menu a number of steps
should be followed before starting automated pipeline analysis. Sidescan sonar data should be
scrolling on the screen, fully scaled and with the pipeline visible, so that it is clear which channel
the pipeline is to be found in.
1. Click on the Analysis Params button in the Application Specific Area of the display to open
the CODA-PI Analysis Parameters pop-up.
2. In the CODA-PI Analysis Parameters window, set the correct analysis parameters for
• pipeline diameter (in inches) and correction (%)
• critical span length (in metres) and height trigger (in metres)
• minimum event length (in metres) and merge event length (in metres)
• pipe grazing angle minimum (°) and maximum (°);
and set
• the correct channel to be processed, that is the display channel which contains the pipeline
to be inspected (either left or right)
• the Zoom Window toggle if required, to display the CODA-PI zoom window.
3. Start playing back the data.
4. Start automated interpretation by pressing the Start Analysis button in the Application
Specific Area of the screen.
5. Reset the pipe position if required, using the Reset Pipe Pos button in the Application
Specific Area.
All tag events which are detected will be displayed to the screen. All information will also be
logged automatically to the event database.
•Note: Automated pipeline inspection will track only one pipeline within a sonar trace. It is very
important that analysis parameters are entered correctly before starting analysis, as they can
significantly affect the frequency and accuracy of automatically generated event tags.
4.3.2 Setting the Analysis Parameters
See also: Section 5.5.1; Section 5.5.2.4
CODA-PI’s analysis parameters can be updated in the Analysis Parameters pop-up, which is
opened by clicking on the Analysis Params button in the Application Specific Area.
The most important paramenter is Pipe Diameter. Expressed in inches, this parameter enables
the automated analysis to calculate measurements such as span height or extent of pipe burial. It
is therefore vital that pipe diameter is entered correctly. It may be necessary to take into account
the thickness of cladding around the pipe (for example, a 36in pipe with 1in of cladding may
require a value of 38in to be entered).
A Pipe Diameter Correction factor (as a percentage of the true pipe diameter) can be entered if
it is known that the span heights calculated by the automated span detection software may be in
error. This may be the case if the pipe is not sitting on a flat seabed.
February 2000 for version 1.40 27
Operating
CODA-PI

Operating
CODA-PI
4.3 Automatic Tagging with CODA-PI CODA-PI User Manual
The remaining pipeline parameters control the type and frequency of the automatically generated
pipe event tags. In the Span Values text-entry box, the Critical Length, expressed in metres,
determines the threshold above which the span tag type changes from a ‘short span’ to a ‘critical
span’; and the Height Trigger determines the minimum gap between the seabed and the pipeline
for which the pipe is considered to be spanning. In the Event Values text-entry box, Merge
Length (measured in metres) determines the distance below which two neighbouring events of
the same type are merged into one single event. As such, this parameter is intended to prevent
long events from being broken up by short distances over which the event is no longer being
tracked. Selecting a long merge length will therefore have the overall effect of generating fewer,
but longer, events. The Minimum Length field similarly allows you to set a threshold (again
measured in metres) for the commencement of tagging of spans. This ensures that spans which
are too short to be of significance are not marked and therefore not stored in the event database.
The Grazing Angle (measured in degrees) is used to define the limits of grazing angle considered
permissible for a given survey and will in future be used to mark tag entries in the database report
file as being in or out of specified survey limits; however, at present these entries are unused.
The Process Channel section allows you to select which display channel is to be processed. By
default CODA-PI will process the data in the right screen channel. In addition, you can toggle
the Zoom Window on or off. When Zoom Window is on, you can see a real-time display of a
zoomed image around the region of the pipeline. This is displayed in the channel of the display
area which is not being used for automated pipeline inspection.
When all the analysis parameters have been entered correctly, they may be applied by clicking
on the OK button. The current pop-up settings can be saved to file for future use by clicking on
the Save button, or a file of previously saved settings can be loaded for the current pop-up by
clicking on the Load button (see Section 2.2.5.1 and Section 2.2.5.2). Selecting the Cancel
button ensures the analysis parameters remain unchanged. It is important to note, however, that
these parameters can be updated at any time during the pipeline survey by selecting the Analysis
Parameters button.
•Note: The pipeline diameter entered in the Analysis Parameters pop-up is used for span height
calculation for both automatic and manual tags.
4.3.3 Displaying Pipeline Survey Data
See also: Section 5.5.1; Section 5.5.2.5; as well as Section 8 of the DA System User Manual
Clicking on the Pipe Data button in the Application Specific Area opens the Pipeline Survey
Data pop-up, which allows you to monitor statistics arising from the automated pipeline
tracking. In addition to the fish height options selected manually in the Processing menu,
CODA-PI automatically updates the Pipe Grazing Angle (or Pipe Striking Angle), the Pipe
Distance (slant distance) from the survey vessel, and the Pipe Height from the seabed to the
bottom of the pipe. To see a visual display of this information, click on the Graphic button at the
bottom of the pop-up. Both of these information windows are dismissed by clicking on their
respective Close buttons.
It should be noted that if pipeline analysis is not switched on, or if CODA-PI is not actually
tracking a pipeline when switched on, some parameters in the Pipeline Survey Data window
will be blank and the Pipe Striking Angle/Height Graphic will not be updated.
4.3.4 Starting CODA-PI Automated Analysis
See also: Section 5.5.1; Section 5.5.2.1
Once data is scrolling on screen, CODA-PI Automated Analysis can be started by clicking on
the Start Analysis button. Initially there will be no noticeable change in the display as the ‘preanalysis’
sonar data is emptied from the display buffer. When the processed data appears,
however, the operator will notice that coloured pipe position markers are displayed over the data.
28 February 2000 for version 1.40

CODA-PI User Manual 4.3 Automatic Tagging with CODA-PI
4.3.5 Displaying Pipeline Information
See also: Section 4.3.2; Section 5.2.11; Section 5.5.2.4
The Analysis Parameters pop-up allows you to select a zoomed display of the processed
channel. This gives you both a standard magnification view and an enlarged view of the
processed pipeline inspection data. The standard view is displayed in the screen channel which
was selected for processing, while the remaining channel shows the magnified view. When the
pipeline is present and detectable, the focus of the zoom for this screen channel will be the centre
of the pipe. If the pipeline is not detectable, the focus will be at the last known position of the
pipeline in the sonar trace.
As with manual event tagging, automatically generated colour-coded tags are laid over the sonar
data. Wider strips of the same colour are displayed alongside these tags; these indicate the
positional parameters in the pipeline tracking (seen, for example, at the front of the pipe). These
lines are not part of tags and therefore cannot be removed. This helps you distinguish between
manually and automatically generated tags. The wide coloured strips indicate the presence and
along-track extent of automated interpretation results, whereas the tag marks denote what is
being stored to the event database. The colour coding of these tags and strips corresponds to
those set up in the System tab of the Tag Setup pop-up (see Section 5.2.11).
4.3.6 Editing Automatically Generated Pipe Events
See also: Section 4.2.3; Section 4.2.4; Section 4.2.5
As with manually generated event tags, automatically generated tags can be edited; for example,
they can be deleted or annotated. Thus, you can enter a client anomaly number, a description of
the event, or flag the need for further inspection.
4.3.7 Selecting Manually the Pipe Position
See also: Section 5.5.1; Section 5.5.2.6
Automatic pipeline inspection may fail to track the intended pipe, either because it cannot find
the pipe or because it tracks a different pipe. In either case, you can point manually to the pipeline
of interest by choosing the Reset Pipe Pos option in the Application Specific Area.
To select the pipe position manually, click on the Reset Pipe Pos button. This will change the
pointer to an automatic tracking pointer (see Section 2.3). Move the pointer into the Data Display
Area. As there is a slight delay between processing and displaying the data, position the pointer
towards the top of the display to ensure that the position selected is closest to the position of the
pipe in the incoming data. Click on the desired pipe position with the left mouse button. The
pointer will revert to an arrow pointer.
You will not see the pipe tracking being re-positioned immediately because the processed data
is buffered before being displayed on the screen. It will take a few seconds to appear.
4.3.8 CODA-PI Analysis Limitations
Automated pipeline processing has been designed specifically to detect and measure spans in
clearly exposed pipelines on a flat seabed. In addition, it can detect instances of pipe exposure,
pipe burial and partial pipe burial. There are, however, a few situations in which automated
processing is unlikely to perform as intended.
o The pipeline is entrenched.
o Some pipe features are hidden, making the detection of pipe events unreliable.
Automated processing should be turned off and the pipe events tagged manually.
o The pipeline diameter is less than 12in, making detection of the pipe and its corresponding
shadow unreliable.
Automated processing should be turned off and the pipe events tagged manually.
o The pipe is close to the first seabed return.
February 2000 for version 1.40 29
Operating
CODA-PI

Operating
CODA-PI
4.3 Automatic Tagging with CODA-PI CODA-PI User Manual
In this situation, the pipe shadow will tend to be too narrow to track reliably because the fish
will be almost over the pipeline. The solution is either to ensure that the pipeline is positioned
further down the sonar trace or to tag the pipe events manually.
o The pipeline passes through highly undulating seabeds (for example, sand waves). Under
these conditions, the software may begin to track the wrong shadow.
Automated processing should be turned off and the pipe events tagged manually.
4.3.9 Pausing and Stopping Automated Pipeline Analysis
See also: Section 5.5.1; Section 5.5.2.2; Section 5.5.2.3
CODA-PI processing can be stopped by clicking on the Stop Analysis button in the Application
Specific Area. This stops all automatic detection of pipe events. As with starting the automated
pipeline analysis, you will not immediately be aware from the display that automatic processing
has ceased. This is because it takes a few seconds for the processed data to empty from the buffer.
Stopping analysis will cause processing to stop completely. Restarting analysis, by clicking the
Start Analysis button, will begin a completely new analysis, with all previous internal pipeline
analysis statistics and context information discarded. Note that this does not discard any previously
generated events from the database.
Although clicking the Pause Analysis button achieves almost the same result as clicking Stop
Analysis, pausing analysis suspends automated processing without discarding the previous
internal pipeline attributes and statistics (gathered by the automated processing). Once the Pause
Analysis button is reselected, analysis will recommence using the information gathered earlier
in the analysis.
Pausing or stopping analysis does not prevent you from tagging pipe events manually.
4.3.10 ROTV Steering
For details about the ROTV Steering option, contact Coda Technologies directly.
4.3.11 Troubleshooting Automated Pipeline Inspection
See also: Section 4.3.7; Section 5.5.2.4
o Automated inspection is generating span events where there are no spans present.
Either the selected pipe diameter is too small or the merge event length is too long. Select
Analysis Parameters and either increase the pipe diameter or reduce the merge event length.
o Automated inspection is not generating span events where they are clearly present.
The selected pipe diameter is probably too large. Select Analysis Parameters and reduce the
pipe diameter in the text-entry box.
o Automated inspection is generating many short pipe events where there should be one longer
event.
The merge event length is probably too short. Increase the merge event length in Analysis
Parameters.
o Automated inspection is missing the intended pipeline.
Reposition the pipe tracking position using Reset Pipe Pos in the Application Specific Area.
o Automated inspection is tracking the wrong pipeline.
Reposition the pipe tracking position using Reset Pipe Pos in the Application Specific Area.
30 February 2000 for version 1.40

CODA-PI User Manual 4.4 Customising the Tag Setup
4.4 Customising the Tag Setup
See also: Section 5.2.9; Section 5.2.13; Section 5.5; Section 5.5.1.1; Appendix E
4.4.1 Setting up Tag Lists
See also: Appendix E
To give CODA-PI users a high degree of flexibility, the names, codes and properties (that is, tag
identity) can be customised for each survey. For each tag type available, there is a tab in the
Tagging→Setup Tags pop-up defining a list of all possible tag identities.
•Note: The tag setup should be defined during mobilisation and before commencing data interpretation,
since making modifications during interpretation may lead to inconsistencies in data
storage and reporting.
To make a tag available (for example, for fast tagging and reporting purposes), the tag should be
activated via the Tag Active button (up to 255 separate active tag identities are possible per tag
type). Tags other than System tags can also be activated by double-clicking on the tag name in
the list of Tag Names or by hitting in one of the text fields when the tag is selected in
the list. You can also assign a unique Tag Name and tag Incident Code.
Within the tab form, you can also define the Tag Properties for a tag (for example, Forced User
Measures) which are followed when the tag is placed. The Message Window (selected from the
Display menu) will indicate which measurements, if any, must be made when tag nodes are
placed in the data.
The Tag Setup pop-up also has two further tabs, for System tag setup and R. Mouse tag setup.
In the System tab, you can set up the incident codes and system tag colours. In the R. Mouse tag
tab, you can pick from the full list of active single tags in order to assign a tag identity to the right
mouse button.
To use a previously saved file of tag setups, for example to ensure consistency with previous
reports, click on the Load button at the bottom of the Tag Setup pop-up. This will produce a
Load Settings pop-up listing all of the available tag setups which may be loaded, together with
a button for loading the Default tag setup. To load a file, click on the file name and confirm by
clicking on OK.
Changes made to the Tag Setup may be saved for future use by clicking the Save option. This
will produce a Save Settings pop-up, allowing you to specify the name of the file in the File
Name text-entry box. Alternatively, an existing tag setup can be overwritten by selecting one
from the current list. This pop-up also allows you to allocate the current tag setup as the default
by clicking on the Make Default button.
Once all modifications have been made to the Tag Setup, click on OK. Any changes which were
made to the Tag Setup will be applied to the Report Setup and will therefore affect subsequent
report generation. In addition, the labels will change on the appropriate fast tag keys in the Application
Specific Area.
•Note: Tag setups are not stored to the tag database. Thus if the tagging and reporting options
are to contain the correct tag names and incident codes, the correct Tag Setup file should always
be loaded.
4.4.2 Setting up Fast Tags
See also: Appendix E
The Fast Tag Area is provided to allow you to quickly place tags in the Data Display Area. The
Fast Tag Setup can be customised, to specify a setup for each survey. Typically, tags chosen to
be fast tags are those most likely to be accessed during the survey. Up to 12 fast tags may be
assigned.
Clicking on Tagging→Fast Tag Setup produces the Fast Tag Setup pop-up. This pop-up
displays a list of all the current fast tags, plus their fast tag colour. To change the fast tag colour,
click on the coloured option button and drag the pointer over the new colour. To add a new fast
tag, click on the Add Tag button and select a tag from the list of all active tags. To delete a fast
tag, select the fast tag by clicking on it and then click on the Delete Tag button.
February 2000 for version 1.40 31
Operating
CODA-PI

Operating
CODA-PI
4.5 Reporting Tagged Events CODA-PI User Manual
As with the Tag Setup, fast tag setups can be both saved and loaded. Once all modifications have
been made to the Fast Tag Setup, you should click on OK.
4.5 Reporting Tagged Events
See also: Section 5.3.2
Tag database files are in binary, machine-readable format to allow them to be read and interpreted
rapidly by CODA-PI. To generate an on-screen, floppy disk or hardcopy tag database
report in ASCII format (as defined by the Report Setup):
1. Open the Reporting→Report Generation pop-up.
2. Select the tag file for which you wish to generate a report.
3. Choose between Text Window, Printer and Floppy Disk output.
Selection of the Text Window option will cause the completed report to be displayed in a
window on the CODA-PI screen, allowing you to browse through it. The Printer option
causes the report to be output to the printer defined by the Printer Setup pop-up. Floppy
output of the report requires a blank DOS-formatted floppy disk to be present in the floppy
disk drive, and saves the report to the disk, allowing it to be imported by database, spreadsheet
or word processing packages.
4. Click on the Generate Report button to produce the report.
5. Exit the pop-up by clicking on Done.
•Note: The length of file which can be displayed in a Text Window report is limited to 2000 entries.
•Note: Copying the report file to floppy disk will take much longer if the system is being used for
playback or acquisition at the same time. To complete the report generation on floppy disk as
quickly as possible, pause the screen until the report output to floppy has been completed.
4.6 Customising the Report Setup
See also: Section 5.3.1; Appendix E
By using the Report Setup option of the Reporting menu, you can define the information to be
included in subsequent reports and how the data will be presented. Within the Report Setup, the
Format can be defined by adding and deleting columns and specifying their contents, including
the Label for the columns, the column Width, and the Precision with which the data will be
reported (that is the number of decimal places to be included). Scrolling down the pop-up allows
the details of each column of the report to be checked.
The Options tab form allows you to define details of labelling and separating columns, how dual
tags will be reported, the presentation of text strings and how the report will be sorted. In the
Contents tab form, you can specify which tags should be included in the report.
To use a previously saved file of report format setups, thus ensuring consistent reporting between
surveys, use the Load button. Clicking on this button will produce a list of files which may be
selected from the appropriate directory. To select a default file, click on either the Select Default
(your default) or Select Factory Default button. To select a file, click on the file name and
confirm by clicking on OK.
Changes made to the Report Setup may be saved for future use by using the Save button.
Clicking on the Save button will produce a pop-up showing the appropriate directory and file
extension for saving the file. To name the file, place the pointer in the File Name text-entry box
and type the file name and extension after the pathway provided by CODA-PI. To make the
report setup the default setup, click on the Make Default button.
When all the changes to the Report Setup have been made, click on OK.
32 February 2000 for version 1.40

Part V: Reference Guide
Reference
Guide

Reference
Guide
34 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual 5.1 Tagging
5 Menu Reference
5.1 Tagging
See also: Section 4.2; Section 4.3; Section 5.2; Section 5.2.9; Section 5.5.1; as well as
Section 10 of the DA System User Manual
A tag is an entity used to mark events which occur in the data. Each tag may consist of a single
point (used, for example, to mark a small target on the seabed) or may be composed of two points
(used, for example, to mark a length of pipeline spanning). One tag may be used to mark an event
that crosses from one data channel to the other. Individual points within a tag are known as tag
nodes; a tag which consists of more than one node is known as a multi-node tag. The first node
placed in the tag is known as the creator node.
Tag nodes appear as small, coloured symbols overlying the point in the data where the event was
marked. Different types of tags have different symbols, (see Figure 5-1, this page). You can
define up to 255 different tag identities for each of the available tag types (see Section 5.2.9).
Tagging can be performed during either acquisition or data playback. Once tags have been
created for a data set, they are saved to the database and can be replayed as required (see Section
10 of the DA System User Manual). Specific pipeline inspection anomaly events can also be
tagged from the automated pipeline inspection processing software (see Section 5.5.1).
5.1.1 Tag Types
Single and dual tags are available in CODA-PI, as well as system and right mouse tags; multinode
tags are NOT available. Figure 5-1, this page, shows the symbols which are used to create
the types of tag available in the CODA-PI software.
Single Tag Node Start Node End Node
Figure 5-1 Symbols of Tag Types available in CODA-PI
5.1.1.1 Single Tags
See also: Section 5.2.12
Figure 5-2 Single Tag
Single tags are markers for single point events which can be represented by a one-node tag; for
example, anodes and pock marks on the seabed. Single tags are the only type of tag which can
be set up as the right mouse button tag (see Section 5.2.12).
February 2000 for version 1.40 35
Reference
Guide

Reference
Guide
5.1 Tagging CODA-PI User Manual
5.1.1.2 Dual Tags
Figure 5-3 Dual Tag
Dual tags consist of a start node and an end node with an inter-node link drawn automatically to
join the start and end nodes. An incomplete dual tag is one in which one of these nodes is missing.
Examples of events where dual tags might be used include pipe spans and trawl scars. It is
possible to swap the start and end node incident codes using the Annotate Tag Node(s) menu
item.
5.1.2 Tagging Modes
CODA-PI has two distinct tagging modes, each of which is detailed below.
5.1.2.1 Add Mode
This mode allows you to place tag nodes of the desired type. Add mode is indicated by the pointer
in the Data Display Area changing from the usual ARROW to a PENCIL. You can change from
select mode to add mode by clicking on one of the fast tag buttons in the Fast Tag Area, or by
pressing the appropriate function key. A tag node with this identity can then be placed in the Data
Display Area. Once the tag node is placed, the system remains in add mode, allowing you to add
more nodes of the same identity by clicking with the left mouse button. To cancel add mode,
deselect the pending tag placement by clicking on the appropriate fast tag button, or by pressing
the appropriate function key.
Note that, whilst the last node placed in add mode is always made the selected node, this
selection cannot be changed until select mode is active.
5.1.2.2 Select Mode
See also: Section 5.2.12
Select mode allows nodes to be marked for subsequent tag operations and manipulation, for
example annotation, deletion, and moving. It also prevents the addition of tag nodes other than
right mouse tag nodes (see Section 5.2.12).
You can change from add mode to select mode in one of two ways. You can select
Tagging→Add Tag Node(s), or you can select the pending tag – as displayed by a black
rectangle in the Fast Tag Area – either by clicking on the fast tag button or by pressing the appropriate
function key.
Select mode is indicated by an arrow pointer in the Data Display Area. A tag node may be
selected by clicking on the node with the left mouse button. A dual tag may have either of its
nodes selected. Selected tag nodes flash between their normal colour and light blue.
5.1.3 Selecting and Deselecting Tag Nodes
See also: Section 5.1.2.2; Section 5.2.2; Section 5.2.3; Section 5.2.6
Once a tag node has been placed, you may wish to manipulate it. For instance, a node may need
to be moved or deleted (see Section 5.2.3, Section 5.2.2). Alternatively, you may wish to update
some of a node’s parameters and therefore will need to use the Annotate Tag Node(s) pop-up
(see Section 5.2.6).
36 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
Nodes can only be manipulated if they are selected. They cannot be selected when CODA-PI is
in add mode; CODA-PI must be in select mode (see Section 5.1.2.2).
5.1.3.1 Selecting Tag Nodes
See also: Section 5.2.2; Section 5.2.3; Section 5.2.6
Once CODA-PI is in select mode, any node in a tag may be selected. Position the arrow pointer
over the desired node in the Data Display Area and click with the left mouse button. A selected
node will flash between its usual tag colour and light blue. If the tag is a dual tag, both nodes may
be selected within the same tag.
If both of the nodes in a dual tag are required for selection, a shortcut is provided: double-click
over one of the nodes. The entire tag will be selected, including any node off screen at the time
of selection.
Once the required nodes have been selected, you can perform tag manipulations, such as moving
or deleting the tag or nodes. If you wish to annotate nodes, each node must be selected separately,
as it is not possible to annotate more than one node at a time.
5.1.3.2 Deselecting Tag Nodes
A selected node can be deselected simply by clicking on it. The node will cease to flash,
indicating that it has been deselected. Both of the nodes in a dual tag can be deselected either by
double-clicking on one of the tag’s selected nodes or by selecting a node in a different tag.
•Note: When a selected node of a dual tag scrolls off the display it remains selected, but will be
deselected automatically when the second node in the tag scrolls off screen.
5.1.4 Replaying Tags
See also: Section 5.2.7; Section 5.2.8; Appendix F; as well as Section 10 of the DA System
User Manual
CODA-PI automatically labels each sonar data file on a Coda format data tape or optical disk
with the file name of its associated tag file. If the selected tag file is in the tag file directory of
the system hard disk or optical disk, the tags in the file will automatically be replayed along with
the data from the tape or optical disk during playback. Loading tag files from tape, saving tag
files to tape, and copying tag files to and from optical disk are described in Section 10 of the DA
System User Manual.
If the Overlay Data toggle in the Display menu is on, then the tags will be overlaid on the sonar
data. If this toggle is off, the tags are still read from the file but they are not displayed to the
screen.
5.2 The Tagging Menu
This menu contains the facilities for creating and deleting tags, and for manipulating tag files.
Figure 5-4 The Tagging Menu
February 2000 for version 1.40 37
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
5.2.1 Add Tag Node(s)
See also: Section 2.3; Section 4.2.2; Section 5.2.12; Section 5.5
Selection of this menu item causes the mouse pointer to change from an arrow to a pencil (see
Section 2.3). If the pencil is placed in the display area and the left mouse button pressed, a tag
node will be marked. The tag type will always be that of the right mouse tag. If the menu item
has been selected, but no tagging is required, or if no further tags are to be added, reselection of
the Add Tag Node(s) menu item will cause the pencil pointer to be replaced by the usual mouse
pointer; the tagging operation will be abandoned.
Single tags can also be added without the use of the Tagging menu, by positioning the mouse
pointer as required in the display area and pressing the right mouse button. However, performing
tagging in this way does not leave the system in add mode. The tag type added can be set up via
the R. Mouse tab for of the Tag Setup pop-up (see Section 5.2.12). Additional tagging tools
available for Pipeline Inspection are described in Section 5.5.
5.2.2 Delete Tag Node(s)
See also: Section 4.2.4; Section 5.1.2.1
Key shortcut: or
Selection of this menu item, or the letter (for kill) or the key on the keyboard,
deletes all the selected nodes from both the Data Display Area and the tag database. You can
therefore decide whether to delete an entire tag or just one of its nodes. After deleting the selected
node or nodes, there will be no tag nodes selected.
If Delete Tag Node(s) is selected but no tag nodes are selected, a warning will appear in the
message bar: ‘No nodes currently selected’.
It is not possible to delete a tag or nodes when CODA-PI is in add mode, even though the last tag
node added is a selected node (see Section 5.1.2.1).
5.2.3 Move Tag Node(s)
See also: Section 2.3; Section 4.2.7; Section 5.1.3.1
Key shortcut:
Move Tag Node(s) allows you to move one or more tag nodes to a different position in the
display. The function may be selected from the Tagging menu, or by using the key shortcut .
Tag nodes must be selected before they can be moved (see Section 5.1.3.1). If Move Tag
Node(s) is selected but no tag nodes are selected, a warning will appear in the display area: ‘No
nodes currently selected’.
The move operation consists of two stages. First the selected nodes are removed from the display
area and the tag database. The pointer then changes to the move pointer (see Section 2.3). Once
you have moved the pointer to the position in the display area where the selected nodes are to be
pasted back into the display, a click should be made with the left mouse button. If a single node
has been moved, it will be repositioned at this point. If start and end nodes are being moved, this
point will be the position of reinsertion of the last node selected prior to the move. The other node
selected is moved with the same relative displacement as this node. (Nodes selected by doubleclicking
are moved relative to the node which was double-clicked on.)
•Note: If an entire tag is to be moved, it is moved with the pointer in the position of the last node
selected or the last node double-clicked on. If a further move is attempted without reselecting the
nodes, the system will automatically reselect all the nodes selected for the original move. The
node placed at the pointer position will now be the end node of the tag.
Once the move has been completed, the last selection will remain active to allow further actions
(for example measurements) to be taken.
Currently tag nodes may only be moved within the same data channel; if the new position for any
of the tag nodes is outwith the valid area of the display, you will hear a warning beep. The move
pointer will remain until the tag nodes are repositioned correctly. Similarly, a move which would
38 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
result in any of the selected tag nodes being placed off screen is not permitted and you will be
warned that the move is not possible. The move pointer will remain until the nodes are repositioned
correctly.
A move may be cancelled and the selected nodes returned to their original positions by selecting
Move Tag Node(s) or by pressing the key shortcut again.
5.2.4 Insert/Append Tag Node
See also: Section 5.5.1.1
Key shortcut:
This menu item allows you to append a start or an end node to a dual tag which is missing one
of these nodes. Nodes cannot be appended to single tags. Inserting tag nodes – creating a new
node between two adjacent nodes – is only possible in multi-node tags, such as those available
in CODA-GeoKit.
To append nodes, the system must be in select mode, with either the start or end node of the
incomplete dual tag selected. Selecting the Insert/Append Tag Node option switches the system
into one of two add modes, depending on whether the selected tag is a fast tag or not.
• fast tag add mode: for an incomplete fast tag with the end node selected, clicking the left
mouse button appends a tag and the system remains in add mode.
• append add mode: for non-fast tags, clicking the left mouse button appends a node and the
system reverts to select mode.
An append operation may be cancelled by pressing the shortcut key in append add mode, or
by clicking on the appropriate fast tag button if in fast tag add mode.
5.2.5 Complete Multi-Node Tag
This menu item is available only in CODA-GeoKit.
5.2.6 Annotate Tag Node(s)
Key shortcut:
This option allows you to update the data associated with the selected tag node. To access the
option, you must have selected a node within a tag (see Section 5.1.3.1).
The tab form displayed when the Annotate Tag Node(s) window is popped up contains four
tabs, allowing different fields of information to be updated.
When all the required annotation has been completed, the changes can be accepted in one of two
ways. Clicking on Update Selected Node will apply all changes to the selected tag node alone
and will dismiss the Annotate Tag Node(s) pop-up. (The exception to this rule is the case where
the Tag Name is changed, and is therefore given a new tag identity, when all nodes in the tag are
given the new tag name.) Alternatively, clicking on Update All Tag Nodes applies the changes
made to all the nodes within the tag, including nodes off screen and also dismisses the Annotate
Tag Node(s) window.
•Note: Changes are always made to the database and screen representations of tag nodes.
If the Annotate Tag Node(s) window is on screen when a selected node is about to scroll off
screen, the display will pause automatically to allow you to complete the annotation. If pause is
released and the tag node scrolls off screen, the Annotate Tag Node(s) pop-up is dismissed,
losing any unsaved annotation.
It is possible to display more than one annotate pop-up on screen at a time by selecting another
tag node and then clicking on Annotate Tag Node(s) before dismissing the previous Annotate
Tag Node(s) pop-up.
February 2000 for version 1.40 39
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
5.2.6.1 Node Identity Tab Form
Figure 5-5 The Node Identity Tab Form
The node identity tab form of the Annotate Tag Node(s) pop-up allows you to change the Tag
Name and the tag node Anomaly Number. It lists further information associated with the tag
node, including Incident Code and System ID. If the selected node is from a dual tag, both its
start and end tag incident codes will be displayed.
To change the Tag Name (and therefore the tag identity), click on the button displaying the
current Tag Name. A list of the available options will appear. This list will contain all the active
tags of this tag type as well as the ‘Unknown’ tag, which is always available. (For this reason it
is not possible to change tag types.) The new name may then be selected by clicking on the
chosen Tag Name. When the Update All Tag Nodes button is pressed, the change will be
applied to all nodes within that tag and, if visible in the display, the tag will be redrawn in the
new tag colour.
Where the Anomaly Number is to be changed, the changes should be typed in the text field. The
Anomaly Number field is provided to allow you to associate a unique identifier with each tag
node.
When the selected node is part of a dual tag, two additional options are available to be toggled
on or off. If Swap dual tag node incident codes is on, the start and end incident codes are
swapped so that the start node is reported as the end node and vice versa. This is useful if a dual
tag start node is on its own and needs to be reported as an end event. If Warn on missing dual
tag nodes is on you will be warned during annotation or report generation if a dual tag is found
to be missing its end node.
40 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
5.2.6.2 Node Position Tab Form
Figure 5-6 : The Node Position Tab Form
The node position form details the positional parameters associated with the tag node. It is
provided solely for information and QC purposes, since the position of nodes can only be altered
using the Move Tag Nodes(s) option of the Tagging Menu (see Section 5.2.3).
Raw nav position data is displayed on the left of the tab form, while corrected nav data (if
available) is displayed on the right.
5.2.6.3 Node Dimensions Tab Form
See also: Appendix C; as well as Section 8.6 of the DA System User Manual
Figure 5-7 The Node Dimensions Tab Form
The Dimensions tab form allows you to update the dimensions of the tag for the node. It contains
five frames, each with a button allowing you to make the relevant measurement. The Height
frame button allows you to choose whether to measure the Height, Depth or Span of the object.
The default is Height, but the type of measurement selected will remain until changed by you.
(When sub-bottom data is being annotated, the Height field becomes a Depth to Horizon field,
making the Height and Span options unavailable.) Each frame also contains a text field which
allows you to enter a value manually.
February 2000 for version 1.40 41
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
Measure
Clicking on the Measure button beside any of the dimensions on the form will indent the button
and cause the pointer to change from an arrow to the crosshair pointer (see Section 2.3). You can
then measure the dimension in the display area in the same manner as a Processing→Measure
operation (see Appendix C and also Section 8.6 of the DA System User Manual), using the
mouse button to press and release. Once the measurement is completed, the measurement is
displayed in the text field and the Measure button is no longer indented. (The start and end
positions of the measure will be saved to the tag database immediately, regardless of whether one
of the Update buttons is pressed.) This allows corrected nav to be applied to the dimensions at a
later date.
To cancel a measure operation, press the indented Measure button, or press the Measure button
in another area of the form. The latter will cancel the first measure and initiate the measure in the
second area of the form.
Using the dimension shortcut keys will also affect the status of a Measure button. For example,
if a Length measure is under way, with the Measure button indented in the usual way, and the
key is pressed, the measure will be cancelled and the Measure button will revert to its
unselected state. Similarly if no measurements are selected and a shortcut key is used, the appropriate
Measure button will indent as if the button had been pressed. You should continue to
measure in the usual way.
Measurements made in this manner are stored internally as two end points and automatically get
distance values recalculated whenever the value is displayed in the system or output to a report.
This means that changing any navigation parameters via corrected nav will cause the distance
values to be updated (see Section 6.6 of the DA System User Manual). This implies that measurements
can be placed on raw data, and then prior to generating a report, a corrected nav file can
be loaded to obtain the most accurate measurement values. When a report is generated, those nav
parameters that have been corrected and used to calculate a measurement value can be indicated
in the report. This allows the integrity of measurement values to be monitored (see Appendix A
and Appendix C).
Dimensions Using Text Entry
The node’s dimensions may also be changed by you typing an entry in the appropriate text field.
However, such a value will not have the necessary associated positional information to allow
navigation correction to be applied in the future.
5.2.6.4 Node Text Tab Form
Figure 5-8 The Node Text Tab Form
42 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
This form contains text fields allowing you to add comments about the feature being annotated.
For the Description and Comparison/Action fields, the text entry can be scrolled through using
the scroll bar at the side of each of the text-entry boxes. Also included are an on/off toggle to
allow you to indicate where Further Inspection is required; and two single line text fields for
entering the names of the Geo and QC.
5.2.7 Manage Tag Files (tape system)
See also: Appendix F
The Manage Tag Files menu item allows you to organise the many tag files which are created
during a survey. If you are using a tape system, selecting this menu item produces the Tag
Database Management pop-up shown in Figure 5-9, this page. If you are using an optical disk
system, see Section 5.2.8.
Figure 5-9 Tag Database Management Pop-up Window
CODA-PI automatically names tag files according to the date and time when recording data
began (that is ddmmyy.hhmmss). The file structure of the Coda system is explained in Section
14.5 of the DA System User Manual.
The Database Location option button allows you to select the drive on which to locate the tag
files you wish to save, load or delete; only Hard Disk is currently available.
When the Tag Database Management pop-up is opened, the default tag file selection is the
current tag file and this is the file highlighted on the list. The scroll bar can be used to move up
or down the list of Tag Files. A tag file can be selected by clicking on it with the left mouse
button. To make a multiple selection, either press and drag the pointer to highlight adjacent files
or hold down while clicking on specific file names.
The pop-up also displays the amount of space available on the hard disk. Each tag database entry
uses about 2KB of file space.
The Store and Factory buttons currently have no function in the tape system.
5.2.7.1 Tape Load/Save
Figure 5-10 The Load/Save Tags to Tape Pop-up Window
February 2000 for version 1.40 43
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
This pop-up allows you to load tag files from tape to hard disk, save tag files to tape and also to
list tag files which have been saved to tape previously. For single tape systems, tag files cannot
be accessed on tape while the tape drive is being used for any other purpose (that is data acquisition
or playback).
•Note: Tag files and sonar data should be saved to different tapes to prevent data being accidentally
overwritten.
Saving Batches
When tag files are saved, each separate save writes a batch of tag files to the tape. The batch
contains the highlighted tag files in the Tag Database Management pop-up and can therefore
contain one or more tag files. Batches can be saved to the tape one after another, but tag files can
be loaded only one batch at a time. Thus, if three tag files were saved as three separate batches,
all three files would have to be loaded individually, whereas if they were saved as a batch
consisting of the three files, they could be loaded together using the Load Batch option. There
is no limit to the number of tag files which can be saved as a single batch.
Tag files are selected for Save by clicking the left mouse button on the tag file name in the list
of tag files. If more than one tag file is to be saved, either press and drag the left mouse button to
highlight a group of tags, or hold down while clicking on the tag file names to add
more tag files to a group.
Listing Batches
Figure 5-11 : The Batch File List Pop-up Window
Batches are read and written to tape sequentially; after a batch has been saved, the tape is
therefore positioned at the end of that batch. To verify that a batch of newly saved tag files
contains the appropriate files, the List Prev Batch option should be used. All the batches on a
tape can be listed by clicking on the List All Batches button. This is useful for determining which
batch on a tape contains the required tag file.
•Note: Listing a batch causes the batch to be read but not loaded. The tape is therefore left at the
end of a batch after a list request.
Tape Movement
The Tape Movement commands in the pop-up can be used to move backwards or forwards
through successive batches.
44 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
Loading Batches
See also: Section 5.3.2
A batch of tag files can be loaded from tape using the Load Batch option. If this is selected, a
pop-up appears with the message ‘Insert tape in tape drive 1 and press OK’ (or tape drive 2,
depending on which tape drive is available). CODA-PI then loads a batch of tag files from the
tape drive into the tag file directory on the system hard disk, and indicates that this is taking
place.
•Note: If any of the tag files on the tape have the same name as those already in the CODA-PI
tag file directory, they will overwrite the files on the hard disk.
The tag database files are saved in binary, machine-readable format using this command. To
access the database in an ASCII format suitable for import into spreadsheets, databases and word
processing packages, use the Report Generation option (see Section 5.3.2).
Load/Save Command Summary
• Load Batch loads the batch file recorded at the current tape position.
• Load Remote allows a tag file to be loaded from another CODA-PI system on the same
Ethernet network. Contact Coda Technologies for further information.
Figure 5-12 : The Load Remote Tag File Pop-up Window
• List Batch lists the batches on a tape before loading. Before using this option, the tape must
be rewound. When the tag file details have been checked, the pop-up is dismissed by clicking
on the Dismiss button at the bottom of the Batch File List pop-up.
• List Previous Batch displays details of the previous batch of tag files on the tape, relative to
the current tape position.
• List All Batches displays details of all the batches of tag files on the tape.
• Save Batch Overwrite saves a batch file, overwriting any data already on the tape. The tape
is automatically rewound to the beginning before saving the batch.
• Save Batch Append saves a batch file to the end of existing data on the tape. The tape is
wound forward automatically to the end of any data on the tape before the batch is saved.
• Rewind rewinds the tag file tape to the beginning.
• Next Batch moves the tape forward by one batch to the start of the next batch.
• Previous Batch moves the tape backward by one batch to the start of the previous batch.
5.2.7.2 Delete
See also: Section 5.2.7.1; Appendix F
If tag files are no longer required, or if they have been saved to tape, they may be deleted from
the tag file directory on the hard disk of the DA System. The selection process is as outlined in
Save (see Section 5.2.7.1).
Make single selections by clicking the left mouse button, and multiple selections by either
clicking and dragging or by clicking with held down. Once the selection process has
been completed, click on the Delete menu item. A pop-up will appear, to ask ‘Are you sure?’; if
you click on Yes, the highlighted tag files will be deleted. Any tags currently on the screen which
were in the deleted tag files will be automatically removed from the screen.
February 2000 for version 1.40 45
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
5.2.7.3 Rescan
See also: Section 5.2.7
Rescan causes the directory entries of the tag file directory on the system hard disk to be re-read,
updating the list of tag files in the Tag Database Management window (see Section 5.2.7). This
should be carried out after loading or deleting tag files, as described above.
5.2.8 Manage Tag Files (optical disk system)
See also: Appendix F
Figure 5-13 Tag Database Management Pop-up Window
If you are using an optical disk system, selecting the Manage Tag Files menu item produces the
Tag Database Management pop-up shown in Figure 5-13, this page. It allows you to organise
the many tag files which are created during a survey.
CODA-PI automatically names tag files according to the date and time when recording data
began (that is ddmmyy.hhmmss). The file structure of the Coda system is explained in Section
14.5 of the DA System User Manual.
The Database Location option selection button displays the drive on which the tag files will be
created. (A list of files on that drive is displayed in the Tag Files window.) It is also the drive
from which files will be deleted and the source for files to be copied. In Figure 5-13, this page,
Database Location is set to Optical 1. Clicking on the option button displays the other options
available: Optical 2 (in a dual drive system) and Hard Disk.
The Tag Files window displays all the tag files that appear on the selected database location. A
tag file can be selected by clicking on it with the left mouse button. To make a multiple selection,
either press and drag the pointer to highlight adjacent files or hold down while
clicking on specific file name. The scroll bar can be used to move up or down the list.
The pop-up also displays the amount of space available on the hard disk. Each tag database entry
uses about 2KB of file space.
The Store action button at the bottom of the pop-up gives you the option of storing the currently
selected database location as the default location. Clicking on the Factory button will restore the
database location to Hard Disk.
5.2.8.1 Copy Tag Files
Figure 5-14 Copy Tag Files Pop-up Window
46 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
The Copy Tag Files pop-up lets you select the target drive for the tag files that you wish to copy
and to direct the system to copy those files from the source database location to the target drive.
To copy tag files, you must first have selected the source drive (Database Location) of the tag
files that you wish to copy and have highlighted the relevant tag files from the list in the Tag
Files window. Clicking on the Copy Tag Files button produces the Copy Tag Files pop-up. The
target drive for the tag files can be selected using the Copy selected files to: option selection
button; the options available are Hard Disk, Optical 1, and Optical 2 (in a dual drive system).
When you click on the OK button, the system automatically copies the files from the source
database location to the target drive. To check that the tag files have been copied to the new
location, you can select the new database location and see that the tag files appear in the Tag
Files window.
5.2.8.2 Delete
The procedure for deleting tag files is similar to that of copying tag files. First, the source of the
tag files must be selected in the Tag Database Management pop-up, using the Database
Location option selection button. Then, the files that you want to delete must be selected from
the list that appears in the Tag Files window. Clicking on the Delete button then deletes the files
from the database.
5.2.8.3 Rescan
This button updates the list of files in the Tag Files window and the disk space available either
on the hard disk or on the selected optical disk. This can be carried out after copying or deleting
tag files, as described above.
5.2.8.4 Unmount
This button directs the optical disk drive to unmount the disk. It must be selected before the
optical disk can be ejected from the optical disk drive.
5.2.9 Setup Tags
See also: Section 5.2.13; Section 5.3.1.3; Appendix E
•Note: The tag setup should be defined during mobilisation and before commencing data interpretation,
since making modifications during interpretation may lead to inconsistencies in data
storage and reporting.
Figure 5-15 The Tag Setup Pop-up Window
The Tag Setup pop-up allows you to define lists of tags for each of the tag types available in
CODA-PI, including System tags, User Defined tags, and the Right Mouse tag.
February 2000 for version 1.40 47
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
As shown in Figure 5-15, this page, clicking on the tab for a tag type produces a form which
allows you to activate or deactivate tags (except for System tags). The Tag Name and Tag Code
(incident code) lists are dual scrolling lists (see Section 2.2.11). This ensures that a tag name and
code always follow one another when either item is selected. In addition, for user tags there is a
set of definable properties. Where certain properties are not applicable to a particular tag type,
the property is greyed out. Changes made to a tag setup within this pop-up will also, where applicable,
be applied to the setups for fast tags (see Section 5.2.13) or report contents (see Section
5.3.1.3).
The pop-up action buttons (for example OK, Apply) function in the usual way (see Section
2.2.5), but it is important to realise that the entire Tag Setup will be affected by their action, not
just the tab form visible on the screen at the time. This allow you to create a single composite tag
setup for the survey rather than a number of individual setups.
5.2.10 Tag Activation
See also: Appendix E
5.2.10.1 Tag Active
See also: Section 5.2.9; Section 5.2.13; Section 5.3.1.3
This on/off toggle allows you to switch each tag type on or off for the current survey. Active tags,
indicated in bold text in the list of tag names (see Section 5.2.9), are those which are available
for use in the survey. This also makes them available in the Fast Tag Setup and Report
Contents pop-up windows (see Section 5.2.13, Section 5.3.1.3).
Tags (other than System tags) may also be activated or deactivated by double-clicking on the
tag name in the list of Tag Names appearing in the Tag Setup pop-up; or by hitting
in one of the text fields when the tag is selected in the list.
•Note: If a tag is not activated in the tag setup, it will be named ‘Unknown’ when accessed by
CODA-PI.
5.2.10.2 Tag Name and Incident Code
When a tag is selected from the scrolling list in this area of the pop-up, the name and associated
code will appear in the text fields below the lists. You may change either or both by entering text
in place of the labels provided in the text-entry boxes. The text in a box is confirmed by hitting
, although the appropriate pop-up action button must be pressed to apply or save the
Tag Setup. Selecting a new item in the list will update the previous item with the value in the
Tag Name and Tag Code text fields.
Each tag name and code for a particular tag type must be unique, as CODA-PI will not accept
duplicates, nor will it accept blank fields. It is possible to give two tags the same name, but only
if they are different tag types; for example, the tag name ‘Support’ could be allocated to two tags
where one was a single tag and the other a dual tag. The exception to this is Dual Tags which
have an additional end incident code text box below the start code box. Start incident codes may
be identical to end incident codes.
48 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
Figure 5-16 Dual Tag Tab Form
5.2.11 System Tag Setup
See also: Section 5.2.9
Figure 5-17 The System Tag Tab Form
System Tags are tags automatically generated by the system and cannot be added manually. They
are set up in the same way as User Defined tags (see Section 5.2.9). The tag types available in
the dual scrolling list may be from any of the tag types available with CODA-PI, each of these
having specific functions within the system. A Fix Line, for example is an example of a special
system single tag. It is important to realise that if you change the name of a system tag, this may
disguise the nature of its function within the system. For this reason changes to system tag names
and codes cannot be saved.
An additional feature in the System Tag tab is the Tag Colour option menu. Clicking and
dragging on this button allows you to select the colours for each system tag type.
February 2000 for version 1.40 49
Reference
Guide

Reference
Guide
5.2 The Tagging Menu CODA-PI User Manual
5.2.12 Right Mouse Tag
Figure 5-18 : The Right Mouse Tag Tab Form
The right mouse tag is the tag node placed by clicking the right mouse button over the data area
of the display. By default this is an ‘Unknown’ single tag type, but you may instead select one
of the previously activated single tags.
The R. Mouse tab form always displays a scrolling list of tag names and incident codes corresponding
to each of the active single tags set up using the Setup Tags pop-up, plus one
‘Unknown’ tag. There can only be one active right mouse tag, as activating a new tag will
deactivate the previous right mouse tag. It does not alter any other Tag Setup settings. If the tag
selected as the right mouse tag is subsequently deactivated via the Single tag tab form, the right
mouse tag reverts to the default ‘Unknown’ type.
50 February 2000 for version 1.40

CODA-PI User Manual 5.2 The Tagging Menu
5.2.13 Fast Tag Setup
See also: Section 5.2.9; Appendix E.
Figure 5-19 The Fast Tag Setup Pop-up Window
Fast Tag Setup allows you to specify which of the active tags previously set up using the
Tagging→Setup Tags options are to be used as fast tags (see Section 5.2.9). Beside each of the
12 fast tag buttons is the tag name assigned by you to the button and an abbreviation indicating
the tag type. This pop-up also allows you to define the colour in which these tags will appear on
the screen. The Fast Tag Setup pop-up always displays the current Fast Tag selections (see
Figure 5-19, this page). Changes to the Fast Tag Setup may be made as detailed below.
At the bottom of the pop-up, you are given the option to Load a previous fast tag setup, or Save
the current setup for future use, in addition to Cancel, Apply, and OK.
5.2.13.1 Fast Tag Colour
The colour of each item on the fast tag list may be changed by pressing the Colour button
opposite the fast tag name and clicking on the new choice from the colour options that appear on
the screen. The same colour may be used for more than one fast tag.
5.2.13.2 Add Tag
This button allows you to increase the number of user-allocated Buttons (function keys F1 to
F12 along the top of the DA System keyboard) specified for fast tagging up to a maximum of 12
tag identities. (If you have not defined a fast tag button it is allocated as an ‘Unknown’ tag.)
February 2000 for version 1.40 51
Reference
Guide

Reference
Guide
5.3 The Reporting Menu CODA-PI User Manual
Figure 5-20 Add Tag Pop-up Window
To allocate a tag to a particular Button, first click on the list in the Fast Tag Setup pop-up on
the button number at which the tag is to be added Before or After. Clicking on the Add Tag
button pops up the full list of tags which were previously defined as active using the Setup Tags
option of the Tagging menu (see Section 5.2.9). From this scrolling list, you can select the
required tag to be added by clicking on the appropriate tag name. The abbreviation before the tag
name in the list indicates the tag type (S for single, D for dual tags). Multiple selections may be
made by using a press and drag action on the required items, or by pressing at the
same time as pressing with the left mouse button.
If the new fast tag is to be placed in the fast tag list after the marked button, you should select the
After current selection option, otherwise the fast tag will be added before the current selection.
The same tag cannot be added to the list twice. All the fast tag button numbers subsequent to the
newly added tag button are increased by one. If 12 fast tag buttons have already been allocated,
you must delete one of the list before another item can be added to the list.
5.2.13.3 Delete Tag
Clicking on this button removes the button currently selected from the list of fast tag buttons.
5.2.13.4 Delete All Tags
This deletes all the current fast tags from the tag setup.
5.3 The Reporting Menu
See also: Appendix E
Figure 5-21 The Reporting Menu
This menu allows you to generate text reports in ASCII format from the contents of tag database
files; this is necessary because the tag database files are stored in binary, machine-readable – but
not human-readable – format. The report files generated can then be saved to floppy disk or
output to the screen or a printer.
5.3.1 Report Setup
The Report Setup pop-up provides the options for defining the contents and style of the report.
Each of the aspects of the Report Setup has its own list of options, contained on the appropriate
tab form pop-up: Format, Options, Contents.
52 February 2000 for version 1.40

CODA-PI User Manual 5.3 The Reporting Menu
At the bottom of the pop-up, you have the option to Load a previous report setup, or Save the
current setup for future use, in addition to Cancel, Apply, and OK. These buttons apply to all
three tab forms in the Report Setup pop-up window, resulting in a single combined report setup.
Section 2.2.5.1 and Section 2.2.5.2 describe how to load and save settings.
5.3.1.1 Report Setup Format
See also: Appendix B
Figure 5-22 The Report Setup Format Tab Form
Clicking on the Format tab of the Report Setup pop-up allows you to alter the number of
columns reported and the order in which they are printed. Report column entries may be added
or deleted. To do so, select one of the report columns from the scrolling form by clicking on a
column number. The Add Item or Delete Item button should then be selected.
You may define some or all of the following parameters for each column in the report.
• Label allows you to define the label for each column in the report.
• Width allows you to specify the width of each column.
• Precision allows you to define the number of figures after the decimal point for non-integer
numbers in the report.
Add Item
Clicking on the Add Item button opens a pop-up window (see Figure 5-23, this page). This
produces an alphabetically sorted list of the report column types.
February 2000 for version 1.40 53
Reference
Guide

Reference
Guide
5.3 The Reporting Menu CODA-PI User Manual
Figure 5-23 The Add Item Pop-up Window
In the Add Item pop-up you can select items from the scrolling list by clicking on the names in
the list and you can specify their position in the report by clicking on either the Before current
selection button or the After current selection button. For a brief description of each of the
reportable items, see Appendix B.
The appropriate action button at the bottom of the pop-up (Add or Done) should be clicked on
when all items have been added. Alternatively, double-click on the item to add it to the report.
Multiple selections may be made by using a press and drag action over the required item in the
list.
Delete Item and Delete All Items
The two delete buttons under the horizontal scroll bar allow you to delete either the selected
column (Delete Item) or all the columns in the report (Delete All Items).
5.3.1.2 Report Setup Options
Figure 5-24 The Report Setup Options Tab Form
54 February 2000 for version 1.40

CODA-PI User Manual 5.3 The Reporting Menu
Report Separator
The options within this section of the pop-up allow you to select the type of separator for the
columns of the report from the one-of option: Tab, Space, and Comma. Tab inserts a single tab
character between columns, Space inserts a single space, and Comma inserts a single comma
with no additional spaces.
Report Headings
This allows you to toggle on or off the labels at the top of the report columns.
Dual Tags
The options within the Dual Tags area of the pop-up allow you to select whether each dual tag
is reported :
• as only one event
• with start and end nodes reported as separate events
• as one event when the start and end incident codes of the tag are identical but as two separate
events when codes differ.
Note that only the first of these options is available if Report start nodes only is selected in the
Multi-Node Tags frame If Report as only one event is selected, it is the start event which will
be reported. Parameters from the end event may be added to the report output by adding the
appropriate columns to the report in the Report Setup Format tab form (see Section 5.3.1.1).
The Assign incident codes on sort order on/off toggle gives you the option of reporting dual
tags as start and end events in two different ways. When this toggle is off, dual tag start and end
nodes are reported as start and end events respectively. When the toggle is on, an end tag node
which appears in the report before the start tag node is reported as a start event. Similarly, if a
start tag node appears in the report after an end tag node, it is reported as an end event.
Multi-Node Tags
The options within the Multi-Node Tags frame also have an effect on the output of reports in
CODA-PI. If Report nodes by sort order is selected, all nodes will appear in the report in their
sort order. If Report nodes grouped by tag is selected, when the first node of a dual tag is
found, the second node will be reported immediately afterwards, irrespective of sort order. If
Report start nodes only is selected, only the start event of a dual tag will be reported.
Sort Order
This option allows you to sort the data by Time or by Kp, and by increasing or decreasing order
in the report. This can affect the reporting of start and end events.
Text Strings
You can select either to Enclose text in double quotes, or to Replace spaces with underscores.
This can be used to ensure that columns whose output contains spaces are not created as
several columns when input to another computer package. You should choose the output best
suited to the software the report will be used with.
5.3.1.3 Report Setup Contents
See also: Section 5.2.9; Section 5.2.13
This pop-up allows you to define which tag types should be included in the report and the order
in which they should appear. For example, you may wish to exclude Fix Lines from the report.
February 2000 for version 1.40 55
Reference
Guide

Reference
Guide
5.3 The Reporting Menu CODA-PI User Manual
Figure 5-25 The Report Setup Contents Tab Form
This form comprises a scrolling list containing the user-defined sub-set of all the active System
and User tags which are to appear in the report (defined in Section 5.2.9). At the bottom of the
form are the Add Tag, Delete Tag, and Delete All Tags buttons. These buttons function in
exactly the same way as those described in Fast Tag Setup (Section 5.2.13). In addition, the Add
All Tags button gives the option of including all the currently active tag types to the report.
Before individual tags may be added or deleted using these buttons, they must be selected from
the scrolling list. You cannot add the same tag name more than once to the report contents list.
Changes made in this form are confirmed or cancelled when one of the action buttons is pressed.
5.3.2 Report Generation
See also: Section 5.3.1; as well as Section 4.1.2, Section 4.2.2 and Section10.10 and
Appendix J of the DA System User Manual
The Report Generation pop-up allows you to generate one or more ASCII text reports in the
style defined by the Report Setup (see Section 5.3.1). To select a report for output, click on the
appropriate entry in the scrolling list. (The current tag database will always be selected when the
window first pops up.) You can select more than one tag file by pressing and dragging over the
required files or by holding down while clicking on the tag file names. To generate
the report, click on the Generate Report button. The watch pointer will appear while the report
is being generated.
Figure 5-26 The Report Generation Pop-up Window
The buttons in the Output Report To frame allow you to select the destination for the report file.
56 February 2000 for version 1.40

CODA-PI User Manual 5.3 The Reporting Menu
If Text Window is selected from the above options, a report file is generated by the system and
displayed in a text window which is overlaid on the screen. You can scroll through this window
to view its contents (Figure 5-27, this page).
Figure 5-27 Report File Displayed in Text Window
If output to Printer is selected, the report file is sent to the printer, according to the options
selected in the Printer Setup menu (see Section 5.3.2.1). The Printer option is available only if
a suitable hardcopy device is connected to CODA-PI (see Section 4.1.2, Section 4.2.2 and
Appendix J in the DA System User Manual). The printing process can be stopped at any point
by pressing the Cancel button.
If the output is to be saved to a floppy disk, Floppy Disk should be selected, and a blank DOSformatted
floppy disk inserted in the floppy disk drive. After Generate Report is clicked, a
further window will appear asking for the name under which the report file should be saved to
the floppy disk. Once the name has been entered, press OK to start copying the report file to disk.
The report file saved to disk will be an ASCII dump of the database contents, in exactly the same
format as the report sent to a printer, or to the screen. All files are saved with the extension ‘.rep’.
Note that the size of ASCII file which can be copied to a floppy disk is limited to the formatted
capacity of the floppy disk – normally 1.44 MB.
•Note: If the system is being used for data acquisition or playback, the process of saving a report
file to floppy disk will take longer to complete. To speed up the process, pause the display until
the report file has been saved to the floppy disk.
5.3.2.1 Printer Setup Window
See also: Section 5.1 and Appendix J of the DA System User Manual
Figure 5-28 The Printer Setup Pop-up Window
Selection of the appropriate printer port is made by clicking on the port to which the printer is
connected. If the port is a serial port (one of the Com ports), the Serial Setup button should be
clicked to set up the serial line parameters.
February 2000 for version 1.40 57
Reference
Guide

Reference
Guide
5.4 The Applications Menu CODA-PI User Manual
Either Portrait or Landscape Format may be selected for PostScript® printers by clicking on
the appropriate toggle. Where a printout is being saved in ASCII format, this selection does not
apply and will therefore be ignored. Type allows a choice of ASCII or PostScript® printer.
Once the required selections have been made, the appropriate action button at the bottom of the
pop-up should be clicked on.
•Note: The printer should be connected to the required port of CODA-PI before OK or Apply is
clicked (see Section 4.1.2 and Section 4.2.2 in the DA System User Manual).
5.4 The Applications Menu
Figure 5-29 The Applications Menu
This menu allows you to select which Coda application you wish to run. The Application
Specific Area of the main display will change according to the application being used.
With the standard DA System you can select Data Acquisition, which allows you to record and
replay data. With oher modules, you can record and play back data as well as using the survey
tools specific to the module. Further information about the capabilities of the additional software
modules is available from Coda Technologies.
When an application is running (for example, automated pipeline inspection), the letter ‘R’ is
appended to the Application menu item. This lets you switch between application modules while
remaining aware of which application is currently running.
GeoKit: The Geophysicist On-line Interpretation Toolkit provides a suite of on-screen and online
interpretation tools for site survey, route survey, search and recovery, and target detection.
The user configurable on-line event-marking tools are enhanced to allow interactive marking of
target objects, seabed features and sediment types in real time. The database facilities allow
flexible, comprehensive reports detailing locations, dimensions, seabed and target type,
surveyor’s comments and automatic calculations to be printed on screen or via a printer.
5.5 The Application Specific Area
5.5.1 Pipeline Inspection Mode
Figure 5-30 : The Application Specific Area of CODA-PI
When Pipeline Inspection is selected under the Applications menu, the Application Specific
Area is updated as in Figure 5-30, this page.
This area can be divided into three main sub-areas:
• Fast Tag Area (labelled Key)
• Position Information Area
• Analysis (automated interpretation) Control Area
58 February 2000 for version 1.40

CODA-PI User Manual 5.5 The Application Specific Area
5.5.1.1 Fast Tagging
See also: Section 5.1.1; Section 5.2.6; Section 5.2.9
The Fast Tag Area consists of specific colour-coded fast tag keys for accelerated event tagging.
The different events can either be marked by clicking on the appropriate button (or by pressing
one of the function keys when the pointer is in the Data Display Area) and then clicking in the
display area to mark the required position of the feature. These keys correspond to either single
or dual tag events, depending on whether the event to be marked occurs at a single point or over
a defined distance (see Section 5.1.1).
Figure 5-31 Single Tag
Single events have a single location reference and are denoted by a coloured square, as shown in
Figure 5-31, this page.
Figure 5-32 Dual Tag
Dual tags, indicated by a D on the coloured button, have start and end locations denoted by start
and end tag nodes, as shown in Figure 5-32, this page. Start tag nodes are represented by the
symbol and end tag nodes by the symbol. If both the start and end tag nodes are on
the screen at the same time, a straight line will be drawn between the two nodes.
The appearance of the tag description field in the Fast Tag Area reflects the status of the selected
tag, as follows:
Figure 5-33 : Fast Tagging, Single Tag or Start of Dual Tag
1. Start of dual tag, or single tag (selected by using the appropriate function key, or by using the
mouse to select the coloured button in the fast tagging area): the text description of the
selected tag type is outlined in black (showing that a tag placement is pending) and the tag
button is indented. For more information on tag names see Section 5.2.9. In addition, the
pointer in the Data Display Area changes from an arrow to a pencil (see Section 2.3).
February 2000 for version 1.40 59
Reference
Guide

Reference
Guide
5.5 The Application Specific Area CODA-PI User Manual
Figure 5-34 Fast Tagging, Second Half of Dual Tag to be Selected
2. Start of a dual tag placed, but selection of this tag type for placing the end of the tag has not
yet been made. The tag name is printed in green to show that the tag has not been completed
and the fast tag button is indented (see Figure 5-34, this page). This occurs if you have
selected another tag to mark before completing the dual tag.
Figure 5-35 Fast Tagging, Second Half of Dual Tag Selected but not yet Placed
3. The second half of dual tag has been selected (either using the appropriate function key, or
by using the mouse button to select the tag button in the Fast Tag Area). The tag description
text remains green and is outlined in black (showing that a tag placement is pending). The
fast tag button is indented (see Figure 5-35, this page).
Figure 5-36 Fast Tagging, Dual Tag Completed
4. The tag has been placed, and the fast tag remains selected until another fast tag is selected or
the current one is deselected. The tag description is black, outlined in black with the tag
button indented. Information such as tag type, location and length of dual tags (start and end
nodes) is automatically logged to the database. Additional annotation information can be
added to the database via the Tagging→Annotate Tag Node(s) menu option or by using the
appropriate keyboard shortcut, as outlined in Section 5.2.6. The mouse pointer stays as the
add mode pencil pointer.
Fast tag selection may be altered simply by clicking on the new choice (or by using the appropriate
function key). The black bordered rectangle will then move to the new choice. If the
previous choice was a dual tag, its state will revert to that before the previous selection was
made, so if the dual tag was not completed the Fast Tag Area will reflect this. To cancel a
selection, simply click again on the same selection and the pointer in the Data Display Area
will revert to an arrow.
60 February 2000 for version 1.40

CODA-PI User Manual 5.5 The Application Specific Area
5.5.2 The Analysis Control Area
See also: Section 5.5.1
This area of the Application Specific Area allows you to control CODA-PI’s automated analysis
tools (see Section 5.5.1).
5.5.2.1 Start Analysis
This button is used to start the automated interpretation function of the CODA-PI software.
When the automated span detection facility is turned on, this button will appear to be depressed.
The automated span detection software takes several seconds (typically up to about 300 pings of
sidescan data) before tags are produced automatically.
•Note: The CODA-PI analysis parameters must be setup before starting analysis.
5.5.2.2 Stop Analysis
This button stops the automated interpretation function of the CODA-PI software. The Start
Analysis button will return to its normal position when this button is selected, showing that the
automated interpretation facility is turned off.
5.5.2.3 Pause Analysis
Selection of this button will stop the incoming data being processed by the automated interpretation
facility, but will not turn it off, nor will it reset internal variables of the automated interpretation.
This allows you to suspend automated interpretation for short periods without having
to restart the automated inspection (and avoiding any delay before output is produced).
5.5.2.4 Analysis Parameters
Figure 5-37 The CODA-PI Analysis Parameters Pop-up Window
Selecting the Analysis Params button causes the Analysis Parameters pop-up to appear. This
controls the operation of the automated span detection software. The CODA-PI Analysis
Parameters window can be used to select which channel of display data is to be processed (left
or right), using the Process Channel one-of selector at the bottom left of the window. Using the
Zoom Window one-of selector you can select a real-time display of a zoomed image of the area
surrounding the pipeline. This is displayed in place of the channel where the data is not being
processed by the automated span detection software.
The remaining areas in the Analysis Parameters window are used for setting up the automated
span detection software. The Span Values section allows the length in metres at which a span is
flagged as turning ‘critical’ to be set manually (Critical Length). The minimum height of the
pipeline above the seabed which is defined to constitute actual spanning of the pipeline, can also
be set (Height Trigger).
The diameter of the pipeline (in inches) is set in the Pipe Diameter section. This parameter
enables the automated analysis to calculate measurements such as span height or extent of pipe
burial. A pipe diameter Correction factor can also be entered. This value, as a percentage of the
February 2000 for version 1.40 61
Reference
Guide

Reference
Guide
5.5 The Application Specific Area CODA-PI User Manual
pipeline diameter, is added to or subtracted from the pipeline diameter before span height calculations
are made. This parameter can be useful when it is known that the span heights are
suffering a degree of error (for example, if the pipe is not sitting on a flat seabed).
•Note: The pipeline diameter entered here is used to calculate span heights for both automatic
and manual tags.
The Event Values section of the window allows you to define rules for how automatic CODA-
PI dual tags are created and extended, thus influencing how automatic dual tags are logged to the
database. The Merge Length allows you to specify the minimum distance which must separate
events of the same type to prevent them being considered a single continuous event (for example
a series of small spans separated by a distance which is less than the merge length will be logged
to the database as a single long span). The Minimum Length defines the minimum length (in
metres) for an event which is to be logged to the database; events of less than this length will be
ignored. See Appendix A for a description of how span heights are calculated.
The Grazing Angle section of this pop-up is used to define the limits of grazing angle considered
permissible for a given survey. In future these fields will be used to mark tag entries in the
database report file as being in or out of specified survey limits; however, at present these entries
are unused.
The ROTV Steering frame allows you to control the position of the ROTV carrying out the
sidescan pipeline inspection survey. The ROTV frame is greyed out unless this option has been
purchased. If you require ROTV steering output capabilities, contact Coda Technologies.
The action buttons at the bottom of the pop-up include a Load option, which lets you load a file
of previously saved settings for the current pop-up, and a Save option, which lets you save the
current pop-up settings to file for reloading at a later date.
5.5.2.5 Pipe Data
Selecting the Pipe Data button will pop up an information window displaying some of the
statistics arising from the pipeline tracking carried out by the automated span detection software
(see Figure 5-38, this page.). The data displayed in this window, with the exception of the Fish
Height, whose input is controlled in the Settings and Processing menus (see Section 5, Section
6 and Section 7 of the DA System User Manual), is all calculated by the automated pipeline
inspection mode (see Figure 5-39, page 63). The Pipe Data pop-up has an additional graphical
mode which can be accessed by clicking on the Graphic button. The data shown in the Pipeline
Survey Data Window and in the Pipe Striking Angle/Height Graphic is from the first ping
visible at the top of the Data Display Area.
Figure 5-38 : The Pipeline Survey Data Pop-up Window
This Graphic button of the Pipeline Survey Data window (see Figure 5-38, this page) allows a
real-time display of the pipeline height relative to the seabed and of the incident sonar beam. This
graphic is only available after CODA-PI begins to track the pipeline, no graphic will therefore
be available before analysis begins. If analysis is not switched on, or if CODA-PI is not tracking
a pipeline, some parameters in the Pipeline Survey Data window will be blank and the Pipe
Striking Angle/Height Graphic will not be updated.
62 February 2000 for version 1.40

CODA-PI User Manual 5.5 The Application Specific Area
Fish
Fish Height
Sonar Beam
Pipe Distance
Seabed
Grazing Angle
Figure 5-39 Components of the Pipeline Survey Data Pop-up Window
Figure 5-40 The Pipe Striking Angle/Height Graphic
Pipeline
This graphic display gives an easily understood impression of the ability of a given set of survey
parameters, towfish height and distance from pipeline, to conveniently represent conditions such
as spanning on the pipeline. It should be noted that this graphic uses a ‘flat seabed’ assumption
when drawing the relation of the pipeline to the seabed, and the limits of the pipeline shadow on
the seabed.
The seabed in the region of the pipeline is represented by the horizontal black line at the bottom
of the image; 10cm across-track range ticks are drawn in blue beneath this line. The pipeline
itself is drawn to scale, as is its position relative to the seabed (above it or resting on it).
Horizontal blue lines indicate height gradations above the seabed of 10cm.
The striking angle of the sonar beam on the pipeline is illustrated by the central one of the three
black lines emerging from the side of the image, whereas the lower and upper lines show the
positions of the start and end of the pipeline shadow, projected onto the seabed.
5.5.2.6 Reset Pipe Position
This button allows you to define the centre of the pipeline search area used by the automated
interpretation software. When it is pressed, the mouse pointer changes from the arrow pointer
into the automatic tracking pointer (see Section 2.3). This should be positioned at the desired
point in the Data Display Area and the left mouse button clicked to move the centre of the
automated interpretation software’s search to that across-track distance. To cancel a pipe
position operation, simply press the Reset Pipe Position button again.
5.5.2.7 Position Information Area
The display in this part of the Application Specific Area shows the position in easting, northing
and Kp for the line of data at the top of the Data Display Area. The information is provided by
the navigation input and the display will indicate whether the source of this information is the
ship or the towfish.
Pipe
Height
February 2000 for version 1.40 63
Reference
Guide

Reference
Guide
5.5 The Application Specific Area CODA-PI User Manual
64 February 2000 for version 1.40

Part VI: Appendices
Appendices

Appendices
66 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual A.1 Initial Span Height Estimation
A Span Height Estimation
This section describes the calculations used by CODA-PI in estimating span height. It refers to
the paper ‘Sidescan Sonars on ROTVs’ by Alan Cameron (Director of Hydrosearch Associates
Ltd, UK), published in Survey World, May 1995, Volume 2, Number 4.
A.1 Initial Span Height Estimation
Sidescan Towfish
Seabed
θ
Ray A
Ray B
L
Figure A-1 Diagram showing elements of span height estimation
Ray A is ray normal to pipe, giving first return from specular reflection
Ray B is first ray to pass under pipe, a tangent to the pipe
R is pipe radius
D is distance of first return
L is distance to trailing edge of pipe return
θ
δ
is grazing angle of specular reflection (first return)
E
is angle between first return and trailing edge return
φ = θ + δ
D
Leading edge of pipe return
Horizontal
H is distance from bottom of pipe to seabed (that is, the span height we wish to measure)
K is vertical distance from trailing edge tangent intercept of pipe to bottom of pipe
J = R – K
C is slant range from trailing edge of pipeline return intercept with pipeline to seabed
E is distance from source to intercept with pipe from pipe trailing edge
Using the sine rule,
J R
--------------------------- = ------------- ⇒ J = Rcosφ sin(
90 – φ)
sin90
K = R – J ⇒ K = R1 ( – cosφ)
H + K
-------------- -------------
C H + K
= ⇒ C =
-------------sinφ
sin90
sinφ
R
H+K
90−δ
R
90-Ø
J
K
H
C
Trailing edge of "pipe return"
February 2000 for version 1.40 67
Ø
We can infer
minimum detectable
span height from
Ø, R
Ø
Appendices

Appendices
A.2 Comparison with Formula in Alan Cameron’s Paper CODA-PI User Manual
so,
H = Csinφ – K = Csinφ– R(
1– cosφ)
Again using the sine rule,
D + R R
------------- = ---------- ⇒ δ=
sin90
sinδ
68 February 2000 for version 1.40
Eqn.A-1
Eqn.A-2
where P is the pulse length in metres (we must measure from the front of the pulse, so subtract
pulse length).
Using Equation A-2, this page,
so from Equation A-1, page 68,
Eqn.A-3
Eqn.A-4
So to calculate the span height, we require pulse length (10us for 500kHZ EG&G 272 and 100us
for 100 kHZ EG&G 272), grazing angle, pipe diameter, distance of first return, distance of
trailing return.
A.2 Comparison with Formula in Alan Cameron’s Paper
Our equation for span height can be re-expressed using Identity A (below) for ( cosφ – 1)
if δ is
assumed to be zero:
In his paper, Cameron derives:
Giving
where
sin 1 –
and Z = θ = φ if δ =
0
⎛------------- R ⎞
⎝D + R⎠
E D R
-------------------------sin(
90 – δ)
+
= ------------- ⇒ E = ( D + R)
cosδ
sin90
L = C + E+ P
C = L – E–
P
C = L – ( D + R)
cosδ
– P
H = ( L– ( D + R)
cosδ–
P)
sinφ
– R1 ( – cosφ)
H = Lsinφ – ( D + R)
cosδsinφ–
Psinφ – R + Rcosφ H = Lsinφ – ( D + R)
sinφ(
– Psinφ + Rcos( φ – 1)
)
= ( L– D–
R – P)
sinφ
+ R( cosφ
– 1)
φ
= ( L– D–
R – P)
sinφ
– Rtan--
sinφ
2
φ
= ⎛
⎝
L– D–
R – P – Rtan-
⎞
2⎠
sinφ
SpanHeight = ( Anomaly – CriticalReturn)
sinZ
Z
CriticalReturn = P + R + Rtan-
2
SpanHeight = ⎛Anomaly – P – R – Rtan
Z
-- ⎞sinZ ⎝ 2⎠
Anomaly = L – D

CODA-PI User Manual A.3 Tracking Angle and Beam Width
So Cameron’s definition of span height becomes:
φ
SpanHeight = ⎛L– D – R – P – Rtan
-- ⎞sinφ ⎝ 2⎠
– which is equivalent to Equation A-4, page 68.
Identity (A)
cosφ– 1 2 φ
= cos ⎛--⎞ – 1
⎝2⎠ =
=
cos 2
cos 2
= – 2
φ φ
-sin-- 2 2
2 – – 1
φ
-- –
2
sin 2
φ
--
2
sin 2
φ
-- –
2
cos 2
φ
2 -φ-φ
– sin sin cos--
2 2 2
= ----------------------------------------cos
φ
--
2
=
=
φ
--
φ φ
– tan ⎛2sin -cos-- ⎞
2⎝
2 2⎠
φ
-- 2
2
φ
– tan sin ⎛--⎞ ⎝2⎠ φ
-- –
2
φ
so cosφ
– 1= – sinφ
tan--
2
sin 2
A.3 Tracking Angle and Beam Width
φ
--
2
The discussion in Section A.1 does not take into account the tracking angle and the sidescan’s
horizontal beam width, which will combine to make the value of C artificially large because the
apparent radius of the pipeline is larger, so this effect must be compensated for.
From Equation A-3, page 68,
C = L – E–
P = L – Dcosδ – R’ cosδ
– P
and from Equation A-4, page 68,
H = Lsinφ – ( D + R’ ) cosδsinφ–
Pφsinφ– R’ + R’ cosφ
where R’
is pipe radius including tracking angle and beam width.
February 2000 for version 1.40 69
Appendices

Appendices
A.3 Tracking Angle and Beam Width CODA-PI User Manual
Towfish Track
ε/2+β
Pipeline
Figure A-2 Diagram showing detail of PipelineTracking Angle
If β is the tracking angle, and ε the beam width, from Figure A-2, this page
R
R’ = -------------------------- – P
ε
cos⎛--+
β⎞
⎝2⎠ Substituting this value for R’ , Equation A-4, page 68, becomes
Note that for a 500 KHz EG&G 272 sidescan,
Equation A-5, this page, is the formula used within CODA-PI for span height calculation.
70 February 2000 for version 1.40
D
E
L
C Span
⎛ ⎞
R
H L φ ⎜D+ --------------------- ⎟ δ φ P φ ---------------------
R Rcosφ = sin –
cos sin – sin – + ---------------------
⎜
--
ε ⎟
ε
⎝ cos + β⎠
cos--
ε
+ β cos--
+ β
2
2 2
ε 2o =
Eqn.A-5

CODA-PI User Manual B.1 Table of Tag Properties
B CODA-PI Report Contents
The table below lists the possible contents of the report. For full details of how to define the
columns in the report, see Section 5.3.1.
B.1 Table of Tag Properties
Field name Applicable
to...
Description
Anomaly Number Node A user defined identifier that can be associated
with a tag node (entered via Annotate pop-up)
Anti-alias Filter Freq Sonar Anti-aliasing filter frequency (Hz)
Channel Sync With Sonar Bitfield indicating which channel the nodes
associated channel is synched with
Channel Type Sonar The type of data channel the node is marked in,
(e.g. Port, Starboard, Seismic)
Comparison Node Any extra comparative details about the tag
node (text entered via the Annotate pop-up)
Course Sonar The actual course of the vessel/towfish in
degrees
Creator Tag ID Node The database ID of the tag’s creator node
DCC Sonar The distance cross course of the ping in metres
(Starboard is positive)
Date Node &
Sonar
The date of the node’s associated ping
Depth From Horizon Node The depth in metres from node to horizon, SBP
only, (entered via Measure)
Depth From Seabed Node The depth in metres from the tag node to the
seabed, SBP only
Depth From Surface Node The depth in metres from the tag node to the
sea surface, SBP only
Description Node Any extra descriptive details about the tag node
(text entered via the Annotate pop-up)
Easting Node The (corrected) nav data easting position
Easting End Node The (corrected) nav data end event easting
position
Feature Offset Node The offset to feature from the node in metres
Fish Height Sonar The height of the towfish above the seabed in
metres
Fish Offset Sonar The (corrected) distance cross-track in metres
from the ship position to the fish position;
Starboard is positive
Fix Number Sonar The previous navigation fix number to the node
Fractional Fix Node The fractional value between the fix lines
where the node lies
February 2000 for version 1.40 71
Appendices

Appendices
B.1 Table of Tag Properties CODA-PI User Manual
Field name Applicable
to...
Fractional Fix End Node The fractional value between fix lines where
the end of the event lies
Further Inspection Node Indicating whether the node is marked for
further inspection. User input via the Annotate
pop-up
GDOP Sonar Geometric dilution of precision (as entered via
the nav string) of associated sonar message
Geo Node Details of the Geophysicist that marked the tag
node (text entered via the Annotate pop-up)
HDOP Sonar Horizontal dilution of precision (as entered via
the nav string) of associated sonar message
Heading Sonar The ship’s heading (degrees)
Heave Source Sonar The source of Heave on the ship. Currently
always set to none – for future expansion
Heave Value Sonar The magnitude of Heave on the ship. Currently
always set to zero – for future expansion
Heave Velocity Sonar The velocity of Heave on the ship (m/s). Currently
always set to null – for future expansion
Height Node The measured height value of the node in
metres
Height CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
height (see Appendix C)
Height CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node height
(see Appendix C)
Incident Code Node The (start) incident code of the node
Incident Code End Node The end incident code of the node
Note: This is not necessarily the incident code
of the end node
Input Channel Node &
Sonar
72 February 2000 for version 1.40
The number of the channel the node was placed
in (from acquisition setup)
Input Gain Sonar The gain of the input sonar signal in decibels
(from the nav string)
Kp Node &
Sonar
Kp End Node &
Sonar
Description
The (corrected) nav data Kp position
The (corrected) nav data end event Kp position
Layback Sonar The (corrected) distance in metres from the
ship position to the fish position
Length Node The Length of the tag (as automatically
generated or measured by the user) in metres

CODA-PI User Manual B.1 Table of Tag Properties
Field name Applicable
to...
Length CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
length (see Appendix C)
Length CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node length
(see Appendix C)
Line Name Sonar The Line name that is entered in the Navigation
Parameter Settings pop-up or via the nav string
allowing the user to mark a specific part of the
survey
Nav Basis Sonar The nav basis of the survey (e.g. UTM or
Lat/Long)
Node CorrNav Off Node A mnemonic indicating which of the node’s
nav parameters are uncorrected (see Appendix
D)
Node CorrNav On Node A mnemonic indicating which of the node’s
nav parameters are corrected (see Appendix D)
Node Type Node The type of (multi) node, e.g. start node (S),
intermediate node (I) or end node (E). Single
tags are reported as start nodes.
Northing Node The (corrected) nav data northing position
Northing End Node The (corrected) nav data end event northing
position
No. Rec. Chans Sonar The number of data channels recorded
Offset CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
offset (see Appendix C)
Offset CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node offset
(see Appendix C)
PDOP Sonar Position dilution of precision (as entered via
the nav string) of associated sonar message
Ping Number Sonar The ping number
Description
Ping Rate Sonar The number of pings per second – calculated
during acquisition
Pitch Sonar The instantaneous pitch of the vessel/towfish
(degrees); forward pitch is positive
QC Node The name of the quality controller – text
entered via the Annotate pop-up
Range Node The corrected true range to fish in metres
Raw DCC Sonar The raw value of distance cross course of the
sonar message
Raw Easting Node The raw nav data easting position
February 2000 for version 1.40 73
Appendices

Appendices
B.1 Table of Tag Properties CODA-PI User Manual
Field name Applicable
to...
Raw Easting End Node The raw nav data end easting position
Raw Fish Height Sonar The raw nav data fish height above the seabed
in metres
Raw Fish Offset Sonar The raw nav data distance cross-track in metres
from the ship position to the fish position;
Starboard is positive
Raw Heading Node &
Sonar
Raw Kp Node &
Sonar
Raw Kp End Node &
Sonar
74 February 2000 for version 1.40
The raw nav data heading (degrees)
The raw nav data Kp position
The raw nav data end Kp position
Raw Layback Sonar The raw distance in metres from the ship
position to the fish position
Raw Northing Node The raw nav data northing position
Raw Northing End Node The raw nav data end northing position
Raw Water Depth Sonar The raw nav data water depth in metres
Roll Sonar The instantaneous roll of the vessel/towfish
(degrees); starboard roll is positive
Sample Interval Sonar The time in seconds between each data sample
Sidescan Flags Sonar Sonar message bitfield
Description
Slant Feature Offset Node The slant corrected fish offset to feature of the
tag in metres
Slant Height Node The slant corrected height of the tag in metres
Slant Range Node The slant corrected range to fish of the tag in
metres
Slant Width Node The slant corrected width of the tag in metres
Sonar CorrNav Off Sonar A mnemonic indicating which nav parameters
are uncorrected in the associated sonar message
(see Appendix D)
Sonar CorrNav On Sonar A mnemonic indicating which nav parameters
are corrected in the associated sonar message
(see Appendix D)
Sonar Frequency Sonar The frequency of the sonar (Hz) – unused
Speed of Sound Sonar The speed of sound through the water (m/s)
Speed Over Ground Sonar The speed over the ground that the fish is
travelling (m/s)
Start Delay Sonar The start delay in milliseconds (set in the
acquisition parameters)
Swell High Freq Sonar The High cut off frequency for the swell
filtering (Hz), SBP only

CODA-PI User Manual B.1 Table of Tag Properties
Field name Applicable
to...
Swell Low Freq Sonar The Low cut off Frequency for the swell
filtering (Hz), SBP only
Swell Source Sonar The source of swell filtering used (i.e. Manual,
Automatic etc), SBP only
Swell Value Sonar The value of swell in metres, SBP only
TDOP Sonar The time dilution of precision (as entered via
the nav string) of associated sonar message
TagID Node The Tag Database Identification Number
Tag-Name Node The name of the Tag (as assigned in the Setup
Tags pop-up)
Tag Source Node An indication of whether the tag node was
automatically (A) or manually (M) marked
Temperature Sonar The water temperature (degrees C)
Time Node &
Sonar
Description
The Nav time of the sonar message at which
the tag was placed on the data
Time Basis Sonar Whether the time zone is local or UTC (GMT)
Transmitted Power Sonar The transmission power of the sonar message
in decibels (from nav input)
Trigger Number Sonar The trigger number of the sonar message (e.g.
A, B, C)
UTM Zone Sonar The UTM zone number of the survey
VDOP Sonar Vertical dilution of precision (as entered via the
nav string) of associated sonar message
Voltage Range Sonar The associated sonar data voltage range as is
set in the Acquisition Parameters (volts)
Water Depth Sonar The corrected water depth in metres (via nav)
of associated sonar message
Width Node The Width of the Tag in metres – Normally
taken from a tag measurement in metres
Width CorrNav Off Node A mnemonic indicating which nav parameters
are uncorrected when calculating the node
width (see Appendix C)
Width CorrNav On Node A mnemonic indicating which nav parameters
are corrected when calculating the node width
(see Appendix C)
Yaw Sonar The yaw of the vessel/towfish (degrees);
Starboard is positive (from nav input string)
Zero Offset Sonar The DC level of data samples. This number is
the sample value for 0V
February 2000 for version 1.40 75
Appendices

Appendices
B.1 Table of Tag Properties CODA-PI User Manual
76 February 2000 for version 1.40

CODA-PI User Manual C.1 Measurement Methods
C Calculations for Tag Node Measurements
Measurements are calculated using the start and end points of the user-placed measure line, as
shown in Figure C-1, this page.
End
heading
End Ping
E,N
Start
heading
Start Ping
E,N
Track
End range
Start range
Figure C-1 Difference in E,N
Measure
Start point
C.1 Measurement Methods
Measure
End point
Measure line
When the measurement method in the Settings menu is set to Difference in E,N pair, both the
start and end points have their E, N (Easting and Northing) calculated from their associated ping
E, N. The ping E, N is first corrected and then, using the heading, fish height and range, a true
range distance and bearing is calculated, to compute the measurement point E, N. The heading
and fish height values will also be corrected if available. The measurement distance is then calculated
from the difference in the Easting and Northing pairs.
The most accurate measurements therefore require corrected values for the start and end points’
E, N, heading and fish height. When the measurement is associated with a tag node (as either
length, width, height or offset) a report may be output that indicates which of the measurement
values have been corrected (or alternatively, which have not been corrected). These are displayed
as letters as follows:
• e = Easting
• n = Northing
• h = heading
• f = fish height
These letters are preceded by either an ‘S’ for start point values or ‘E’ for end point values. For
example, Senhf Eenhf indicates that the Easting, Northing, heading and fish height have been
corrected for both the start and end point. If any letter had been missing, a less accurate
measurement would result.
When the measurement method is set to Speed x Time, only the start point has its position calculated.
The end point is then calculated based on the along-track and across-track distance differences
(see Figure C-2, page 78).
February 2000 for version 1.40 77
Appendices

Appendices
C.1 Measurement Methods CODA-PI User Manual
Start
heading
Start Ping
E,N
Track
Start range
Figure C-2 Speed x Time
Along-track
Measure
Start point
The distances are calculated as follows:
This measurement method is less accurate than Difference in E,N pair if corrected nav is
available, but may give more accurate results when only raw nav is available. Typically the
accuracy of this method is determined by the ship speed values input via the nav string. If these
values are inaccurate, the along-track distance will also be inaccurate. Across-track distances are
generally very accurate, provided that the speed of sound is approximately correct.
If the nav positions are given as Lat/Long rather than E,N, then the Lat/Long pairs are first
converted to E,N and then the above calculations performed to get the required position. This
position is then reconverted back to Lat/Long.
78 February 2000 for version 1.40
Across-track
Measure
End point
Measure line
StartPointShipSpeed + EndPointShipSpeed
AlongTrack = ------------------------------------------------------------------------------------------------------------------- × Time
2
AcrossTrack = SpeedOfSound × Time
Distance ( AlongTrack ) 2 ( AcrossTrack)
2
=
+

CODA-PI User Manual D.1 Measure Mnemonics
D Corrected Nav Report Mnemonics
See also: Appendix C
D.1 Measure Mnemonics
• S = Start point of measure
• E = End point of measure
These are prefixes to the following letters:
• e = Easting
• n = Northing
• h = heading
• f = fish height
For example
SenEnh = Start point Easting and Northing, End point Northing and heading.
D.2 Sonar Mnemonics
These represent values for the sonar ping, as follows:
• e = Easting
• n = Northing
• h = heading
• k = Kp
• d = dcc
• l = layback
• o = fish offset
• f = fish height
• w = water depth
D.3 Node Mnemonics
These represent values stored for each tag node. Nav fields not mentioned here are taken from
the tag’s associated ping information (see Appendix C):
• e = Easting
• n = Northing
• k = Kp
• d = dcc
February 2000 for version 1.40 79
Appendices

Appendices
D.3 Node Mnemonics CODA-PI User Manual
80 February 2000 for version 1.40

Part VII: Checklists
Checklists

Checklists
82 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual E.1 GeoKit/CODA-PI Mobilisation Checklist
E Mobilisation Checklists
Before starting a survey with the CODA-PI system, you should check that the equipment is
mobilised correctly. Correct mobilisation procedures ensure that, at the time of sailing, the
system is functioning correctly and is receiving all the data it needs in a form that it understands.
We recommend that the mobilisation procedures are observed every time a vessel sails, and that
they form the basis of any ISO9000 definition of readiness for use before sailing.
If any of the items in the list below are unclear, feel free to consult our Technical Support staff
at any time. Details are given on the inside front cover of this manual.
Our Technical Support staff may ask about the mobilisation checklist items if technical support
is required during a survey.
E.1 GeoKit/CODA-PI Mobilisation Checklist
1 Tag Setup Files
GeoKit/CODA-PI Mobilisation Comments Initials
1.1 Are the correct tag types set up? Have you
included all the tag types required by the
client?
1.2 Are the start/end codes correct?
1.3 Are the correct tags active?
1.4 Are the forced measures set for the
appropriate tags?
1.5 Is the Tag Setup saved on the system hard
disk/optical disk?
1.6 Has the Tag Setup been saved to
tape/optical disk, using Maintenance
Menu→Backup Setup Files?
1.7 Has the Tag Setup file name changed on
the system hard disk/optical disk?
1.8 Has the Tag Setup been reloaded onto the
system hard disk from tape/optical disk,
using Maintenance Menu→Restore
Setup Files?
1.9 Is the tape/optical disk labelled and writeprotected?
2 Fast Tag Files
2.1 Are the Fast Tag Setup files correct for
the job?
2.2 Is the Fast Tag Setup saved on the
system hard disk/optical disk?
2.3 Has the Fast Tag Setup saved to
tape/optical disk, using Maintenance
Menu→Backup Setup Files?
February 2000 for version 1.40 83
Checklists

Checklists
E.1 GeoKit/CODA-PI Mobilisation Checklist CODA-PI User Manual
2.4 Has the Fast Tag Setup file name changed
on the system hard disk/optical disk?
2.5 Has the Fast Tag Setup been reloaded
onto the system hard disk from
tape/optical disk, using Maintenance
Menu→Restore Setup Files?
2.6 Is the tape/optical disk labelled and writeprotected?
2.7 Has the right mouse button been set up for
maximum efficiency?
3 System Hard Disk
3.1 Have all previous interpretations and tag
files been stored to tape/optical disk and
labelled correctly?
3.3 Have all unwanted tag files on the system
hard disk/optical disk been deleted?
4 Report Files
4.1 Are the Report Setup files correct for the
job?
4.2 Can the Report ASCII output on floppy
be read by the system the report is
intended for?
4.3 Is the report format as required and
meaningful?
4.4 Is the Report Setup file saved onto the
system hard disk/optical disk?
4.5 Have the Report Setup files been
saved to tape/optical disk, using Maintenance
Menu→Backup Setup Files?
4.6 Has the Report Setup file name changed
on the system hard disk/optical disk?
4.7 Has the Report Setup been reloaded onto
the system hard disk from tape/optical
disk, using Maintenance Menu→Restore
Setup Files?
4.8 Is the tape/optical disk write-protected
and labelled?
84 February 2000 for version 1.40
GeoKit/CODA-PI Mobilisation Comments Initials
CODA system mobilised for Tagging
& Reporting
Signed Date

CODA-PI User Manual E.2 CODA-PI Mobilisation Checklist
E.2 CODA-PI Mobilisation Checklist
1 Tagging & Reporting
CODA-PI Mobilisation Comments Initials
1.1 Have all the checks in the GeoKit/Pipeline
Inspection Mobilisation Checklist
(above) been carried out successfully?
2 Pipeline Inspection
2.1 Is the pipeline external diameter known
for all the pipelines to be surveyed?
2.2 Is the client spec for touchdown known
for all the pipelines to be surveyed?
2.3 Is the minimum span length to report
known for all the pipelines to be
surveyed?
CODA system mobilised for Pipeline Inspection
Signed Date
February 2000 for version 1.40 85
Checklists

Checklists
E.2 CODA-PI Mobilisation Checklist CODA-PI User Manual
86 February 2000 for version 1.40

CODA-PI User Manual F.1 Saving Tag Files to Tape/Disk Checklist
F On-Line Checklists
The purpose of these checklists is to ensure that the system operator is carrying out all the
required steps when tagging or generating reports with the Coda system.
F.1 Saving Tag Files to Tape/Disk Checklist
Tape System:
Blank tape loaded into drive 1 q
Files saved using Tagging→ManageTag Files→TapeLoad/Save.
(Save Batch Overwrite to overwrite existing data on tape; Save Batch Append
to write to the first blank section of the tape)
Tag files saved correctly (List Previous Batch showed the appropriate tag files) q
Optical Disk System:
Blank optical disk loaded into drive. q
Tag files located and selected using Tagging→Manage Tag Files→Database
Location
Tag files copied to target location using Copy Tag Files q
Tag files saved correctly (Database Location showed the appropriate tag files) q
Tape/Disk Systems:
Tag file tape labelled correctly: q
Date and time of recording q
Data Source q
Client q
Kp (start and end) q
Tag file name q
Tag file tape/optical disk write protected q
Tag file stored with data file tape/optical disk q
F.2 Loading Tag Files to System Hard Disk Checklist
Tag file tape/disk loaded into correct drive q
Tag file tape rewound (tape system only) q
Tag file copied correctly. Tag filename appears in Tagging→Manage Tag Files
window following Rescan
q
q
q
February 2000 for version 1.40 87
Checklists

Checklists
F.2 Loading Tag Files to System Hard Disk Checklist CODA-PI User Manual
88 February 2000 for version 1.40

Part VIII: Glossary &
Conversions
Glossary &
Conversions

Glossary &
Conversions
90 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual
Conversion Table
The following tables may be used for conversion from one unit of measurement to another. The
units are grouped under the headings: angle, area, length/distance, temperature, time, velocity/
speed, weight.
An Example of Use of the Tables
To convert a measurement from a unit in the first column (Unit A) to a unit in the fourth column
(Unit B), you multiply the measurement by the multiplier/conversion factor in the second
column (Unit A to Unit B multiplier/conversion). For example, to convert 10 knots to metres per
second: 10 x 0.5145 = 5.145 metres per second.
To convert a measurement from a unit in the fourth column (Unit B) to a unit in the first column
(Unit A), you multiply the measurement by the multiplier/conversion factor in the third column
(Unit B to Unit A multiplier/conversion). For example, to convert 10 metres per second to knots:
10 x 1.944 = 19.44 knots.
Angle
Area
Unit A Unit A→Unit B
multiplier/conversion
Length/Distance
Unit B→Unit A
multiplier/conversion
degrees (angle) 1.745 10 57.3 radians
2 – ×
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
Unit B
acres 4.356 10 square feet
4 × 2.296 10 5 – ×
acres 4047 2.471 10 square metres
4 – ×
square feet 9.290 10 10.76 square metres
2 – ×
square miles 3.098 10 square yards
6 × 3.228 10 7 – ×
square miles 640 1.562 10 acres
3 – ×
square miles 2.59 0.3861 square kilometres
square millimetres 1973 5.067 10 circular mils
4 – ×
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
chain (surveyors’) 66 1.515 10 feet
2 – ×
fathoms 6 0.1667 feet
Unit B
feet 30.48 3.281 10 centimetres
2 – ×
feet 0.3048 3.281 metres
February 2000 for version 1.40 91
Glossary &
Conversions

Glossary &
Conversions
Temperature
Time
Unit A Unit A→Unit B
multiplier/conversion
92 February 2000 for version 1.40
CODA-PI User Manual
inches 2.54 0.3937 centimetres
inches 8.333 10 12 feet
2 – ×
inches 1.578 10 miles
5 – × 6.336 104 ×
inches 1000 0.001 mils
inches 2.778 10 36 yards
2 – ×
kilometres 3281 3.048 10 feet
4 – ×
leagues 3 0.33 miles (approximately)
metres 1.094 0.9144 yards
miles (nautical)* 6076.1 1.646 10 feet
4 – ×
miles (nautical)* 1852 5.400 10 metres
4 – ×
miles (nautical)* 1.1508 0.869 miles (statute)
miles (statute) 1.609 0.6214 kilometres
miles (statute) 5280 1.894 10 feet
4 – ×
yards 3 0.3333 feet
* Conversion factors for the nautical mile and, hence, for the knot, are based on the International
Nautical Mile
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Centigrade (Celsius) Fahrenheit
⎛ 9
C° × --⎞
5
+ 32 ( F° – 32)
×
--
⎝ 5⎠
9
Unit A Unit A→Unit B
multiplier/conversion
GMT date & time see Appendix F
of the DA System
User Manual
UTC seconds see Appendix F
of the DA System
User Manual
Unit B→Unit A
multiplier/conversion
Unit B→Unit A
multiplier/conversion
see Appendix F
of the DA System
User Manual
see Appendix F
of the DA System
User Manual
Unit B
Unit B
Unit B
UTC seconds
GMT date & time

CODA-PI User Manual
Velocity/Speed
Weight
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
knots** 1.688 0.5925 feet per second
knots** 30.87 0.0324 metres per minute
knots** 0.5145 1.944 metres per second
knots** 1.1508 0.869 miles (stat) per hour
metres per minute 3.281 0.3048 feet per minute
metres per minute 0.06 16.67 kilometres per hour
miles per hour 0.4469 2.2374 metres per second
miles per hour 88 1.136 10 feet per minute
2 – ×
miles per hour 1.609 0.6214 kilometres per hour
** Nautical miles per hour
Unit A Unit A→Unit B
multiplier/conversion
Unit B→Unit A
multiplier/conversion
Unit B
kilograms 2.205 0.4536 pounds (avoirdupois)
February 2000 for version 1.40 93
Glossary &
Conversions

Glossary &
Conversions
94 February 2000 for version 1.40
CODA-PI User Manual

CODA-PI User Manual
Glossary
A/D conversion the process of converting an analogue signal to a digital one
absolute using a predefined frame of reference (0 Kp, or 0:00 on 1st January,
1970); see also relative
AC Alternating Current; mains supply
acquisition see data acquisition
acquisition mode see data acquisition mode
acquisition parameters the settings used within the acquisition sub-system to determine
the quality and volume of the digital data obtained
acquisition sub-system the parts of the DA100/DA200 concerned with obtaining a digital
form of the analogue sonar inputs
across-track at 90° to the towfish or vessel track
across-track resolution the distance across-track covered by each sample of sonar data
active channel a data channel which is currently being digitised
aliasing distortion of the input signal caused by carrying out digitisation
at too low a sampling frequency
along-track along the line of the towfish or vessel track
along-track resolution the distance along-track covered by each sample of sonar data
altitude (of towfish) the distance above the seabed
ambient temperature the temperature of the surrounding air
analogue conveying information by changes in signal amplitude and phase;
see also digital
annotation (of sonar records) the practice of using an external device to overlay
the analogue sonar data with navigation information
Application Specific
Area
the part of the DA100/DA200 display (in the bottom right of the
screen) whose functions change in playback and acquisition
modes
Apply A button which applies the settings or options selected and
retains the pop-up window on the screen.
ASCII American Standard Code for Information Interchange; the worldwide
standard means of sending alphanumeric characters in a
7-bit format
auto pause release (of the DA100/DA200) a feature which prevents the freezing of
the screen display by the Pause button if further pausing would
cause loss of data to the screen
automatic position
pointer
the pointer type used for resetting the position of automatically
tracked features during PI100 operation
automatic sub-sample (of the DA100/DA200) the default sub-sample mode; this automatically
derives a sub-sample rate which allows the full swathe
width to be displayed on the screen
batch a group of tag files saved in the same save operation
February 2000 for version 1.40 95
Glossary &
Conversions

Glossary &
Conversions
96 February 2000 for version 1.40
CODA-PI User Manual
baud rate (of RS-232 interfaces) the rate at which raw data bits are sent;
roughly equivalent to bits/second
bit binary digit; the smallest information unit in a digital system
BNC connector industry-standard bayonet connector for analogue and digital
signals
bottom tracking (of the DA100/DA200) automated location of the seabed first
return to allow the towfish altitude to be calculated
byte 8 bits
Cancel this button cancels any items or options selected and dismisses a
pop-up window, retaining the previous settings
case sensitive recognising the difference between lower and upper case letters
(for example, ‘a’ and ‘A’)
Centronics industry-standard parallel interface for connecting devices such
as printers and plotters to computer equipment
cleaning cartridge the means of carrying out head cleaning for DAT or Exabyte tape
drive units; a tape cartridge which holds cleaning tape rather than
recording tape
click press down and release the appropriate mouse button; if no button
is specified, the left button should be used
clipped (of analogue input signals) not converting the whole of the input
range, thus losing some of the signal (for example, the outgoing
pulse in sonar data); this should only be allowed to happen if the
information being discarded will NEVER need to be recovered
Coda format Coda Technologies’ format for storing data to a recording media;
retains more information about the recorded data than other
proprietary data formats
COM1 the name commonly used in DOS systems for the first serial port
COM2 the name commonly used in DOS systems for the second serial
port
compression (of tape drives) the practice of eliminating redundancy in the data
being recorded, allowing a larger amount of data to be stored in a
given space
continuous record (of the DA100/DA200) a facility which allows recording of
incoming data to carry on continuously, without the need to stop
recording when changing data tapes or optical disks
contrast the variation in shades of grey or hue within the display
corrected navigation
data
navigation information which has been smoothed to remove
spikes or jitter from the positional information
creator node the first node in a multi-node tag
critical length (PI100) the length in metres that an automatically detected span
must be before it is deemed to be a critical span (user-defined)
cross track at ninety degrees to the direction of travel of the towing vessel
cross-track offset the straight line cross-track distance from the vessel datum point
to the point where the tow cable passes over the stern of the
vessel

CODA-PI User Manual
cross-track slant
distance
the distance measured between two points solely in the crosstrack
direction. It is a non-slant corrected measure (i.e. it is
dependent on fish height)
cross-track smoothing (of sidescan sonar data) low pass filtering of the sonar signal
from the nearest to the farthest end of the swathe, using a filter of
fixed frequency response
current tag (of the DA100/DA200) the event marker selected to be active by
clicking on the appropriate area of the Data Display Area. The
selected tag flashes between its normal colour and light blue
cursor symbol that shows the position on the display where any typed
text will be entered
DA100 Coda Technologies’ system for acquiring, processing and
replaying sidescan sonar or sub-bottom data, with single trigger
capability
DA200 Coda Technologies’ system for acquiring, processing and
replaying data from two independently firing sonars, e.g.
sidescan sonar and boomer
DAT Digital Audio Tape; an international standard for the recording of
analogue data to digital tape; see also DDS and DDS2
data acquisition the process of obtaining data (usually in digital form)
data acquisition mode (of the DA100/DA200) the operation mode in which the DA100/
DA200 is digitising and records data; see also data playback
mode
data bits the number of bits used to hold the information from each
sample; usually an integer number of bytes (8, 16 or 32 bits)
data channel a flow of data (for example, sonar data) into or within the DA100/
DA200; see also display channel
Data Control Area (of the DA100/DA200) that part of the DA100/DA200 interface
which controls the operation of the tape or optical disk drive unit
or units
Data Display Area (of the DA100/DA200) that part of the screen given over to the
display of data from the acquisition sub-system or from tape or
optical disk; the upper portion of the screen
data format (of tapes or optical disks) the scheme used to record the digital
data onto the tape or optical disk. Different formats can result in
different amounts of data being stored; see also Coda format,
Q-MIPS format, SDEF format, SEG-Y format
data playback mode (of the DA100/DA200) the operation mode in which the DA100/
DA200 reads previously recorded data from tape or optical disk
and displays it on the screen
database a structured means for storing and retrieving data in digital form,
allowing rapid random access to individual data entries
datum point the point on the towing vessel from which all measurements are
referenced
DCC Distance Cross Course; the across-track distance of a point from
the survey line
DDS Digital Data Storage; the standard format for storing computer
data to DAT tapes
February 2000 for version 1.40 97
Glossary &
Conversions

Glossary &
Conversions
98 February 2000 for version 1.40
CODA-PI User Manual
DDS2 an improvement to the DDS standard, allowing a higher recording
density to be used, hence obtaining more storage capacity
from a given length of magnetic tape
dead time (in digitisation) the time allowed between the end of sampling for
a given data line (or ping), and the arrival of the next trigger
pulse
DGPS Differential GPS. A form of GPS which uses a base station to
send corrections to the satellite derived positions, allowing more
accurate fixes to be obtained
digital representing information by a sequence of bits, rather than using
the signal amplitude and phase; see also analogue
digital signal processing
using numerical techniques to carry out signal filtering or amplification
in the digital domain, rather than the analogue domain
digitisation the process of converting an analogue signal’s amplitude and
phase information into digital form
display channel a data channel which is displayed on the DA100 screen
DOS see MS-DOS
DOS formatted (of floppy disks) formatted on the MS-DOS operating system
double-click press and release the specified mouse button twice in rapid
succession; if no button is specified, the left button should be
used
dual tape (of DA100/DA200) a system having two tape drive units, rather
than one
dynamic range that portion of an analogue signal which actually conveys
information; that is, the range of values between the highest and
lowest encountered
Eastings distance East or West in metres of a given position from the UTM
or lat/long origin
edge sensitive (of TTL input) reacts to the change in voltage level, rather than to
the steady-state voltage level
Encapsulated Postscript®
EOT End Of Tape
a form of Postscript® which is suitable for incorporating into
documents on word processing packages, spreadsheets, and so on
Ethernet Local Area Network using a coaxial cable with BNC connectors,
capable of up to 1.25MB/second transfer rate
event (DA100/DA200) a point in the data which the user wishes to mark
using a database entry
Exabyte 8mm magnetic tape drive unit (based on 8mm video tape technology)
used for storage of digital computer data
external trigger (DA100/DA200) a TTL trigger which originates outwith the
DA100/DA200, used by the system to initiate the acquisition for
each ping
fast tag (PI100/GeoKit) colour-coded keys for accelerated marking of
events during pipeline inspection

CODA-PI User Manual
file a set of data which exists as a distinct entity; on tape, file extents
are defined by end of file markers; on disk, they are defined by
the operating system
filtering the alteration of the frequency content of a signal; usually the
removal of unwanted (noise) frequencies
first return (in sonar data) the first echo which rises above the noise level of
the water column; the first point of contact of the outgoing pulse
with the seabed
fish abbreviation for towfish
fish height (PI100) the true height of the sonar transducer (fish) above the
seabed
fix a reference point (in time and space) for navigation purposes
fix tag the database entry for a given fix; see also tag
floppy disk portable magnetic media. Usually refers to 3½ inch double-sided,
high density disks with a capacity of 1.44MB (formatted)
flow chart method of breaking down a task into a sequence of actions and
decisions in diagrammatic form
flow control also known as handshaking
forced measure (following tag operation in PI100/GeoKit mode) a sequence of
measurements of the tag’s features which may have to be carried
out manually, rather than automatically by the system. The Tag
Placement Rules define which measurements are required for a
given tag
full resolution (zoom) using all the available samples for display; no subsampling
of any sort is carried out
gamma (colour mapping) the exponential function used to map incoming
intensities to greyscale values
gamma correction the process of redisplaying the image data displayed on screen
using a new gamma value
GB Gigabyte, approximately 1 000 000 000 bytes
General Information
Area
(DA100/DA200) that area of the screen which holds the current
ping number, time and cursor position; situated above the Data
Control Area
GeoKit Coda Technologies’ software module for geophysical interpretation,
which allows the user to tag events and generate ASCII
report output
goto (DA100/DA200) a command allowing random access to sonar
data stored on magnetic tape or optical disk
GPS Global Positioning System – a satellite-based navigation system
graphical user interface the means of interaction of the computer user with the programs
running on the computer; uses the display, the keyboard and the
mouse/trackball
greyed out (DA100/DA200) menu items which cannot be selected are greyed
out, written in lighter, grey text
greyscale the range of shades from black to white
February 2000 for version 1.40 99
Glossary &
Conversions

Glossary &
Conversions
grip see grip point
100 February 2000 for version 1.40
CODA-PI User Manual
grip point (DA100/DA200) a point on an interactive graph, signified by a
small square, which can be moved by users (using the mouse/
trackball) to alter the shape of the graph
GUI Graphical User Interface
half-wave rectify remove those portions of an incoming analogue signal which are
below some threshold value (usually 0 volts)
handshaking (of RS-232 interfaces) the means by which the starting and
stopping of data transfers is effected; this can be carried out in
hardware or software
hard disk the magnetic disk which is permanently attached to a computer
system
hardcopy printed output; the generation of printed output
hardware electronic components
hardware handshaking handshaking carried out by electronic components, without the
intervention of any computer program
heave compensation
unit
a piece of equipment external to the sonar which monitors the
vessel’s heave, and varies the timing of the trigger pulse sent to
recording equipment (for example, the DA100/DA200), so that
the effect of vessel heave is largely eliminated; used for subbottom
profiling
height trigger (PI100) the minimum height of the bottom of the pipe above the
seabed that will trigger the pipe span condition (user-defined)
high contrast a large proportion of the available grey is used to display the
regions of the image the user is interested in
high pass filtering removing the low frequency component of a signal
high resolution (of digital storage) retaining a large proportion of the original
information content of the signal
hue the shade or tint of a colour
Hz Hertz; the SI equivalent of cycles/second
icon small symbol on the computer screen which represents some
entity or function within the computer system
image enhancement performing image processing in order to improve the quality of
an image (for example, the display of sonar data on a screen)
image processing performing manipulations to an incoming digital signal on the
assumption that the data contained therein has some meaning as
an image
indented (DA100/DA200) the buttons used to control the functions of the
DA100/DA200 (for example the data control buttons) have a
three-dimensional look; when a button has been activated, the
shading changes and the button appears to have sunk into the
interface – to have been indented
information window a window which supplies the user with information, but does not
accept any input from the user (for example, the Survey Data
window)

CODA-PI User Manual
input voltage range the range of voltages which can be digitised by the DA100/
DA200
intensity strength, brightness, magnitude or amplitude of a signal
interface a means of transferring information from one piece of computer
equipment to another
internal trigger (DA100/DA200) a TTL trigger pulse which is generated by the
DA100/DA200, allowing it to trigger other equipment (for
example, to trigger the sonar ping)
interpolation the practice of estimating the value of a variable at a point by
setting it between the values of later and earlier samples
invert causing the range of shades (for example, from black to white) to
be reversed, so that items which were coloured black become
white, and vice versa
IO Input/Output
ISA Industry Standard Architecture; a type of signal bus used inside
PCs
jitter the noise present on a signal, causing observations which should
be identical to differ
KB Kilobytes (1 024 bytes)
Kp Kilometre post (distance along the survey line or pipeline, in kilometres)
Landscape mode (Postscript®) printed so that the bottom of the Postscript®
document is aligned with the long edge of the sheet of paper
layback the along-track distance from the datum point on the vessel to the
towfish
LED Light Emitting Diode: small coloured light attached to electronic
equipment
line of data all the data arising from a given sonar ping; for sidescan this
implies both port and starboard channels
local area network the cabling and interfacing standards which allow a collection of
computers to be connected to each other to share data and
resources (for example, Ethernet, Token Ring)
lookup table the rule used to translate incoming digital signals into grey levels
or colours for display; also known as palette
loopback testing a piece of equipment by using its own output as an input
signal, thus testing both the input and output functionality
low contrast a comparatively small range of grey levels is used to display all
the parts of the image the viewer is interested in; see also
contrast, high contrast
low pass filtering removing the high frequency component of a signal
LPT1 the name commonly used on DOS systems for the first parallel
port
LUT Lookup Table
master trigger a trigger used to start a number of pieces of electrical equipment,
to ensure their synchronisation
February 2000 for version 1.40 101
Glossary &
Conversions

Glossary &
Conversions
MB Megabyte; roughly 1 000 000 bytes
Media Recognition
System
102 February 2000 for version 1.40
CODA-PI User Manual
second-generation DDS standard tapes, which have markings
which allow the length of tape to be determined by the tape drive
unit
megabyte approximately 1 000 000 bytes; see also MB
menu an area of the display (either a Menu Bar or a window) which
allows users to choose from a number of options, using either the
keyboard or the mouse/trackball
Menu Bar an area (at the top of the display in the DA100/DA200) in which a
number of menu items are permanently displayed
merge length (PI100) the minimum length (or separation) between separate
pipe events (e.g. spans) that will prevent the events from being
merged as one single event (user-defined)
Microsoft Windows a windowing operating system for IBM-PC compatibles
minimum length (PI100) the minimum length a pipe event (e.g. span) can be
without it being discarded as being too short (user-defined)
Mosaic Coda’s software module for Mosaicing sidescan sonar records
mosaicing the process of geopositioning sidescan sonar records such that an
image of a large area of the seafloor is built up line by line
Motif a library of software routines used for building user interfaces,
giving a characteristic ‘look and feel’
mouse a pointing device for use with computers. Movement of the
mouse moves the screen pointer; see also trackball
MS-DOS Microsoft Disk Operating System; see also DOS
multi-node tag an event marker which has several user-positioned points (or
nodes), used to define a boundary or a layer
multi-resolution capable of displaying or processing data at a number of scales
multi-tasking (of operating systems) able to run several programs simultaneously
nav string abbreviation for navigation string
navigation data any form of navigation information within the DA100/DA200
navigation input any form of navigation input to the DA100/DA200 system
navigation library (DA100/DA200) the reference table which allows the DA100/
DA200 to interpret incoming navigation strings
navigation string an ASCII string holding navigation data
node see tag node
non-interlaced (of computer monitors) displaying all the pixels within the
display in a single pass; interlaced displays take two passes, each
displaying every second line of pixel data
northings distance North or South in metres of a given position from the
UTM or lat/long origin
off-line processing which does not take place as data is being acquired, or
at the rate of acquisition

CODA-PI User Manual
offset (DA100/DA200) the distance of a given sample from a datum
point; usually the distance of the start of the raw data line to the
start of the displayed line
OK a button which selects and applies the settings or options selected
and dismisses the pop-up window from the screen
on-line processing which takes place as the data is being acquired, and at
the rate of acquisition
on/off toggle a switch on the DA100/DA200 display which turns a system function
on or off; each selection of the switch changes the state of the
function (if it is ‘on’, selection turns it ‘off’; subsequent selection
turns it ‘on’ again)
one-of selection a form of switch on the DA100/DA200 display which selects one
from a number of possible options, where all the possible options
are displayed
operating system the program which ‘manages’ a computer, allowing the user’s
programs to run (e.g. Unix, Windows, DOS)
option selection a form of switch on the DA100/DA200 which selects one from a
number of possible options, where all the options except the one
selected are hidden
outgoing pulse the pulse of sound energy which is reflected to form sonar
images; visible on recorded sonar data as the bright stripe at the
beginning of each line
overlay plane additional coloured graphics which can be displayed on top of
sonar data; these may be switched on and off without affecting
the displayed data
overwrite record another set of data over the first, making the first data set
unrecoverable
palette equivalent to lookup table
parallel port a form of interface which allows a computer to interchange data
with the outside world in parallel form (that is, passing all 8 bits
of a byte simultaneously)
parity a form of error checking for each byte of data transferred (for
example, through a serial or parallel port)
password a collection of letters and numbers which uniquely allows access
to a computer or a set of programs on a computer
PCI Peripheral Component Interconnect: an advanced, high-speed bus
system used by PC-compatible computers
PI100 Coda Technologies’ Pipeline Inspection system, which allows
complete pipeline surveys to be undertaken without the use of
thermal recorders
ping a single sonar scan, resulting in a line of data being acquired
pipe distance (PI100) the slant distance from the sonar transducer (fish) to the
front of the pipe
pipe grazing angle (PI100) the angle made between the ensonified pipe, the transducer
and the seabed directly below the transducer
pipe height (PI100) the true height of the bottom of the pipe above the seabed
February 2000 for version 1.40 103
Glossary &
Conversions

Glossary &
Conversions
pipe striking angle see pipe grazing angle
104 February 2000 for version 1.40
CODA-PI User Manual
pixel picture element; the dots on the screen from which an image or
GUI is built
playback mode see data playback mode
playback speed the rate at which sonar lines are displayed on the screen
pointer the icon which reflects changes in the mouse position, or movements
of the trackball. Usually an arrow, but may take other
forms
pop-up menu a menu which appears as the result of a selection in a previous
menu
pop-up window any form of window which appears as the result of a mouse/
trackball, or keyboard selection from a menu in the interface
port equivalent to interface; also left – see also starboard
Portrait mode (of Postscript® documents) printed so that the bottom edge of the
document is aligned with the shorter edge of the paper
positive edge (of TTL inputs) a signal which changes from 0 to 5V
Postscript® a language for describing printed matter (text, diagrams and
images)
power down the procedure to be observed when turning off the mains power to
an item of electrical equipment
power up the procedure to be observed when turning on the mains voltage
to an item of electrical equipment
pre-emptive scheduling allowing one program running in a multi-tasking operating
system to cause other programs to be suspended and only
restarted once the pre-empting program has completed its tasks
press and drag press down the appropriate mouse button, and without releasing
it, move the mouse so that the pointer is in the desired position on
the screen; then release the mouse button
processed navigation
data
see corrected navigation data
PSU Power Supply Unit: converts mains (AC) voltage to the lower
voltages required by computer equipment
pull-down menu a menu which appears when a Menu Bar option is selected; items
within a pull-down menu are selected by pressing and dragging
to the required menu item
Q-MIPS format a format for the storage of sonar data to tape
random access obtaining data from a file or memory in an order which is not the
same as the order the data was stored in
real-time occurring at the speed of data acquisition, or faster
reboot cause a computer system to completely re-initialise itself, as
though the power had been turned off, then on again
recording session the time from the start of recording data to the cessation of
recording

CODA-PI User Manual
relative using a local frame of reference (for example, time or distance
measurements as an offset from the current time or distance); see
also absolute
resolution the level of detail which may be extracted from a set of data
ROTV Remotely Operated Towed Vehicle. Subsea vehicle on which a
sidescan sonar or sub-bottom profiler may be mounted
RS-232 an international standard for the interchange of serial data
between computers
sampling to convert analogue data to digital form, it is necessary to
measure its amplitude at regular intervals; this is known as
sampling the signal
sampling frequency the frequency at which an analogue waveform is sampled to
allow it to be converted to digital form
saturation (of colours) the depth of a given tint or shade
screen dump producing an image of the screen display, and either printing it or
saving it to disk
scroll bar the means by which all the items in a list appearing in a menu or
pop-up window may be examined
scrolling moving gradually up or down the display; one line of data must
move out of the bottom of the display for every new line which
appears at the top
SCSI-2 Small Computer Systems Interface, version 2; an improved
version of the SCSI standard for connection of peripheral devices
(such as tape drives, disks and scanners) to computers
SDEF format Sonar Data Exchange Format: sonar interchange format developed
by Meridian Sciences and US Geological Survey
SEG-Y format Society of Exploration Geophysicists ‘Y’ format; obsolescent
standard for seismic and sonar data storage
seismic using vibrations to obtain an understanding of the underlying
geological structure
select click the left mouse button on the appropriate item
serial port a form of interface which allows a computer to interchange data
with the outside world in serial form (that is, one bit at a time)
shortcut key a single typed character or sequence of keyboard inputs which
allows the user to carry out interaction with the DA100/DA200
interface without using the mouse
sidescan sonar a form of sonar which uses twin sideways looking transducers to
obtain an image of the seabed as it is towed through the water
signal processing see digital signal processing
single tape (of DA100/DA200) a version of the DA100/DA200 which has
only one tape drive unit
slant range the distance across-track to a point on the seabed from the
towfish position; this is directly proportional to the time from the
outgoing pulse transmission
February 2000 for version 1.40 105
Glossary &
Conversions

Glossary &
Conversions
106 February 2000 for version 1.40
CODA-PI User Manual
slant-range correction a geometric correction to the incoming sonar signal which
converts the across-track scale of the sonar data so that it is
directly proportional to distance across-track, rather than to time
slave trigger the incoming TTL trigger pulse which causes a piece of electronic
equipment to start a sequence of operations (for example,
the digitisation of sonar data)
smart icon an icon which if selected causes a sequence of operations to take
place on the interface (for example, the inversion of the display)
smoothed navigation
data
see corrected navigation data
software computer programs
sonar sound navigation and ranging; the use of sound underwater to
detect objects or make measurements
sonar input the analogue signal output by a sonar processing and control unit
(for example, EG&G 260) which can be accepted as an analogue
input by the DA100/DA200
span (PI100) section of pipe that is unsupported by the seabed
spline a function which smoothes the line of a graph through a number
of points
stacking see trace mixing
starboard right; see also port
stop bits (of RS-232 interfaces) the number of bits following the data bits,
before the start of the next byte transmission
string (of ASCII data) a collection of valid ASCII alphanumerical
characters
sub-bottom profiler a low-frequency sonar device for obtaining seismic information
about the geology under the seabed
sub-sampling the practice of missing out data samples at regular intervals,
allowing a signal to be represented by fewer samples
substrate the material which makes up the seabed or sub-bottom
swathe the area of the seabed covered by a sidescan sonar trace
tab form a form which contains a number of related items of information
or selections and has a labelled tab at the top. As tab forms
overlap, the required tab form may have to be brought to the front
of the pile by clicking on its tab
tag (of the DA100/DA200) a group of one or more interconnected tag
nodes
tag node (of the DA100/DA200) a unique database entry defining a point
within the data, or the screen graphic associated with it
tape cartridge the plastic cartridge containing the magnetic tape medium
tape drive see tape unit
tape head that part of the tape drive which is in contact with the tape
medium, and causes the data to be written to the tape

CODA-PI User Manual
tape unit (or tape drive unit) that part of the DA100/DA200 mechanism
which contains the tape head, and into which the tape cartridge is
loaded
TCP/IP Transmission Control Protocol/Internet Protocol; an interface
standard for local area networks
tear-off menu a pull-down menu which can be detached from the Menu Bar to
allow it to be displayed permanently on the interface
telemetry measurements carried out at a distance (for example of the
towfish altitude)
text-entry box an area in a window which allows the user to type input using the
keyboard, thus changing system parameters
thresholding the act of setting a level (for example, a greyscale intensity level,
or a voltage), above and below which different actions are taken
on the incoming signal
TIFF Tag Image File Format – a common, industry standard format for
storing and exchanging binary image data
time varying gain see TVG
titlebar (of the DA100/DA200) the area at the top of the DA100/DA200
screen which holds copyright information
toggle a form of switch which if pressed once is on, and if pressed again
is off
Token Ring the IBM Token Ring protocol for local area networking
toolkit a set of tools or functions accessed through a single pop-up
window
topology the shape of a surface
towfish the vehicle towed by a surface vessel in which the sonar transducers
are mounted
trace mixing adding (or subtracting) the data from succeeding sonar pings to
remove along-track noise; also known as stacking
track the path of the vessel or towfish over the seabed
trackball a pointing device for use with computers; movement of the trackball
moves the screen pointer; see also mouse
TrackPlot Coda’s software module for displaying vessel and towfish track
information
transducer a mechanism which transforms energy from one form into
another (for example, a sonar transducer converts electrical
energy to sound energy)
Transverse Mercator a geographical projection, similar to UTM, in which the user can
define the origin of the projection, by defining the footpoint latitude
and central meridan
trigger either an input which causes a piece of electronic equipment to
start a sequence of operations, or an output generated by one
piece of equipment, which others will use in this way; see also
slave trigger and master trigger
trigger source the piece of electronic equipment from which the trigger pulse
originated
February 2000 for version 1.40 107
Glossary &
Conversions

Glossary &
Conversions
108 February 2000 for version 1.40
CODA-PI User Manual
TTL Transistor-Transistor Logic; an electrical interfacing standard for
digital signals
TVG Time Varying Gain: an amplification applied to sidescan sonar
signals which compensates for the spreading loss of the signal,
which is roughly proportional to the log of the range in metres
TVG enhancement (of the DA100/DA200) a set of facilities which allow users to
alter the time varying gain applied to the incoming sonar signal
undersampling sampling at too low a sampling frequency, so that aliasing occurs
Unix a multi-user, timesharing operating system, with real-time
facilities; uses the X Window graphical user interface
update a revision to the DA100/DA200 software, incorporating new
features and/or bug fixes
user-specific (of files) the files in the DA100/DA200 system which are placed
there by users (for example, database files, smoothed navigation
data files)
UTC Coordinated Universal Time; the world time standard; equivalent
to GMT
UTM Universal Transverse Mercator; a form of geographical projection
which allows positions to be measured relative to each other
in metres, over a restricted area
watch pointer the pointer which appears on the display screen when the DA100/
DA200 is waiting for an operation to complete
water depth the depth of water input into the system; the user may define this
relative to a datum on the vessel, as the depth under the keel, or as
the depth under the echo-sounder transducer
waterfall display a scrolling display of image data
window an area of the graphical user interface set aside for a specific
operation, often disappearing when that operation has been
completed
Windows see Microsoft Windows, X Window
write protect (of disk or tape cartridge) set so that it cannot be written to, only
read from
X Window a graphical user interface standard for the Unix operating system
zoom the process of selecting an area of the display to be redisplayed in
greater detail
zoom mode defining the type of zoom operation to be carried out (for example,
full resolution, fixed magnification)

CODA-PI User Manual
Software Defect Report Form
Coda Technologies has made every effort to ensure that its software is reliable and performs
satisfactorily at all times. However, as with any software-based product, some defects may still
be present. If you encounter unexpected, undocumented or illogical behaviour by the system,
please complete this form and fax or mail it to:
Coda Technologies Ltd
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
Tel: +44 131 553 1380
Fax: +44 131 554 7143
User
Company
Unit Type
(rental/sale)
Date
Time
System Type
(e.g. DA100/PI100)
Software Version
Number
Serial Number
Mode in which fault
occurred (playback/
acquisition)
Description of Fault
(please be as specific as
possible)
Was recovery possible?
How?
On receipt of this form, Coda Technologies will contact you and issue a reference number for
this report and describe the remedial action to be taken.
For Coda office use only: Reference Number:
February 2000 for version 1.40 109
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
110 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
CODA-PI User Manual
Fourth
Fold -
tuck
into
flap

CODA-PI User Manual
Product Feedback
We at Coda value your opinion. Please give us your opinion of our products, in each of the
following areas. We’ll send you a free mousemat on receipt of your form.
Product Name
Excellent Good Fair Poor
Ease of Use: is the product easy to use? r r r r
Hardware: is the hardware reliable? r r r r
Software: is the software reliable? r r r r
Range of Facilities: are there enough tools? r r r r
Appearance: Do you like the format of the display?
Physical: Is the product ergonomically
designed?
Suitability: Is the system suited to your application?
Automation: Do you rely on automated interpretation?
Does the product meet your need? Why, or why not?
r r r r
r r r r
r r r r
r r r r
What’s the single most important improvement we could make to the product?
Please complete the following information:
Name (optional):
Job Title or Function
Organisation
Address
Phone
If we need more information, may we contact you? Yes r No r Thank You
February 2000 for version 1.40 111
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
112 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
CODA-PI User Manual
Fourth
Fold -
tuck
into
flap

CODA-PI User Manual
Manual Feedback
We at Coda value your opinion. Please give us your opinion of this manual, in each of the
following areas. We’ll send you a free mousemat on receipt of your form.
Manual Title
Please complete the following information:
Excellent Good Fair Poor
Accuracy: Is the information correct? r r r r
Completeness: Is information missing? r r r r
Organisation: Is the information easy to find? r r r r
Clarity: Do you understand the information? r r r r
Examples: Are there enough? r r r r
Illustrations: Are there enough? r r r r
Appearance: Do you like the page format? r r r r
Physical Binding: Do you like the cover and binding?
Does the manual meet your need? Why, or why not?
r r r r
What’s the single most important improvement we could make to the manual?
Name (optional):
Job Title or Function
Organisation
Address
Phone
If we need more information, may we contact you? Yes r No r Thank You
February 2000 for version 1.40 113
Glossary &
Conversions

Glossary &
Conversions
Third
Fold
114 February 2000 for version 1.40
Coda Technologies Ltd.
Admiral House
29-30 Maritime Street
EDINBURGH
EH6 6SE
UK
First Fold
Second Fold
Fix
Postage
Stamp
CODA-PI User Manual
Fourth
Fold -
tuck
into
flap

A
add mode 36
Add Tag Node(s) 38
Analysis Control Area,
Application Specific Area 61–63
Analysis Params button 27, 61
Annotate Tag Node(s) 39–43
Application Specific Area
Coda systems 7
the PI100 system 58–63
Applications menu 58
Apply button 9
automatic processing
See also automatic tagging
analysis parameters, setting
27–28, 61–62
automated analysis
pausing 30, 61
starting 28, 61
stopping 30, 61
limitations (and solutions)
29–30
overview 27
parameter settings
loading 28
saving 28
pipe events, editing 29
pipe position, selecting
manually 29, 63
pipeline information,
displaying 29
pipeline survey data,
displaying 28, 62–63
ROTV steering 30
troubleshooting 30
automatic tagging 27
B
Buttons (Fast Tag Setup pop-up),
assigning tags to 51
buttons. See particular buttons
C
Cancel button 9
checklists
for mobilising GeoKit/PI100
83–85
for saving/loading tag files
87
Coda systems
main display 7–8
menu features 8–13
pointer types 13–14
security device iii
conversion table 91–93
corrected nav report mnemonics
79
D
Data Control Area 8
Data Display Area 7
Delete Tag Node(s) 38
Index
deleting
tag files 45, 47
tag nodes 25, 38
tags from fast tag list 52
deselecting tag nodes 25, 37
dual tag, described 36
E
event marking. See interactive
tagging
event, described 23
F
Factory button 9
Fast Tag Area, Application
Specific Area 59–60
fast tag buttons, Application
Specific Area 59
fast tag keys, Application
Specific Area 59
Fast Tag Setup 51–52
fast tag setup
adding tags to list 51
changing fast tag colour 51
customising 31
deleting tags from list 52
loading a previous setup 32,
51
pop-up, described 51
saving the current setup 32,
51
fast tagging
adding tags 59–60
creating tags 24
Filter button 10, 11
forced measures 24
G
General Information Area 7
glossary 95–108
I
Insert/Append Tag Node 39
interactive tagging
See also fast tagging
adding tag nodes 38
annotating tag nodes (see
tags, annotating)
appending tag nodes 39
creating tags 24–25
deleting tag nodes 25, 38
deselecting tag nodes 25, 37
measuring tag nodes 26
moving tag nodes 26, 38–39
overview 24, 35
selecting tag nodes 25, 36–37
K
key shortcuts 19
L
Load button 9
115
Load Remote button 45
loading
analysis parameter settings
28
fast tag setups 32, 51
pop-up settings 9–10
report setups 32, 53
tag files 45
tag setups 31
M
main display, Coda systems 7–8
Make Default button 10
Manage Tag Files
optical disk system 46–47
tape system 43–46
Measure button 42
measurement methods 77–78
Menu Bar 7
menu features 8–13
menus
See also particular menus
detaching from Menu Bar 7
Message Window 12
mobilisation checklists
for GeoKit/PI100 83–84
for the PI100 85
Move Tag Node(s) 38–39
O
OK button 9
on/off switch 8
one-of selection switch 8
on-line checklists
loading tag files 87
saving tag files 87
optical disks, recommended
brand iii
option selection button 8
P
Pause Analysis button 30, 61
PI100
applications 3
starting 19
using, an overview 23
Pipe Data button 28, 62
Pipe Striking Angle/Height
Graphic button 28, 62
placement rules. See forced
measures 23
pointer types 13–14
pop-up action buttons 9–11
pop-up selector 8
Position Information Area,
Application Specific Area 63
printer setup 57
printing, text reports 57–58
Q
quick-start procedure 19
Index

Index
R
Report Generation 56–58
Report Setup 52–56
report setup
adding columns 53–54
adding tag types 56
customising 32
deleting columns 53–54
deleting tag types 56
loading a previous setup 32,
53
multi-node tags 55
report headings 55
report separators 55
reportable items 54, 71–75
saving the current setup 32,
53
setting column parameters 53
sort order 55
text strings 55
Reporting menu 52–58
reports, generating
displaying in text window 57
instructions for 32
printing hardcopy 57
saving to floppy disk 57
Rescan button 46, 47
Reset Pipe Pos button 29, 63
right mouse tag, setting up 50
S
Save button 9
saving
analysis parameter settings
28
fast tag setups 32, 51
pop-up settings 10–11
report setups 32, 53
tag files 43
tag setups 31
scroll bar 12
Scrolling Option List 11
Select Default button 10
Select Factory Default button 10
select mode 36
selecting tag nodes 25, 36–37
settings, pop-up
loading 9–10
resetting to factory default 9
saving 10–11
storing as the default 9
Setup Tags 47–50
shortcuts 19–??
single tag, described 35
Spin Box 11
Spin Boxes 11
Start Analysis button 28, 61
Stop Analysis button 30, 61
Store button 9
switches. See particular switches
systems tags, changing settings
49
Index
T
tab forms 13
tag database. See tag files
tag files
managing, optical system
copying to/from disk 46–
47
database location 46
deleting files 47
rescanning directory 47
selecting files 46
unmounting disks 47
managing, tape system
database location 43
deleting files 45
listing batches 44
loading batches 45
rescanning directory 46
saving batches to tape 44
selecting files 43
tag node measurements,
calculations for 77–78
tag nodes 35
See also tag types, interactive
tagging
tag properties, table of 71–75
tag setup
activating/deactivating tag
types 48
changing system tag settings
49
changing tag name/incident
code 48
customising 31
loading a previous setup 31
pop-up described 47–48
saving the current setup 31
setting up right mouse tag 50
tag types
described 24, 35–36
in fast tag keys 24, 59
symbols of 35
Tagging menu 37–52
tagging modes
add mode 36
select mode 36
tagging. See automatic
processing, interactive tagging,
fast tagging
tags
See also tag types
described 35
replaying 37
tags, annotating
adding comments 42
changing tag name/anomaly
number 40
overview 25
updating tag data 39
116
updating tag dimensions 41
viewing positional data 41
tapes, recommended brands iii
tear-off menus 7
terminology
commonly used terms 14–15
Text Window option, reports 57
Title Bar 7
Tool Bar 12
U
Unknown tag 50, 51
Unmount button 47
Update All Tag Nodes button 39
Update Selected Node button 39
using the PI100, an overview 23