Monta Jux Detect

montaj UX-Detect
UXO Target Analysis Extension for Magnetic,

1VD and EM-61 Data for Oasis montaj v7.2
TUTORIAL and USER GUIDE
www.geosoft.com
The software described in this manual is furnished under license and may only
be used or copied in accordance with the terms of the license.
Manual release date: 8/22/2010.
Written by, Nancy Whitehead. Please send comments or questions to

info@geosoft.com
Copyright © 2010 Geosoft Inc. All rights reserved. Geosoft is a registered

trademark, and Oasis montaj is a registered trademark of Geosoft Inc. Other
brand and product names mentioned herein are properties of their respective
trademark owners. No part of this publication may be reproduced, stored in a
retrieval system or transmitted, in any form, or by any means, electronic,
mechanical, photo-copying, reading, or otherwise, without prior consent from
Geosoft Inc.
The software described in this manual is furnished under license and may only
be used or copied in accordance with the terms of the license. OMx.t.2010.08
Windows, and Windows NT™ are either registered trademarks or trademarks

of Microsoft Corporation.
Geosoft Incorporated
Queens Quay Terminal

207 Queens Quay West
Suite 810, PO Box 131
Toronto, ON Canada
M5J 1A7
Tel: (416) 369-0111
Fax: (416) 369-9599
Web Site: www.geosoft.com
E-mail: info@geosoft.com
Contents
Geosoft Software License Agreement 1
Finding More Help Information 4
Contacting Technical Support 4
montaj UX-Detect Overview and Capabilities 5
Who is this software intended for? 5
montaj UX-Detect Menu and Processing Sequence 6
UX-DataPreparation 6
UX-ParameterDetermination 7
UX-TargetManagement 8
Before you begin 9
Creating a Project 9
Working with the Project Explorer 10

Project Data 10
Project Tools 11
Loading the UX-Detect Menus (First time use) 11
Chapter 1: montaj UX-Detect Tutorials 14
Before you begin 15
Tutorial 1: UX-Data Preparation 15
Import 15
Import Data 15
Editing Header Cells 17
Dump Geonics Instrument to File 18
Data Corrections 19
A p p l yi n g M a g n e t i c B a s e S t a t i o n C o r r e c t i o n s 19
Quality Control on Base Station Data 20
Applying Base Station (Diurnal) Corrections to a
Database 20
Instrument Drift Corrections 24
Apply instrument drift corrections using reference points 27
Apply Instrument drift corrections using control points 29
Path Corrections 30
Warp a Database 30
Sensor Offset Corrections 32
UX Lag Correction 36
Line List Table 37
Offset Correction 38
QC QA Tools 40
Calculate Coverage Map 40
Calculate Coverage Area 43
Progress Reporting 44
View Audit Log 44
Tutorial 2: UX-Parameter Determination 45
1VD Magnetic Data 45

U s i n g t h e S t e p - b y - S t e p A n a l yt i c S i g n a l P r o c e s s 45
Gridding the Vertical Derivative Data 45
Calculating the horizontal derivative grids 47
Smoothing the horizontal derivative grids 48
Calculating and Displaying the Analytical Signal Grid 48
C a l c u l a t e a n d D i s p l a y A n a l yt i c S i g n a l G r i d ( O n e -
Step Process) 50
Target Selection 53
Blakely Test 54
Peakedness 56
Digitize Additional Targets 58
Adding Targets from a Grid 58
Adding Targets from a Profile 61
Create/Reset Mask Channel 63
Target Analysis 65
Combining Magnetic and EM-61 data 65
Calculate Target Sizes 65
C a l c u l a t i n g t h e t a r g e t d e p t h s a n d we i g h t s f r o m
Mag Data 66
Calculating target depths from EM Data 68
Calculating Magnetic Weights from EM Depths 68
Tutorial 3: UX-Target Management 69
Target List Management 69

Window Target List 69
Subset Target List 70
Remove a UXO Target from the Target List 71
Remove Multiple UXO Targets 72
Move a UXO Target 72
Merge UXO Targets 73
Reset Target IDs 76
Create/Reset Mask Channel 77
Target Utilities 77
Resample Grids from Target Locatio ns 77
Target Maps 78
Create Standard Map 78
Plot Targets on Map 83
Display Grid 83
Displaying the Analytic Signal Map as a Shaded Grid 83
Contour 85
Adding Analytic Signal Quick Contours to your Standard
Map 85
Site Plans from AutoCAD DXF Files 86
Create a 3D View 87
Chapter 2: Total Field and EM-61 Data Processing 91
Total Field Data 91
EM-61 Data 91
Appendix 1: Theory 93
The Magnetic Method 93
Understanding the Transient Electromagnetic Method (TEM) 97
References 98
Glossary 99
Index 102
1
Geosoft Software License Agreement

GEOSOFT agrees to supply the Licensed Program(s) as specified in my purchase order. Geosoft shall grant me a non-
transferable, non-exclusive license to use the Licensed Program(s), subject to the Terms and Conditions herein
contained.
Should there be a separate signed agreement between you and Geosoft, or between your company and Geosoft, pertaining
to the licensed use of this software, that agreement shall take precedence over the terms of this agreement.
1. DEFINITIONS:
In this Agreement:
"Licensed Program(s)" means the actual copy of all or any portion of Geosoft’s proprietary software technology, computer
software code, components, dynamic link libraries (DLLs) licensed through the Geosoft license server, including any
modifications, improvements or updates provided by GEOSOFT.
“Effective Date” is the date the Geosoft license is installed. This date is recorded by the Geosoft License server when the
Licensed Program(s) is installed.
"Services" means the Services described on Section 4.
"Termination" means the occurrences contemplated by Section 6 and 7.
2. LICENSE:
GEOSOFT grants to me a non-transferable and non-exclusive license to use the Licensed Program(s) for my own
purposes and solely in executable code format, whereby the Licensed Program(s) are being used only by myself, on one
computer, at any one time.
Title and all intellectual property rights in and to the License Program(s), including, without limitation, copyright, trade
secrets and trademarks, shall remain with GEOSOFT and its licensor(s). I agree to refrain from raising any objection or
challenge to such intellectual property rights, or from assisting or causing or permitting other(s) to do so, during the term
of the Agreement and thereafter
I may not assign this Agreement or any part thereof or sub-license the rights granted herein, or lend, rent, time-share, sell
or lease the software without the prior written consent of GEOSOFT.
I may not attempt to reverse engineer, de-compile or disassemble the software.
I may not copy the Licensed Programs other than for a single archival copy and reasonable number of backup copies.
I may not use the Licensed Program(s) for commercial network services or interactive cable or remote processing
services.
I may not make any attempt to circumvent the License Manager that controls the access to the software use.
I may not remove or obscure any copyright, trademark, or legend or notice.
3. TERM:
The Term of this Agreement shall commence on the Effective Date and shall continue until termination, as described in
Section 6.
4. SERVICES:
(i) According to the terms of my initial purchase, GEOSOFT shall make available to me, without additional fees such
corrections and improvements to the Licensed Program(s) as may be generally incorporated into the Licensed
Program(s) by GEOSOFT. (Normally this will be for a period of twelve (12) months).
(ii) GEOSOFT has a strong commitment to customer service and product support. GEOSOFT offers me, subject to
applicable Service Charge(s), continuing support in the form of email or telephone advice and other assistance in
problem diagnosis and the correction of errors or faults in the Licensed Program(s) during the life of this License. When
a problem occurs which appears to be related to errors or faults in the Licensed Program(s), I may contact GEOSOFT
and GEOSOFT will make an honest effort to solve the problem. However, GEOSOFT cannot guarantee service results
or represent or warrant that all errors or program defects will be corrected. Also it is to be noted that each Licensed
Program is designed to operate on a Windows XP (32 bit) or Windows Vista Business (32 or 64 bit), Windows 7 (32 or 64
bit) platform.
(iii) Further, if I request service relating to the modification of the Licensed Program(s) to meet a particular need or to
conform with a particular operating environment, GEOSOFT may, at its discretion, modify the Licensed Program(s) to
meet these particular needs, subject to applicable Services Charge(s). However, all intellectual property or other rights
which may arise from such modifications shall reside with GEOSOFT.
2
5. PROTECTION AND SECURITY OF LICENSED PROGRAM

I agree that all additions, modifications, revisions, updates and extensions to the Licensed Program(s) shall be subject to
all of the terms and conditions in this agreement.
I acknowledge that all copies of the Licensed Program(s), provided by GEOSOFT or made by me pursuant to this
Agreement, including, without limitation, translations, compilations, partial copies, modifications, derivative materials
and/or updated materials, are proprietary, and the property of GEOSOFTor its licensor'(s), and may not be distributed to
any other persons, without GEOSOFT’s , or its licensor(s) prior written consent.
I will not provide or otherwise make the Licensed Program(s) available to anyone in any form without GEOSOFT's prior
written consent.
6. TERMINATION:
This agreement shall terminate upon the termination date, if any, specified in your purchase agreement with Geosoft.
This agreement may be terminated only upon thirty-days prior written notice to GEOSOFT.
GEOSOFT may terminate this Agreement upon prior written notice effective immediately if I fail to comply with any of the
terms and conditions of this Agreement.
This Agreement shall terminate automatically upon the institution, or consenting to the institution of proceedings in
insolvency or bankruptcy, or upon a trustee in bankruptcy or receiver being appointed for me/us for all or a substantial
portion of my/our assets.
7. EVENTS UPON TERMINATION:
I shall forthwith discontinue use of the Licensed Program(s), on the day Termination shall occur and agree not to resume
such use in the future without written authorization from GEOSOFT.
I shall uninstall and remove all software from my computer. Within thirty days after Termination, I shall destroy all
physical and digital copies of the Licensed Program(s) and certify such destruction in writing to Geosoft within 10 days
thereof.. This obligation relates, without limitation, to all copies in any form, including translations, compilations,
derivatives and updated materials, whether partial or complete, and whether or not modified or merged into other
materials as authorized herein.
8. WARRANTY:
GEOSOFT, nor its licensor(s), does not warrant that the functions contained in the Licensed Program will meet my
requirements or will operate in the combinations which may be selected for use by me, or that the operation of the
Licensed Program will be uninterrupted or error free or that all program defects will be corrected.
Each Licensed Program shall be furnished to me in accordance with the terms of this Agreement. No warranties either
express or implied are made to me regarding the Licensed Program.
THE FOREGOING WARRANTIES ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.
9. LIMITATION OF REMEDIES
I agree to accept responsibility for the use of the programs to achieve my intended results, and for the results obtained
from use of said Program(s). I therefore accept complete responsibility for any decision made based on my use of the
aforementioned Licensed Program(s).
In no event shall GEOSOFT, or its licensor(s) be liable for any damages, or loss of any kind, whether special direct,
indirect, incidental or consequential, arising from use of, or performance or non-performance of the Licensed Program(s),
including but not limited to any lost profits, lost savings or other consequential damages, or liability for use of the
Licensed Program in a high-risk activity. Even if GEOSOFT or its licensor (s0 has been advised of the possibility of such
damages, or for any claim against me by any other party.
10. GENERAL:
I agree that this Agreement is a complete and exclusive statement of the agreement with GEOSOFT.
This Agreement supersedes all previous Agreements with respect to the Licensed Programs, with the exception of a
current signed Technical Service Agreements.
GEOSOFT is not responsible for failure to fulfill its obligations under the Agreement due to causes beyond its control.
Should any part of This Agreement for any reason be declared invalid, such declaration shall not affect the remaining
portion which shall remain in full force and effect as if this Agreement had been executed without the invalid portion
thereof.
The relationship between the parties is that of independent contractors. Nothing contained in this Agreement shall be
deemed to constitute or create a partnership, association, joint venture or agency.
3
The provision of this Agreement shall be binding upon me and GEOSOFT and my respective successors and permitted
assigns.
This Agreement will be governed by the laws of the Province of Ontario and applicable laws of Canada.
RD
11. ACCESSING DATA ON 3 PARTY SITES
Licensee shall not use the software to transfer or exchange any material where such transfer or exchange is prohibited
by intellectual property laws or other applicable laws. Geosoft neither endorses nor assumes any responsibility for the
safety, accuracy or availability of data sites or the information contained on them. Data sites, their operation and content
are the responsibility of the person or entity for which they were created or maintained (the “Owner”). Both your use of a
data site, and your right to use or reproduce information or materials from a linked site, are subject to the terms of use
governing that particular data site. Any comments or inquiries regarding a data site must be directed to its Owner.
12. YEAR 2000:
The Licensed Programs have been tested to conform to DISC PD2000 1:1998 Year 2000 Conformity Requirements
(www.bsi.org.uk/disc/year2000/2000.html), with the exception of clause 3.3.2, paragraph b. Section 3.3.2 paragraph b)
requires that inferences for two-digit year dates greater than or equal to 50 imply 19xx, and those with a value equal to or
less than 50 imply 20xx. The Licensed Programs will recognize all two digit years as 19xx. This is to prevent errors
importing historical data that pre-dates 1950. All dates that follow 1999 must use four digit dates in the Licensed
Programs.
4
Finding More Help Information

There are several other functions included in the basic Oasis montaj help system that
may be useful to your work. The entire documentation for the system is available
through the online help system. This electronic library of information enables us to
constantly update the information and provide you with the most up-to-date information
available.
The best way to find information in this system is to use the Search tab to perform a
full-text search of all help topics. If you still can‟t find the information you‟re looking
for, the Online Books help system contains complete Geosoft manuals and tutorials in
Adobe PDF format.
Contacting Technical Support
The list below provides contact information for Geosoft Technical Support around the
world.
North America Europe and North Africa

Geosoft Inc., Geosoft Europe Ltd.
Queens Quay Terminal 20/21 Market Place, First Floor
207 Queens Quay West Wallingford, Oxfordshire
Suite 810, PO Box 131 United Kingdom
Toronto, ON Canada OX10 OAD
M5J 1A7
Tel: +44 1491 835 231
Tel +1 (416) 369-0111 Fax: +44 1491 835 281
Fax +1 (416) 369-9599
Email: tech.eu@geosoft.com
Email: tech@geosoft.com
South America Australia and Southeast Asia
Geosoft Latinoamerica Ltda. Geosoft Australia Pty. Ltd
Praça Floriano 51 / 19º Andar Unit 14, 100 Railway Road,
CEP: 20031-050, Centro Subiaco WA 6008
Rio de Janeiro, RJ, Brasil Australia
Tel: (55-21) 2111-8150 Tel +61 (8) 9382 1900
Fax: (55-21) 2111-8181 Fax +61 (8) 9382 1911
Email: tech.sa@geosoft.com Email: tech.au@geosoft.com
South and Central Africa
Geosoft Africa Ltd.
Buren Building, Second Floor
Kasteelpark Office Park
c/o Nossob & Jochemus Streets
Erasmuskloof X3, Pretoria
Tel: +27 12 347 4519
Fax: +27 12 347 6936
Email: tech.za@geosoft.com
montaj UX-Detect Overview and Capabilities

The montaj UX-Detect system is designed for use with Oasis montaj to analyze
Geonics EM-61 and EM61-MK2 data, magnetic vertical gradient (1VD) data, and/or
total field magnetic data to yield quantitative and qualitative information on UXO and
other buried manmade targets.
Target selection is an automated process that locates peaks in the Analytic Signal
(magnetic data) and peaks in the EM-61 and EM61-MK2 data. EM-61 and EM61-MK2
target depths are calculated from the ratio of the top and bottom coils. Magnetic data
source depths are calculated by solving Euler's equation for a window centred on the
Analytic Signal peak. Together, these approaches provide you with very effective yet
simple methods of determining plan location, apparent depth and weight (magnetics
only) of UXO targets and other buried metal objects.
The UX-Detect system, which is accessed through a series of menus for importing,
verifying, analyzing, visualizing and presenting UXO survey data, has been updated
with a restructured menu system for an improved workflow. The updated menus
combine the UX-Detect and DoD UX-Process (previously named USACE DoD QA/QC)
systems enabling them to be fully integrated providing a logical and consistent
workflow. The updated system includes three main menus and is a run from within the
Oasis montaj core software platform. For more information on UX-Process and other
government sponsored UXO software, visit:
www.geosoft.com/pinfo/oasismontaj/extensions/ux-process.asp
Who is this software intended for?

In order to get started quickly, you must be familiar with Oasis montaj (including its
basic operation, components such as the Oasis database, and data management
procedures). If you are not already familiar with these topics, we strongly recommend
examining the Oasis montaj – Quick Start Tutorials (Help/Manuals and Tutorials).
Please note that it is imperative that expert geophysical interpreters carry out proper
analysis of the magnetic, EM-61, and EM61-MK2 data. The data must also be
processed prior to analysis, to enhance the components of the data that are of interest and
to minimize the effects of noise and any other problems that affect data quality. Note
also that the method of data presentation can significantly change the appreciation of the
data.
6 montaj UX-Detect Overview and Capabilities
montaj UX-Detect Menu and Processing Sequence

The montaj UX-Detect menu system has been restructured to provide improved
workflow to lead you through the main processing, analysis and presentation functions
you can perform with the system . The montaj UX-Detect menu system (shown below)
is divided into three main menus:
UX-DataPreparation UX-ParameterDetermination UX-TargetManagement
UX-DataPreparation
1. 1.) Import This menu opens a sub-menu containing the following import options:
 Import Data
 Dump Geonics Instrument to File
2.) Data Corrections This menu opens a sub-menu containing the following data
correction options:
 Base Station Correction
 Instrument Drift Correction
3.) Path Corrections This menu opens a sub-menu containing the following path
correction options:
 Warp a Database
 Sensor Offset Correction
 UX Lag Correction
 Line List Table
 Offset Correction
4.) QC QA Tools This menu opens a sub-menu containing the following quality control
and quality assurance tools:
 Calculate Coverage Map
 Calculate Coverage Area
5.) Progress Reporting This menu displays the View Audit Log menu option:
 View Audit Log
UX-ParameterDetermination
1.) Total Field Magnetic Data This menu opens a sub-menu containing the options for
calculating and displaying an analytic signal grid for total field magnetic data:
 Calculate and Display Analytic Signal Grid
 Step-By-Step Analytic Signal
 Grid Magnetic Data
 CalculateDerivative Grids
 Smooth Derivative Grids
2.) 1VD Magnetic Data This menu opens a sub-menu containing the options for
calculating and displaying an analytic signal grid for the first vertical derivative
magnetic data:
 Calculate and display analytic signal grid
 Step-By-Step Analytic Signal
 Grid 1VD Data
 Calculate Horizontal Derivative Grids
 Smooth Horizontal Derivative Grids
3.) EM Data This menu opens a sub-menu containing the options for calculating and
displaying an analytic signal grid for EM data:
 Grid Multiple Channels
4.) Target Selection This menu opens a sub-menu containing the options for selecting
targets:
 Blakely Test
 Peakedness
 Digitise Additional Targets
 Create/Reset Mask Channel
5.) Target Analysis This menu opens a sub-menu containing the options for target
analysis:
 Calculate Target Sizes
 Calculate Target Depths and Weights
from Mag Data
 Calculate Target Depths from EM Data
 Calculate Magnetic Weights from EM
Depths
8 montaj UX-Detect Overview and Capabilities
UX-TargetManagement
1.) Target List Management This menu opens a sub-menu that contains target list
management options:
 Window Target List
 Subset Target List
 Remove UXO Target(s) From Target List
 Remove Multiple UXO Targets
 Move UXO Target
 Merge UXO Targets
 Reset Target IDs
2.) Target Utilities This menu opens a sub-menu that contains the following target
utility options:
 Resample Grids from Target Locations
3.) Target Maps This menu opens a sub-menu containing the options for creating target
maps:
 Create Standard Map
 Plot Targets on Map
 Display Grid
 Contour
 Site Plan from AutoCAD DXF File
 Create a 3D View
Before you begin 9
Before you begin

This section describes how to begin working with the montaj UX-Detect system in
Oasis montaj. Topics discussed in this chapter include:
 Creating a project (page 9)
 Working with the Project Explorer (page 10)
 Loading the montaj UX-Detect menu (page 11)
Creating a Project
To work in montaj UX-Detect requires an open Project. An Oasis montaj "Project"
encompasses every item in your working project; from the data files in your project
(databases, maps, and grids), to the tools used, to the project setup including the menus
you have displayed and whether you are working on a map or profile and the state in
which you left it the last time you used it.
The project also controls your working directory. Projects are saved as (*.gpf) files. If
you open an existing project from a directory, the system assumes that all your project
files are located in the same directory. To streamline your work, as well as keep it
organized, you may wish to make sure that your project file is in the same directory as
the other files you want to use. We recommend that each project you work on have its
own project (*.gpf) file. If you use a number of applications or add-on tools in Oasis
montaj that have different menus, you can use the project to display only the menus you
require.
The Project Explorer tool enables you to browse as well as open any project item. The
Project Explorer has two tab windows, the Data window that includes all data files
included in the project and the Tools window that organizes and maintains the project
tools.
T O C REATE A P ROJECT :
2. Start Oasis montaj.

3. On the File menu select Project and then select New. The New Project dialog is
displayed.
4. Specify a name and directory for the project. For example name the project
Tutorial and specify the working directory as D:\UXODemo.
Note: Oasis montaj assumes that your data is in the directory containing this project.
10 Before you begin
5. Click the [Save] button. The system saves the project and indicates it is open by
opening the Project Explorer window, enabling the buttons on the Main toolbar
and adding menus to the menu bar. These are visual clues indicating that you are
ready to start working with the system.
Working with the Project Explorer
The Project Explorer tool enables you to browse as well as open any project item. The
project file (*.gpf) is used to keep track of all files and information related to a working
project.
The Project Explorer has two windows, the “Data” window that includes all data files
included in the project and the “Tools” window that organizes and maintains the project
tools. To access the “Tools” window click the [Tools] bar on the bottom of the Project
Explorer window. To return to the “Data” window, click the [Data] bar on the top the
Project Explorer.
P ROJECT D ATA
The Project Data includes all Databases ( ), Grids ( ), Maps ( ), Voxels ( ) and
ArcGIS MXDs ( ) opened or created in the current project. The Project Explorer
Before you begin 11
provides “Data Tools” that enable you to keep track of project information, including the
new data description tool that enables users to add descriptive text to project items,
which are then displayed with the Data properties. Enhanced metadata capabilities
provide access to the "Properties" of all data items displayed in the Project Explorer
using the Metadata Browser.
For more information on the Project Explorer‟s Data Tools, see the online help topic
“Project Data”. Use the Search tab in the Online Help (Help|Help Topics) to quickly
locate the help topic.
P ROJECT T OOLS
The Project Tools provide quick and easy access to all the tools available for working
with your data. There are three types, Tools, Auxiliary Tools and Toolbars.
 Tools; Project Explorer, Undo/Redo Tool, View/Group Manager Tool
 Auxiliary Tools: Histograms, Scatter plots, Probability plots and Triplots
 Toolbars; Database Tools Bar, Map Group Editing Bar, Map Layout Bar,
Map Template Tools Bar, Map Tools Bar, Polygon Edit Bar, Script Bar,
Standard Bar
The Project Explorer enables you to show/hide the tools as needed, enabling you to keep
your Project as streamlined as possible.
For more information on the Project Explorer‟s Tools, see the online help topic “Project
Tools” using the Search tab in the online help system (Help|Help Topics).
Loading the UX-Detect Menus (First time use)
Before you can start working with the montaj UX-Detect system for the first time, there
are some setting changes you can make to the menus to ensure that the UX-Detect
menus are displayed automatically each time you start Oasis montaj.
First, you must clear any existing menus and then set montaj UX-Detect as the default
menu. You then have to load the menu manually (you only have to manually load the
menu the first time you use the system).
T O C LEAR E XISTING M ENUS
1. From the GX menu select Remove all Menus to remove any existing menus.
T O S ET UX-D ETECT AS Y OUR D EFAULT M ENU (F IRST T IME O NLY )
1. On the Edit menu, select Settings and then select General. The Default settings
dialog is displayed.
12 Before you begin
2. In the Default menus box, click the Browse ( ) button to select the UX-
Detect.omn file, and click the [Open] button to return to the Default settings
dialog.
Note: To select multiple menus, hold the [Ctrl] key as you select (highlight) the menu
files. The system saves the setting and in future will automatically load the
UX-Detect (and any additional) menus.
3. Click the [Next >] button to display the More settings dialog and then click the
[Next >] button again to display the Internet Settings dialog.
4. Click the [Finish] button to save the settings.
5. For more information on Oasis montaj setting, click the Help ( ) button on the
Default settings dialogs.
T O L OAD THE UX-D ETECT M ENU M ANUALLY (F IRST U SE )
Since the system is already running, the default is not yet active and you must load the
UX-Detect menu manually.
1. On the GX menu, select Load Menu. The Load menu dialog will be displayed.
2. Select UX-Detect.omn from the list of files and click the [Open] button. The
system displays the UX-Detect menus (UX-DataPreparation, UX-
ParameterDetermination and UX-TargetManagement) on your menu bar.
Note: If you want to modify your default menus again at a later time, you can use the
Default settings dialog box to change your settings. If you are really interested
in system configurations and want to see all of the system settings you can
open the Advanced Settings (Edit|Settings|Advanced) in the Metadata
Browser.
Before you begin 13
After completing these steps, you are now ready to start using the montaj UX-Detect
system. If you require more details about Oasis montaj capabilities, please refer to the
Oasis montaj Quick Start Tutorial or the Online Help (Help|Help Topics). .
14 Chapter 1: montaj UX-Detect Tutorials
Chapter 1: montaj UX-Detect Tutorials

To help you learn how to use the montaj UX-Detect UXO Target Analysis System for
Magnetic, 1VD and EM Data, we provide the following tutorials:
Tutorial 1: Data Preparation (page 15)

 Import (page15)
 Data Corrections (page 19)
 Path Corrections (page 30)
 QC/QA Tools (page 40)
 Progress Reporting (page 44)
Tutorial 2: Parameter Determination (page 45)
 Create Analytic Signal Grid (page 45)
 Target Selection (page 53)
 Target Analysis (page 65)
Tutorial 3: Target Management (page 69)
 Target List Management (page 69)
 Target Utilities (page 77)
 Create Standard Target Maps (page 78)
These tutorials demonstrates how to import data and then guides you through a typical
data workflow for magnetic data, starting from a database of levelled vertical gradient
data and finishing with a list of potential UXO targets, with calculated location, apparent
depth and apparent weight information.
The dataset “UX-Detect_tut.xyz” that accompanies this tutorial has been provided by
Barthel & Schriber GmbH, Cologne, Germany. It forms part of a much larger dataset
collected within Germany to detect Unexploded Ordnance buried in the sediments of the
Rhine River. The data was collected using a towed array of gradiometers and has been
pre-processed to remove levelling problems caused by calibration errors. This dataset
has a nominal sample interval along line of 10 cm and with a nominal line spacing of 70
cm. The location information (X and Y columns) are in UTM coordinates while the Z
column represents the corrected vertical gradient of the local magnetic field (dz) and has
units of nT|m.
To help demonstrate some of the data and path corrections as well as EM processing and
other options that the “UX-Detect_tut.xyz” dataset is inappropriate for, we will use a
variety of public domain datasets.
Before you begin
This tutorial uses sample data provided with the installation of Oasis montaj and can be
located in the (C:\Program Files\Geosoft\Oasis montaj\data\uxo) directory. The UX-
Detect tutorial and data files can also be downloaded from the Geosoft website
(www.geosoft.com/resources/tutorials/). Before you begin, copy this tutorial data to your
working directory (for example, D:\UXODemo).
Tutorial 1: UX-Data Preparation

The UX-Data Preparation menu provides options for importing data, data corrections,
path corrections, QC/QA tools and progress reporting.
Note that, the XYZ file we will import (UX-Detect_tut.xyz) in this tutorial has been
pre-processed; removing levelling problems caused by calibration errors. Therefore, to
demonstrate some of the correction options we will use the database file
(uxo_mag.gdb).
Import
The UX-Detect system enables you to import a number of different potential field data
types into an Oasis montaj database and manipulate or view the data in the Spreadsheet
window.
I MPORT D ATA
Before we can process the UXO data, we import the data into a database. For this
tutorial, we will import the XYZ file (ux-detect_tut.xyz). The Geosoft XYZ Import
enables you to create an XYZ import template, or use a pre-existing template, to import
XYZ data into a database. Note that, if the import file does not contain line breaks, the
data will be placed in a single random line (type 'D').
T O I MPORT AN XYZ F ILE :
1. On the UX-DataPreparation menu, select Import|Import Data. The Import survey

data dialog is displayed.
2. Specify the name of the Database file you want to import your XYZ data into as
(Mag Data). (The database extension .GDB will be added to this file.)
3. Using the Import Data Type dropdown list, select (XYZ (mag or EM)) and then
using the Browse ( ) button locate the Data file (ux-detect_tut.xyz) in your
project directory (e.g. D:\UXODemo).
Tip: The dropdown lists ( ) enable you to select files that have previously been
open in your project. If a file has not been opened, you can use the Browse
( ) button to locate the file from anywhere on your computer or network
drives. This assists in ensuring the selection of the proper files from the
correct directory are chosen.
4. Select (No) for the Add Projection to Database? parameter and then, leaving the
remaining parameters to the default values, click the [OK] button. If the database
file you are importing into does not already exist, the Create New Database
dialog will be displayed.
5. The New database name (Mag Data.gdb) is automatically copied from the
previous dialog‟s Database file parameter.
6. Using this dialog you can specify the Maximum lines/groups and Maximum
channels/fields. The defaults are 200 and 50, which is fine for the purposes of this
tutorial, but generally we recommend that you specify a number that is
representative of the final estimated project size. This strategy ensures that you
have enough space available in your project while not consuming excessive
storage space. The size can be changed later via the Maintenance|Grow menu
option from the Data menu, should your project expand in scope.
7. Using the Compression dropdown list, select Compress for SPEED and click the
[OK] button. The system imports the data into the database (Mag Data.gdb).
Editing Header Cells

Editing the Header cell channel names (X_m_, Y_m_ and dz_nT_m_) can be easily
done using the Edit menu on the database popup menu.
T O E DIT THE C HANNEL H EADER C ELLS :
1. Select (highlight) the X_m_ header cell. Right-click and from the popup menu,
select Edit. The Edit Channel dialog is displayed.
2. In the Name box change (X_m_) to (X) and click the [OK] button.
3. Repeat this for the Y_m_ channel, changing the Name to (Y) and for the
dz_nT_m channel, changing the Name to (dz).
Note: If any of your channels appear as a series of two asterisks, then the channel is
not wide enough to display the values. To widen the channel, move your
curser over the right side of the channel, the curser will change to two arrows.
While holding down the right mouse button, stretch the channel to the right.
4. You will notice that markers have been added to the coordinate channels header
cells to indicate that these channels are currently defined to be the "current" X and
Y channels. The markers are little rectangles on the right side of the header cell,
and contain "x" and "y" in reversed display. These labels identify the primary
coordinate channels.
D UMP G EONICS I NSTRUMENT TO F ILE
Use the menu option UX-DataPreparation|Import|IDownload data from Geonics

Instrument to download data from Geonics EM31, EM38 or EM61 instrument to your
PC.
From the dropdown list, select the Instrument type, then using the Browse button ( )
specify the Name of the file on the instrument. Then, select the Port that you are
connected through. Note that, it is recommended that the instrument be turned on first
and ready to dump data, before this dialog is run.
Data Corrections
There are two Data Correction options available Base Station Correction and
Instrument Drift Correction and depending on your data you may need to perform one or
both of these corrections to your data.
Note: The Heading Correction option is available in the UX-Process software

package. For information on UX-Process and other Government Sponsored
UXO Software, visit: www.geosoft.com/pinfo/oasismontaj/extensions/ux-
process.asp.
Many types of geophysical data contain a time-varying error fundamental to the type of
data being measured. A variety of factors can cause errors including diurnal variations of
the earth's magnetic field and instrument variations. UX-Detect include tools for
removing base station and instrument drift errors from your data.
Before you apply corrections or process your data, we recommend importing the
downloaded base station data into an Oasis montaj database and evaluating it on a line-
by-line basis. The objective is to examine the data in spreadsheet and profile views, and
correct any noise or extreme values prior to applying the actual base station corrections
to survey data.
Note: Because the data we imported in the earlier step has been pre-processed,
removing the levelling problems caused by diurnal and instrument errors,
some of these options will not apply and we will use other database files for
these corrections.
A PPLYING M AGNETIC B ASE S TATION C ORRECTIONS
The magnetometers used in geophysical surveys measure minute variations in the

Earth‟s magnetic field. This field intensity has two distinct components, the one of
interest to us is caused by subsurface physical variations, the other component that has to
be eliminated prior to further processing is time varying. The time varying field has
cycles from a few seconds to days. The Earth‟s rotation causes a long-period, slow
varying field known as the diurnal effect. The diurnal variation depends on the latitude
and can be as much as 60nT. There are also random but severe magnetic disturbances or
magnetic storms of the order of several 100 nT that are caused by events such as solar
winds and solar flares. The magnetic base station correction option is used to remove the
smooth diurnal variations of the Earth‟s magnetic field. Due to the irregular nature and
strong variations of magnetic storms, it is highly recommended NOT to survey during
such events. The signature of a UXO object could easily reside within the noise of a
magnetic storm. The magnetic storms are monitored and published by governmental
agencies in real time, they are also recorded by the instrument (i.e. flag GSC= “active”).
If a survey must be carried out during a storm because of other dependencies, the rate of
data collection of the base station magnetometer should be increased.
A typical magnetic survey will include placing a digital recording base station
magnetometer at the site and constantly measure the magnetic field during the course of
the survey, normally at a rate of 10 to 600 readings per minute, depending on the
specifications of the survey. The base station site should be located away from any
natural or man-made magnetic sources, and should be tested to insure that the
background magnetic field is relatively constant over a distance of 10 meters or more.
To correct this error, base station values representing diurnal variation are subtracted
from the survey instrument data. Base station corrections are recommended for any total
field magnetic survey where base stations are used. Base station corrections are not
required for magnetic gradient surveys.
Quality Control on Base Station Data

As mentioned in the previous section, we recommend importing the base station data
into an Oasis montaj database and evaluating it on a line-by-line basis. The objective is
to examine the data in spreadsheet and profile views, and evaluate for the presence of
drop-outs, spikes, magnetic storms, and/or any other features that will degrade the
quality of the data.
If you detect extreme values (i.e. spikes) in line data, for instance, you may want to
remove these using a non-linear filter. Alternately, you may find high-frequency
instrument chatter that is most effectively removed using a low-pass filter.
When you are satisfied that the base station data is acceptable, a base station (diurnal
drift) correction may be applied to the field magnetometer data.
Applying Base Station (Diurnal) Corrections to a Database

Diurnal corrections are applied to survey data contained in an Oasis montaj database.
The system uses the date and the time of each line in the database to find the appropriate
diurnal correction from the corresponding line in the base station table. By default, the
system protects your original data by copying the corrected base station data into a new
channel.
For this option we will use the database file (uxo_mag.gdb) that is also included with
the tutorial data.
T O A PPLY B ASE S TATION (D IURNAL ) C ORRECTIONS TO A D ATABASE :
1. Using the Data|Open Database option, open and select (highlight) the database to
process (uxo_mag.gdb).
2. On the UX-DataPreparation menu, select Data Corrections|Base Station

Corrections. The Mag base correction dialog is displayed.
3. On the Survey database tab, the name and location of the current project Input
database is displayed (uxo_mag.gdb).
4. We will leave the Date Channel to the default (today‟s date), as our data does not
contain this information.
5. Using the Time channel dropdown list, select (time). Then, in the Input
channel(s) window select (highlight) the magnetic sensor channels (bottom, top,
VertGrad).
6. The Output channel(s) names will automatically be provided as (bottom_bas,
top_bas, VertGrad_bas).
7. The correction process generates an intermediate database of the base station data.
You are offered the option to Save Interim Base Station Data. By default it lives
only through the duration of the process. This database will have the base name of
the base station data and the extension GDB for this tutorial we will not select ( )
this option.
8. Select the Basemag file tab.
9. Using the [Browse] button, select the ASCII Base station file (Basestation.XYZ)
that has been included with the tutorial data.
10. The Select label line window displays the base station file, enabling you to select
(highlight) the label line that contains the channel names (//time mag).
Note: If there are no headings for the fields in the base station correction file, then the
first row of „values‟ for the fields in the base station file are displayed, and
can be used as a guide.
11. Using the Magbase field dropdown list, select the field name of the magnetic data
in the base station file as (mag) and using the Time field dropdown list, select the
time field as (time).
12. As the base station data does not include a Date field, we will leave this and the
Date format parameters blank.
13. Specify the Base station tolerance as (1.00). The purpose of the tolerance field is
to enable on-the-fly filtering of potential noise in the base station data. Base
station data varies gently with time, and any abrupt variations are attributed to
noise.
14. Select ( ) the Despike Base Station Data option to apply a non-linear filter to the
data and then click the [OK] button. If the base station data exceeds the tolerance
specified, a warning message is displayed.
Note: The base station data that represents the greatest deviation from the specified
tolerance is displayed and highlighted in the database profile window (as
shown above). The base station data is displayed at the survey frequency, and
the correction (if you decide to proceed with it) is performed on the original
base station data, prior to interpolating it to the increment of the survey data.
15. Click the [OK] button to proceed with the corrections. You will be prompted to
de-spike the base station data by applying a non-linear filter.
16. Click the [Yes] button to de-spike/de-step the base station data. You will again be
prompted and asked if you want to walk through the de-spiking/de-stepping
process?
Note: If you click [Yes] the system will walk you through each spike/step that exceeds
the tolerance however, if you click [No] the de-spiking/de-stepping will be
done in one step.
17. Click the [Yes] button and the dialog is displayed asking, “Would you like to de-
spike/de-step at Fid 2565?”
18. Click the [Yes] button and you will be prompted with the next spike/step in the
data. Continue selecting [Yes] until all of the spikes that exceed the tolerance are
corrected.
19. The data is corrected and displayed in the database and the profile window as
shown below (Note that depending on your computer, this may take a few
minutes.)
I NSTRUMENT D RIFT C ORRECTIONS
Instrument Drift is a gradual change in a reference reading that should remain constant.
During measurement, the base or "no-signal" value recorded on an instrument can drift
up or down. A drift correction is designed to remove this drift, on a line-by-line basis
based on the time-based variations.
Without any known controls, the default setting for the drift correction is calculated to
be a non-linear long wavelength signal with a wavelength of 100 seconds, and a
tolerance equal to 1% of the standard deviation of the data. These parameters can be
altered if the result is not satisfactory, by selecting the [Advanced] option of the Apply
instrument drift calculations dialog. If spatial overlapping data is available the
difference at the overlap points can control the long wavelength drift calculation.
This procedure requires the EM database file (em61Data.gdb) that is provided with this
tutorial.
T O A PPLY I NSTRUMENT D RIFT C ORRECTIONS :
1. Open and select the database file (em61Data.gdb) from your current project
directory.
2. On the UX-DataPreparation menu, select Data Corrections|Instrument Drift
Correction. The Instrument drift correction dialog is displayed.
3. Using the Time channel dropdown list, select (TIME), and from the Input data
channel dropdown list, select (M1). In the Output data channel dropdown list
specify a new channel (M1_DriftCorr).
4. The Reference/Tie Line Data Channel will not be used in this exercise. We will
accept the default and leave the field blank.
5. Using the %of lowest values to ignore dropdown list, select (5) and from the %of
highest values to ignore list, select (5).
6. Select the Drift correction method as (Non-linear filtering). From the Despike?
dropdown list, select (No). Click the [OK] button and the Non-linear filter
parameters dialog is displayed.
Note: The drift correction methods available are, Non-linear filtering, Zero, First and
Second order trend removal, Median filtering and All five above methods.
7. You can accept the default values and click the [OK] button to apply the
instrument drift.
8. You can display the input channel (M1) as well as the drift corrected channel
(M1_DriftCorr) for inspection. To display data channels in the profile window,
select the channel header of the channel(s) to display, click the right mouse button
and from the popup menu, select Show profile.
Note: If the drift as calculated is not satisfactory you can run the Apply instrument
drift correction again and modify the parameters for the drift correction
method selected. The “Non-linear filter” parameters are wavelength and drift
tolerance. The wavelength of the non-linear filter defaults to 100 units.
Depending on the signal this drift may not be a good representation of the
drift. The drift is a long wavelength smooth signal. 1% of the standard
deviation of the observed data must adequately generate a smooth drift signal.
If however you observe a visible chatter in the calculated drift, decrease this
parameter.
Apply instrument drift corrections using reference points

The user may layout the survey as to derive a relative knowledge of the drift from the
survey itself. This approach consists of running a number of tie lines that intersect the
transects. At the intersections one will have the amplitude of both the transect and the tie
line. These points are reference points that can be used to control the calculated long
wavelength drift. The frequency of these points depends on the survey design and the
character of the drift. Prior to performing the drift correction, the user should generate a
new channel in the transect database by clicking the [CreateRefCh] button. This
channel will be populated with dummies except at the intersection points, where the
amplitude of the tie lines is saved. The drift correction option then should be supplied
with the name of this reference point channel in order to ensure that the calculated drift
honours the actual drift at the specified intersection points.
Note: The database provided for the Instrument Drift Corrections (em61data.gdb)
does not include X, Y channels, therefore can not be used to create a reference
channel. However, the channel referencepoint is supplied to use for the
following procedure.
T O A PPLY I NSTRUMENT D RIFT C ORRECTIONS USING REFERENCE POINTS :
1. Use the same database (em61data.gdb).

2. On the UX-DataPreparation menu, select Data Corrections|Instrument Drift
Correction. The Apply instrument drift corrections dialog is displayed.
3. In the output data channel specify (M1_drift_ref) and this time for the Reference
data channel, select (referencepoint). This channel contains a second reading at
a given special point.
Note: If X, Y data for both transects and tie lines exist, you can click the
[CreateRefCh] button to populate a reference channel with the difference at
each cross over point.
4. Select the Drift correction method as (All five above methods) and whether to
Despike? as (No).
5. Click the [OK] button and the Non-Linear filter parameters dialog is displayed.
We will accept the default values (100 and 0.0589) and click [OK]. The Median
filter parameters dialog is displayed.
6. Specify the Rolling window width (sec) as (2) and click the [OK] button to apply
the instrument drift corrections.
7. All 5 filtered channels will be generated and each one will have an appropriate
extension identifying the method that has been applied (e.g. Non-linear filtering -
M1_drift_ref_nl, Zero order trend removal - M1_drift_ref_0tr, First order trend
removal - M1_drift_ref_1tr, Second order trend removal - M1_drift_ref_2tr,
and Median filtering - M1_drift_ref_md).
Note: This time in addition to the long wavelength drift removal, the drift has been
forced to honour the difference at each cross point.
Apply Instrument drift corrections using control points

As displayed in the image below, EM data occasionally suffers from discontinuity.
Furthermore the discontinuity may span over few readings, through which the data may
be noisy. The collection of these symptoms makes it difficult to automatically locate the
start and end of the discontinuity. This is where the user intervention is required. The
user will display the profile and identify the start and end of each discontinuity. This
information is saved in a channel named "ControlPoints". If the drift correction GX finds
a channel by this name in the database to be corrected, it will automatically remove the
discontinuities.
T O A PPLY I NSTRUMENT D RIFT C ORRECTIONS USING CONTROL POINTS :
Scroll to Line 4 of the database (em61data.gdb) using the Database Tools Bar
( ), and notice the unsatisfactory drift correction around the
discontinuity. To overcome this problem, we require a user interaction in order to define
the start and end of the discontinuities. For your convenience this information has been
saved in the channel CP. Proceed with the exercise; however you may opt to simply
rename the channel CP to ContolPoints.
1. Display the profile of the channel M1.
2. On the profile window, place your cursor at the first discontinuity, right click and
from the popup menu select Add control point.
3. Repeat this step at each discontinuity. This process will accumulate a channel of
discontinuity points. When finished selecting the discontinuities, run the Apply
instrument drift correction dialog again, changing the Output data channel to
(M1_Drift_ControlP) and change Apply control points? to (Yes).
4. Observe the difference in the drift correction on Line 4.
Path Corrections
There are three Path Correction options available Warp a Database, Sensor Offset
Correction and UX lag Correction (Line List Table, Offset Correction) and depending
on your data you may need to perform one or all of these corrections.
Note: The Instrument Latency Correction option is available in the UX-Process

software package. For information on UX-Process and other Government
Sponsored UXO Software, visit:
www.geosoft.com/pinfo/oasismontaj/extensions/ux-process.asp.
W ARP A D ATABASE
The Warp a Database dialog enables you to fit a survey within a specified quadrilateral.
The area to be warped is determined by 4 points inputted by the user. You may enter the
information manually or interactively on a map. In the latter case, the two quadrilateral
areas delineating the original and the warped areas are displayed on the map and you are
prompted to confirm the correctness of the selection, re-select or cancel. You have to
enter all four corners before being prompted.
In this exercise we will demonstrate how to warp your data manually. This procedure
does not require an open map, but does require that you know both the original and new
X and Y values. We will warp the data by shifting the grid two metres to the north and
east.
Note: Our data does not need to be warped. However, in order to illustrate how the
transformation works we will create and use a copy of the database file (Mag
Data.gdb) for this procedure.
T O W ARP A S URVEY D ATABASE M ANUALLY :
1. Open and select the database file (Mag Data.gdb).

2. On the Data menu, select Save Database As. The Save database as dialog will be
displayed. In the New database file box, specify a new name, such as (WarpMag
Data.gdb) and click the [OK] button.
3. The database will be saved as WarpMag Data.gdb and will be open and selected
in your current project.
4. On the UX-DataPreparation menu, select Path Corrections|Warp a Database.
The Warp a Database dialog is displayed.
5. Using the [Browse] button you can locate the Database to warp as (WarpMag
Data.gdb). Note that, if you have opened and selected a database, it will be the
default in the Database to warp box.
6. From the Definition mode dropdown list, select the mode as (Manual). The Map
to use parameter is for Interactive mode only and doesn‟t apply to this procedure.
Click the [OK] button the Enter lower left coordinate dialog is displayed.
7. Specify the Original X and Y and the New X and Y values as shown above and
click the [Next>] button. Complete the dialogs using the values listed below:
Original X Original Y New X New Y
Lower Right 2570512.02 5610882.1 2570514.02 5610884.1
Upper Right 2570512.02 5610923.95 2570514.02 5610925.95
Upper Left 2570476.07 5610923.95 2570478.07 5610925.95
Note: For more information on Warping a Database, click the Help ( ) button.
8. When you have finished adding the coordinates on the four dialogs provided,
click the [Finish] button. Your data will be warped two meters to the east and
north. The original X and Y channels are saved in the database as “_X” and “_Y”.
S ENSOR O FFSET C ORRECTIONS
Often the geometry of a UXO survey cart has a fixed separation between the centre of
measurement, e.g. the centre of a coil, and the location of the GPS device used to record
position. This offset is a function of the orientation of the instrument, which normally
remains fixed relative to the line heading, for instance an instrument trailer pulled behind
an operator.
The Sensor Offset Correction is generally the first path correction you would run on
your data, and then you would use the corrected data to run any further corrections.
The Sensor Offset Correction menu item is used to calculate the actual X, Y coordinates
for up to 10 sensors, which are located at fixed offsets from the GPS receiver. Up to 10
channels of data can be associated with each sensor. As each sensor will have its unique
coordinates, the offset data is copied to a new database. Each sensor is represented in the
new database with the same line number but with a different line version.
This dialog takes as input for each sensor a fixed offset distance (both along line and
perpendicular to the line direction) and up to 10 channels that are associated with each
sensor. The heading is determined from a smoothed version of the line path; the user can
specify the distance over which to smooth the data prior to calculating the offset; the
longer the distance the smoother the calculated path. The calculated offset is then added
to the original location and the new coordinate set copied, along with the associated
channels, to a new line version.
For this option we will use the database file (uxo_mag.gdb) that is also included with
the tutorial data.
TO APPLY S ENSOR O FFSET C ORRECTIONS :
1. On the UX-DataPreparation menu, select Path Corrections|Sensor Offset

Corrections. The Sensor offset corrections dialog is displayed.
2. Specify the input database as (uxo_mag.gdb) and click the [Next>] button. The
Sensor offset corrections dialog is displayed.
3. Specify the Number of sensors in array as (1) and the Number of database
channels per sensor as (2).
Note: You can select an unlimited number of sensors in an array, which can have up to
10 channels of data associated with each sensor.
4. Using the Lines to correct dropdown list, select (Selected lines). We will leave
the Roll, Pitch and Yaw channel(s) blank as our data does not include these
channels. However, if you do record the roll, pitch and yaw angles during your
survey you can enter the channels here to correct for the absolute position of each
sensor.
5. We will accept the default names for the X and Y backup channel(s) as
(_X_Offset and _Y_Offset) and specify the Output database name as (Sensor
offset.GDB).
6. Click the [Next>] button to continue. The Enter parameters for sensor 1 dialog is
displayed.
7. Using the Data channel 1 dropdown list, select (top) and from Data channel 2,
select (bottom). . Then specify the distance between the sensor and the GPS
instrument in a relative Cartesian coordinate system where the Y-axis is aligned
with the direction of travel (i.e. the Sensor offset in direction of travel) as
(1).Then, for the Sensor offset across direction of travel and Sensor vertical offset
specify (0)
8. We will accept the default value for the Acceptance Threshold as (0.015) and a
Smoothing interval for heading as (5). This will ensure that the input locations are
thinned to be no more than 5 metres apart, and then smoothly re-interpolated at
five times the average point separation to produce a curve from which the heading
at any point is determined. If left blank, then this interval is calculated to be the
greater of the input offset distance, or two times the average point separation. For
more information on these parameters, click the Help ( ) button.
9. Click the [Preview] button to view a diagram of the layout of the instruments in
the direction of travel, to ensure that geometry is correct. The UCEOffSetMult
dialog is also displayed, asking “Would you like to save the layout?”
10. Click the [Yes] button and the layout is saved in your working directory as
(Multi-sensor layout.map) and the Enter parameters for sensor 1 dialog is again
displayed. Click the [Finish] button to correct for the sensor offset and create and
display a new offset database (Sensor offset.gdb). A dialog is also presented
telling you that the map has been saved to your working directory.
11. Click [OK] and a dialog is presented asking if you want to “Display map?”
12. Click the [Yes] button and the offset database (Sensor offset.gdb) and the sensor
map (uxo_mag_offset_sensor1.map) are opened and displayed in your current
project. Note that, if you have a number of sensors to offset, you may want to
suppress displaying the maps. However, for demonstration purposes we will
produce the maps.
Note: The output database has additional channels named “Combined1” and
“Combined2”. These channels catch all the offset data, and assuming that the
data is surveyed on the same datum and has been levelled, it enables the user
to grid all the data together. Caution is advised in using these channels for
further processing, as the above 2 conditions are important in being able to
use the data from different sensor homogeneously.
UX L AG C ORRECTION
The UX Lag Correction is used to apply an offset correction, based on direction of

travel, to locations in a database. The UX Lag Correction includes two sub-menus; Line
List Table and Offset Correction. The Line List Table option creates a table of
information about the lines in your survey. The Offset Correction option uses this
information, if applicable, when applying lag corrections.
Line List Table

The Line List Table option enables you to create a table of information on the different
lines in your survey. The Line List Table is stored in the current database as (LineList).
Line List Table Information
Line Name The line names are placed in the "Line" Channel.
Starting Position The first location in the line is given in the "X" and "Y"
channels.
Line Heading The number of degrees counter clockwise from Y (azimuth) is

given in the Azimuth channel. This value is calculated using
the first and last positions in the line.
Number of The number of data points in the line is given in the "NVal"
measurements channel.
Offset Correction The values in this channel are used by the Offset Correction
channel dialog to override the default offset correction direction set in
the dialog. Enter one of the following values:
"*" (dummy) – The initial, default value. In this case no

special direction is implied, and the default-offset direction
specified in the Offest correction dialog is used.
0: Shift Forward
1: Shift Backward
2: Shift Right
3: Shift Left
All other values (less than 0 and greater than 3) are treated
like dummies, and the default-offset direction is used.
T O C REATE A L INE L IST T ABLE
1. Select (highlight) the database (uxo_mag.gdb).

2. On the UX-DataPreparation menu, select Path Corrections|UX Lag
Correction|Line List Table. The Create line information table dialog is displayed.
3. In the Line information database box, specify the name for the new database.
Note that, by default the name (uxo_mag_LineInfo.gdb) is provided, the original
database name, with “_LineInfo” appended.
4. Using the dropdown list, select to Append or Overwrite any current items, if the
table already exists.
5. Click [OK] to add the survey line information to the new database file
“uxo_mag_LineInfo.gdb”.
Offset Correction
The time it takes for the measurement sensor to move to the position of the positioning
sensor is known as an offset. An offset correction corrects data for the distance between
the measurement sensor and the positioning sensor by subtracting the offset (in fiducials)
from the start fiducial of the data channel.
As the figure below demonstrates, the effect of offset on the data shifts the data points
behind where they should be. This causes straight-line features (those with common
value points) on a map to appear as “zigzag” or “chevron” patterns when adjacent survey
lines are recorded in opposite directions.
Survey
Direction
t
Uncorrected Corrected
Offsets can also be introduced by the data recording system. Some instruments need
time to accumulate a signal. By the time the signal is recorded, the result might belong to
a point halfway back to the start of the signal collection. This is known as positive offset.
Some instruments automatically correct for this, others don't.
T O A PPLY O FFSET C ORRECTIONS TO Y OUR D ATABASE
1. On the UX-DataPreparation menu, select Path Corrections|UX Lag

Correction|Offset Correction. The Location offset correction dialog is displayed.
2. Specify the Offset distance as (1.5) and from the Default offset direction drop
down list, select the direction of offset for you data (Shift forward). From the
Lines to correct dropdown list, select the lines in your database you want to
correct for. Then, specify the names for the Raw X, Y backup channel(s). For
information on the Smoothing interval for heading parameter or any of the other
parameters, click the Help ( ) button.
Note: The first time this dialog is run, the original locations are copied into the backup
channels; by default these are "X_Raw" and "Y_Raw". These channels are
protected, and should not be altered by the user. Then the dialog recovers the
locations from the "X_Raw" and "Y_Raw" channels to use in processing. The
"X" and "Y" channel values are never used, except when they are copied once
(and only once) into the "X_Raw" and "Y_Raw" channels. The "X" and "Y"
channels are overwritten with the results of the offset calculation. To restore
the "X" and "Y" channels to the original values, you can enter "0" for the
offset distance. The dialog will then just copy the "Raw" data back into the
"X" and "Y" channels.
3. Click the [OK] button. The system copies the original X and Y values into the
backup channels and then enters the location-offset corrections into the X an Y
channels in the database.
QC QA Tools
montaj UX-Detect includes two QC QA Tools menu items that enable you to determine
the coverage of your data, Calculate Coverage Map and Calculate Coverage Area. The
Calculate Coverage Map option is useful for determining the sample coverage over a
given survey grid. Sample locations are "pigeon-holed" into a grid, and the number of
valid samples in each grid cell is summed. Then, the grid cells are plotted with different
colours, depending on the number of samples falling within each one. It is useful (for
instance) to assign one colour for all cells with no samples (range <= 0), another for
those with just a single sample (range <=1) and another colour for those with greater
than one sample.
The Calculate Coverage Area option is used to calculate the total area of coverage from
a coverage grid. The total area is calculated by, counting the number of grid cells with at
least one measurement, and multiplying that value by the area for each cell.
C ALCULATE C OVERAGE M AP
The Calculate Coverage Map option enables you to determine the sample coverage over
a given survey grid and plot this information to the current map. For more detailed
information on the Coverage Map, click the Help button ( ) on the Plot Sample
Coverage Grid dialog.
T O C ALCULATE A C OVERAGE M AP
The Calculate Coverage Map option plots a grid to the current map. Before we begin,
we will create a new blank map using the Oasis montaj Map Tools options.
1. Select the database to be processed (Mag Data.gdb).
2. On the Map Tools menu, select New map, and then select New Map from X,Y. The
Data range to map dialog is displayed.
3. Click the [Scan data] button to scan the Mag Data.gdb, then click the [Next>]
button. The Create a new map dialog is displayed.
4. Specify the Map name, Map template, and Map scale as shown above, and click
[Finish]. A new empty map (Coverage Map.map) will be displayed in your
project.
5. On the UX-DataPreparation menu, select QC QA Tools|Calculate Coverage
Map. The Plot Sample Coverage Grid dialog is displayed.
6. Specify the Data channel as (dz) and the Output grid, Grid cell size, and Number
of Ranges as shown above, and then click the [Ranges] button. The Specify
Sample Numbers dialog is displayed.
7. Specify the # Samples for colour 1 (<=), 2 (<=), and 3 (<=), as shown above,
and then click the [<Back] button. The Plot Sample Coverage Grid dialog is
again displayed.
8. Now click the [Colours] button. The Specify Colours dialog is displayed.
9. Click inside the Colour #1 box to display the Colour dialog. Select a colour from
the Basic Colors pallet, and click [OK] to return to the Specify Colours dialog.
Repeat this for each, Colour # as shown above. When you have selected the four
colours for your grid click the [<Back] button to return to the Plot Sample
Coverage Grid dialog.
10. Click [OK]. The UX Sample Density Plot dialog will be displayed in the
foreground and the Coverage.grd will be displayed on the Coverage.map in the
background.
11. The UX Sample Density Plot dialog tells you how many sample values were
located in the survey area (43408). Click [OK] to close the dialog. The Define
Area dialog will be displayed.
12. This dialog tells you to use the mouse to define an area on your map in which to
plot the legend. Click the [OK] button and your cursor will change to a cross-hair
enabling you to specify the area for the legend.
13. Your map should look similar to the map below.
C ALCULATE C OVERAGE A REA
The Calculate Coverage Area option makes use of the coverage grid to calculate the
total area of coverage, by counting the number of grid cells with at least one
measurement, and multiplying that by the area for each cell.
T O C ALCULATE THE C OVERAGE A REA
1. On the UX-DataPreparation menu, select QC QA Tools|Calculate Coverage

Area. The Calculate area of coverage dialog is displayed.
2. Using the [Browse] button, select the Coverage grid (Coverage.grd) and then
using the Area units dropdown list, select the units of the coverage grid (Square
metres).
3. Click the [OK] button, the Survey Coverage dialog is displayed.
4. The Survey Coverage dialog tells you the Coverage area is 917.4 Square metres
with a Cell size of 0.25 m. Click the [OK] button to close the dialog.
Note: For more information on this, or any of the montaj UX-Detect options, click
the Help ( ) button on the top right of every dialog.
Progress Reporting
The Progress Reporting records all of the parameters used and the processes performed
on each database. The Progress Reporting (by default) is always on.
V IEW A UDIT L OG
The database audit logs are stored within the individual database files. This menu item
copies the contents of the stored log to an RTF file for convenient viewing, editing and
printing. Changes made to the displayed RTF file are not stored in the database file.
Note: A database must be open in the current project to enable the View Audit Log
menu item.
T O V IEW THE A UDIT L OG FILE :
1. Open and select (highlight) a database to view/edit the log as (Mag Data.gdb).
2. On the UX-DataPreparation menu, select the Progress Reporting|View Audit Log
menu. The Audit log file (_Mag Data.rtf) is displayed in your default text editor
(e.g. Notepad).
Tutorial 2: UX-Parameter Determination

The UX-Parameter Determination menu provides options for calculating the analytic
signal grid from total field magnetic data, 1VD magnetic data and EM data as well as
options for target selection and target analysis.
To demonstrate calculating the analytic signal grid we will use the 1VD magnetic data
we imported at the start of the tutorial, the Mag Data.gdb. For more information on
calculating the analytic signal grid using total field and EM data, see Tutorial 4: Total
Field and EM-61 Data Processing on page 91.
1VD Magnetic Data
The analytic signal grid is used to find the location of potential UXO targets within the
survey area. The analytic signal can be considered as being an energy envelope, and is
dependent on the distance from the magnetic source. It thus tends to peak over the poles
of buried magnetic ordnance and can be used to locate potential targets. The analytic
signal grid is derived by adding the three orthogonal derivative grids of the total field
grid T, namely dT|dx, dT|dy and dT|dz.
The Analytic Signal grid is calculated through either a simple one-step calculation or
alternatively by a more interactive step-by-step methodology. Although this tutorial
provides the steps for both methods, we recommend you follow the step-by-step method
because each step in the sequence can be explained in more detail.
U SING THE S TEP - BY -S TEP A NALYTIC S IGNAL P ROCESS
The Step-By-Step Analytic Signal approach enables each derivative grid to be created
separately, which allows problems such as „ringing‟ to be identified and removed before
calculating the Analytic Signal grid.
Gridding the Vertical Derivative Data

The dataset accompanying this tutorial has a nominal sample interval along line of 10
cm, along with a nominal line spacing of 70 cm.
TO CREATE THE VERTICAL DERIVATIVE GRID
1. Open and select the data to process as (Mag Data.gdb).

2. On the UX-ParameterDetermination|1VD Magnetic Data menu, select Step-by-

Step Analytic Signal|Grid 1VD Data. The Grid 1VD data dialog is displayed.
3. Using the 1VD channel to grid dropdown list, select dz and specify the Grid cell
size as 0.20. The defaults for the other entries need not be changed. For the
Display grids in new map? box ensure that Create new map is selected.
4. Click the [OK] button to continue. The Data range to map dialog is displayed.
5. Click the [Scan data] button to query the database for the data ranges and report
the Minimum X,Y and Maximum X,Y co-ordinates.
6. Click the [Next>] button. The Create a New Map dialog is displayed.
7. Enter a Map name (Vertical Derivative) and we will leave the remaining
parameters to the intelligent defaults and click the [Scale] button. The system
automatically chooses a scale that will fit the data on the map template. Just
remember to round the scale to a more efficient number.
8. Click the [Finish] button. The system displays the Vertical Derivative map.
Calculating the horizontal derivative grids

The next step requires calculating the two horizontal derivative grids dT/dx and dT/dy,
where T represents the total field grid.
T O C ALCULATING THE H ORIZONTAL D ERIVATIVE G RIDS AND THE T OTAL F IELD G RID

Step Analytic Signal|Calculate Horizontal Derivative Grids. The Calculate total
field and horizontal derivatives dialog is displayed.
2. Specify the name of the Input Z-derivative grid (1VD) as 1vddz. The default
output grid names can be left as their defaults.
3. Click the [OK] button. The system creates a total field grid (1vdtf.grd) and two
horizontal derivative grids (1vddy.grd and 1vddx.grd).
At this part of the process a Fourier transform is applied to the vertical derivative
grid so that a frequency-domain filter can be applied to integrate the data and thus
derive the total field magnetic grid. Using the total field grid, the horizontal
derivative grids are then derived by applying two additional frequency domain
filters.
Smoothing the horizontal derivative grids

If „ringing‟ is evident in either of the two horizontal grids (1vddy.grd and 1vddx.grd),
the user has the option to attenuate this by applying a Hanning filter via the UX-
Detect|1VD Magnetic Data|Step-by-step Analytic Signal|Smooth Horizontal Derivative
grids menu option. However, the horizontal derivative grids for this particular dataset do
not need to be smoothed.
Calculating and Displaying the Analytical Signal Grid

Now that all the derivative grids have been created, we can calculate the Analytic Signal
grid from the derivative grids.
T O C ALCULATE THE A NALYTICAL S IGNAL G RID

Step Analytic Signal|Calculate and Display Analytic Signal Grid. The Calculate
analytic signal dialog is displayed.
2. Specify the input and output grid names, as shown in the dialog above. For the
Display AS grid in new map? ensure that Create new map is selected. Click the
[OK] button to continue.
3. The Data range to map dialog is displayed. Click the [Scan Data] button and
click the [Next>] button to continue. The Create a new map dialog is displayed.
4. Specify the Map name as Step-by-Step Analytic Signal Map. Using the Map
template dropdown list, select Landscape A4 and click the [Scale] button. The
system calculates a scale that will fit the data on the map template. Remember to
round the scale to a more efficient number.
5. Click the [Finish] button. The system displays the grid in a new map (Step-by-
Step Analytic Signal Map.map).
6. The resulting Step-by-Step Analytic Signal Map should look similar to the
image above.
C ALCULATE AND D ISPLAY A NALYTIC S IGNAL G RID (O NE -S TEP P ROCESS )
The one-step process creates the analytic signal grid, and the (dx, dy, dz) derivative grids
all at once. The process then guides you through the steps necessary to create a map to
display the calculated target solutions on one of the grids.
Note: Because in the previous “Step-by-Step” method we gridded the data using the
default grid names, we will need to either rename or overwrite the default
grids in the “One-Step” process.
1. Select (make active) the database to process as (Mag Data.gdb).
2. On the UX-ParameterDetermination menu, select 1VD Magnetic Data|Calculate

and Display Analytic Signal Grid. The 1VD, TF, X/Y derivative and AS grids
dialog will be displayed.
3. Using the Z-derivative (1VD) channel to grid dropdown list, select dz from your
current database. For the Output grids you can leave the output grid names as the
defaults and overwrite the previously created grids, or rename them as we have
done above. The remaining parameters can be left with the defaults.
4. In the Display grids in new map? box, select Create new map.
5. Click the [Controls] button and the Minimum curvature gridding controls dialog
is displayed.
6. This dialog enables you to modify the minimum curvature gridding parameters.
Specify the Grid cell size as 0.20 and leave the remaining parameters to the
intelligent default values. For more information on the Minimum Curvature
Gridding Controls, click the Help ( ) button.
7. Click the [OK] button. The system returns to the 1VD, TF, X,Y derivative and AS
grids dialog box.
8. To have the system grid the data and begin the process of creating a map to
display the analytic signal grid, click the [OK] button.
9. The system displays the Data range to map dialog box.
10. Click the [Scan data] button to have the system query the database for the data
ranges and report the Minimum X,Y and Maximum X,Y co-ordinates.
11. Click the [Next] button. The system displays the Create a New Map dialog box.
12. Enter a Map name (Analytic Signal Map). Using the Map template dropdown
list, select Landscape A4 and click the [Scale] button. The system calculates a
scale that will fit the data on the map template. Remember to round the Map scale
to a more efficient number (e.g. 400).
13. Click the [Finish] button. The system displays the grid in a new map (Analytic
Signal Map.map).
Note: You also have the option to apply a Hanning (smoothing) filter to the horizontal
derivative grids (dT|dx and dT|dy). This type of filtering is occasionally
needed to attenuate „ringing‟ which may be caused by the large magnetic
gradients due to near-surface anomalies. However, it is not necessary to
smooth the horizontal derivative grids derived from the data in this tutorial.
Target Selection
As mentioned earlier, the peaks in the Analytic Signal grid are assumed to occur directly
above the buried magnetic ordnance, which are the potential UXO targets we are looking
for. The montaj UX-Detect system now has a number of Target selection tools
including two automated peak-picking algorithms, the Blakely and the Peakedness
algorithms.
Note: The Pick Peaks along Profiles option is available in the UX-Process software
package. For information on UX-Process and other Government Sponsored
UXO Software, visit: www.geosoft.com/pinfo/oasismontaj/extensions/ux-
process.asp.
B LAKELY T EST
The Blakely Test automatically selects target picks from a grid and stores the selected
targets in a new Target database and displays the targets as symbols on the current map.
T O U SE T HE B LAKELY A UTOMATED P EAK -P ICKING A LGORITHM
The automated peak-picking algorithm based on a technique by Blakely (1986) is used

to find the location of individual peaks or both peaks and ridges in the Analytic Signal
grid.
1. Open the project database (Mag Data.gdb) and then select (highlight) the Step-
by-Step Analytic Signal Map.map.
2. On the UX-ParameterDetermination menu, select Target Selection|BlakelyTest.
The Select the target database dialog is displayed.
3. Accept the default Target database name as (Mag Data_Targets.gdb). Click the
Help button ( ) for more information on the “Target database”. Click the [OK]
button and the Locate targets dialog will be displayed.
4. Make sure the Grid to pick targets is selected as (1vdas.grd) and we will accept
the default name of the Target list as (Targets).
5. The definition of what constitutes a peak can be controlled through the Level of
peak-detection (Blakely index) dropdown menu. You can increase (or decrease)
the number of picked targets by decreasing (or increasing) the Blakely Index. We
will use the default Normal (4).
6. The Grid value cut-off level (0.5) enables the user to enter the minimum
amplitude so that Analytic Signal peaks below this level are excluded from the
target list, which is written to the line Targets in the new database (Mag
Data_Targets.gdb).
7. The remaining options can be left as their defaults. For more information on the
Locate Target parameters, click the Help ( ) button.
Note: The cut-off amplitude used should represent the detection limit of the measuring
equipment, but will be very dependent on the local survey conditions e.g.
noise due to ferrous „contaminants‟ such as nails, etc. It should be
remembered that near-surface objects could always be windowed out later in
the processing sequence once the depths of all the targets have been
calculated. Finally, the locations of the picked peaks are plotted as symbols on
the current map, which should be the “Step-by-Step Analytic Signal” map.
In this way, if any anomalies were missed by the peak-picking routine, they
can be added manually. Manually adding targets is explained in the
Digitizing Additional Targets section below.
8. To determine the symbol options, click the [Symbol] button. The Target symbol
definition dialog is displayed.
9. Using this dialog you can specify the Symbol, Size, and Attributes. When you are
satisfied with your symbol, click the [<Back] button. The Locate targets dialog is
again displayed.
10. Click the [OK] button. Using the above parameters should result in over 260
potential UXO targets being picked and written to the Targets line in the
database and displayed on the current map (Step-by-Step Analytic Signal Map)
as symbols.
Note: For more information on the Blakely target picking method, click the Help ( )
button on the Locate Targets dialog.
P EAKEDNESS
The Peakedness method automatically creates a “peakedness” grid from an input scan
grid, and picks targets from the peakedness grid. The selected targets are stored in the
current “Target” database (Mag Data_Targets.gdb) and displayed as symbols on the
current map.
T O U SE T HE P EAKEDNESS A UTOMATED P EAK -P ICKING A LGORITHM
The Peakedness algorithm automatically creates a “peakedness” grid and selects targets
from this grid. In this example we will use the first Analytic Signal Map (Analytic
Signal Map.map) we created.
1. Select the database file (Mag Data.gdb) and then select (highlight) the Analytic
Signal Map.map.
2. On the UX-ParameterDetermination menu, select Target Selection|Peakedness.
The Peakedness Grid & Locate targets dialog is displayed.
3. Using the Grid to pick targets dropdown list, select the analytic signal grid
(1vdas.grd) and for Target list select (Targets). Then in the Channel to save grid
values box, specify (Grid_value_Peak).
4. Specify the Peakedness Grid as (peakedness.grd) and then leaving the remaining
parameters to the intelligent defaults as shown above, click the [Symbol] button
to change the symbol type. The Target symbol definition dialog is displayed.
5. From the Symbol to plot targets dropdown list, select (x). Then click the [<Back]
button to return to the Peakedness Grid & Locate targets dialog.
Note: Clicking the [Targets] button enables you to select the “Target” database to
store your results to and the “Target list” and “Mask” channel.
6. Click the [OK] button and your results, over 260 potential UXO targets, will be
picked and written to the Grid_value_Peak channel in the “Target” database
(Mag Data_Target) and displayed on the current map (Analytic Signal Map) as
“x” symbols.
Note: For more information on the Peakedness target picking method, click the Help
( ) button on the Peakedness Grid & Locate targets dialog.
D IGITIZE A DDITIONAL T ARGETS
Once a list of targets has been generated and their locations plotted on a map, as symbols
(+) as on the Step-by-Step Analytic Signal Map, (or as symbols (x) as on the Analytic
Signal Map) the data should be cross-examined with the original dz and analytic signal
data to verify that no anomalies have been missed. The montaj UX-Detect system now
has two methods to digitize additional target locations; from a grid in a displayed map
file or from a profile displayed in a spreadsheet.
In the first example, we will show you how to digitize additional targets using a grid
displayed in the Step-by-Step Analytic Signal Map. The second example will
demonstrate how to digitize addition targets from a profile, using the line (L63:0) of the
(dz) channel.
Adding Targets from a Grid

If any anomalies have been missed by the automatic peak-picking routine, these can be
added manually from a grid displayed on a map.
T O A DD M ISSED T ARGETS FROM A M AP M ANUALLY :
1. Select (highlight) the Step-by-Step Analytic Signal Map.map.
2. Before you digitize any additional targets use one of the Zoom button (e.g.
)
and zoom up closely to an anomaly on the Step-by-Step Analytic Signal Map.
3. On the UX-ParameterDetermination menu, select Target Selection|Digitize

Additional Targets. The Digitize targets from map dialog is displayed.
4. Using the dropdown lists, select the Target list as (Targets) and the Mask channel
as (Mask).
Note: If the Target list you want to use is not displayed, click the [Targets] button at
the bottom of the dialog and the Select the target database dialog will be
displayed. Using this dialog, select the Target database and click the [OK]
button, the Select/Set up the target list dialog will be displayed. Using the
dropdown lists select the Target list (group) and the Mask channel. Click the
[OK] button and selected Target list will be displayed.
5. Using the Browse button ( ) select the Grid file #1 as (1vdas.grd) (Note that,
this should be displayed as the default grid file). Then, in the Channel to save grid
value #1 box, specify (Grid_Value).
6. Using the Append or Overwrite? dropdown list, select Append, this will add the
new digitized targets to the existing (Targets) list.
7. Click the [Symbol] button to specify the symbol type (+). Then click the [OK]
button to return to the Digitize targets from map dialog.
8. Click the [OK] button. The Digitize additional targets dialog is displayed.
9. This dialog instructs you on how to use your mouse to digitize targets on a map,
click the [OK] button and your cursor changes to a cross-hair.
10. Use the left mouse button to digitize a point on the target centre. You can select
numerous targets by clicking on the anomaly centres. During the selection
process, a line is drawn between each digitized point to enable you to keep track
of the locations of the targets you selected.
11. Click the right mouse button to display a popup menu. Using this menu, you can
Undo Last Point, Create a Snapshot, Pan, Zoom, and Redraw different sections of
the map window. Select (Done) from the popup menu to end the digitizing
process.
12. The additional selected targets will be added to the list of targets in the database.
The Grid_value channel in the database will be updated and the symbols on the
map will be updated to show the new targets. This process can be repeated several
times.
Tip: This option is also useful if the user simply wants to calculate depth and apparent
weight solutions for some typical anomalies before processing a whole dataset.
Adding Targets from a Profile

If any anomalies have been missed by the automatic peak-picking routine, these can be
added manually from a profile displayed in a spreadsheet. The Profile is a “graphical
window" to your Oasis montaj database.
T O A DD M ISSED T ARGETS FROM A P ROFILE :
1. Select (make current) the map file (Analytic Signal Map.map), and then select
the project database (Mag Data.gdb).
2. Display L63:0 in the spreadsheet window.
Note: To display L63:0 right click on the Line ID Cell and from the popup menu,
select (List). Scroll down the list and select L63:0. Line L63:0 will be
displayed in the spreadsheet window.
3. Select the Header cell of the channel you wish to profile (dz). Right click and
from the popup menu, select Show Profile. The channel profile will be displayed
in the profile window below the database window.
4. While holding your cursor over the profile window, right click and from the
popup menu, select UX-Process: Target Selection Options. The Digitize
additional targets dialog is displayed.
5. Using the dropdown lists, select the Channel # 1to save value as (dz). You can
select up to 4 channels to save values for.
6. Click the [Symbol] button to specify the symbol type (x) and then click the
[<Back] button to return to the Digitize additional targets dialog. Click the
[Targets] button to display the Select the target database dialog.
7. Select the Target database as (Mag Data_Target.gdb) and click the [OK]
button. The Select/Set up the target list dialog is displayed. Select the Target list
(Targets) and the Mask channel (Mask) and click the [OK] button to return to
the Digitize additional targets dialog.
8. Click [OK] to begin digitising additional targets.

9. Select a peak on the profile line exactly where you want to specify a new target
location. Right click, and from the popup menu, select UX-Process: Select Target.
10. The target will be added to the bottom of the dz channel in the Target database
(Mag Data_Target.gdb). The target will also be plotted on the Analytic Signal
Map.map.
11. Continue selecting targets along this profile line by selecting a target, right-
clicking and selecting UX-Process: Select Target. You can change lines using the
Line/Group tools ( ).
C REATE /R ESET M ASK C HANNEL
Use the Create/Reset Mask Channel menu option to create a new target mask channel, or
reset an existing target mask channel to 1.
T O C REATE /R ESET M ASK C HANNEL :
1. Select the database to Create/Reset the Mask Channel as (Mag

Data_Targets.gdb).
2. On the UX-ParameterDetermination menu, select Target Selection|Create/Reset
Mask Channel. The Reset/CreateTarget Mask Channel dialog is displayed.
3. In the Target mask channel box, specify (TargetMask).
4. To specify the Targets database, click the [Targets] button. The Select the target
database dialog will be displayed. Select the Target database as (Mag
Data_Targets.gdb). For more information on selecting the target database, click
the Help ( ) button.
5. Click the [OK] button on the Reset/Create Target Mask Channel dialog and a
new “Mask” channel (TargetMask) will be added to the Target database
Note: A new Mask channel initially has its value/flag set to “1” to indicate that all
Targets are selected. If the value is set to 0 or dummy (*), then the target will
be ignored in operations making use of the Mask channel.
Target Analysis
The Target Analysis options enable you to analyse your magnetic and EM data to
determining Target sizes, depths, and weights. For additional information about each
analysis method, click the Help ( ) button on the dialog of interest.
C OMBINING M AGNETIC AND EM-61 DATA
When magnetic and EM-61/EM61-MK2 data from the same site are available, you have
the opportunity to blend the data. For example, you can place magnetic target picks on
the EM grid. Due to the fixed geometry of the EM-61/EM61-MK2 systems, the depth
determination of the selected targets from the EM-61/EM61-MK2 data is often
considered more accurate than those calculated from the magnetic data. To use this
option, select the Calculate Target Depths from EM Data from the UX-
ParameterDetermination|Target Analysis menu.
The accuracy of the target's magnetic weight determination is very dependent on the
accuracy of the target depth. When determining the apparent weight, the system provides
the option of using target depth values determined from the EM-61/EM61-MK2 data
instead of magnetic data. To use this option, select the Calculate Magnetic Weights from
EM Depths from the UX-ParameterDetermination|Target Analysis menu.
C ALCULATE T ARGET S IZES
The apparent depth values for each picked target are calculated by solving Euler‟s
Homogeneity equation for a square window of cells positioned directly over the peak in
the Analytic Signal grid. The minimum dimensions of this window must be 4x4 grid
cells. There is no upper limit but it should be remembered that the processing time is
approximately proportional to the total number of window cells. In order to calculate
depth values accurately, the Euler window should sample the full width of each
anomaly, but not adjacent anomalies.
T O C ALCULATE T ARGET S IZE :
1. Select (highlight) the target database (Mag Data_Targets.gdb).

2. On the UX-ParameterDetermination menu, select Target Analysis|Calculate
Target Sizes. The Calculate target sizes dialog is displayed.
3. Using the dropdown list, select the Grid to define target sizes as (1vdas.grd) (this
is the analytic signal grid we created earlier).
4. From the Target list dropdown list, select (Targets) and then we will accept the
default name for the Channel to save target sizes as (Target_Size).
5. Click the [OK] button. The UX-Detect system automatically calculates the
appropriate window size (in ground units) for each of the anomalies in the target
list. It does this by calculating the average distance between the inflection points
on eight profiles across the Analytic Signal anomaly, with this median distance
representing the half-width of the anomaly. The values for the target size is stored
in the database (Mag Data_Target.gdb) and displayed in the spreadsheet
window in the channel (Target_Size).
C ALCULATING THE TARGET DEPTHS AND WEIGHTS FROM M AG D ATA
Now that you have determined the appropriate window size for each anomaly in the list
of potential UXO targets, we can now solve Euler‟s equation to calculate the apparent
depth, and use an empirical relationship to derive an apparent weight for each of our
targets.
T O C ALCULATE T ARGET I NFORMATION
1. On the UX-ParameterDetermination menu, select Target Analysis|Calculate

Target Depths and Weights from Mag Data. The Calculate Mag target
information dialog is displayed.
2. Specify the parameters as shown below. (The Instrument height is the height to
the centre of the gradiometers).
Note: The Structural Index value (Target type) of (2.7 ordnance) used in this tutorial
may not be correct for all the anomalies we have picked. If the Structural
Index is lower for a particular target, then the calculated depth and apparent
weight values will be an overestimate. Likewise, if the Structural Index for a
particular target is higher than 2.7, the opposite will be true.
3. Click the [Grids] button to continue.
4. The system displays the Grids used in calculation dialog box. Specify the Total
field mag grid, X, Y and Z derivative grids, and the Analytic signal grid you
created earlier in the appropriate boxes.
5. Click the [Finish] button to calculate the target information.
6. The Euler solutions are calculated and written to the specified line (Targets) in
the database. The system has created several new database channels:
Target_ID: Target ID number to identify anomalies
Target_Size: Calculated size of the target
Mag_Depth: Calculated depth to target (in ground units)

App_Weight: Apparent weight of the target (Kg)
Bkgrd_field: Analytic Signal background value
Depth_err: Error in the calculated depth (%)
C ALCULATING TARGET DEPTHS FROM EM D ATA
You can use the Calculate Target Depths from EM Data option to calculate the apparent
depths of targets from the original two-coil EM data (top and bottom) grids. The grid
values at those target locations are saved in a Target database.
C ALCULATING M AGNETIC W EIGHTS FROM EM D EPTHS
Use the Calculate Magnetic Weights from EM Depths option to estimate apparent weight
of targets using the depth values derived from EM data.
Tutorial 3: UX-Target Management

The UX-Target Management menu provides options for target list management, target
utilities and creating target maps.
Target List Management
The Target List Management menu provides a variety of options for managing the target
list including the following options.
 Window Target List
 Subset Target List
 Remove UXO Targets from Target List
 Remove Multiple UXO Targets
 Move UXO Targets
 Merge UXO Targets
 Reset Target IDs.
W INDOW T ARGET L IST
Once we have a set of solutions for our target list, we can now begin to window out poor
solutions or targets, which are not of interest to us. Use the Window Target List menu
option to window out poor solutions or targets that are not of interest.
T O W INDOW T HE T ARGET L IST :
1. Open your Target List database (Mag Data_Target.gdb).

2. On the UX-TargetManagement menu, select Target List Management|Window
Target List. The Refine target list dialog is displayed.
3. Specify the input parameters as shown above to window out solutions below 250
and above 3000 values.
4. Click the [OK] button. The system will remove the targets with values outside the
range you specified.
5. Note that selecting the Mask channel (click twice on the header cell) and then
right-click and select Statistics from the database popup menu, displays the Stat
Report dialog, which shows that 46 items (targets) are included in the Mask
channel.
Any of the database channels can be windowed in the same way. The refining mode
option enables the user to either continue windowing out solutions using several
different criteria (e.g. depth, apparent weight, depth error, etc.) or to reset the windowing
to include all the targets in the list.
In addition to this approach, solutions may also be windowed out manually by linking
the location symbols to the solution line in the database and cross-referencing between
the Analytic Signal and the original vertical magnetic gradient grid. To remove a
solution, the user needs only to delete either of the relevant X or Y coordinates.
S UBSET T ARGET L IST
Once you have a Targets list you may, at this point, want to copy a subset of the Targets
list to a new Targets list.
T O S UBSET T ARGET L IST :
1. Open your Targets List database (Mag Data_Target.gdb).

2. On the UX-TargetManagement menu, select Target List Management|Subset
Target List. The Subset targets to new list dialog is displayed.
3. Using the dropdown list, select the Input target list as (Targets) and the Mask
channel as (Mask). Then, in the Output target list box, specify the name of the
new target list as (Targets_2).
4. Click the [OK] button and the new Target list is created in the Target database
(Mag Data_Target.gdb).
Note: The new Subset Target List (Targets_2) only includes the 46 items (targets)
that were marked “1” in the Mask channel. .
R EMOVE A UXO T ARGET FROM THE T ARGET L IST
Use the Remove a UXO Target from the Target List menu option to “remove” a selected
target from the current target list. Note that, the target is not actually removed from the
target list; instead the value of the current mask channel is set to dummy, effectively "de-
selecting" it, so that when the targets are re-plotted, it no longer appears.
T O R EMOVE A UXO T ARGET FROM THE T ARGET L IST
1. Select (highlight) the Analytic Signal Map.map.
2. Before you remove any targets use the Zoom button ( ) and zoom up closely to
a target on the Analytic Signal Map.
3. On the UX-TargetManagement menu, select Target List Management|Remove
UXO Target(s) from Target List (or in Shadow Cursers mode ( ), mouse over
the current map, right click, and from the popup menu select Remove UXO
Target). The curser will change to a crosshair ( ).
4. Left-click on the targets which are to be removed and the targets are re-drawn on
the map. Note that, the target is not actually removed from the target list; instead
the value of the current mask channel is set to dummy, effectively "de-selecting"
it, so that when the targets are re-plotted, it no longer appears.
5. When you have finished removing targets, right-click and select Done from the
popup menu.
R EMOVE M ULTIPLE UXO T ARGETS
Use the Remove Multiple UXO Targets menu option to remove multiple targets. Note
that, the targets are not actually removed from the target list; instead the values of the
current mask channel are set to dummy, effectively "de-selecting" them, so that when the
targets are re-plotted, they no longer appear.
T O R EMOVE M ULTIPLE UXO T ARGETS FROM THE T ARGET L IST
2. Before you remove any targets use the Zoom button ( ) and zoom up closely to
group of targets on the Step-by-Step Analytic Signal Map.
3. On the UX-TargetManagement menu, select Target List Management|Remove
Multiple UXO Targets (or in Shadow Cursers mode ( ), mouse over the
current map, right click, and from the popup menu select Remove Multiple UXO
Targets). The Define polygon dialog is displayed.
4. This dialog asks you to enter point on a polygon around the targets to be removed.
Click the [OK] button and the curser will change to a crosshair ( ).
5. Digitize the area that you want to remove the targets from and then right-click and
from the popup menu, select Done.
6. The targets will be “de-selected” and the targets will be redrawn on the current
map.
M OVE A UXO T ARGET
Use the Move a UXO Target menu options to select a target on a map and move it to
another location. The Target list is then updated with the new X, Y locations.
T O M OVE UXO T ARGETS
2. Before you move any targets use the Zoom button ( ) and zoom up closely to a
target on the Analytic Signal Map.
3. On the UX-TargetManagement menu, select Target List Management|Move UXO
Target (or in Shadow Cursers mode ( ), mouse over the current map, right
click, and from the popup menu select Move UXO Target). The Move Target
dialog is displayed (this dialog is only displayed the first time this option is run).
4. Click the [OK] button and the cursor changes to a crosshair ( ). Left-click on
the target which is to be moved, and then click a second time on the new location
for the target. Between the first and second clicks a line is drawn on the screen to
show you the relationship between the old and new location. The targets are then
re-drawn on the map.
M ERGE UXO T ARGETS
Use the Merge UXO Targets menu option to locate clusters of targets and merge them
into single targets. This works by creating a TIN (Triangular Irregular Network) from
the X, Y locations of the input targets. Then, for each node in turn, it locates adjacent
nodes that are within the specified merge radius. If such targets are located, then they are
replaced with a single target at the geometric center of the original locations.
T O M ERGE UXO T ARGETS

2. On the UX-TargetManagement menu, select Target List Management|Merge
UXO Targets. The Select the target database dialog is displayed.
3. Select the Target database as (Mag Data_Targets.gdb) and click the [OK]
button. The Select/Set up the target list dialog is displayed. Select the Target list
as (Target_2) and select the Mask as (Mask). Click the [OK] button and the
Merge clustered targets dialog is displayed.
4. Using the Initial target list dropdown list, select (Targets_2). To create a New
target list, click inside the box and type the name of the new list as
(Merged_Targets). A new list is created so that the process may be repeated with
different parameters without losing the original data. Select the remaining
parameters, as shown above.
Note: For more information on Merging targets, click the Help ( ) button on the
Merge clustered targets dialog.
5. Once the parameters have been selected, click the [OK] button. The Grouping
Targets dialog is displayed.
6. This dialog will tell you how many targets have been merged (in this case 6) and
the number of remaining targets (43) in your new merge list (Merged_Targets).
7. Click the [OK] button and the Sample grids at target locations dialog is
displayed.
8. This dialog enables you to select and sample up to four grids, and write the results
in up to four channels, in the target list. Note that, the X and Y locations for the
targets are taken from the targets in the specified target list. To continue, click the
[OK] button. The Plot target on a map dialog is displayed.
9. You can experiment with the type of target symbol you would like to plot on you
map. From the Symbol to plot targets dropdown list, select (triangle) then left-
click inside the Symbol fill colour box. The Colour dialog is displayed.
10. You can select a colour from the Basic colours pallet, or by clicking the [Define
Custom Colors>>] button you can create your own custom colour.
11. For the purposes of this tutorial select (light blue) from the Basis color pallet, and
then click [OK] to return to the Plot targets on map dialog.
12. Click the [OK] button to display the new merged targets on your map.
R ESET T ARGET ID S
This menu item enables you to reset the Target_ID values in the spreadsheet, with items
numbered from 1 in sequence. This is useful, for instance, when a subset of the data is
selected using the mask channel, and the Target_IDs that are posted have gaps.
T O R ESET T ARGET ID S
1. Open the target database file Mag Data_Targets.gdb. Display the target list
(group) Targets_2 and note the Target_ID values are not sequential.
2. On the UX-TargetManagement menu, select Target List Management|Reset
Target IDs. The Reset Target IDs dialog is displayed.
3. From dropdown lists select the Target list as (Target_2) and the remaining
parameters as shown above.
4. Click [OK] button and the target IDs will be reset in sequential order.
C REATE /R ESET M ASK C HANNEL
Use the Create/Reset Mask Channel menu option to create a new target mask channel, or
reset an existing target mask channel to 1.
For more information on this option see Create/Reset Mask Channel on page 63.
Target Utilities
UX-Detect include the target utility Resample grids from target locations. This option
enables you to easily determine grid values at specified target locations.
R ESAMPLE G RIDS FROM T ARGET L OCATIONS
Use the Resample Grids from Target Locations menu option to resample up to four grids
based on the X, Y locations of targets found in a specified Target list. The results of the
re-sampled grids are stored in specified channels in the Target list.
T O R ESAMPLE G RIDS FROM T ARGET L OCATIONS

2. On the UX-TargetManagement menu, select Target Utilities|Resample Grids from
Target Locations. The Sample grids at target locations dialog is displayed.
3. Use this dialog to select up to four grids to be resampled, based on the X, Y

locations of the Targets found in the specified Target list. The results are written
to the specified channels in the Target database.
4. Note that, new target locations and grid values can be added to the target lists by,
digitizing new targets from a grid or a profile, moving a target on a map, and
merging clustered targets.
Target Maps
The Target Maps menu provides a variety of options for creating target maps including,
creating a standard target map, plotting target to a map, displaying grids, contouring
your data, adding a site plan in DXF format and 3D symbol plotting tools.
We will use the database Mag Data.gdb, and its associated Target database Mag
Data_Targets.gdb, to create our map.
C REATE S TANDARD M AP
Once the windowing of the solutions has been completed and the user is confident that
the remaining solutions do represent potential UXO targets, the final step is to display
the location and calculated target information on a standard target map.
1. On the UX-TargetManagement menu, select Target Maps|Create Standard Map.

The Plot UXO targets dialog is displayed.
2. Using the New map? dropdown list, select (Create new map). Specify the
remaining parameters as shown in the dialog above and click the [OK] button.
3. The Data range to map dialog is displayed. Click the [Scan Data] button and
click the [Next>] button. The Create a new map dialog is displayed.
4. Specify a Map name (i.e. Standard Map) and using the Map template dropdown
list, select (landscape A4). Click the [Scale] button to determine the default map
scale, remembering to round the Map scale to a more efficient number (e.g. 400).
5. Click the [Finish] button and the new map (Standard Map.map) is displayed in
the background and the Basemap layout dialog is displayed in the foreground.
6. Using the Basemap layout dialogs you can customize your basemap with many
elements, including north arrows, reference grids, latitude/longitude annotations,
line styles and thickness and titles. The layout of your base map can either be
Map or Figure style. Figure style maps have a layout with the title, scale bar and
north arrow located at the bottom of the map whereas map style maps have a
layout with the title box, scale bar and north arrow along the right hand side of the
map.
7. Using the Map style dropdown list, select (figure) and then accepting the
remaining default parameters, click the [Next>] button. The Figure style base
map dialog is displayed.
8. This dialog can be used to create a figure map style base map. Select the
parameters as shown above (the default values) and click the [Next>] button. The
Figure Titles dialog is displayed.
9. Specify the titles for your map and click the [Finish] button. The standard target
map is created and displayed in the background and the Locate Legend dialog is
displayed in the foreground.
10. Click the [OK] button and then click the left mouse button on the map to locate
the centre of the legend. Your map should look similar to the image below.
11. The linking between the target locations and the solutions in the database is
illustrated below for target number 132 (zoomed map image).
Dynamic Link
P LOT T ARGETS ON M AP
Use the Plot Targets on Map option to plot the currently selected target locations on a
map.
1. Open the target database file (Mag Data.gdb) and then select (highlight) the map
file (Standard Map.map).
2. On the UX-TargetManagement menu, select Target Maps|Plot Targets on Map.
The Plot targets on a map dialog is displayed.
3. Complete the parameters as shown in the dialog above and click the [OK] button.
Each target location will be displayed on the map with a red circle.
D ISPLAY G RID
The UX-Detect system includes a number of grid display options, including the ability
to display single grids, colour-shaded grids, display a grid histogram on a map and
display ternary images and 2, 3 and 4-grid composites.
Displaying the Analytic Signal Map as a Shaded Grid

When displaying analytic signal maps, it is often a useful to display the grid as a shaded-
relief image with a normal (Gaussian) colour distribution to highlight the high amplitude
peaks and mask the lower-amplitude „noise‟.
T O D ISPLAY A G RID AS A S HADED R ELIEF I MAGE
1. Make sure the Standard Map.map is selected in the project.

2. On the UX-TargetManagement menu, select Target Maps|Display Grid and then
select Colour-Shaded Grid.
3. The Colour-shaded grid image dialog is displayed.
4. Specify the parameters as shown above and click the [Current Map] button to
create a colour shaded image of the Analytic Signal grid and place it on the
current Standard Map.map.
Note: The View/Group Manager Tool was used to hide the Targets and Symbols on
the map above to uncluttered the data view.
C ONTOUR
UX-Detect contouring functionality is designed to help you make contour maps from a
gridded data file. There are a number of Contour options including:
 Quick – uses default parameters
 Custom – uses parameters specified by the user
 Logarithmic –uses a grid that has been gridded logarithmically
 Control file –uses an ASCII control file that provides full cartographic cosmetic
control of plotting options. You can define up to 32 hierarchical levels, each with
separate line colour, thickness, style, and labelling options.
Adding Analytic Signal Quick Contours to your Standard Map

When you want to create a contour map for basic interpretation, you can use the quick
contouring method. This method generates default contours based on your data values.
1. Open the map you want to add contours to as (Standard Map.map).
2. On the UX-TargetManagement menu, select Target Maps|Contours and then
select Quick. The Contour dialog is displayed.
3. Using the Grid file dropdown list, select the grid file (1vdas.grd) and click the
[OK] button. The contours are drawn on the map using default settings, as shown
below.
S ITE P LANS FROM A UTO CAD DXF F ILES
Use the Site Plans from DXF File to import vector entities in a DXF file into a new or
existing map. This dialog operates as a wizard.
Note that, there is no DXF file available to import into this project, however the steps
involved in importing a DXF file are provided below.
T O I MPORT A DXF F ILE INTO A M AP :
1. Open and make current (highlight) a map you want to import a DXF file to.
2. On the UX-TargetManagement menu, select Target Maps|Site Plan from

AutoCAD DXF File. The Import AutoCAD DXF File dialog is displayed.
3. Using the Browse ( ) button, select the DXF file from your project directory.
Then, using the dropdown list select to Plot layers to either separate groups or
one map group.
4. Using the Colour dropdown list, select either to “retain colours” or select a
specific colour from the Colour dropdown list.
5. Click the map to plot the file to as either “New map” or “Current map” and
depending on which map you are plotting to the Import to “new” or ”current”
map dialog is displayed.
6. Use this dialog to specify the “map name”, which data view you are importing the
dxf file into (e.g. plan, E-W Section, or N-S Section) and “map scale”. Click the
[Next>] button and the DXF Coordinate system dialog is displayed. Click the
“Modify” button to specify the coordinate system and click the [OK] button to
plot the DXF file to your map. For more information on these parameters click the
Help ( ) button on the Import AutoCAD DXF File dialog.
C REATE A 3D V IEW
UX-Detect include Geosoft‟s redesigned 3D Viewer, which provides all of your 3D-
mapping tools, functions and settings in one integrated 3D environment. The 3D Viewer
has been designed to streamline your workflow and enhanced usability.
Using the tools in the 3D Viewer you can plot 3D symbols with fixed or variable colours
to a 3D map. The colours are fixed or varied based on the data values of the colour data
channel.
TO CREATE A 3D VIEW :
1. Open the database that includes the data you want to plot using the 3D Viewer
tools as (Mag Data_Targets.gdb).
2. On the UX-TargetManagement menu, select Target Maps|Create a 3D View. The

Create a 3D View dialog is displayed
3. Ensure that the New map radio button is selected. In the Map name text box,
specify your new 3D map name as (UX-Detect 3D View).
4. We can leave the remaining parameters to the intelligent defaults. Click [OK] and
a new empty 3D map will be created and opened in the background and the 3D
Viewer will be displayed in the foreground.
5. Note that, the 3D Viewer provides a range of options for visualizing your data in
three dimensions including; displaying multiple surfaces, each with own relief
and contents, and each with its own orientation in 3D space.
T O P LOT 3D C OLOUR R ANGE S YMBOLS :
1. In the open 3D Viewer, on the Add to 3D menu, select 3D Symbols. The 3D

Coloured symbols plot dialog is displayed.
2. Using the dropdown lists, select the parameters that best suites your data. Note
that, to colour your data using the values from a secondary channel, select
(Variable colour) from the Colour option dropdown list and then select a
Variable colour: Colour data channel.
3. Click the [OK] button to plot the 3D colour range symbols on the 3D Viewer
(foreground) and on the new map, UX-Detect 3D View.map (in the background).
4. The 3D Viewer enables you to change the point of view and work with all the
attributes that make up the 3D View by using the controls on the 3D Viewer
toolbar.
5. When you are satisfied with the 3D View, close the 3D Viewer and the 3D View
will de displayed on the 2D map (UX-Detect 3D View.map) just as it last
appeared in the 3D Viewer.
6. You can move and resize this view to place it at a better location, just like any
view in a map. For information on these or any dialog parameters, click the Help
( ) button.
Chapter 2: Total Field and EM-61 Data Processing 91
Chapter 2: Total Field and EM-61 Data Processing
Total Field Data
The previous tutorials in this document outline the steps required to grid measured
gradient data, create an analytic signal grid, locate and refine targets and prepare a final
target location map for 1VD magnetic data. The procedure for processing Total Field
Magnetic data is almost identical. The only difference is the processing steps required to
create the analytic signal grid. If you use the one-step method when creating the analytic
signal grid, the process is the same.
EM-61 Data
The processing of EM-61 data follows a similar processing sequence as the one used for
the 1VD data.
T O P ROCESS EM-61 D ATA
1. On the Data menu, select Open database. The Open database dialog is
displayed. Select the database file (uxo_em.gdb) and click the [Open] button.
The database is displayed in your current project.
2. The first step in processing EM-61 data is to grid the top and bottom data
channels. From the UX-ParameterDetermination menu select EM Data and then
select Grid Multiple Channels. The Multiple Channel Gridding dialog is
displayed.
3. In the Database Channels window, select (TOP_EM and BOT_EM) and using
the [Add->] button move them to the Channel to Grid window.
4. Using the Gridding Method dropdown list, select (Minimum Curvature). For
this tutorial we will accept the remaining intelligent defaults, however you can
specify a number of gridding parameters, for more detailed information click the
Help ( ) button.
92 Chapter 2: Total Field and EM-61 Data Processing
5. Click the [OK] button to create the output grids and display them in temporary
map files.
6. The second step is to select targets from the grids. The target selection, refining
and map-making procedures are the same as that used for the 1VD data. Refer to
the Target Selection procedures on page 53.
.
Appendix 1: Theory
Ground-based electromagnetic and magnetic surveys are useful for determining the
presence and subsurface locations of unexploded ordnance (UXO) and other metallic
objects.
Shallow subsurface geophysics investigations are increasingly used in mapping

distributions of buried metallic objects on land and underwater (Pawlowski, 1994).
Geophysical investigations are vastly superior to traditional sampling programs as they
minimize time, danger and cost factors, yet maximize the amount of information.
The two most common geophysical methods used in ordnance detection are
electromagnetics, which constitutes about 90% of the surveyed data, followed by
magnetics. The electromagnetic method (using measurements by electromagnetic
induction, without electrodes) detect all metallic objects as opposed to only ferrous
material and are used in a wide variety of investigations ranging from buried hazardous
wastes and landfill sites, to groundwater contamination studies (Glaccum et al, 1982;
Greenhouse, et. al., 1983; Valentine et. al., 1985). The magnetic method (typically based
on a proton or cesium vapour sensor configuration) is generally used for detecting the
presence of ferro-magnetic objects (barrels, pipes) and geological structures (dikes,
faults). While magnetic methods see deeper, the resulting data does not define the
geometry of the object as well as electromagnetic methods. On the other hand, the
electromagnetic methods have a smaller depth penetration range. Both methods offer
fast tools for mapping buried metallic objects in shallow (0 to 10 m) subsurface zones.
With proper survey procedures, effective processing and interpretation, both TEM and
magnetics are very suitable for detecting buried ordnance. Wherever possible, both
geophysical techniques should be employed to optimize the detection process and
provide a check on results.
The Magnetic Method

The theory and use of magnetics is well described in numerous papers (Breiner, 1973).
Generally two types of field magnetometer systems (proton and cesium) are used to
measure the local total magnetic field. Anomalies in the data are then selected by an
interpreter and analyzed for ordnance detection.
Several manufacturers supply a variety of commercial magnetometers. The proton

precession magnetometer sensor measures the precession of spinning protons of a
hydrocarbon fluid to determine the magnetic field intensity. A cesium vapour
magnetometer sensor comprises a miniature atomic absorption unit from which a signal
proportional to the intensity of the ambient magnetic field is derived.
One difficulty with interpreting total field magnetic data is anomaly complexity. The
shape, orientation, susceptibility, permanent magnetization and distance and direction to
94 Appendix 1: Theory
the magnetic body are all factors to consider in interpreting the magnetic data. Also, the
direction of the magnetic field of the earth must be taken into account.
Of all these considerations, the permanent magnetization is often a very significant

factor when searching for magnetic anomalies. When a man-made ferrous object cools,
the earth‟s magnetic field magnetizes the body in the same direction as the earth‟s field.
However, as soon as the body is moved, this “permanent magnetization” is no longer
parallel with the earth‟s field. Because of this, the direction of permanent magnetization
of a man-made ferrous object is almost-always different to the local magnetic field
direction. Figure 1 (page 95) shows the effect on the magnetic response when you vary
the direction of the permanent magnetization. Note that an extended metallic body is
more easily magnetized along its major axis.
It is important to note that when a magnetic body suffers an impact (e.g. it is dropped
from a plane and hits the ground), its magnetic history (permanent magnetism) is usually
erased because the energy dissipated through the object and randomly re-orientates all
the magnetic dipoles in the body. So permanent magnetization may not always be a
useful indicator of an anomaly.
When dealing with magnetic field data, the goal is to simplify the complex information
contained in the original data. montaj UX-Detect uses the 3D analytic signal
(Nabighian, 1984; Roest et al., 1992; MacLeod et al., 1993) and Euler‟s homogeneity
relationship (Reid et al., 1990) to determine the plan location and apparent depth of
magnetic sources.
Typically, only a few of the survey area targets can be positively identified by the total
field magnetics. They are usually better represented by the calculated vertical gradient.
However, even with the vertical gradient there still exists the problem of locating the
centre of the source and more importantly, the effects of permanent magnetisation.
As shown in Figure 1 (page 95), 3D analytic signal results show a positive peak over the
centre of each UXO, with the shape indicative of the type and orientation. The
amplitude of the 3D analytic signal of the total magnetic field produces maxima over
isolated magnetic sources regardless of the direction of the magnetization (MacLeod et
al., 1993).
The amplitude of the 3D analytic signal at any location can be derived from the three
orthogonal gradients of the total magnetic field using the expression:
2
dT 2 dT dT 2
A( x , y ) = ( ( ) +
dx
(
dy
) +( )
dz
)
where:
A( x , y ) is the amplitude of the analytic signal at ( x , y )
T is the observed magnetic field at ( x , y )
For a total magnetic field grid, the 3D analytic signal is calculated utilizing a simple 3x3
convolution filter to find the (x,y) horizontal gradients and a Fast Fourier Transform
(FFT) to find the (z) vertical magnetic gradient. When the vertical gradient is measured
directly using a gradient magnetometer, the FFT is used to create a total field grid, which
is then used to determine the two horizontal derivative grids.
Magnetic
Field
Profile (nT)
Buried
Drums
(depth)
Magnetic
Field Plan
(nT)
Analytic
Signal Plan
(nT/m)
3-D Euler
Deconvolut
ion
Modelling
Figure 1: Magnetic Data and Processed Results over Buried Drums
Data is modelled over buried drums with three orientations of permanent magnetisation.
The 3D analytic signal reduces anomaly offsets due to magnetic field direction and
remnant magnetisation.
After the analytic signal is calculated, montaj UX-Detect uses the Blakely algorithm
(Blakely and Simpson, 1986) to automatically find peaks in the gridded analytic signal
data. This test analyzes for peaks in up to 4 directions around each grid cell (left-to-
right, up-and-down, and two diagonals). If the grid cell being examined has a higher
value than those do on all sides, it is selected as a target. (Note that the location can thus
be determined only to the nearest grid cell location.) After the initial automatic
selection, you can use various methods to reduce or increase the number of picked
targets, or you may edit the list of target locations directly.
Following the selection of target locations, the apparent depth to the magnetic source is
derived from Euler‟s homogeneity equation (Euler Deconvolution). This process relates
96 Appendix 1: Theory
the magnetic field and its gradient components to the location of the source of an
anomaly, with the degree of homogeneity expressed as a “structural index”
(Yaghoobian et al., 1992). The structural index (SI) is a measure of the fall-off rate of
the field with distance from the source. Euler‟s homogeneity relationship (Reid et al.,
1990) for magnetic data can be written in the form:
x  x0  T   y  y0  T z  z0  T  N B  T 
x y z
where:
x0 , y0 , z0 is the position of the magnetic source

whose total field (T) is detected at (x, y, z,).
B is the regional magnetic field.
N is the measure of the fall-off rate of the magnetic

field and may be interpreted as the structural index (SI).
We have already calculated the three gradients (generated for the 3D analytic signal)
required for the Euler Deconvolution process. This process is applied at each target to
determine the apparent depth results.
The method involves setting an appropriate SI value and using least squares inversion to
solve the equation for an optimum xo, yo, zo and B. As well, a square window size must
be specified which consists of the number of cells in the gridded dataset to use in the
inversion at each selected target location. The window is centred on each of the target
locations determined in the previous step. All points in the window are used to solve
Euler‟s equation for target depth, inversely weighted by distance from the centre of the
window. The window should be large enough to include each target anomaly of interest
in the total field magnetic grid, but ideally not so large as to include any adjacent
anomalies.
The structural indices for simple models in a magnetic field are summarised in Table 1
(following page). The “cultural model” description is in relation to the instrumentation
dimensions. For example, a long pipe must be “long” enough that it is essentially
infinitely long as far as the magnetic response at the target location is concerned.
Decimal values (e.g., 2.7) may also be used. The default setting for the montaj UX-
Detect is 3.0, since UXO can most readily be represented as a sphere (unless they are
very close to the surface).
Table 1: Structural Indices (SI)
SI
1.0 Large Sheet

2.0 Long Pipe
3.0
The advantages of this technique over conventional depth interpretation methods (i.e.,
characteristic curves, inverse curve matching, etc.) are that no particular geological or
cultural model is assumed, the target analysis process is objective, and the process can
be directly applied to large gridded data sets.
Apparent weight calculations are obtained from the magnetic data using a reference grid
(UXOKG.GRD). Given the 3D analytic signal data calculated above, which is directly
related to magnetic moment, and the calculated apparent depth of the magnetic source,
the apparent weight can be found. The table of weight information included in the
lookup table is based on theoretical and empirical evidence (Pennella, 1982).
Understanding the Transient Electromagnetic Method (TEM)

In the transient electromagnetic method (TEM), one established system (the Geonics
EM61-MK2) is the most common for detection and analysis of buried metallic objects.
The EM portion of montaj UX-Detect is specifically oriented to the EM-61 instrument.
In the EM-61, two coils, which serve as a transmitter and a receiver, are situated on or
near the earth surface. A steady voltage is applied to the transmitter coil for a
sufficiently long time to allow turn-on transients in the ground to dissipate. The current
supplied to the transmitter (bipolar rectangular current) is sharply terminated at each
cycle. A rapid reduction of the transmitter current, and thus of the associated transmitter
primary magnetic field, induces an electromotive force in nearby conductors.
This electromotive force causes electrical eddy currents to flow in conductors with decay
characteristics that are a function of the conductivity, size, and shape of the conductor.
The decaying currents generate a secondary magnetic field that is detected and measured
by a receiver coil. The measured quantity is usually the response of the instrument to
metallic objects or the apparent conductivity of the material (Pawlowski, 1994).
The EM-61 consists of a transmitter with a peak power of 100W that generates a pulsed
primary magnetic field, which induces eddy currents in nearby metallic objects. The
decay of these currents is actually averaged over 4 time gates. EM61-MK2 has 2 distinct
modes. In the regular mode all 4 gates are read on the lower coil centered at 216 μs, 366
μs, 660 μs and 1256 μs. In the differential mode, lower gates 216, 366, 660 as well as
the coinciding time gate 660 on the upper coil are measured. The reader is referred to
the Geonics technical material for further details.
.
98 References
References
Blakely, R. J. and Simpson, R. W., 1986, Approximating edges of source bodies from
magnetic or gravity anomalies: Geophysics, v.51, p. 1494-1498.
Geonics Limited, 1993, „EM61 High sensitivity metal detector‟, Operating

Instructions, Geonics Publication, Mississauga, Canada.
MacLeod, I. N., Jones, K. and Dai, T. F. 1993, „3-D Analytic signal in the
interpretation of total magnetic field data at low magnetic latitudes‟, Exploration
Geophysics, 679-688.
Nabighian, M.N. 1984, „Toward a three-dimensional automatic interpretation of

potential field data via generalized Hilbert transforms: Fundamental relations‟,
Geophysics 49, 780-786.
Pawlowski, J. 1994, „Ordnance Investigation Using an Electromagnetic Method, Lake

Erie, Port Clinton, Ohio‟, report for USAE Waterways Experiment Station, by
Geomar Geophysics Ltd., Mississauga, Ontario.
Pennella, John J. 1982, „Magnetometer Techniques in the Detection of Projectiles‟,

NAVEODTECHCEN Technical Report TR-239, Naval Explosive Ordnance
Disposal Technology Center, Indian Head, Maryland.
Reid, A. B., Allsop, J. M., Grasner, H., Millett, A. J., and Somerton, I. W. 1990,
„Magnetic interpretation in three dimensions using Euler deconvolution‟,
Geophysics, v. 55, 80-91.
Roest, W. R., Verhoef, J. and Pilkington, M. 1992, „Magnetic interpretation using the
3-D analytic signal‟, Geophysics v. 57, 116-125.
Yaghoobian, A., Boustead, G. A., and Dobush, T. M. 1992, „Object delineation using
Euler‟s Homogeneity Equation‟, Proceedings of SAGEEP ‟92, San Diego,
California.
Glossary 99
Glossary
Array channels Special channels in columns of the spreadsheet that
contain multiple channels of data. Array channels are
represented graphically by a curve in the spreadsheet.
See also channels, sub-array channels.
channels In the Oasis montaj spreadsheet, a channel is

essentially a column that contains a specific type of
data.
column In the Oasis montaj spreadsheet, a vertical line of cells

that contain data.
database See Oasis database
desktop Background area in the Oasis montaj project. You can

open and display a virtually unlimited number of
Spreadsheet, Profile and Map windows in this area.
fiducials Points accepted as fixed bases of reference. A mark

that indicates the order in which each reading or
sample reading was taken.
Geosoft Database A proprietary binary database architecture that stores

(.GDB) spatial data in a format that enables rapid access,
processing and analysis of high volume data (tested up
to 10 gigabytes).
Graphical User Interactive software environment where functions are

Interface performed by selecting graphic objects.
grid Collection of points along rows and columns that

define a two-dimensional rectangular area on some
plan, usually a ground plan.
Grids or Grid file Files containing location (X and Y) and data (Z)
values. Values are typically interpolated to create a
regular and smoothly sampled representation of the
locations and data.
groups A set of graphics elements that make up a graphic

component of the map. For example, a line path plot, a
contour plot or a profile plot would all be separate
graphics groups within the Data View.
GX or Geosoft Programmed process (identified by the *.GX file

100 Glossary
eXecutable extension) used to process data in Oasis montaj.
Images or Image Files containing location (X and Y) and color values.

file The values are not interpolated. Standard PC file types
created using imaging or electronic photo-editing
techniques.
line Linear array of observation points.
Main window Primary tool used to create and maintain databases,

display data and process data. Oasis montaj is a
Graphical User Interface (GUI) system that provides
all functionality required to process and display
virtually any type of Earth Science data.
Map (*.MAP) Geosoft-developed file that integrates all graphics

elements (lines, polygons and text) and layers (base
maps, data, grids, plots and images) constructed in
Oasis montaj.
map description file File used when making a standard map that has a sheet
(*.MDF) size and margins inside which there is a map area with
a specified origin and scale. Usually, MDF files are
created with the MAPSET GX. MDF files may also be
created manually by editing an ASCII file with
extension .MDF.
menu (*.OMN) Graphical list of commands or functions that a user

may choose from.
Oasis montaj Oasis montaj is the core software platform that

provides all functionality required to manage,
manipulate, visualize and map spatially located Earth
Science data.
Project (*.GPF) Binary file that defines a desktop environment. It is

essentially an “electronic briefcase” that helps
organise data and the activities related to a data
processing project.
random XYZ data Located XYZ data that cannot be grouped naturally
into separate lines. For example, regional gravity
surveys or geochemical surveys are commonly
considered random data because the locations appear
somewhat random in nature.
row In the Oasis montaj spreadsheet, a horizontal line of

Glossary 101
cells that contain data.
Sub-array channels Individual channels of data from an array channel.
template A file used to manage data in a particular format.
View Stored snapshot of the screen settings, current line,

displayed channels and displayed profiles in Oasis
montaj.
102 Index
Index
Adding Base Station, 20
missed targets from a Map, 59 Instrument Drift, 24
missed targets from a Profile, 62 offset, 24, 38
Amplitude Offset, 39
cut-off, 55 Creating
Analytic signal, 94, 96 Line list table, 37
amplitude, 95 Cut-off amplitude, 55
background value, 68 Data
grid combining, 65
creating, 45 Data Preparation, 15, 45
one-step process, 50 importing, 15
Step-by-Step process, 45 Database
Analytical Signal Grid Oasis, 20
Displaying, 48 Displaying
Apparent conductivity, 98 target map, 79
Apparent depth, 96 target plots, 78
Apparent weight, 68, 97 Dynamic links, 82
AutoCAD files, 86 Electromagnetic induction, 93
Automated peak-picking, 54 Electromagnetics, 93
Base map EM-61
latitude/longitude annotations, 80 data processing, 91
north arrow, 80 using, 97
reference grids, 80 Error
scale bar, 80 magnetic depth, 68
titles, 80 Euler
Base station deconvolution, 96
magnetometer, 20 Euler window size
Quality Control, 20 calculating, 65
Base station corrections, 20 description, 65
Blakely algorithm, 96 Ferro-magnetic objects, 93
Buried drums, 95 Fiducials, 38
Calculating Filters
Analytical Signal Grid, 48 low-pass, 20
Calculating non-linear, 20
apparent depth, 65 Geological structures, 93
Calculating Geonics Data
target depths and weights, 66 Dump, 18
Calculating Gridding
magnetic depth, 68 horizontal derivative, 47
Calculating vertical derivative, 45
apparent weight, 68 Grids
Calculating total magnetic field, 95
target depths from EM data, 68 Horizontal derivative
Calculating Calculating, 47
magnetic weights from EM depths, 68 smoothing, 48
Calculating Instrument Drift
vertical gradient, 94 Corrections, 24
Calculating Line List Table
apparent weight, 97 creating, 37
Corrections Information, 37
applying, 19 Line List Table:, 37
Base station, 20 Low-pass filter, 20
Glossary 103
Magnetic Surveys
direction, 94 ground-based, 93
method, 93 Target
response, 94 Edit Target Symbol, 75
Magnetic data Target Management, 69
interpretation, 94 Target plots
total field, 94 displaying, 78
Magnetic depth Target Utilities, 77
calculating, 68 Merge UXO Targets, 73
error, 68 Move a UXO Target, 72
Magnetic Field Profile, 95 Remove a UXO Target from the Target List, 71
Magnetization Remove Multiple UXO Targets from the Target
permanent, 94 List, 72
Magnetometer Resample Grids from Target Locations, 77
base station, 20 Reset Target IDs, 77
Magnetometers Targets
cesium, 93 adding manuallyfrom a Map, 59
EM-61, 97 adding manuallyfrom a Profile, 62
proton, 93 apparent depth, 65, 96
montaj UX-Detect menu, 5 automated peak-picking, 54
Non-linear filter, 20 Blakely method, 54
Oasis database, 20 calculating depths and from EM data, 68
Offset correction calculating depths and weights, 66
applying, 24, 39 calculating magnetic weights from EM depths,
description, 38 68
Orthogonal gradients, 95 calculating size, 65
Path Corrections digitizing, 61
Sensor Offset Correction, 32 locating, 54, 57
Warp a Database, 30 mapping, 79
Path Corrections:, 30 missed, 58
Permanent magnetisation, 94 Peakedness method, 56
Plot selecting, 96
targets, 78 windowing
Polygons results, 69
digitizing, 61 Theory, 93
Processing To Create a Project, 9
EM-61 data, 91 Total field processing, 91
Magnetic and EM-61 data, 65 Total magnetic field, 94, 95
sequence, 5 grid, 95
total field data, 91 Transient electromagnetic method (TEM), 97
Project UXO targets. See Targets
Creating, 9 UXO Theory, 93
Quality Control Vertical derivative
Coverage Area, 43 Creating grid, 45
Coverage Map, 40 Vertical gradient
Quality Control:, 40 calculating, 94
Smoothing Windowing
horizontal derivative, 48 Euler, 65
Spikes, 20 results, 69
Structural index, 67, 97 XYZ Files
definition, 96 importing, 16

Monta Jux Detect

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Monta Jux Detect

Transféré par

Droits d'auteur :

Formats disponibles

montaj UX-Detect

UXO Target Analysis Extension for Magnetic,

TUTORIAL and USER GUIDE

Manual release date: 8/22/2010.

Written by, Nancy Whitehead. Please send comments or questions to

Copyright © 2010 Geosoft Inc. All rights reserved. Geosoft is a registered

Windows, and Windows NT™ are either registered trademarks or trademarks

Queens Quay Terminal

Web Site: www.geosoft.com

Geosoft Software License Agreement 1

Finding More Help Information 4

Contacting Technical Support 4

montaj UX-Detect Overview and Capabilities 5

Who is this software intended for? 5

montaj UX-Detect Menu and Processing Sequence 6

Before you begin 9

Working with the Project Explorer 10

Loading the UX-Detect Menus (First time use) 11

Chapter 1: montaj UX-Detect Tutorials 14

Before you begin 15

Tutorial 1: UX-Data Preparation 15

Tutorial 2: UX-Parameter Determination 45

1VD Magnetic Data 45

Tutorial 3: UX-Target Management 69

Target List Management 69

Chapter 2: Total Field and EM-61 Data Processing 91

Total Field Data 91

The Magnetic Method 93

Understanding the Transient Electromagnetic Method (TEM) 97

Geosoft Software License Agreement

5. PROTECTION AND SECURITY OF LICENSED PROGRAM

Finding More Help Information

Contacting Technical Support

North America Europe and North Africa

montaj UX-Detect Overview and Capabilities

Who is this software intended for?

montaj UX-Detect Menu and Processing Sequence

UX-DataPreparation UX-ParameterDetermination UX-TargetManagement

Before you begin

2. Start Oasis montaj.

Working with the Project Explorer

Loading the UX-Detect Menus (First time use)

T O C LEAR E XISTING M ENUS

T O S ET UX-D ETECT AS Y OUR D EFAULT M ENU (F IRST T IME O NLY )

Chapter 1: montaj UX-Detect Tutorials

Tutorial 1: Data Preparation (page 15)

Before you begin

Tutorial 1: UX-Data Preparation

T O I MPORT AN XYZ F ILE :

1. On the UX-DataPreparation menu, select Import|Import Data. The Import survey

Editing Header Cells

T O E DIT THE C HANNEL H EADER C ELLS :

D UMP G EONICS I NSTRUMENT TO F ILE

Use the menu option UX-DataPreparation|Import|IDownload data from Geonics

Note: The Heading Correction option is available in the UX-Process software

A PPLYING M AGNETIC B ASE S TATION C ORRECTIONS

The magnetometers used in geophysical surveys measure minute variations in the

Quality Control on Base Station Data

Applying Base Station (Diurnal) Corrections to a Database

T O A PPLY B ASE S TATION (D IURNAL ) C ORRECTIONS TO A D ATABASE :

2. On the UX-DataPreparation menu, select Data Corrections|Base Station

8. Select the Basemag file tab.

specified, a warning message is displayed.

I NSTRUMENT D RIFT C ORRECTIONS