Geomage GPlatform Manual July-2017

g-Platform©
Seismic Data Processing Software

User’s Manual
Page 1 of 171 July, 2017
www.geomage.com info@geomage.com
Contents
Introduction ........................................................................................................................ 5
How to use this manual .................................................................................................. 5
Chapter Description ........................................................................................................ 6
System requirements ...................................................................................................... 8
Mouse button guide ....................................................................................................... 8
Keyboard Shortcuts......................................................................................................... 9
Chapter 1: g-Platform© Main Window ............................................................................ 10
Project Tree ................................................................................................................... 11
Flow Viewer .................................................................................................................. 12
Workflows ..................................................................................................................... 12
Templates...................................................................................................................... 13
Workflow History .......................................................................................................... 15
Project Data .................................................................................................................. 17
Global Properties .......................................................................................................... 19
Jobs ............................................................................................................................... 20
Re-arranging panels and Columns ................................................................................ 20
Chapter 2: Creating a New Project in g-Platform ............................................................. 26
Adding a new Database ................................................................................................ 26
Adding a New Project ................................................................................................... 30
Adding Flows to a Project ............................................................................................. 32
Using Templates............................................................................................................ 33
Creating New Templates............................................................................................... 39
Chapter 3: g-Navigator ...................................................................................................... 42
Main menus and Toolbar .............................................................................................. 43
Module Manager .......................................................................................................... 44
Module Properties ........................................................................................................ 45
Graph View.................................................................................................................... 48
Help View ...................................................................................................................... 49
Tracking info.................................................................................................................. 50
View Manager ............................................................................................................... 51
Vista Items from DB ...................................................................................................... 51
Progress View................................................................................................................ 52
Output View .................................................................................................................. 52
Chapter 4: Building Flows ................................................................................................. 53
Adding Modules ............................................................................................................ 53
Read SEG-Y Traces & Read Seismic Traces ................................................................... 53
Connecting data ............................................................................................................ 54
Gather Seismic & The Seismic loop .......................................................................... 58
Other Special Modules.............................................................................................. 61
The Sub-sequence ..................................................................................................... 61
Saving Data.................................................................................................................... 62
Saving other data items ................................................................................................ 63
Executing Flows............................................................................................................. 66
Special Actions .............................................................................................................. 68
Saving Workflows and Workflow revisions .................................................................. 70
Chapter 5: Distributed Execution and The Coalition ........................................................ 71
Connecting to the Coalition .......................................................................................... 71
The Coalition Window................................................................................................... 71
Jobs ........................................................................................................................... 71
Workers ..................................................................................................................... 72
Activities and Logs..................................................................................................... 73
Distributed Execution ................................................................................................... 73
Chunks – How data is distributed ............................................................................. 74
Chapter 6: Views and Vistas.............................................................................................. 77
Adding Views................................................................................................................. 77
View Manager ............................................................................................................... 82
View Windows .............................................................................................................. 83
Interactive Views........................................................................................................... 84
Zooming Views, and moving around inside views ........................................................ 85
Re-Arranging Views ....................................................................................................... 86
Spectral Analysis Tool ................................................................................................... 88
Ruler .............................................................................................................................. 91
View properties............................................................................................................. 92
View Properties ......................................................................................................... 96
Vista Items............................................................................................................... 103
Vista Items Properties ............................................................................................. 104
Other view parameters ............................................................................................... 114
Export Images ............................................................................................................. 128
Chapter 7: Sample Flow Work Through .......................................................................... 130
Appendix 1: Header definitions ...................................................................................... 164
Header list in Program default order: ......................................................................... 164
Header list in Alphabetical order: ............................................................................... 166
Table of Tips and Questions............................................................................................ 168
Index................................................................................................................................ 169
Introduction
This manual is intended for users who want to process seismic data using the g-
Platform© geophysical software.
The way this manual is written should suit any audience already familiar with the
fundamental technology of seismic data processing, but it is intended to act as a guide
but not as a tutorial. Note that the capabilities of the software are not limited to the
minimal processing sequence described here and that the software can be customized
to suit the users.
How to use this manual

This manual is designed to familiarize you with the various panels, windows, and
features of g-Platform©. It does not contain documentation on specific modules or
procedures, but should instead give you the tools and skills required to build databases,
projects and workflows on your own. Module documentation can be found inside g-
Navigator in the Help View panel, and online at our YouTube Channel. Each chapter is
designed to stand on its own, but some
chapters may refer to information found in Tip: we will use “database” and
earlier chapters. Refer to the chapter “DB” interchangeably in this
description in the next section for more manual, and within g-Platform©
information on what these chapters cover.
1 – Tip: Databases and DBs
Inside chapters you will find blue tip boxes like the one above, and grey Question boxes,
like the one below. These boxes contain additional information that may help you use g-
Platform© more efficiently, or help to clarify the way that the program works.
The final chapter of this manual is a

Question: Where else can I go for help? walk-through of a sample flow that
The Geomage YouTube channel has full combines information from all of the
video tutorials on specific modules and previous chapters.
features. Additionally, you can go to our
website: www.geomage.com and try a live Lastly, you can refer to the table of
chat with a member of our support team. Contents, the Index, and the table of
Finally, you can email us at
Tips and Questions to search this
support@geomage.com with questions,
manual more closely.
concerns or comments.
2 – Question: Where else can I go for help?
Chapter Description
The Introduction covers the system requirements, and basic functions, such as mouse
button control, and keyboard shortcuts.
Chapter 1: g-Platform© Main Window describes the function of various panels

present in the main program window. This chapter also covers how to re-arrange panels
within the program, and customize the information shown by the various panels (Re-
arranging panels and columns).
Chapter2: Creating a New Project in g-Platform© is about how creating new databases
and new projects in the system (Adding a New Database and Adding a New Project). It
also describes how to add new flows to a project, and how to use templates. This is a
good place to start if you are new to the program, and would like to start processing
your own projects right away. It also covers the basics of what a database is.
Chapter 3: g-Navigator describes all the panels available in the main g-Navigator
window, similar to the descriptions covered in Chapter 1. g-Navigator is the portion of
the program in which all data processing takes place, and is also the program that opens
when a user opens a flow. IN addition to panel descriptions, this chapter covers the
various toolbars and buttons (Main Menus and Toolbar), and many other useful
features available in g-Navgator via these panels, including mouse tracking (Tracking
info) , module documentation (Help View), and module execution progress (Progress
View).
Chapter 4: Building Flows covers how to build flows to process data within g-Navigator.
Data is processed in this system by building flows out of modules. This chapter covers
Modules (Adding modules), reading in seismic data (Read Seg-Y Traces & Read Seismic
Traces), Connecting data to modules, and connecting modules to eachother (Connecting
Data), Saving seismic data to the database (Saving data), and executing flows (Executing
flows). This chapter also covers additional actions available inside modules that are
related to their interactive properties (Special Actions), and saving other types of data,
such as Deconvolution operators or velocity picks to the database (Saving Other Data
Items). Finally, this chapter also covers saving workflows (Saving Workflows and
Workflow revisions).
Chapter 5: Distributed Execution and the Coalition covers the coalition (which requires
a special g-Platform© licence), and running modules in distributed execution. There is
information on connecting to the coalition (Connecing to the Coalition), the Colition
window itself, and running flows in a Distributed Execution via the coalition.
Chapter 6: Views and Vistas describes the windows (aka. Views) inside g-Navigator that
display data, tables, and other information that is generated by modules (vistas). It
covers the various ways someone can add views to gNavigator (Adding Views), The
View Manager, and adding new windows inside the view manager to hold vistas (View
Windows). It describes how to change the properties of those views (View Properties,
Other View Parameters), how to zoom and move around inside views (Zooming Views,
and Moving around inside views), and how to Export Images. Finally, it also describes
useful tools that are available inside views and vistas, including the Spectral Analysis
Tool and the Ruler (which operates in combination with the Tracking Info panel).
Chapter 7: Sample Flow Work Through provides a working example of the things
described in the previous chapters. In this chapter, we build an SC Deconvolution flow,
and go through adding the modules, connecting the data, adding the views from those
modules, running the flow, and saving out the final result
System requirements
Operating system:
64-bit; Windows 7/8; Linux RH/CentOS 6.x/7.x
CPU: 2 cores minimum. g-Platform© designed to work in multi-thread mode in order to

get optimum performance.
Disk: SSD storage for seismic prestack (recommended) and HDD drive for the rest of the
project data.
RAM: 16GB per 100M prestack traces.
GPU: NVIDIA GPU card with at least 1GB RAM (recommended).
Mouse button guide

Actions that can be applied to any mouse button include:
• Click: Briefly depress the mouse button.
• Double-click: Quickly depress the mouse button twice.
• Shift-Click: Hold the shift key while depressing the mouse button.
• Ctrl-Click: Press the Ctrl key while depressing the mouse button.
• Drag: Hold down the mouse button while moving the mouse.
• Scroll: Use the mouse wheel located between the left and the right mouse
buttons for scrolling.
Keyboard Shortcuts
General
F2 – re-name. Use this key to re-name projects, flows modules, windows and views
Insert – Replicates the button for the current window
Delete – Replicates the button for the current window
g-Navigator
CTRL + n – New Blank Workflow
CTRL + s - Save Workflow
CTRL + SHIFT + s – Save Workflow revision
CTRL + C – Copy
CTRL + V – Paste
ALT + E – Execute/Stop Execution of Module /
ALT + SHIFT + E – Execute all modules
SHIFT + F11 – Hide all panels
Chapter 1: g-Platform© Main Window
Once you have launched g-Platform©, you will see the main window:
The g-Platform© main window is used for creating and managing projects and
databases. It enables users to view the project tree, switch between different projects,
and connect/disconnect databases.
The main window consists of several panels including:
Project Tree
The Project Tree contains a list of existing projects, databases and storage paths and is
used to navigate between different project surveys. See Chapter 2: Creating a New
Project in g-Platform© for more information about this panel
You can search the project tree or press Ctrl + D:
Using the tool panel you can:
• Add project and DBs (databases)

• Delete projects and DBs (databases)
• View Properties
• Open a DB
• Close a DB
• Move Projects up and down
• Export or Import DB/project with data
• Try to repair DB from backup
Flow Viewer
Consists of a Module name, Module Parameters and a Graphic flow chart of the
workflow. You need to open a DB so the “Flow viewer” will be visible.
Workflows
Allows users to view the Modules used in the workflow, check revisions and compare
results.
You can search Workflow by typing in the search field or by pressing Ctrl + W.
Templates
Templates are used as standard workflows for performing different processing
procedures in the g-Platform©. They consist of combinations of modules and are easy
to modify. We go into more detail about Templates in Chapter 2.
You can use the Templates tool bar to do the following:
• Delete a Template
• Open a Template
• Export a Template
• Import a Template
• Copy a Template
• Paste a Template
Workflow History
Consists of Revision and Module/Item panels.
You will see a list of workflows used in the current project and their versions. Every
version has a different creation date and time.
The Revision panel allows you to:
• Open a revision , or double click on the revision name.

• Export a revision
• Copy a revision
• Compare a Revision
• Execute a Revision
• Test a revision
You can open any revision of a flow in the same manner as you would a regular flow.
The Module/Item panel allows users to view the modules applied in the workflow and
information about them. Information about each specific module in the flow appears in
the bottom window after you select that module.
Project Data
Contains important details as Nickname, Binary data size, Creation date and File storage
paths.
Project data can be deleted by selecting the item name in question, and hitting the
delete key on your keyboard
Global Properties
You can Add, Delete and Open Global Property using these three buttons on the panel:
You can search property by typing in this field or by pressing Ctrl + P.
Jobs
This section contains a list of flows applied in particular projects.
To delete a job, click on the red cross.
Re-arranging panels and Columns

The g-Platform© software provides a flexible user interface which allows the user to
customize their workspace on the screen, make changes and save their own preferred
settings.
Now we can:
• Modify the size of every information panel.

• Drag and move the panels around the screen to change their position.
• Hide unnecessary panels as well as columns and headers.
Let's start with the Project Tree and organize it the way you want. As you can see there
are a few different columns with related details such as:
• DB/Project Name
• Flow/History Path
• Binary Data Path
• Owner
• Version
Right-click on the headers panel and click Select columns
The ‘Select columns to show’ dialog will appear. Uncheck the column headers you don’t
want to see and click .
This is how the Project Tree looks like now:
To change the width of the panel, position the mouse on the right border of the panel
until a horizontal line with arrows appears:
You can change the position of any panel by simply clicking and dragging it freely until
you see a suitable location for it. A blank panel will appear with the shape that your
panel will take once you place it there.
Once you are satisfied with the new position, release the mouse and the panel will fit
into the new position automatically.
You can also group panels together by dragging the panel you want to add and placing it
close to the title of the panel you want to group it with.
Release the mouse:
Now you can switch between the all of these different panels by clicking on their tabs.
Tip: You can also switch between the tabs by pressing Ctrl key
and scrolling the mouse wheel. Please note, in order to use
this option the mouse cursor should be hovering above the
tabs in question.
3 – Tip: Switching between tabs
Chapter 2: Creating a New Project in g-Platform
Before we start performing data processing steps using g-Platform©, let's take a look at
how to create a new project. The project will contain the initial data, processing flows,
final results; all organized into a database created by the user. The project data can be
stored on a local workstation, virtual storage and networks.
Initially the Project Tree might look empty as if you’ve never launched g-Platform©
before.
Adding a new Database

To add a new database, click on in the top left corner of the screen.
Question: What is a Database? Do I need additional Database Software?

A Database is the basic unit of project organization within gPlatform. DBs are completely handled
within the program – you do not need addition al software to handle gPlatform Databases (DBs).
A DB consists of three main parts – Data storage, Flow/History Path, and the Binary data path.
Once the program has been installed, the average user only needs to worry about the Data
storage. This is the location on your computer or network where project data is actually stored –
and you set these locations by defining one or more storage paths when you set up a DB. Once a
DB and its storage locations is set up, the program automatically takes care of organizing and
retrieving all the data for you.
4 – Question: What is a Database? Do I need Additional Database Software?
A new window titled Create DB will open.
Type a name for your new Database in the Project Name field:
You will notice that the storage path is set by default

as D: /Data.
Tip: The locations you choose for
By clicking on the button you can add a new each storage path are the locations
at which all of your project data will
Storage path to your Database. A new window will
be stored, including all the data sets
appear where you can add your desired path name you write out. You can define
and a description or a name for your directory path. multiple storage locations, but
make sure that the locations you
Click on the button to select a path to an existing choose have enough space to hold
local drive or network for your database. This will the various pieces of your project.
allow g-Platform© to use relative paths to the data It is also helpful to delete the
files. default storage path if you do not
plan to use it.
5 – Tip: Data storage locations
Select a parent folder for your database and click .
To view the Flow/History and Binary Data Paths, click on the button.
Flow/History Path - Location where all history and workflow data will be stored. This
contains the most important data needed to reproduce the project, but takes up only a
very small amount of space on disk.
Binary Data Path - Location where all binary data associated with the project will be
stored. That information includes all data items, and occupies a lot of disk space at the
defined location. This data can be reproduced by rerunning workflows, but is required in
order to preserve previous results.
Tip: These two paths should point to a location to that is frequently backed up. They
create a project.bdb file at the defined location. These files are typically not large,
and do not contain any seismic data.
6 – Tip: Binary Data, and Flow/History Path locations
The new database will appear in the Project Tree. The Project Tree will contain a list of
existing databases and projects with these details displayed:
• DB/Project Name
• Flow/History Path
• Binary Data Path
• Owner
• Version
Adding a New Project

Every new DB has two projects included automatically by default – Survey 1 and Batch
Projects. You can rename these projects to anything you like, or you can create your
own new projects. To create a New Project, right-click on the name of your database
and select Add Project.
Enter the Project Name in the new window and click .
The new project will appear in the Project Tree panel just below the database.
Users can have any number of databases and projects defined.
You can add sub-projects underneath your main project by following the same
procedure. All of the projects within one DB share the same storage locations, so you
will be able to access data generated by one project in any other project within the
same DB. You cannot access data generated by projects in other DBs without first
importing that data into your active DB.
You can click on the button to minimize the view and hide the projects you don’t
want to see.
By clicking back on the button, you can expand the database tree and view the
projects you wish to see.
To rename your database, right-click on it and select Properties. You can then rename
your database in the Properties DB window.
Adding Flows to a Project
To add a new flow to the project Go to your Workflows window:
Click the button, or use the insert key on your keyboard to add a new workflow to
the project. A new dialogue window will appear:
Enter a name for your flow.
The new flow will appear in the workflows window under Flow name.
Double click the flow name to open it. Your new flow will open in g-Navigator.
It is also possible to add new flows to a project using pre-existing Templates
Using Templates
g-Platform© has a few preinstalled workflow
templates listed in the Templates panel. They are
used for implementing various data processing
workflows that can be exported, imported, copied
and pasted in g-Platform©.
When you click on a template name, you will see

the modules the workflow contains in the
Procedure Name part of the Flow Viewer panel.
Another way to get a full view will be to click on the name of the template in the bottom
part of the screen and click on the Open Template button.
Once we are familiar with the flow, we can use the selected template in our workflow.
There are three ways to do this:
1 - Click on the Open Template icon as described earlier. Or double-click on the
template to open it.
The Project Selection Dialog window will appear. Select your project and click next.
The template name will now be listed in the Workflows section:
2- You can use the buttons on the Templates panel to add a workflow. Select the flow
and click on Copy Template.
Go to the Workflows panel and click on the Paste Flow button
The flow will appear in the list of workflows.
You will see an enlarged version of the flow. Click Finish in order to add the template to
your workflow.
3- You can also press the insert button on the keyboard to add a flow. Enter the name of
the flow you wish to add and click OK. The Template to Flow Conversion Wizard will
appear.
Once you have added the template, the g-Navigator window will launch automatically:
You will see the selected 2D Binning template in
the Module Manager panel in the top right part Tip: Templates are common to all your
of the g-Navigator screen. DBs and all your projects, and, are thus
stored in a special DB of their own. You
Please, note that this flow is just an example and can check to see where your templates
you can remove and add new modules. are stored by finding their location in the
Geomage Config editor, found under the
Help tab:
Creating New Templates

It is simple to create new templates from your
existing flows. To do this, first choose a saved
flow from the workflows window that you would
like to use to create a template:
7 – Tip: Templates are stored in their own databases
Copy the flow with the button, and then go to the Templates panel and paste the
flow there with .
The Flow to Template Conversion Wizard should appear, displaying the outline of the
flow in question:
You can name your new template, and give it a description.
Hit Finish to create your template. It should appear in the Templates List, available for
use.
Chapter 3: g-Navigator
All Workflows will open in g-Navigator. This is the window in which you will do all
seismic data processing.
Similar to the main g-Platform© window, g-Navigator consists of several different

panels and toolbars
Main menus and Toolbar
The top of the g-Navigator window contains the main menu and the top tool bar. From
this toolbar you can:
• Save the current flow

• Save a Flow Revision: This will show up as a specific revision change in the
Workflow History window
• Open a New Flow
• Save the GUI state to file - This allows you to save your current arrangement
of windows to a file, that can be recalled later, in this or other flows
• Open a GUI state file - use this option to load a saved GUI file.
• Open the Coalition server (cluster version only)
• Hide all Panels - This button will dock and hide all the panels, leaving only the
views displayed. You can restore all the panels by clicking on their name, or by
clicking the button at the top of the section containing that panel
• Sync Views
• Run the entire flow
• Run the selected module in the drop down menu

• Cancel the current execution
• Switch between View windows
Module Manager
The tool bar of the Module Manager can be used to:
• Add new modules to a flow

• Remove Flows from a module
• Move a module higher or lower in the list
• Run an individual module
• Run all the modules in a flow, or run a loop all the way through
• Stop the execution of a module or flow
• Copy a module
• Paste a module
• Add all the views of the current module to the top window in the view manager
For more information on adding and removing modules, see Chapter 4: Building Flows
Module Properties
The Module Properties panel allows you set data connections, and change the
properties of a module inside a flow. The content of this window is specific to the
module highlighted in the Module manager.
There are several tabs across the top of the Module Properties window. Some or all of
these tabs can be active for any individual module.
Input data is where you set the incoming data for the module:
Parameters Is where you can adjust the properties of the module, including additional
inputs, and the parameters of how the module will run
Settings allows you to adjust how the module will run on your individual machine
Output Data shows you all of the individual data items output from this module. Some
data items can be saved as vista items to the data base by right clicking and selecting
“save to DB”.
Information shows specific information about the module that has run, such as the
number of traces read in.
Graph View
The Graph View panel is a visual representation of your current flow. It shows each
module, and the data connections between the modules.
Help View
The Help View panel will display the documentation for the module currently
highlighted in the Module Manager. Clicking on anything in the Module Properties
window will zoom the Help View panel to that heading in the documentation as well.
Tracking info
The Tracking info panel will display information from vistas containing gather or map
information at the location of the cursor. It will also display the output of measurements
made with the ruler ( ) on any vista
View Manager
The View Manager displays all of your active views, and all of your active windows, and
allows you to add new windows, delete existing views and windows, and switch
between windows
Vista Items from DB
Vista items from DB displays a list of vista items that have been saved to the data base
that can be displayed as a view in the main g-Platform© window. Items in this list can
be displayed by dragging them out into the main window, or on top of another view.
Progress View
This panel will display any tasks that are currently executing, and will display the type of
task, the approximate percentage completed, the start time of the task, the current run
time of the task, the number of chunks completed, the average time per chunk, the
approximate time remaining in the task, and the number of slaves being used, in the
case of multi-threading.
Output View
The Output View panel will display a summary of the tasks that have been run in the
Tip: You can re-arrange all of these panels, and dock them anywhere you wish. Re-
arranging panels in g-Navigator works in exactly the same manner as it does in
gPlatform (See: Re-Arranging Windows and Columns, [Chapter 1]). Panels can also be
detached from the sides and bottoms of the main window and be left floating. Use
this button to prevent a panel from docking, and this one to return the panel
to its previous docked position.
8 – Tip: Rearranging panels in gNavigatr
current flow. It will display the task name, the type of task, the start and stop time of
the task, and the status of that task (OK, stopped, failed)
Chapter 4: Building Flows

In this Chapter we will learn how to build a flow in g-Navigator. All the flows are built
inside the Module Manager of individual modules. The outputs of the modules are then
connected together to build a flow.
Adding Modules Question: What is a Module?

The Module Manager is where you can add or A Module is the basic unit of processing
remove modules from a flow. To add a new within g-Platform. A module is designed to
module to a flow, use the key, or insert on take in data, or trace headers, perform an
your keyboard to search the list of modules. operation on that data, and the output that
Modules are added when you click on them data in a format that can be then used by
To delete a module from the flow click on it and another module. Modules are connected
together within gPlatform to form flows
click the button to remove the selected
module.
9 – Question: What is a Module?
Read SEG-Y Traces & Read Seismic Traces

In a typical flow, the first step is to load in a SEG-Y or seismic data set. To do this, you
use the Read SEG-Y traces, and Read Seismic Traces module.
Read SEG-Y Traces is used when you want to work with an external SEG-Y file.
Read Seismic Traces is used when you want to work with seismic data already stored
within the g-Platform database in its internal format (.gsd)
Once you have loaded in some data, you are now freely add more modules to
manipulate that data.
Connecting data
Most modules that are not designed to read in external files (such as read SEG-Y traces)
require an input that was generated by another module. To connect that input, go to
the Input tab of the Module properties panel:
The required input here is “Input DataItem”. Double click on this item to select an input
(set a reference) for this item. When you do, the following dialogue will appear
By selecting the “read SEG-Y Traces” module in the “Set Reference” window, we can see
the item “Output DataItem” appear on the right. Output data item, in this case, is the
output of Read SEG-Y traces. Double click on this to set Output DataItem to the module
in question.
The entry will turn yellow, and we can see the reference is now set to the output of the
Read SEG-Y traces:
We can expand this input item to learn more information about it:
In this example, you can see that this module only requires input in the form of trace
headers, but by using the input DataItem tag, the trace
Tip: Check the Help view headers from Read SEG-Y traces are connected
panel for more guidance automatically.
on the type of data you
need for a module, and The information in the Input data tab can help you decide
what, exactly that how a module can be used, and where it should go in a
module does flow. In the following example, the module requires trace
headers and a SEG-Y data handle as an input:
10 – Tip: Check the Help View
You can check and see which modules output these items by checking the output data
tab. The output data tab for Read SEG-Y traces looks like this:
While the output data for Sort Traces looks like this:
Note, that this module only outputs the sorted headers. It does not output the SEG-Y
data handle. Match the outputs of your modules to then inputs of the next modules in
the flow.
Tip: For modules that require more than one

input (such as SEG-Y data handle and trace
headers), you can connect inputs from more
than one different module
11 – Tip: Modules that require more than one input
Gather Seismic & The Seismic loop

Some modules require an input in the form of Input Gather. These modules are
generally ones that will, in some way, modify the actual seismic traces of your data. So,
to use these modules, we need a module that will output the data item Gather.
That module is the Seismic loop. Seismic loop takes in a SEG-Y Data handle, and a set of
sorted headers, and outputs the item gather:
The Seismic loop is a special type of module that
contains other modules, and it forms a new layer within
your flow. Modules added to the Seismic loop will be
slightly indented to indicate that they are contained
within the loop.
The Seismic loop is also special, because the data connections between the modules are
set automatically. As soon as you add a new module to the loop, the item Input gather
will automatically be set to the output
gather of the module before it in the list Tip: Don’t set data connections in the Seismic
(or in the case of the first module, to loop yourself. Doing so can cause the
the output of the Seismic loop). automatic connections within the loop to fail,
Changing the order of items in the list which can cause errors. If you have
will automatically change the data accidentally set a data connection, delete the
connections between those modules module and re-add it to the flow
12 – Tip: Data connections inside the Seismic loop
Question: Why can’t I use the Gather output of Read SEG-Y traces or Read Seismic
traces?
You may have noticed that both of these modules have the item “output Gather” listed under the
output data tab. If these modules produce gather seismic outputs, why do you need to use the
Seismic loop?
The answer is that you can but, only under specific circumstances. Normally, these modules do not
automatically load all the traces of the data into RAM memory right away – in the case of un-
stacked data, to do so could stack the system. The Seismic loop breaks the data into manageable
chunks based on the input sort order, which allows us to operate on traces in smaller increments
than “all of them at once”.
However, if you have a very small seismic data set, such as a SEG-Y or seismic data set of stacked
data, you can force the program to load all the traces to RAM memory right away, by choosing
“yes” under Load data to RAM in the properties tab for the module:
With the data loaded to RAM memory, you can treat the output of Read SEG-Y traces and Read
seismic traces as gather seismic, and use it in any module that requires a gather output.
Remember: Only do this with small data sets.
13 – Question: Why can’t I use the Gather output of Read SEG-Y traces or Read Seismic traces?
14 – Tip: Set references to almost anything
Tip: You can set references to almost anything within gPlatform.

Try setting references for things like filename within the
parameters tab to other modules. You can even set references
to modules that exist within other flows in the same database –
go to the DB tab and find the flow and module you need, and
set the reference to an item from there.
Other Special Modules
Flow: The Flow module is another module that contains other modules.
This is useful for organizing your modules, if you wish to have multiple versions of the
same flow within the same g-Navigator window. Flow can also be used to safely
interrupt the data connections inside the Seismic loop. Modules contained by flow, set
inside a Seismic loop will not be automatically connected to the other modules inside
the loop. You may safely set these connections yourself.
Seismic Distributed Loop: This behaves similarly to the Seismic loop, but is designed to
be run in distributed execution. When using this module, you do not need to add a
separate Save Seismic by Gather module to save your data.
The Sub-sequence
Many modules have sections underneath them called Sub-sequence:
The sub-sequence is desigend to allow the user to perform pre-processing or post-

processing steps to the data without the need to generate additional data sets, for
modules that are designed to work outside the Seismic loop. The type of sub-sequence
is indicated by the name, although most sub-sequences are designed to perform pre-
processing steps.
Similar to the seisimic loop, modules added to the sub sequence of a process will be
automatically connected to the correct input for that process, and subsequent modules
will also be automatically connected to ones higher in the sub-sequence.
Saving Data
The end of a flow typically involves saving the products of this flow. There are several
modules you can use to do this
Save Seismic - is used to save data to the internal .gsd format. This module is designed
to take in data in the form of SEG-Y data handle and headers.
Save Seismic by Gather - is used to save data to the internal .gsd format. This module is
designed to take in data in the form of gathers.
Save SEG-Y – similar to Save Seismic by Gather, but is used instead to save data in the
external SEG-Y format.
Tip: As a rule of thumb, if you need to save data

outside the Seismic loop, use Save Seismic.
When saving data inside the Seismic loop, use
Save Seismic by Gather, and Save Seg- y
15 – Tip: Use Save seismic by gather inside the Seismic loop
Direct & Append

There are two save modes available in all of these modules. Direct mode and Append
mode. You may use either mode to save your data, but there will be circumstances
where one is faster than the other.
Direct mode saves your traces in their original sort order – that is, whatever sort order
your file was in when you read it in, that’s the order they will be saved out again as. So,
if your data was originally in an FFID sort, when you save it using Direct, you’ll get a new
data set that is in an FFID sort, regardless of anything else you’ve done. If traces arrive
to the save module (save seismic, save seismic by gather, or save seg-y) in an order
other than the original sort order – say for example you have changed the sort from
FFID to CMP, and are now running a seismic loop over CMPS – the program will hold
those traces in memory until they can be put into the file in the original sort order.
Append mode saves your traces in
whatever order they arrive to the Tip: The save mode is a more important
save module in. So, if you are consideration when using traditional Hard disk
running a seismic loop over CMPs, drive (HDD) storage, as the mode can
it will put the traces into the new dramatically impact I/O times. It is less vital
file in CMP order, regardless of the when using Solid state disk (SSD) storage, due
original file’s sort order. to the way data is written to SSDs.
16 – Tip: Saving on HDD vs SSD
Saving other data items

The Save Seismic and Save Seismic by Gather modules are useful for saving out your
seismic data sets, but there are other types of data you can save to the database.
Many modules will produce dataItems that are used in other modules that are not
seismic data, such as statics correction items, Amplitude and Deconvolution operators,
and velocity picking items:
You can save any one of these items to the data base by right clicking on the item in
question and selecting “Save to DB”
The new item will be saved in your data base, and can be recalled later by any module
that needs it. To set your reference to the new saved database item, go to the DB search
tab under the Set Reference window:
All the saved items of the required type will appear in this list, and you can select the
one that you need.
Tip: It’s a good idea to save operators and items like them to the DB instead of
setting the reference directly to the module that made them. This extra step will
ensure you will always have the same operators for the same data, and protect you
against changes.
17 – Tip : Save operators to the DB
Executing Flows
When your flow is complete, Select Flow next to Module on the panel bar and click on
the button to execute , or run the flow:
Or you can run the modules individually by clicking on the arrow as shown in the
picture:
In the drop down window you can select a specific module:
And click on the button Execute Module or press Alt + E
You can also do it from in the Module Manager by double-clicking on a selected

module, or by using the same buttons located at the top of the module manager
Once all input files are set, you can:
• Double-click on the Flow in the Module Manager panel to execute the flow
Or
• Click on the green button with double arrows to Execute All Modules
This will cause the modules to run one after another until it is complete.
- Currently in progress.
- Successfully complete.
- Failed.
You can observe the current status

Tip: You can also execute the Seismic loop at a of the job in the Progress View
specific location by clicking on that location in the panel. It will also show you the
Location Map vista. (See Chapter 5: Views and estimated time remaining and run
Vistas). This is a good option for module time elapsed, as well as the
parameter testing. module name. Seismic loop
The loop can also be executed at certain locations

by typing in the numerical value of that location
(i.e. Shot point) under “first”
18 – Tip: Run the Seismic loop at a specific location
Tip: When running the Seismic loop, the execute module button will run a single
iteration of the loop (i.e., if your input sort is shot point, the loop will execute for a
single shot point). To run the entire loop, use the execute all modules button . This
www.geomage.com
will run through the entire data set. Use this option when using Save Seismic by
info@geomage.com
Gather or Save SEG-Y

Once it is complete, the entry in the Progress View and Progress Bar will disappear.
Special Actions
Some Modules have additional actions that can be performed. These special actions are
found in a list that appears to the right of the module list in the module manager when
that module is selected:
19 – Tip: Executing the entire Seismic loop
These actions are generally unique to that module, and are generally related to its
interactive features. You can execute these special actions by clicking on the item in
question, or by using its associated keyboard short cut (shown in”< >” brackets next to
the action).
The keyboard shortcuts for any special action will not work if the current module is not
active (i.e., not highlighted in the module manager). The progress of an action will be
showed at the bottom of the screen by the progress bar, the same as if you had
executed a flow or module. The action is complete when the progress reaches 100%
Saving Workflows and Workflow revisions
While building a workflow, it is a good idea to save periodically using or CTRL+S.
You also have the option of saving a workflow revision with instead of just a
standard save. When you save a workflow revision, that particular version of the flow
will be marked out in your Workflow History panel in g-Platform©, to make it easier for
you to find that version of the workflow later.
Tip: Save your workflow before running the flow, or

before running a module. Running modules with
incorrect inputs, or with data that contains errors can
occasionally cause program crashes. Save to avoid re-
doing your work.
If you experience a crash: Make sure use the built –in

crash reporter to tell Geomage what has happened. This
helps to improve the software, and avoid crashes in the
future
20 – Tip: Save often.
Chapter 5: Distributed Execution and The Coalition
g-Platform© has the capacity to connect to a coalition server to perform parallel
processing. This requires a coalition licence of the software. This licence also comes with
full support from g-Platform© specialists, to help with the installation and set up a
coalition server. This chapter will cover connecting to the coalition, and using it for
distributed execution with flows
Connecting to the Coalition

Once the coaltion has been set up, you can open the Tip: The coalition software
coalition server using the globe button: is not compatible with all
browsers. If the coalition
The Coalition will then open up in its own browser window. does not open properly, re
Alternately, the user can get to the coalition window open the server using the
directly from their browser by typing in the IP address of Firefox browser. Firefox
their coalition server, or can be downloaded for free
at www.mozilla.org/firefox
From here, you can view all the jobs currently running,
completed jobs, and queued jobs. This window will also 21 – Tip: Use Firefox with the Coalition
show you which user started the job, and the expected
completion time of the job.
The Coalition Window

The top header of the Coaltion should look something like this:
To view an up-to-date version of the jobs running on the coaltion, hit the “Refresh”
button. To have this list update automatically, check off the Auto checkbox next to it
Jobs
Under the jobs tab, you can check on the status of the execution of any job. The
execution is divided into chunks, and the job is complete when all the chunks have
executed successfully. You can see all the chunks and their status by double click on job.
Every chunk has a state parameter, with a value of WAITING, WORKING, ERROR, or
FINISHED. Each chunk gets five attempts at execution before an error will occur.
You can restart the jobs using the “reset” button, or only restart failed chunks using the
“reset errors” button .
Every job has an affinity for a type of worker (Ie. CPU, GPU). If the affitinity and the
worker match, that worker will execute the job. You can change the affinity of your jobs
in the g-Platform© configuration
The bottom of the Jobs server window will show this:
Clicking on any job will show you the job, command, and the directory path that
contains the version of g-Platform© that was used for this job. You can change this
directory path in the configuration settings under “Help” in g-Platform©.
Workers
The Workers tab shows the type of workers available to complete jobs. For example if
you have five GPUs available, this will show you five workers with the affinity “GPU”.
Each worker has five properties: “Name”, “State”, “Affinity”, “Load”, “Memory”.
“Name” is the name of a worker, “State” shows a state of a worker. The “Affinity” field
shows affinity of a worker, AKA the type of the worker. “Load” shows processor usage of
a worker, and “Memory” shows memory usage of a worker.
Each worker can be in the states: TIMEOUT, WAITING, WORKING.
If a worker is out of order its state is TIMEOUT. If a worker is processing the job, its
state is WORKING. If a worker doesn’t have a job to process its state is WAITING.
To start a worker a user can select a worker from the list and press “Start” button, to
stop a worker a user can select a worker from the list and press “Stop” button.
A job will be executed on a worker depending on its affinity. You can see which affinities
of workers a job can be executed on by checking that parameter in the Geomage Config
Editor in g-Platform:
Nodes that match the Affinity under “value” will be used to execute jobs.
Nodes can be broken up into groups by assigning them different affinities (ie. GPU_1,
GPU_2). Users can be assigned to specific nodes by changing the affinities of those
nodes, and then by adjusting the affinity in the g-Platform config editor to match.
Activities and Logs

The activities and logs tabs show information about exactly those things – activities that
users have taken on the coalition, and logs related to individual jobs and chunks. The
logs for a chunk can be views by double clicking on that chunk.
Distributed Execution
To run jobs on the coalition, you need to run them in distributed execution mode. Not
all flows have a distributed exectution mode, for those that do, you can find this mode
under the settings tab in the Module Properties panel.
If the coalition server is open, this will automatically send the execution of this module
to the server.
There are also several modules that are

designed specifically to be run in a
Tip: Most modules that run in
distribued execution, chief among them
distributed execution will write data
the seismic distributed loop. Seismic
directly to a storage file or stored data
distributed Loop does the same job as the
item. This means that they do not
seismic loop, but is instead designed to
require a Save Seismic, or Save seimic
run in distributed execution. It is generally
by gather module. Make sure you set
a good idea to do parameter testing in a
the correct name for your output data
regular seismic loop, and then copy all
or storage file under the Input data tab
those modules into the distributed loop
of the module properties panel
when you are prepared to write out a final
version.
22 – Tip: Distributed modules save their own outputs
Chunks – How data is distributed

As mentioned earlier in this chapter, when using Distributed execution, your data is
broken up into chunks that are executed by the nodes on your coalition server.
The size of any given chunk is determed by the Bulk Size listed under Distribution
Options, under Settings:
In this case, the bulk size is referring to a number of gathers. For example, if you are
sorted to CDP, the bulk size, or chunk size will be 20 CDPS. As a general rule you should
set this parameter so that your job does not have more than 1000 chunks, to reduce the
server response time and increase efficiency, although this may be slightly different
from server to server.
When deciding on a chunk size, it is also important to consider the amount of RAM
available on your server. By default, the server will load up one chunk per active node
into memory. So, if you have 10 nodes, you need enough memory to load 10 chunks. In
addition, each node should have enough memory to run each chunk. It is generally a
good idea to have more RAM than required available to ensure things run smoothly and
avoid crashes
Example: If you have a 500 GB data set with 100 000 CDPS that you would like to run in
distributed execution on a 10 node server :
100 000CDPs / 1000 chunks = 100 CDPs per chunk

500 GB / 1000 chunks = ~ 0.5 GB RAM needed per chunk
10 Nodes x 0.5 GB/Chunk = ~5 GB RAM MINIMUM needed on the server.
Question: What if I don’t have enough RAM?

If you don’t have enough RAM on your server, you have a couple of options.
1) Stagger the Executiton: To do this, start your distributed execution, and
then go to the coalition server and pause all of your nodes save one.
Wait for that node to finish loading in the data, and then start the next
node, and so on until all of your nodes are in use.
2) Use Fewer Nodes: Go to the Workers tab in the coaltion window, and
change the affinity of the some of nodes to something else (ie. GPU_1).
Then, go to the Config editior in g-Platform and change the affinity
there to your new affinity. This will ensure that distributed processes
will only run on those nodes.
23 – Question: What if I don't have enough RAM? (distributed execution)
Chapter 6: Views and Vistas
Most modules inside g-Navigator have a set of Views that you can use to see the output
of a module. These views also allow you to use the interactive features of a module, if
any exist.
Adding Views
To see a list of the default views and vistas for a module, Right click on the module
name, and go to the Vista Groups section:
You can add any individual vista by clicking on it, or you can add all the views by
selecting “All Groups” at the bottom. This is the fastest and easiest way to add new
views, especially for interactive modules.
Question: What’s the difference between a Vista and a View?
While Vista and View can be used somewhat interchangeably, they are slightly
different. It’s helpful to think about a View as the frame around the window, and a
Vista as the content within that window. So, one view can contain one or more
vistas. For example, a map view could contain several different vistas, each one
displaying something different – one for shot points, another for receiver points,
and a third for the bin grid, or in another scenario, one view could contain two
different versions of a stack as different vistas.
24 – Question: What's the Difference between a View and a Vista?
Alternately, you can drag a module out into the main g-Navigator window and add a
view that way: vista
Left click the module name and hold it to drag:
Bring the module to the main section of the screen and release. The following window
will appear:
In this example, we’re creating a seismic view, to hold seismic traces. We can name this
view anything we want.
The view will appear, and you can now choose which seismic outputs (vistas) you want
to display within this view:
Those vistas will appear as individual layers in the same View:
You can do the same thing with items saved in the “Vista Items from DB” Panel. Simply
grab the item you want to view, and drag it out into the project. If you drag the vista out
into empty space, the program will create a new view to hold that vista. If you drag the
vista on top of an already existing view, the program will add your vista as another layer
inside that view:
Tip: You can cycle through the

different layers of a view using the
scroll wheel of your mouse by
holding down CTRL + SHIFT on your
keyboard.
To see which layer is currently active,

pop open the view properties for
that view and look at the Vista Items
section. The highest item in the list is
the top layer of the view.
25 – Tip: Cycle through vistas with the scroll wheel
There is one last way to add the views of a module, and that is the Add module views
button:
This will automatically add all the default vistas of a module to the top window of your
project (see the next section: view windows to learn more about windows). This is a
good way to quickly see the results of a module. However, if you already have similar
views in that top window, say from another module, this button will add your new views
as new vista layers on top of your existing views.
View Manager
All the views you have added to the project will show up in the View Manager panel.
From here you can:

• Re-name views (F2 on your keyboard, or right click with the mouse)
• Re-arrange views and windows
• Delete views
• Switch between view windows.
View Windows
In large flows, you will inevitably end up with many different views. While there in no
limit to the number of views you can have active in any one window, it is easier to keep
them all organized by using multiple different windows that you can switch between.
To add a new window to the project, go to the View Manager panel, and select the drop
down menu next to the button. Click “Add Window”
You will then have the opportunity to name the window

anything you want. Hit enter, and your new window will Tip: If you hit enter without
appear: naming the window, it will
automatically be named as
another numbered window
(I.e. Window 2). You can
always re-name your
windows later.
26 – Tip: Windows are automatically named
Switch between your active windows by clicking on the window name, or by choosing
the appropriate window from the Window drop down menu on the top tool bar.
Windows can be renamed by right clicking on them, and selecting “rename” or by
pressing F2 on the keyboard.
When you add new module views, they will automatically be added to the active
window.
Views can be moved between windows by clicking and dragging.
Interactive Views
Many Views within g-Navigator are interactive. This means that, as a user you can click
within the view to set parameters of the module, or to perform actions like velocity
analysis. Generally, you can tell if a view is interactive by clicking on it. If something in
the window changes, or if you get an option to choose a check box, that view is
interactive:
You can also check the interactive properties of a module by clicking the button. This
will display a list of which interactive options are currently active:
27 – Tip: Multiple interactive options
Tip: If two or more interactive options are checked off that conflict with each other,
the active interactive option will be the one higher in the list.
In general interactive modules follow the same basic rules:
• Right click to set a point or selection

• Left click to remove a point or selection
• Right Click and drag to move a point or selection.
Some views will have additional actions that you can perform. To discover what these
are, check the help view panel for that module.
Zooming Views, and moving around inside views

There are several ways to zoom in and out of your views
You can zoom along any axis by hovering your mouse cursor over that axis and the using
the scroll wheel of your mouse, or by right clicking and holding on the axis, and then
dragging the mouse cursor.
You can also zoom by holding down CTRL on your keyboard, and drawing a box around
the area you would like to zoom to.
Un-zoom by holding down CTRL and left clicking inside the same window.
You can return the zoom to encompass the entire view using the Adjust to Size button,
or with CTRL+A .
Use the scroll bars at the sides and bottom of the view to move around inside a
particular view
Re-Arranging Views
To re-arrange your views, grab the view by the title by clicking and holding with the left
mouse button. You can grab the title at the top, or at the bottom of the view
Hover the mouse near the edge of another view that you would like to dock to. A grey
bar will appear at the edge of that view, indicating that your view will be docked on that
edge. You can pick the top, bottom, or either side of the view. Release the mouse
button to dock the view.
Views can be stacked on top of one another by grabbing a view, and dragging it to
somewhere in the center of another view. When the mouse button is released, the
views will stack on top of one another, and the user can switch between windows by
clicking on the tabs at the bottom.
If the mouse button is released over empty space (Not Tip: Although groups of
overtop of another view, or when no grey bar is free floating views can be
present to indicate the view will be docked), it will moved as a group, each
remain free floating. Views can be docked to other view is still treated
free floating views along any edge, and the resulting independently for the
group of views can be moved independently. Views purposes of docking and
can also be stacked on top of other free floating views. stacking, and will be
removed from the group
when they are grabbed
and moved somewhere
else.
28 – Tip: Free floating views
Spectral Analysis Tool
The view windows for any seismic data also contain another button, the spectral
analysis tool:
When the user presses this button, a window will automatically appear that will display
the spectrum of the entire view:
From here, we can add the spectrum of other seismic views active in the same
workflow, by checking off the box next to their name, and pressing “apply”.
We can also change the normalization type to Db or amplitude, adjust the smoothing of
the display, change the maximum frequency of the display, or change the colours of any
of the lines currently displayed. Remember to hit “apply” after making any changes to
the graph parameters – the image will not update otherwise. The colours of any lines
can be changed by clicking on the coloured box next to its label.
By default, the spectrum analysis tool will display the
Tip: You can tell which lines on the
spectrum of the entire view, but you can analyze a
graph belong to which view, because
smaller section by going to the view in question, and
an outline of the same colour will
drawing a box around the area that you want to
appear around the data of the view it
analyze.
corresponds to. These colours are
chosen automatically, so you may
The graph can be exported to an image file (jpeg,
want to change them if the contrast
bmp, tiff, png) using the “export” button
with your view is too low.
29 – Tip: Spectrum analysis colours
Ruler
The ruler tool , allows you to make measurements inside any view window. To use it,
press the ruler button and then click and drag to draw a line between two points. Your
ruler measurements will show up in the Tracking info panel:
The ruler can also be used on vistas of seismic data, to measure traces and times
View properties
In this example, we will take a look at Input Gather viewing parameters.
Users can change view settings by clicking on the button Show Properties from the
panel bar:
Or with a right-click on the title of the image in the View Manager:
A new window, View properties will appear.
It consists of three parts: View properties, Vista items and Vista item properties.
Each of them contains various parameters and options to modify the view of images in
g-Platform©.
You can minimize each part by clicking on the little triangle .
Click back on a triangle to expand the properties.
View Properties
Let's expand the View properties panel. This panel corresponds to general properties of
the entire view – things like the scale, axes, colour bars and background colours.
Here you can:
• Change the horizontal and vertical axis orientation to increase or decrease
• Enable/disable a colour bar by checking/unchecking the box
• Enable a general range for that colour bar by checking the box and typing a
Minimum and Maximum Range Values as shown in the picture below
• Change vertical, horizontal scales and precision
• Enable/disable legend
• Add/delete headers
• Show/hide grid by checking/unchecking the box
• Select a background colour
Let's enable the colour bar and select a general range from -0.15 to 0.15.
Change vertical/horizontal scales and their precision.
You can click on the existing parameter and type a desired value.
You can adjust a value by using the mouse, move the mouse cursor to the
corresponding slider , then press the left mouse button and, (keeping it pressed) move
the slider left or right. Alternatively, you can click on arrows .
Enable legend to be able to compare the views with different properties.
Click on button to add a header.
Every time you click on the button, an FFID header will be selected by default. Let's
keep it this time as we want to have it in the view.
Let's add CDP and Source X headers.
ABS_OFSET header will be set. Click on it and select CDP and then Source X.
You can move the headers up and down by using .
To delete headers click on .
You can check/uncheck the grid.
For now the background colour is set as white.
Click on and select a new colour and click OK or stay with the white background.
Page 100 of 171 July, 2017
Once you are happy with selected viewing properties you can close the window.
Page 101 of 171 July, 2017
If you want to apply these view properties to all your similar Views and Vistas, click on
the button Propagate in the top right corner . Click on to reset properties to
default settings.
Tip: You can make these settings

the program default for ALL
views by checking off the “make
as default” box:
30 – Tip: Set the program defaults for view

properties
Page 102 of 171 July, 2017
Vista Items
In the Vista Items section you can see which vista is currently being displayed in this
particular view. In this example, it is Input gather.
If you want to make this image invisible, uncheck the box .
You can save a vista item to your database by clicking on . Enter a name for your vista
item in the new window.
You can also choose to save a vista to the DB by right clicking on it, and selecting “Save
to DB”. Saved Vista items will appear in the “Vista Items from DB” panel (See Chapter 3:
g-Navigator) for more information on this panel.
Page 103 of 171 July, 2017
Vista Items Properties
Let's take a look at Vista items properties. This section of the View properties always
corresponds to whichever item is selected in the Vista Items section.
In this section, you will have the option to change the properties of that specific vista.
The properties that you can change depend entirely on what type of vista item it is. For
Seismic data, for example, you can change:
• The Transparency level

• The colour bar (for density display)
• The display normalization type and range
• The gain
• The display AGC
• The trace display type (Density vs. Wiggle)
• The trace display colour (for wiggle display)
• Antialiasing, clipping, and normalization for wiggle displays.
Other views, such as map or graph views will allow you to change the colour, shape, and
line type of any points or lines displayed in that view.
You can propagate these view properties to all similar views using the button on the
Vista Item properties tab.
Tip: When you propagate Vista Item properties, those settings will only be applied
to vistas of the same type as the current vista – That means that the settings you
choose for a display of seismic traces will be applied to all other vistas of seismic
traces, but will not be applied to map or graph views. Similarly to the View
properties, you can also make your settings for that vista type the program default
by checking off the “make as Default check box
31 – Tip: Propagate Vista item properties
In this example, we are using a Stack colour bar. Click on it, if you want to change it.
Page 104 of 171 July, 2017
A drop down menu with choices of various colour bars will appear.
In this case, let's try Seismic.
Once you have changed the colour bar, the Input gather image will change
automatically.
Page 105 of 171 July, 2017
You can change the Gain parameter by typing a new value or by using arrows .
If you want a variable area/wiggle display, check the box next to Wiggle and the view
will change.
This display has positive ‘peak’ samples of each trace filled in black, and the negative
‘trough’ samples as a thin line.
You can keep it as is, or select specific colours.
Click on the Wiggle positive colour to change it.
Page 106 of 171 July, 2017
Select a new colour and click OK.
Page 107 of 171 July, 2017
Now the positive samples are shown in a different colour.
Page 108 of 171 July, 2017
You can change the Wiggle negative colour the same way if needed.
You can also change a wiggle null line colour by clicking on it. In this example we have
selected a blue colour.
Page 109 of 171 July, 2017
To delete a colour, click on the red cross:
The wiggle null line will become black by default.
You can also change a wiggle line width to make it thicker or thinner.
Simply type a desired value and the image will change.
Wiggle line anti-aliased: check the appropriate box to enable this parameter.
Page 110 of 171 July, 2017
You can also change wiggle clipping:
Check/uncheck an auto normalisation:
And change a precision value if needed.
Page 111 of 171 July, 2017
Once you have set up the view parameters you can click on the Propagate properties
button in order to apply these properties to other images. Or reset properties to
defaults clicking on .
Page 112 of 171 July, 2017
Page 113 of 171 July, 2017
Other view parameters
Let's take the Location map display as an example to demonstrate more view
parameters.
Go the Module Manager and right-click on module Binning2D Vista groups  Location
Map  Add view.
Page 114 of 171 July, 2017
The Location map image will appear on the screen. You can now see its name in the
View Manager. Add a new window and call it Window 2.
Move the Location map image to the Window 2.
Page 115 of 171 July, 2017
Drag the Seismic loop from the Module Manager with the mouse and release it on the
image of Location map to add CMP, Sources, Receivers and Selected Point XY and click
OK.
Page 116 of 171 July, 2017
Double-click on the Location map in the View Manager panel.
A View parameters window will start:
You can see axes, filters 1 and 2, vista items selected, procedures tree and vista items
allowed.
Filter 1 includes vista items from Binning 2D module.
Filter 2 includes Seismic loop vista items.
All of them will be displayed in the Location map view.
Page 117 of 171 July, 2017
Page 118 of 171 July, 2017
Page 119 of 171 July, 2017
Right-click on the Location map image and select selected point receiver.
Or click on in the top right corner of vista items to set control item. Check the box
next to selected point receiver.
This point will become active and you can move it along the line by clicking with the left
mouse button.
Page 120 of 171 July, 2017
4
You can change the view properties as you are already familiar with the View Properties
panel.
Go to Vista items properties section.
Click a point type and select a different shape, for example Square.
Page 121 of 171 July, 2017
.
Page 122 of 171 July, 2017
Change a colour and adjust the size to make the point more visible:
Set up a line size typing a desired value.
Page 123 of 171 July, 2017
Now select a point source and set up vista items properties as was described earlier.
Select selected receivers in the Vista items panel.
Change the point type and the size of selected receivers following the steps described
earlier. Do the same for selected sources.
Page 124 of 171 July, 2017
Zoom-in the image.
Now you can see:
• Selected point source
• Selected point receiver
• Selected receivers
• Selected sources
Set the control point by clicking on and click the checkbox next to selected point
receiver. Now you can move it along the line and view the sources .
Page 125 of 171 July, 2017
You can change the visibility settings for vista items by checking/unchecking the box .
Selected sources are invisible now:
Page 126 of 171 July, 2017
Page 127 of 171 July, 2017
You can make MP invisible and view CMP points – the little yellow points.
Change the size of CMP points to make them more visible.
Export Images
It is possible to export any view as a still image in jpeg, png, tiff, gif, or bmp format,
using the button. When you press this button, you will be prompted to choose a file
name and image format, and then the Export View to file dialogue will appear:
Page 128 of 171 July, 2017
From here, you can adjust the
parameters of your output image, Tip: You can also use this option to create
including the scales and resolution of animated GIFs – to do this, make sure you
the image, if you intend to print it have more than one layer inside the same
later. view, and then choose .gif from the drop
down menu as your save option.
32 – Tip: Create animated gifs
Page 129 of 171 July, 2017
Chapter 7: Sample Flow Work Through
In this chapter will build and execute a surface consistent deconvolution flow as an
example. Surface Consistent deconvolution requires that we have a data set that
already has geometry applied – that is, a full set of coordinates, and a bin grid. In this
flow, we are going to calculate a set of
Deconvolution operators with one module,
Tip: The flow in this section is only and then, with a second module inside a
one example. You can find many Seismic loop, apply them.
more examples of flows, and
explanations of specific modules on To build this new flow, we will start in g-
the Geomage YouTube channel Platform© from the main window. As you
can see, we already have one existing flow,
called 1_Load_Geometry, which we used to
33 – Tip: Geomage YouTube channel create the Project data item, “Binned”:
Page 130 of 171 July, 2017
We’re going to add a second flow using the button in the Workflows window:
Double click the new flow to open it in g-Navigator:
Page 131 of 171 July, 2017
To start, we’ll go to the module manager and add a Read Seismic Traces module:
Page 132 of 171 July, 2017
Page 133 of 171 July, 2017
In the module properties panel for this module, we’ll choose the input “binned” under
seismic file name:
Note: Load Data to RAM is set to “No”. (See Question: Why can’t I use the Gather
output of Read SEG-Y traces or Read Seismic traces (pg. 60), for an explanation as to
why)
Page 134 of 171 July, 2017
Double click this module to run it. You can run each module as you add it, or run the
whole flow at once. Modules that have finished running gain a blue symbol next to
their name.
Next, we will return to the module manager and hit the insert key on the keyboard, and
search for “SC” to add the SC Deconvolution - Calculate module to the project.
Page 135 of 171 July, 2017
We can see that SC Deconvolution – calculate requires two inputs: SEG-Y data handle,
and Trace headers, combined under one heading, DataItem.
We can get both from the Read Seismic Traces. We’ll set the reference for DataItem to
that module:
Page 136 of 171 July, 2017
Page 137 of 171 July, 2017
With the References set, we can now adjust the parameters of the SC Deconvolution
module:
SC Deconvolution – Calculate has a Sub-sequence. Sub-sequences are very common in

modules like this, that operate on the traces of your data, but that can be used outside a
Seismic loop. Modules added to the sub-sequence here will operate before the main
module. We’re going to use that sub-sequence to window the data before we operate
on it.
Page 138 of 171 July, 2017
To this, we’ll add a Mute by velocity function to the Sub-sequence:
We’ll add all the views of Mute by velocity:
Page 139 of 171 July, 2017
Note: In order to view the output of any module in the sub-sequence, we have to run
the SC Deconvolution module once:
It is currently too difficult to see the results of the module because it is too zoomed out.
By hovering over the top axes of the first view, Difference – Gather of difference, we can
zoom in:
Page 140 of 171 July, 2017
And then use the button on the top tool bar to make the other views match:
Page 141 of 171 July, 2017
We’ll adjust the parameters of Mute by velocity, re-running that module each time until
we arrive at something that we like:
Page 142 of 171 July, 2017
Page 143 of 171 July, 2017
Now that we have a set of parameters, we can run the SC Deconvolution – Calculate
module. When we run this module, anything in the sub-sequence will automatically run.
To see the results of this module, we’ll have to add its views. However, we already have
some views in the main window. To keep things organized we’ll add a second window in
the View Manager with the drop down menu , and then re-name the first window
using F2 on the keyboard:
Page 144 of 171 July, 2017
With the new window selected, we’ll add all the views of the SC Deconvolution –
Calculate module, and use the button to hide all the unnecessary panels:
We can see that the SP and RP amplitude correction maps are interactive by clicking on
the mouse icon:
Page 145 of 171 July, 2017
Page 146 of 171 July, 2017
And then by clicking on the maps themselves. The source at that location appears:
When we are satisfied with the results of this module, we can save out the operators to
the data base, by going to the Output Data tab, right clicking on the operators
Page 147 of 171 July, 2017
(FrequencyResponseSpectrumItem), and selecting Save to DB:
Page 148 of 171 July, 2017
34 – Tip: Reference operators directly
Tip: You don’t have to save items like deconvolution operators to the database – you
can set the reference for them directly to the module that generated them. If you
plan on running multiple versions of any operator, it’s best to save them to the
database instead.
We’re now ready to apply those operators to the data base using the SC Deconvolution
– apply module. Let’s take a look at that module:
We can see right away that this module requires an input gather, as well as the
FrequencyResponseSpectrumItem generated by the Calculate module. According to the
guidelines outlined in Chapter 4 – Building Flows [Gather Seismic and the Seismic loop],
an input gather input means we have to use a Seismic loop.
Page 149 of 171 July, 2017
To set up a Seismic loop, we will first sort our data:
Here, we’ve added two sort indexes – a trace grouping of FFID, or Field file, and a trace
sorting of Channel. Don’t forget to set the references for the input data for this module.
Next, we’ll add the Seismic loop, and connect it to the Sort Traces. Because we’ve set
the primary sort as FFID, the loop will update automatically, and let us know the total
range of Field files under the First and Last Sequential Gather numbers:
Page 150 of 171 July, 2017
Finally, we can add the SC Deconvolution – Apply module to the Seismic loop. Because
we are adding a module inside the Seismic loop, the input reference is set automatically.
We can see that the Input Gather is set to the Seismic loop as soon as we add the
module:
Page 151 of 171 July, 2017
The FrequencyResponseSpectrumItem is not automatically set, so we have go do that
ourselves. We can find our saved operators under the “DB search” tab:
Page 152 of 171 July, 2017
With all the input references set, we are now free to test the parameters of our SC
Deconvolution apply module, to find some settings that we like. To do this, we are going
to use some of the unique features of the Seismic loop.
We’re going to go ahead and add a third window the project, to contain the views we’ll
use for this testing. In this window we’re first going add the Location Map Vista from
Page 153 of 171 July, 2017
the Seismic loop:
Page 154 of 171 July, 2017
The Location map will appear, showing us Field File points:
We can make these points a little easier to see by opening up the View Properties for
the Location map view. In this case, we’re interested in the Observed Points vista item.
With this Vista Item selected, we can change anything we want, including the point size,
Page 155 of 171 July, 2017
colour, and shape:
Page 156 of 171 July, 2017
Page 157 of 171 July, 2017
Next, we’ll add the input and output vistas from SC Deconvolution Apply:
Page 158 of 171 July, 2017
All the vistas appear as blank red because we haven’t run the module yet. Let’s say we
want to look at a location in the middle of the line. We can very simply click on the
location map at a point near the center:
Page 159 of 171 July, 2017
The loop will run the SC Deconvolution at the point indicated on the map, and the Vistas
from the SC Deconvolution module displays the results.
If we want to test the parameters of the module at this location, we can change one of
the settings, and the double click the module name to run it again at the same location.
Running the whole seismic loop with a double click will increment the whole loop to the
next location (The next field file, in this case, as we are sorted to field file).
At this point, we can add as many subsequent procedures as we want to this loop, and
each one will link automatically to the one before it in the loop:
Page 160 of 171 July, 2017
Everything run up to this stage inside the loop has been testing only – nothing has been
saved. For that, we need to add one final module to the loop, a save module.
There are several different save seismic modules, so how do you decide which one to
use? Well, we can check the output of the last module in this list, band pass filter:
Band Pass filter’s Output DataItem is an Output Gather. This means we need to use the
Save Seismic by Gather module to save the output of this module.
Page 161 of 171 July, 2017
As a general rule, Always use Save Seismic by Gather when saving data out of Seismic
loop.
We’ll set a name, and choose a storage location for the output file.
Page 162 of 171 July, 2017
Question: What is the difference between Direct and Append, and when
saving data, which should I use?
Direct mode saves your data in its original sort order – that is, whatever order
the traces were in in the original input SEG-Y, this is the order that they will be
saved in in your output data fire.
Append mode saves your data in its current sort order – that is, whatever sort
order it appears in when it hits the module.
You can use either mode with any data set, but Direct mode tends to be faster
when you haven’t changed the sort order (i.e. the output of any module that
didn’t require trace sorting), and append mode will be faster when the data sort
order has changed (I.e. when using a Seismic loop).
35 – Question: What is the difference between Direct and Append, and when saving data, which should I use?
Now, we just need to run through the entire Seismic loop, to ensure our entire data set
is written out to a file. To do this, we’ll select the loop and use the button to run the
entire thing.
Tip: Don’t add the Save Seismic by Gather

module to the loop until you are ready to
write out your data set – otherwise every
time you run the loop for testing, the
module will try to write out single loop
iterations to the data set specified under
Seismic File Name.
36 – Tip: Save Seismic by Gather and the Seismic Loop
Once that data is saved, we can check on in the Project Data panel in g-Platform©. Our
new data set should show up in that list, and will be available for use in other flows
Save your workflow with
Page 163 of 171 July, 2017
Appendix 1: Header definitions
The following is a list of all header items in g-Platform©, and what they represent
Header list in Program default order:

Start Byte - Geomage
Header Description default format
FFID field file number 9
CHANNEL channel number 13
SOURCE_SP source/shot point number 17
CDP common depth point number 21
TRACE_TYPE trace flag (0 for dead traces, 1+ for live traces) 29
DATA_USE data use trace flag 35
OFFSET trace offset 37
receiver_ELEV receiver/field station elevation 41
SOURCE_ELEV source / shot point elevation 45
SOURCE_DEPTH source/shot point depth 49
receiver_DATUM receiver/field station datum 53
SOURCE_DATUM source/shot point datum 57
SOURCE_WDEPTH source/shot point water depth 61
receiver_WDEPTH receiver/field station water depth 65
SCAL_ELEV elevation coordinate scalar 69
SCAL_COORD coordinate scalar 71
SOURCE_X source/shot point X coordinate 73
SOURCE_Y source/shot point Y coordinate 77
receiver_X receiver/field station X coordinate 81
receiver_Y receiver/field station Y coordinate 85
COORD_UNIT coordinate unit (1 = metric, 2 = imperial) 89
SOURCE_UPHOLE source/shot point up-hole time 95
receiver_UPHOLE receiver/field station up-hole time 97
SOURCE_STATIC source/shot point total static 99
receiver_STATIC receiver/field station total static 101
TIME_DELAY recording delay time 109
SAMPLE_NB number of samples 115
SAMPLE_INTERVAL sample rate of data 117
TRACE_WEIGHT trace weight 169
BIN_X CDP bin X coordinate 181
BIN_Y CDP bin Y coordinate 185
Page 164 of 171 July, 2017
INLINE CDP inline number 189
CROSSLINE CDP crossline number 193
receiver_SP receiver/field station number 197
SCAL_SP point number scalar 201
BIN_ELEV CDP bin elevation 211
BIN_SP station closest to CDP 215
SOURCE_LINE source line/shot line number 223
receiver_LINE receiver line/field station line number 225
SOURCE_ID source type 227
SOURCE_REFSTATIC source/shot point refraction static 229
receiver_REFSTATIC receiver/field station refraction static 231
TRACE_STATIC total trace static 233
receiver_DEPTH receiver/field station depth 235
SURVEY_ID survey ID 239
HEADER_1 auxillary header n/a
Page 165 of 171 July, 2017
Header list in Alphabetical order:
Start Byte - Geomage
Header Description default format
BIN_ELEV CDP bin elevation 211
BIN_SP station closest to CDP 215
BIN_X CDP bin X coordinate 181
BIN_Y CDP bin Y coordinate 185
CDP common depth point number 21
CHANNEL channel number 13
COORD_UNIT coordinate unit (1 = metric, 2 = imperial) 89
CROSSLINE CDP crossline number 193
DATA_USE data use trace flag 35
FFID field file number 9
INLINE CDP inline number 189
OFFSET trace offset 37
receiver_DATUM receiver/field station datum 53
receiver_DEPTH receiver/field station depth 235
receiver_ELEV receiver/field station elevation 41
receiver_LINE receiver line/field station line number 225
receiver_REFSTATIC receiver/field station refraction static 231
receiver_SP receiver/field station number 197
receiver_STATIC receiver/field station total static 101
receiver_UPHOLE receiver/field station up-hole time 97
receiver_WDEPTH receiver/field station water depth 65
receiver_X receiver/field station X coordinate 81
receiver_Y receiver/field station Y coordinate 85
SAMPLE_INTERVAL sample rate of data 117
SAMPLE_NB number of samples 115
SCAL_COORD coordinate scalar 71
SCAL_ELEV elevation coordinate scalar 69
SCAL_SP point number scalar 201
SOURCE_DATUM source/shot point datum 57
Page 166 of 171 July, 2017
SOURCE_DEPTH source/shot point depth 49
SOURCE_ELEV source / shot point elevation 45
SOURCE_ID source type 227
SOURCE_LINE source line/shot line number 223
SOURCE_REFSTATIC source/shot point refraction static 229
SOURCE_SP source/shot point number 17
SOURCE_STATIC source/shot point total static 99
SOURCE_UPHOLE source/shot point up-hole time 95
SOURCE_WDEPTH source/shot point water depth 61
SOURCE_X source/shot point X coordinate 73
SOURCE_Y source/shot point Y coordinate 77
SURVEY_ID survey ID 239
TIME_DELAY recording delay time 109
TRACE_STATIC total trace static 233
TRACE_TYPE trace flag (0 for dead traces, 1+ for live traces) 29
TRACE_WEIGHT trace weight 169
Page 167 of 171 July, 2017
Table of Tips and Questions
1 – Tip: Databases and DBs______________________________________________________ 5
2 – Question: Where else can I go for help? _______________________________________ 5
3 – Tip: Switching between tabs __________________________________________________ 25
4 – Question: What is a Database? Do I need Additional Database Software? __________ 26
5 – Tip: Data storage locations ___________________________________________________ 27
6 – Tip: Binary Data, and Flow/History Path locations ________________________________ 29
7 – Tip: Templates are stored in their own databases _________________________________ 39
8 – Tip: Rearranging panels in gNavigatr ___________________________________________ 52
9 – Question: What is a Module? _______________________________________________ 53
10 – Tip: Check the Help View ___________________________________________________ 56
11 – Tip: Modules that require more than one input___________________________________ 58
12 – Tip: Data connections inside the Seismic loop ___________________________________ 60
13 – Question: Why can’t I use the Gather output of Read SEG-Y traces or Read Seismic
traces? _____________________________________________________________________ 60
14 – Tip: Set references to almost anything _________________________________________ 61
15 – Tip: Use Save seismic by gather inside the Seismic loop __________________________ 62
16 – Tip: Saving on HDD vs SSD _________________________________________________ 63
17 – Tip : Save operators to the DB _______________________________________________ 65
19 – Tip: Run the Seismic loop at a specific location __________________________________ 67
18 – Tip: Executing the entire Seismic loop _________________________________________ 68
20 – Tip: Save often. __________________________________________________________ 70
21 – Tip: Use Firefox with the Coalition ____________________________________________ 71
22 – Tip: Distributed modules save their own outputs _________________________________ 74
23 – Question: What if I don't have enough RAM? (distributed execution) _____________ 76
24 – Question: What's the Difference between a View and a Vista? ___________________ 78
25 – Tip: Cycle through vistas with the scroll wheel ___________________________________ 81
26 – Tip: Windows are automatically named ________________________________________ 83
27 – Tip: Multiple interactive options ______________________________________________ 85
28 – Tip: Free floating views_____________________________________________________ 87
29 – Tip: Spectrum analysis colours_______________________________________________ 90
30 – Tip: Set the program defaults for view properties _______________________________ 102
31 – Tip: Propagate Vista item properties _________________________________________ 104
32 – Tip: Create animated gifs __________________________________________________ 129
33 – Tip: Geomage YouTube channel ____________________________________________ 130
34 – Tip: Reference operators directly ___________________________________________ 149
35 – Question: What is the difference between Direct and Append, and when saving data,
which should I use? _________________________________________________________ 163
36 – Tip: Save Seismic by Gather and the Seismic Loop _____________________________ 163
Page 168 of 171 July, 2017
Index
Binary Data Path · 21, 28, 29
data storage path · 17, 27
A Flow/History · 21, 28, 29
flow · 32, 53, 61, 67, 131
Add module views · 82 new · 43
Adjust to Size · 85 Flow to Template Conversion Wizard · 40
Flow Viewer · 33
panel · 12
B
bmp · 129
G
bulk size · 75, See chunk
gather · See input
Geomage Config Editor · 73
configuration settings · 72
C gif
animated · 129
cancel · 43 Global Properties
chunk panel · 19
size · 75 Graph View · 48
chunks · 71 GUI state · 43
coalition server · 43, 71
Connecting data · 54
copy · 9, 44
H
Help View · 49
D hide all panels · 9, 43, 148
history · 29
data connections · 45, 48
database · 11, 26, 31
properties · 31
dataItem · 63, 137
I
delete · 9
distributed execution · 73 information · 47
distribution options · 74 input
dock · 86 data · 46, 135
DataItem · 54, 56
gather · 152
item · 56
E insert · 9, 32, 37, 136
interactive · 69, 77
execute · 9, 66 internal format
run · 43, 44, 136, 163 .gsd · 53
run time · 52
export
spectrum image · 90
view · 129
J
jobs · 71
Jobs
F panel · 20
jpeg · 129
file storage
Page 169 of 171 July, 2017
L R
load · 53 Read SEG-Y Traces · 53
Load Data to RAM · 136 Read Seismic Traces · 53, 133, 138
location map · 118, 162 read traces · 53
re-arrange views · 86
reference · 56, 65, 154
M set reference window · 55, 65
restart jobs
Coalition · 72
module · 53
revision · 9, 15
add modules · 53
save · 43, 70
add modules · 44 ruler · 50, See Tracking info
delete modules · 44
run · 66, 166
delete modules · 53
execute modules · 66
properties · 45
special actions · 68 S
sub-sequence · 61
Module Manager · 44, 53, 66, 68, 133 save
Module Properties · 45, 49, 73, 135 append · 63
Mute by velocity · 141 direct · 62
save to DB
item · 46, 64
O operators · 151
vista · 103
seismic · 164
operators · 63, 150
workflow · 9, 43, 70, 166
output
Save SEG-Y · 62
Data Tab · 46, 57
Save seismic
DataItem · 55
append · 166
Gather · 165
direct · 166
view panel · 52
Save Seismic · 62
vistas · 162
Save Seismic by Gather · 61, 62, 165
SC Deconvolution – apply · 152
SC Deconvolution - Calculate · 136
P SEG-Y · 53, 62
SEG-Y data handle · 56, 58, 137
panel · 20, 23, 42 seisimic loop · 61
parameters · 46 seismic · 53
paste · 9, 44 seismic distributed loop · 74
png · 129 Seismic loop · 58, 61, 67, 131, 152
pre-processing · 61 location map · 156
Progress Bar · 68 seismic distributed loop · 61
Progress View · 52, 67, 68 set reference · 138
project · 11 connecting data · 54
new project · 26, 30 data connections · 60
sub-projects · 31 DB search · 65, 155
Project Data · 166 Show Properties · 92
panel · 17 sort · 153
Project Tree · 21, 26, 30 sort indexes · 153
panel · 11 Special Actions · 68
spectral analysis · 88
spectrum · 88
statics correction · 63
Page 170 of 171 July, 2017
stop · 9, 44 axis · 96
storage location · 165 background colour · 96, 100
storage path · 27 colour bar · 96
sub-sequence · 61, 140, 147 default settings · 102
Surface Consistent deconvolution · 131 headers · 96, 98
precision · 96
propagate · 102
T scales · 96
vista items · 103
Template to Flow Conversion Wizard · 37 vista properties · 104
Templates AGC · 104
create a template · 39 colour bar · 104
panel · 13 density · 104
using templates · 33 display normalization · 104
tiff · 129 propagate · 104
trace headers · 56, 137 wiggle · 104
Tracking info · 50 View Windows · 43, 83
ruler · 91 views
floating · 87
vista · 52, 78, 82, 104
V Vista Groups · 77
Vista Items from DB · 51, 81
velocity picking · 63
view · 52, 77, 147
add a view · 77, 78, 81 W
add views · 44
interactive · 148 windows · 51
interactive · 84 worker · 72
sync · 144 affinity · 73
un-zoom · 85 nodes · 73
window · 83 Workflow History
zoom · 85 panel · 15
View Manager · 51, 82, 118, 147 Workflows · 12, 32, 35, 36, 42, 132
view properties · 92, 96, 158
Page 171 of 171 July, 2017

Geomage GPlatform Manual July-2017

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

Geomage GPlatform Manual July-2017

Transféré par

Droits d'auteur :

Formats disponibles

g-Platform©

Seismic Data Processing Software

Page 1 of 171 July, 2017

Page 2 of 171 July, 2017

Page 3 of 171 July, 2017

Page 4 of 171 July, 2017

How to use this manual

The final chapter of this manual is a

2 – Question: Where else can I go for help?

Page 5 of 171 July, 2017

Chapter 1: g-Platform© Main Window describes the function of various panels

Page 6 of 171 July, 2017

Page 7 of 171 July, 2017

64-bit; Windows 7/8; Linux RH/CentOS 6.x/7.x

CPU: 2 cores minimum. g-Platform© designed to work in multi-thread mode in order to

Mouse button guide

• Click: Briefly depress the mouse button.

• Double-click: Quickly depress the mouse button twice.

Page 8 of 171 July, 2017

Page 9 of 171 July, 2017

Page 10 of 171 July, 2017

You can search the project tree or press Ctrl + D:

Using the tool panel you can:

• Add project and DBs (databases)

Page 11 of 171 July, 2017

Page 12 of 171 July, 2017

Page 13 of 171 July, 2017

Page 14 of 171 July, 2017

Page 15 of 171 July, 2017

• Open a revision , or double click on the revision name.

Page 16 of 171 July, 2017

Page 17 of 171 July, 2017

Page 18 of 171 July, 2017

You can search property by typing in this field or by pressing Ctrl + P.

Page 19 of 171 July, 2017

To delete a job, click on the red cross.

Re-arranging panels and Columns

• Modify the size of every information panel.

Page 20 of 171 July, 2017

want to see and click .

Page 21 of 171 July, 2017

Page 22 of 171 July, 2017

Page 23 of 171 July, 2017

Release the mouse:

Page 24 of 171 July, 2017

3 – Tip: Switching between tabs

Page 25 of 171 July, 2017

Adding a new Database

Question: What is a Database? Do I need additional Database Software?

4 – Question: What is a Database? Do I need Additional Database Software?

Page 26 of 171 July, 2017

You will notice that the storage path is set by default

Page 27 of 171 July, 2017

Page 28 of 171 July, 2017

6 – Tip: Binary Data, and Flow/History Path locations

Page 29 of 171 July, 2017

Adding a New Project

Enter the Project Name in the new window and click .

Page 30 of 171 July, 2017

Users can have any number of databases and projects defined.

Page 31 of 171 July, 2017

Enter a name for your flow.

Page 32 of 171 July, 2017

It is also possible to add new flows to a project using pre-existing Templates