SS FlowRep NoCover

Production Processing with
SeisSpace Flow Replication

copyright 2007 by Landmark Graphics Corporation
Part No. 200002A June 2007

2007 Landmark Graphics Corporation
All Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or
disclosed to third parties without the express written permission of:
Landmark Graphics Corporation

2101 CityWest Blvd, Building 2, Houston, Texas 77042-3021, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone:713-839-2000
Help desk: 713-839-2200
FAX: 713-839-2401
Internet: www.lgc.com
Trademark Notice
3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance, ADC, Advanced
Data Transfer, ARIES, ARIES DecisionSuite, Asset Decision Solution, Asset Development Center, Asset Journal, AssetLink, AssetLink Advisor,
AssetLink Director, AssetLink Observer, Asset Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingSeat,
COMPASS, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, DecisionSpace, DecisionsSpace 3D
Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace AssetView 2D,
DecisionSpace AssetView 3D, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace for
Production, DecisionSpace Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace
Reservoir, DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, DepthTeam
Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS,
Discovery, Discovery Asset, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth Model, DSS,
Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineers Data Model, Engineer's
Desktop, Engineers Link, ESP, Event Similarity Prediction, Executive Assistant, ezFault, ezSurface, ezTracker, FastTrack, FG+, FieldPlan, Field
Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, GeoProbe, GeoProbe GF
DataServer, GES, GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field Operator, HHFO, I2 Enterprise, iDIMS, IsoMap, iWellFile,
Landmark, Landmark Decision Center, Landmark & Design, Landmark Logo and Design, Landscape, Lattix, LeaseMap, LMK Resources,
LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus,
Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Development
Kit, OpenWorks Well File, OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Master Data Store, PetroWorks, PetroWorks Asset,
PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family,
PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerView,
PrecisionTarget, Presgraf, PRIZM, Production Asset Manager, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC
Server, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMax 4D, ProMax Family, ProMAX MVA, ProMAX VSP, pSTAx, Query
Builder, Quick, Quick+, QUICKDIF, QuickWell, QuickWell+, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+,
Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production
Surveillance, Real Time Surveillance, Real-Time View, Reference Data Manager, RESev, ResMap, RightTime, RTOC, SCAN, SeisCube,
SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks
PowerJournal, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert,
SimDataStudio,SimResults, SimResults+, SimResults+3D, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap,
StrataModel, StrataSim, StratWorks, StrataWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SynTool, SystemStart,
SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, The Engineers
Desktop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA,
VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-
THERM, WavX, Web Editor, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, Well Seismic Fusion,
WellSolver, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered
trademarks or service marks of Landmark Graphics Corporation.
All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this
manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,
this statement may not apply to you.
Contents
SeisSpace Flow Replication Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Ultimate Goal:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Flow Replication Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
Flow Replication Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6
SeisSpace Flow Replication Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

PM2000 Seismic Project Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Line List and Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Acquisition Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Begin the Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Building the Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Building the Replica Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Set up the template parameter substitution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18
Building Replica Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-20
Flow Chaining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27
Reading data from other lines / projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35
Guidelines for Success with Flow Replication . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Landmark Production Processing with SeisSpace i

Contents
ii Production Processing with SeisSpace Landmark

Chapter 1
SeisSpace Flow Replication Basics
This chapter provides an overview of the various components and features found in SeisSpace
Flow Replication
In This Chapter
In this chapter, you will learn about:
o The SeisSpace Flow Replication Components
o The procedure for replicating flows
o Descriptions and locations of files generated by Flow

Replication
Landmark Production Processing with SeisSpace 1-1

Chapter 1: SeisSpace Flow Replication Basics
Introduction
SeisSpace Flow Replication is a flow replication, job submission, and

project management tool designed to work with SeisSpace to assist in
large scale seismic processing projects. SeisSpace flow replication is
designed to help increase productivity by reducing the effort required to
build, submit, delete, and monitor jobs for big 3D surveys or projects
with many 2D lines. Flow replication reduces errors by eliminating
many of the repetitive tasks required to create and submit flows and
helps you keep data organized by providing a single location for
entering parameters and processing flows.
Project management with SeisSpace Flow Replication utilizes the

Replica Job tool to graphically track all jobs for all lines in your project
and can monitor all projects in your processing center simultaneously.
You can easily identify lines or projects falling behind schedule and
better plan your resource needs because the Replica Job table is always
current.
This course assumes you are familiar with the SeisSpace User Interface,
and will teach you how to use the Flow Replication capabilities within
SeisSpace.
1-2 Production Processing with SeisSpace Landmark

Ultimate Goal:
The goal of using SeisSpace flow replication is to build, submit, and manage all processing jobs
for your surveys efficiently. This is accomplished using the Replica Jobs Table (RJT) shown
below.
Processing Flows
Data swaths
This Replica Job Table (RJT) allows the user to manage the whole processing project from this
simple 2D matrix view. The rows in this matrix indicate units or subsets of data, such as a 3D
swath or a 2D line, which will be processed individually. The columns represent the processing
flows. From this matrix, the user can build, submit, and QC jobs and monitor the status of the
entire project.
Above is an example of the status window of a finished 3D survey. This survey was processed in
9 swaths, one swath per row starting with the row labeled SEG1. Each swath was processed

through 5 different replicated flows, one flow for each column starting with SegyExtract2 and
ending with DMOSTK3D2.
There is additional processing, such as geometry and velocity analysis, which are done once for
the entire survey rather than on a swath by swath basis. The user has the option of not including
this in the Replica Jobs window, or they can create templates, or master processing flows, out of
these flows as well, and run them within this window. This enables the user to keep track of the
entire processing sequence for the project. In the next example, the full survey processes were
included, and managed in the row labeled SEG0. Columns containing the entire survey processes
have cells for the individual swaths set to Unknown.
Although the Flow Replication utility is best demonstrated when you have a large number of lines
and setup and submission time is significant, even the complete survey processes are easier to
manage from the status window. In the above example, the flows were built for each swath,
submitted to the appropriate machines, and monitored from this window.
Terminology
Replica: A replica represents a subset of data to be processed For a marine 3D survey, this might
be a sail line. Other 3D replicas could be a ranges of inlines or individual offset planes. For 2D
data, each replica will typically be an entire 2D line.
Template: A template is a processing flow from which copies are made. You can think of a
template as the master copy of a flow. Parameters which may vary from replica to replica are
selected for substitution in this template.

Flow Replication Procedure
The steps involved in building and executing a Flow Replication project are:
Design a processing sequence as a series of flows.

Convert these flows to templates
Identify which parameters need to change from replica to replica and select
these in your templates
Create a Replica table and populate it with the values for the parameters you
have selected in the previous step.
Build, submit, monitor and QC jobs from the Replica Jobs table.

Flow Replication Components
Flow Replication is integrated into the SeisSpace user interface. We will

run through an example which follows the Flow Replication procedure
to introduce the components of flow replication.
In this example, we have obtained SEG-Y shots of the Manhattan 3D

survey, and wish to process it in 9 swaths through geometry
initialization.
1. Start a SeisSpace session, and highlight the

PROMAX_DATA_HOME your instructor tells you to use in the
Navigator window.
2. Click MB3 -> New Project, and type Flow Rep class -<your user
name>
3. Highlight your Flow Rep class... project, and click MB3 ->
New -> New Subproject. Type in Manhattan 3D.
4. Highlight your Manhattan 3D project, and click MB3 -> New -

> New Flow. Type in SEG-Y Extract.Your new folders should
look similar to the following:

5. The empty SEG-Y Extract flow will display in your flow editor.
Incorporate the following modules:
Note: You may see both ProMAX and SeisSpace modules. Make sure
and use the ProMAX modules, as designated by the blue P in the
picture above. The SeisSpace modules would be designated by a green
S symbol before it such as:
As of version 2003.19.1, SeisSpace modules can be used with Flow

Replication, but we will be using only ProMAX modules in this class.
6. We can now make this flow into a template. With SEG-Y Extract
as the active flow, click the following icon:

You will receive the following warning message:
This is what we refer to as Templatizing the flow.
7. Click on Templatize. Your flow will now contain bullets in front

of each parameter such as:
Bullets to mark parameters for substitution
If you do not see parameters on the right side of your flow click the
show/hide parameters list icon, which is located on the left hand side
of the T icon and looks like:
You can change from a template to a flow again by clicking on the same
T icon. The T icon is a toggle between inactive (flow view) and
active (template view) templates.

Note the asterisk in front of the Flow name:
asterisk
The asterisk means this flow has been edited and not saved. This asterisk
will appear in any flow editor where the parameters have been changed
but not saved. It is a good practice to save your edits before proceeding
to another task, especially if these future tasks depend on these edits.
8. Save your flow using File->Save or the following icon:
Guidelines for substitution:

Keep it simple. Only substitute parameters which change from
replica to replica.
Do not substitute parameters which alter the menu. A good
example of this would be the TYPE of mute parameter in the
Trace Muting module. Changing the parameter from Top to
Surgical alters other parameters under the menu, as seen below:

Importing ASCII file to Replica table:

In this example, we have been given an ASCII file with the
following details about the project. The items in the ASCII file are
tab separated.:
We will create a replica table and import this swath related information
into it.
9. With the SEG-Y Extract flow highlighted, click Tools ->

Replica Editor or the following icon:
A replica table should appear. If it contains the following message, click

OK:

10. Click MB3 -> Add Rows, and add 10 rows to this project.
We now need to populate our replica table with the columns of

information provided in the ASCII file.
11. Click MB3 -> Add Column. Fill The Add Column GUI as
indicated below:.
The available column types you can create are STRING, FLOAT, and
INTEGER. STRING can create FLOAT, INTEGER, or alpha-numerics
combinations, so it is the most versatile. In this example, we are simply
creating columns and column headers (names) to import our ASCII file
into. We choose the default Type STRING because data to be
imported from the ASCII file is alphanumeric, not single numeric
values.
Note that columns you create, by default, are placed at the beginning of
the list. In order to place them at the end, you need to uncheck Add to
beginning.
12. Repeat Step 11 to create FFID_Range, Min_ILINENO and

Max_ILINENO columns. Make sure that the Add to beginning
parameter is uncheck marked so you obtain the columns in the
same order as our ASCII text file we will import into this replica
table. If the columns are not in the order that you would like, use

MB1 to drag them to the desired order. Once complete, your

replica table should look as follows:
13. Highlight all your cells as shown below:
Click File -> Import at the top left hand side of the SeisSpace Interface.
Change Files of Type to All Files and Import the ASCII
manh3dswathinfo.tab file. The directory location will be specified by
your instructor.
14. This will activate the Confirm Import GUI. Make sure the
Using delimiter character: is toggled to Tab as our columns

are tab separated. The GUI should now contain the following
information:
15. We dont want to import our header information, so indicate you

want to import from rows 3 to 12. Also, we do not need to import
our SEQ number as it is already provided in our replica table, so
indicated columns 2 to 6.

16. Toggle Paste at selected cell, and click Yes. Your replica table
should now look like:
17. Save this Replica Table using File->Save or the following icon:.
18. Go to our SEG-Y Extract flow in the Flow Editor. If you do not
see parameters listed on the right hand side of you flow, click the
show/hide parameters list icon:

19. Toggle the following parameters for substitution and modify the
parameters indicated by the arrows:
We have toggled three parameters for substitution in the first two

modules of our flow, two in SEGY Input and one in Extract Database
Files. These are selected using the radio buttons at the left of menu

parameters names. These selected parameters are also highlighted in

yellow.
Before we proceed, we need to explain how to create these substitution

values that will be inserted into these menu locations:
Substitution Naming Conventions
The syntax for substitution expressions is similar to the Java syntax for
strings. Text within double quotes is passed without evaluation. Within
an expression, the + symbol indicates concatenation. Math functions
are performed after parameter substitution. Replacement values have
the following naming conventions:
r.xxxxxx is a value coming from the Replica Parameters Table.
s.Template is the template name (SEG-Y Extract in this example)
s.Project is the project name (Manhattan 3D in this example)
A special syntax exists to allow the user to read data from another
Project. The Project, Subproject (Area and Line), and Dataset
information are separated by the pipe character, |. An example of this
is provided in chapter 2.
The syntax of any substitution value can be checked through use of the
Validation Table, which is activated by the following icon:

Substitution Expression Examples:

1. Go to our SEG-Y Extract flow in the Flow Editor. If you dont see
parameters listed on the right hand side of you flow, click the
show/hide parameters list icon:
2. To better understand how to create these substitution expressions,

toggle the DEFINE trace header equation(s) parameter in our
Trace Header Math module for substitution, and type in the
following expression:
value=+r.Seq+1
The +r.Seq in this equation can be dragged and dropped from the
Seq attribute shown in your Replica Parameters table. If +r.Seq is
not enclosed in quotes, it is replaced with the corresponding value found
in the Seq column of the replica table. If you dont see your Replica
Parameter listed in the right side of your SeisSpace GUI, click the
show/hide template parameters icon:
3. Check the resulting expression by clicking the Validation icon:
4. If necessary, resize the column to see the results of the substitution.

You should see the following:

5. Change the Trace Header Maths Define trace header

equation(s) expression to the expression listed in the bullets
below and check the result for the following expressions, by
clicking the Refresh button in the Validation Table.
value=+r.Seq+1 (should validate to value=+r.Seg+1 as it is all

in double quotes)
value=+r.Seq+ +1 (should validate to value=#+1, with the

pound symbol replaced by an integer)
range= ILINE_NO:+r.Min_ILINENO+-+r.Max_ILINE_NO. You

can drag and drop the r.* parameters. Make sure there are no
spaces between the + symbols. This should evaluate to:
6. Delete Trace Header Math from this SEG-Y Extract flow. We

simply used it to test that substitution expressions produced the
desired result.
Now lets enter substitution values we will use in the SEG_Y Extract
flow.
1. As this flow contains many parameters that we are not altering, use
the following icon to view only parameters targeted for
substitution:
This is a toggle icon, so if you wish to view all your parameters, you can
simply click this icon again.
2. Parameterize the Enter file path name for SEG-Y Input with
the full pathname to the file, which will be provided by your
instructor. The diskfile name is one field we imported in our

replica table, so the end of your expression should match the

following example:
/disk1/training_data/+r.SEGY_Filename
3. Drag and drop r.FFID_Range for the Specify PRIMARY input

list parameter in SEG-Y Input.
For the Extract Database Files Mode of Operation parameter,

we need to specify whether we want to append or overwrite the
database. We will overwrite the database for the first swath, and
append to the database for the subsequent swaths, so we need to add
a value to our replica that indicates this.
4. Click on the Replica Parameters tab, or the R icon, and click

MB3 -> Add Column. Fill the Add Column GUI as follows:
An AppendFlag column will be added to the end of the Replica

Table and filled with 0s. A 0 value indicates Append and a 1
indicates Overwrite.
5. Change the value of the AppendFlag column for SEG1, or

swath 1, to be 1, indicating Overwrite. The default value of

0, or Append is fine for the other rows. Now your Replica table
should look like:
6. Save your Replica Parameters table using File->Save or the Save

icon.
7. Go back to your Flow by clicking on the Flow Editor tab and

drag and drop Replica Parameter AppendFlag into the Extract
Database Files Mode of Operation parameter.
8. Click on the Validate icon, and you should see the following:

9. If your expression parameters match the diagram above, close

your validation table and save your flow. If they dont, fix the
problem first.
We are now ready to create flows and run them using the Replica
Jobs Table (RJT).
10. Bring up the Replica Jobs Table by clicking Tools -> Replica
Jobs, or clicking on the following icon:

Your Replica Jobs Table should look like this:
Job Replica Table Details:

Job View: You can select any of the following attributes to be shown in the

cells in the Replica jobs table:
Job Status: Job Status is the default setting for what to show in RJT cells.
The Job Status values are color coded with the following possibilities:
Unknown: This is the initial status before any action is taken on a
job.
Build Pending: Job is waiting to be built

? Build Pending
Built: Flow has been built
Build Failed: Indicates there was a problem building the flow
Submit Failed: Indicates there was a problem submitting the flow
Chain Failed: Indicates there was a problem chaining the flow.
Submit Pending: Job is waiting to be submitted

? Submit Pending

Submitted: Job has been submitted for execution
Queued: Job has been sent to the user specified Queue
Chained: Job is chained to another job.
Initializing: Jobs will go through this state before building or

execution
Running: Job is executing
Paused: Running job has been paused by user (using MB3->Pause

on selected cell)
Completed: Job completed normally
Failed: Job bombed
Most of the other views available for the Replica Job table are self
explanatory with the exception of:
Percent Complete: The percentage of data read by ProMAX or JavaSeis

datasets. This is driven by ProMAX and SeisSpace Input tools only. A SEG-
Y job will report 0 percent complete even if it has completed normally.
Hostname: The name of the host where the job was run
Desc Name: The descriptive name of the flow
Reqid: The processid of the job
Replica Version: This indicates the number of times the flow has been run.
Detailed View Icon:

This icon activates the sideways replica job table, which allows you
to view all the Job View attributes of the replicas for a given
template.
Stop Icon:
This icon can be used to stop the build, build and submit, or submit
procedures. This feature is inactivated (greyed out) unless the job is
being built or submitted.
Refresh Icon:
The refresh icon can be used to refresh the contents of the Replica
Job table.
Share this Project:

The Share this project toggle defines where each replica is built.
When this is check-marked, the replicas will be built in the same
Subproject, or Line, as the template, sharing the same database. If
the Share this Project button was unchecked, or turned off, each
replica would be built in its own subproject, or line. You would
uncheck Share this Project when working with 2D data.
NOTE: The choice to share or not share is extremely

important. Choose wisely before starting your flow
replication work.
Show inactive templates:

If a template has been manually set to inactive status, (via the T
icon which toggles the template between active (template view) and
inactive (flow view)), by default, the column representing that
template is removed from the Replica Job table. If Show inactive
templates is checkmarked, you will see all Templates.
Autoscroll Table:
When a long list of flows are selected to be built, or built and submitted,
the Autoscroll option can be checkmarked to automatically scroll as the
flows are being built or submitted.

Flow building example:

Lets build a flow and examine some of these features available in
the Replica Jobs table.
1. Make sure Share this Project is checkmarked, as we want our

replicas to be built in the same directory as the template for this 3D
survey.
2. Click MB3 on the SEG-Y Extract cell for the SEG1 subproject
and select Build and Submit -> Local Submit:
MB3
MB3
MB#
MB3
3. Make sure the Job View is set to Job Status, and watch the status of
the job change from initialized, built, submitted, initializing,
running, to completed or failed. If your job fails, click MB3 ->Log
Viewer or CTRL-V to view the job log (formerly called
job.output) for details.
Intelligent Parameterization on replicated flows:

Using SeisSpace, you do not actually have to execute a flow to find
problems with parameters. You can use intelligent parameterization
on any built flow to investigate potential parameterization problems

1. In the replica job table, highlight a SEG-Y Extract cell for SEG1
and click MB3 -> Open Replica Flows. This will bring you to the
flow editor with the latest version of your highlighted flow, such as
the following:
2. With this replicated flow active, click on the Test parameters

intelligently icon:
This icon will run your flow through a job initialization phase to check
for invalid parameterization such as missing parameter tables and
datasets, invalid pathnames, and parameter inconsistencies. It will list
the first problem it encounters that would cause the flow to fail.
For example, if the user ran Test parameters intelligently on a flow

which had a Disk Data Input with a primary and secondary header for

sort specified but only an input range for primary sort such as the
following:
After clicking the Test Parameters Intelligently icon, the offending

module will be highlighted in red and you will receive the following
error message:
Say we fix this problem by entering *:*/ for the Sort order list for the
dataset. We should check our fix by clicking the Test Parameters

Intelligently icon again. In this example, we find the first problem was
fixed, but there was another problem:
Once we enter a velocity file in our Normal Moveout Correction, we

should click the Test Parameters Intelligently icon again until we see
the following:
3. Back to our flow example, if no parameter problems were found,

you should see a Successful Init Phase! message at the bottom of
your flow:

If you did not find any problems, lets temporarily alter this flow, and
intentionally create a problem. One common mistake is a missing /
when creating a complex expression for the Enter DISK file path
name(s) in SEG-Y Input. We can simulate this by editing this
parameter and taking out the / between the line name and the disk
name.
Edit the Enter DISK file path name(s) parameter in SEG-Y

Input so the expression looks like:
With this replicated flow active, click on the Test parameters

intelligently icon:
SEG-Y Input becomes red and the following error message is

generated:
Fix your pathname and click the Test parameters intelligently

icon again, until you receive the Successful Init Phase!
message.
Note: Any parameterization problems you find in your replicated

flow should be fixed in your template. This is the only way the flow
replication flow building process can incorporate the correction.

4. If you did find a problem with your flow using the job.output
listing or intelligent parameterization, fix the problem in the
template, save the template, and re-build and submit the flow.
5. Once the first job completes normally, highlight SEG2 through

SEG4 and use the Submit instead of local submit to submit
these flows through your single job queue. Cancel this submit if
you do not have a single job queue, and run each job individually
after the other finishes. These need to be run one after the other
because they are writing to the same database. We will cover a
way to automate this process in our flow chaining section in
Chapter 2.

If you did have a single queue set up, the Submit job GUI should be set
up similar to the following:
Any Queue available for SeisSpace should automatically be visible

in your Queue name section once the Queue button is toggled.

Submitting to your single job queue, a job will start after the
preceding job finishes.
6. For a more detailed view of each job, highlight a SEG-Y Extract

cell and click the following icon, which produces a Sideways-
Replica Job Table, or S-JRT:
7. All the available job view attributes will be presented in a

scrollable table for each SEG-Y Extract job we ran. The left side
of this table should look as follows:
Note: The percent complete is correctly shown when ProMAX or

SeisSpace datasets are input. The system has no way to know how
much data it will find when reading SEG or third party formats, the
the value is always shown as 0%. It may be useful to have the flow
list the ensemble information in the job log as a way for you to
monitor job progress.
8. When finished viewing, close this window.
Accessing Flows built by Flow Replication

You can access your replicated flows in two different ways. The first, as
we discovered in the Intelligent Parameterization on Replicated flows
section, is from the Replica jobs table. The second is from the
Navigation window. In this section, we will access replicated flows
using both of these methods and discuss the files created by flow
replication.
1. We used the SEG-Y Extract template to build the Replica flows. In

the replica job table, highlight a SEG-Y Extract cell for one of

your completed jobs and click MB3 -> Open Replica Flows to
view the corresponding flow:
Note the name of the flow:
Replicas will have an R icon in front of the name and [Replica] is

appended to the end of the flow name. Templates and regular flows are
designated with an appropriate icon:
Back to our replica, in this example the flow name is SEG-Y

Extract.r3.1 The r indicates this is a replicated flow. r3.1 means the
second time I ran this flow. If I ran this flow again, it would be r3.2.
r3.0 designates the first time a flow was run. You can access these
older versions of your flow through the Navigation Window.

2. In the Navigation tree view, click MB3 -> Navigate from your
SEG-Y Extract template as follows:
You should see a list of all the flows you ran from the Replica Job
table. You may have multiple flows with the same Name but
different File if you ran a flow multiple times. In the example
below, I will see two SEG-Y Extra0002 flows, r2.0 and r2.1
because I ran this job twice.
Accessing SeisSpace Flows from disk:

On your disk, all data generated from flow replication are stored in
flat files under $PROMAX_DATA_HOME/<AREA>/<LINE>
and $PROMAX_DATA_HOME/<AREA>/<LINE>/<FLOW>

directories. SeisSpace offers a convenient way to get to these

directories:
1. In the Navigator window highlight your Manhattan 3D line. You

will see the Address field populate with the full pathname to this
line as follows:
2. In a unix window, type cd and cut and paste the full pathname
from your Address field.
3. Type ls to get a listing of files in this directory. You should see

files similar to the following:
Most of these files are standard ProMAX files with the exception
of the replica* files.
replicaParms.txt: The replicaParms.txt file is a tab delimited text

file containing SeisSpace flow replication parameters. This file
can be imported to Microsoft Excel for editing.
replicaParms.txt~: The replicaParms.txt~ file is a backup of
replicaParms.txt which is generated whenever replicaParms.txt is
successfully loaded
replicaPrefs.xml: This file contains some constants stored
concerning the replica table such as column width and display
order.
4. Type more replicaParms.txt to examine the contents.

Template flow Files:
5. Change directories to your seg-yextract flow. Since we check

marked Share this Project in the Replica Jobs table, all the
flows that you listed in step 2 should be included in this template
flow directory. The contents should be similar to the following:
exec.#.*: These are the files associated with the template flow
exec.r#.#.* These are the files associated with each replica flow.
The first # represents the sequence number and the second # is the
replica version number (starting with 0)
*.log files: Similar to ProMAX job.output listings. These ASCII

files contain information output from the executing/executed job.
replicas.#.stat: These are binary files contain the job status

information for replicas of a particular version.
replicasInfo.xml: This file indicates the flow is a template and

stores the users descriptive names of the replica flows.
Summary:
This chapter should have provided you with a better understanding of
the components involved in SeisSpace Flow Replication. You should
also have a general understanding on how to use these components to
create a project and build and submit flows using Flow Replication. The
next chapter will provide further examples of creating flow replication
projects and introduce more advanced topics such as flow chaining and
reading data from other projects.


Chapter 2
SeisSpace Flow Replication
Workshop
This workshop is intended to provide practical examples of the use of SeisSpace Flow Replication
on a large seismic processing project. We will also introduce the more advanced concepts of Flow
Chaining and reading data from other lines. In the end, we provide tips for effective flow
replication and for avoiding pitfalls.
Workshop Overview
In this workshop you will set up and execute flow replication for a
virtual project called PM2000 by doing the following:
o Create a Template for Converting SEGY field tapes
o Build a Replica Table for the PM2000 seismic project
o Utilize the Replica Job Table (RJT) to build, submit, and

monitor jobs on the system.
o Learn how to use Flow Chaining in several different ways.
o Learn how to read data from other lines/subprojects.
o Review Guidelines for Success using Flow Replication

Chapter 2: SeisSpace Flow Replication Workshop
PM2000 Seismic Project Background
The PM2000 Seismic Project is a virtual project we will use to

demonstrate some of the features and functionality of SeisSpace Flow
Replication.
Acquisition was undertaken by a single vessel pulling three streamers

that are 6000 meters long and 50 meters apart. It has dual alternating
sources firing every 25 meters. In this workshop, there are 88 sail lines
that generate 528 CMP lines. The incoming data is organized by
saillines, so you will be building the SeisSpace Flow Replication project
to process the 88 sail lines due to arrive today.
You have received a list of saillines for the completed survey along with
field reel numbers and FFID range for each of the sail lines. Your boss
wants you to get all field data converted to internal processing format as
quickly as possible. Today is the last day of the workweek. Do you have
plans for the weekend?

Line List and Map
The following table contains the current data shipment listing of lines,
field reel numbers, and processing range for the PM2000 Marine survey
you are going to process.
seq PM200 Line list reel # FFID seq PM2000 Line list reel# FFID
1 PM2000_100106 10002 3-216 26 PM2000_115156 10027 3-590
2 PM2000_100712 10003 3-216 27 PM2000_115762 10028 3-590
3 PM2000_101318 10004 3-216 28 PM2000_116368 10029 3-590
4 PM2000_101924 10005 17-230 29 PM2000_116974 10030 3-590
5 PM2000_102530 10006 9-222 30 PM2000_117580 10031 3-590
6 PM2000_103136 10007 3-216 31 PM2000_118186A 10032 32-619
7 PM2000_103742 10008 3-590 32 PM2000_118792 10033 3-590
8 PM2000_104348 10009 3-590 33 PM2000_119398 10034 3-590
9 PM2000_104954 10010 3-590 34 *PM2000_119904 10035 3-590
10 PM2000_105560 10011 3-590 35 PM2000_120510 10036 3-590
11 PM2000_106166 10012 3-590 36 PM2000_121116 10037 3-590
12 PM2000_106772 10013 27-614 37 PM2000_121722 10038 3-590
13 PM2000_107378A 10014 3-590 38 PM2000_122328 10039 3-590
14 PM2000_107984 10015 3-590 39 PM2000_122934 10040 3-590
15 PM2000_108590 10016 3-590 40 PM2000_123540 10041 3-590
16 PM2000_109196 10017 4-591 41 PM2000_124146 10042 3-590
17 *PM2000_109702 10018 2-589 42 PM2000_124752 10043 3-590
18 PM2000_110308 10019 3-590 43 PM2000_125358 10044 3-590
19 PM2000_110914 10020 3-590 44 PM2000_125964 10045 3-590
20 PM2000_111520 10021 3-590 45 PM2000_126570 10046 3-590
21 PM2000_112126 10022 3-590 46 PM2000_127176 10047 3-590
22 PM2000_112732 10023 3-590 47 PM2000_127782 10048 3-590
23 PM2000_113338 10024 20-607 48 PM2000_128388 10048 3-590
24 PM2000_113944 10025 3-590 49 PM2000_128994 10050 1-588
25 PM2000_114550 10026 3-590 50 *PM2000_129500 10051 1-588

seq PM200 Line list reel # FFID seq PM2000 Line list reel# FFID
51 PM2000_130106 10052 3-590 73 PM2000_143338 10074 3-590
52 PM2000_130712 10053 3-590 74 PM2000_143944 10075 3-590
53 PM2000_131318 10054 3-590 75 PM2000_144550 10076 3-590
54 PM2000_131924 10055 3-590 76 PM2000_145156 10077 3-590
55 PM2000_132530 10056 3-590 77 PM2000_145762 10078 3-590
56 PM2000_133136 10057 3-590 78 PM2000_146368 10079 3-590
57 PM2000_133742 10058 3-590 79 PM2000_146974 10080 3-590
58 PM2000_134348 10059 3-590 80 PM2000_147580 10081 3-580
59 PM2000_134954 10060 3-590 81 PM2000_148186A 10082 3-570
60 PM2000_135560 10061 3-590 82 PM2000_148792A 10083 3-560
61 PM2000_136166 10062 3-590 83 PM2000_149398B 10084 3-550
62 PM2000_136772 10063 3-590 84 *PM2000_149904 10085 3-540
63 PM2000_137378 10064 3-590 85 PM2000_150510 10086 3-530
64 PM2000_137984 10065 3-590 86 PM2000_151116 10087 3-520
65 PM2000_138590 10066 3-590 87 PM2000_151722 10088 3-510
66 PM2000_139196 10067 3-590 88 PM2000_152328 10089 3-500
67 *PM2000_139702 10068 3-590
68 PM2000_140308 10069 3-590
69 PM2000_140914 10070 3-590
70 PM2000_141520 10071 3-590
71 PM2000_142126 10072 3-590
72 PM2000_142732 10073 3-590
Line names proceeded by an asterisk (*) mark the beginning of each Fill operation

Acquisition Configuration
NRP
30 m
75m
50 m
50 m 50 m
Near Group
6000 m

Begin the Workshop
Building the Templates
The first step is to build a template to process the data. With our primary
goal of converting the field SEGY data into our internal processing
format, we will begin by creating a simple SEGY Input flow.
Create the Area, Line, and Flow

1. In the Navigator tree view, click on your Flow Rep class -
<Username> area and click MB3 -> New -> New Subproject.
2. Create a line called <your initials> PM2000.
3. Under the <your initials> PM2000 line, add a new flow called
segycvrt.
4. Build a flow with SEG-Y Input and Disk Data Output. Open
the SEG-Y Input parameters and set the Type of storage to use
to Disk like the following:
5. Save this flow. We will come back to it later to Templatize it and

mark parameters for substitution.

Building the Replica Table
The replica table defines the lines (or data segments) that make up the
survey. In this workshop, you will be creating a replica table listing the
sail lines found on Line list.
1. With your segycvrt flow active, open a replica table using either
Tools -> Replica Editor or clicking on the replica Icon
2. If the Adding Replicas message comes up, then click OK. Now
add the necessary rows to accommodate all 88 lines listed in the
PM2000 Line list (MB3 -> Add Rows)

3. Highlight the Subproject column from row 1 to 17 and with MB3,

select Fill Column to launch the String Fill GUI which should
look like:
Our Goal is to populate the Subproject column with the names as seen
in the Line List. The string fill GUI will add any information contained
on the left side of the + symbol when the plus symbol is clicked.
4. The first string our line list contains is PM2000_. Enter this into
the String field and hit the + symbol.
Our rows, represented by [0] through [16] on the lower right hand side
of the GUI, should now be populated with PM2000_. If they are not,
you can hit the Clear button and try step 4 again.

5. The second part of our line starts with 100106 and increments by
606. Enter these values into the Number Range Start and Incr
columns and clear out the Sep, End, and Incr columns. After
hitting the + symbol associated with the Number Range, [0]
through [16] should be filled in with the appropriate linenames as
follows:
If the results look like the example above, click the OK button. If they
dont, click the Clear button and change your values until they do.
In this example, the fill column operation returns the desired results for
the first 16 lines. The resulting value for sequence 17 however is
incorrect, because the increment changed for this line. We need to
modify the fill column starting value to attain the correct line names.

6. Highlight rows 17 - 33 and launch the Fill Column dialog.
7. We now want to alter the starting value of the number range to be

109702. The steps to perform this are outlined in the GUI below.
You can highlight the 100106(606) at the bottom part of the GUI
[Step 1], click Edit [Step 2], change the starting value of the
number range [Step 3] and click the checkmark sign [Step 4]:
Step 4
Step 3
Step 1
Step 2
8. When you achieve the desired result, mimicing the line numbers
from the line list map for rows 17-33, click OK.
9. Continue the process of adding the lines until all the lines listed on
the PM2000 Line list are generated. The line names proceeded by
an asterisk on the line list are the starting lines for each fill
operation.

Note that several lines in this survey were reshot (as indicated by the
alpha character following the line name).
10. Review the Line List and locate the (A) and (B) lines.
11. In the Replica table, double click the row you need to edit (so it is
no longer a grey box but contains a flashing cursor) and append
these (A) or (B) values.
12. Save this replica parameter table.
Once all of the sail lines in the survey are listed in the replica table, we
can begin to add sail line specific information to the table for later use
in flow replication.
Generate field reel number list
1. In the Replica Parameters table, click MB3 -> Add Column to add
a new column to the replica table. This will define the field reels
associated with each sail line.
2. Name the column Field_Reel_Number.
3. For column type, select Integer. Uncheck Add to beginning,

and click OK.
4. Highlight all the rows in the new column, select the MB3 -> Fill
Column option, enter the appropriate Start and Increment values
to fill each line with the appropriate reel number and click OK.
5. Import the FFID ranges
In modern acquisition, much of the line acquisition parameters are

delivered to the processing center in the form of a spreadsheet or ASCII
file. When this is the case, you can import the line parameters directly
into the Replica table using the File -> Import option.

1. Add two new INTEGER columns to the end of the Replica table.
Name the first column, Start_FFID, and the second, End_FFID.
2. Highlight all rows under the Start_FFID column and select File -
> Import from the top left corner of the Navigator GUI. You will
receive a dialog similar to the following:
3. Change Files of Type to All Files.
The instructor will direct you to the location of the

master2_Start_FFID.txt file containing the Column Start FFID values.

4. Select the appropriate file and click on Open, and fill out the
Confirm Import window as follows:
We do not want to import the header lines, so we are importing starting

at row 7. We just want the first column, which contains our Starting
FFID numbers, and we selected Paste at selected cell, so it will import
into the highlighted rows for Start_FFID.
5. When the GUI is filled out appropriately, click Yes. The

Start_FFID column should now be filled out with the imported
information.

The illustration below shows the header information

and format of this column.txt file:
6. Repeat this process for the End_FFID column using the

master2_End_FFID.txt file.
7. Save your replica parameter table.
Import Row Files:
Just as we saw in the previous chapter, it is not always necessary to

import values from an ASCII file column by column. If the organization
of the replica table matches the ASCII file, the entire contents may be
imported with a single import command.
In this example we will assume we received 10 additional lines (beyond

the 88 original saillines), including ASCII file that includes replica
parameters earlier work done in ProMANAGER (Landmarks previous
flow replication software). The attribute fields in a text file exported

from ProMANAGER are separated by & signs. Here is the

master2_rows_4_columns.txt ASCII file we will be importing:
Now lets append these additional10 rows of information into our

replica parameter table.
1. Make sure you have the columns for the import rows in the same
order as the ASCII file. If necessary, use MB1 on the column
headers to drag and drop them into this order:
2. From the top left corner of the Navigator GUI select File ->
Import.

3. From the resulting dialog, change to the Replica_import_rows

directory and import the master2_rows_4columns.txt file.
In this file, all the attributes are separated by an & sign so we will
indicate we want to use & as the delimiting character and append these
rows to our table. Our import file begins with the Subproject. As Seq
is the first column in our replica table, we will start appending to the
table at column 2. Also, there are 6 lines of header information, so we
will start importing from row 7.
4. Fill out the Confirm Import GUI as follows and click Yes:
The new rows with all the values for each column are appended to the
bottom of the replica table.
There should now be 98 rows in your Replica Parameters table. If any

empty rows exist beyond row 98, highlight the rows, and use MB3 ->
Remove Rows to delete them.
When you delete rows you are prompted for a response on what to do
with Replica Flows the may have been built against these sequences for
some templates.

Delete stranded replicas will delete any replica flows for these
sequence numbers when you delete the rows.
Proceed without deleting will delete the rows without deleting any
replica flows that may exist for any template for these rows.
5. We have not created any replicas against these rows, so this is a

not an issue for this case. Click Delete stranded replicas.
6. Save your replica parameter table.
Checking the Project
At this point, all of the lines in the survey are entered into the Replica
table along with some basic information associated with each line.
Before building the Templates, confirm that all 98 of the lines are listed
in the Replica Jobs Table.
1. Confirm the active project element in the navigator tree is set to

<user initials> PM2000.
2. Launch the JobStatus dialog using either the Icon or the Tools ->
Replica Jobs pull down option.
Your display should match the following:

3. Scroll down through the listing and make sure all 98 lines are
present.
4. Resize the columns if necessary using MB1 on the column title.
5. If all the lines are present, proceed to the next section. If they are
not, go back to the Replica Parameters table and fix the problem.
Set up the template parameter substitution
1. Highlight the segycvrt flow in the Navigator tree to view the flow
in the Flow Editor window.
2. With segycvrt as the active flow, click on the Toggle between

flow and template view icon:
3. In the Templatize flow warning dialog, click Templatize.
4. Target Enter DISK file path name(s), in SEG-Y Input for

substitution (click on the radio button to the left of the parameter).
5. If you do not see your Replica Parameters listed on the right hand
side of your Navigator GUI, click the Show or Hide Template
parameters Icon:
6. Create the necessary substitution parameter to define the path to

the input SEGY file.
The instructor will provide the necessary directory path for the above
operation. Field data in this example is cataloged using the line name
and _segy. The substitution parameter created will need to address
this naming convention to insure the correct SEG-Y data is assigned to
each line.
For this example, we need to combine text and the line name defined in
the Replica Parameters table to create the path name to the appropriate
segy file, then append _segy to the string to create the completed input
path name. Use the following format:
/path/to/segy/input/+r.Subproject+_segy

As we saw in the previous chapter, entries in quotes are passed

unchanged. The +r.Subproject will be substituted with values from
the Subproject column from the Replica Parameter table.
7. In the parameter section for Disk Data Output, target the Output
Dataset Filename parameter for substitution.
NOTE: In SeisSpace, the Output Dataset Filename must always be

targeted for substitution, even in the 2D case where these datasets are in
separate lines and the dataset name might not change. This was not
necessary with ProMANAGER.
8. Create a substitution parameter to name the converted SEG-Y field

data by dragging and dropping the Subproject field under the
Replica Parameters and appending a +_convert
In this example, the output name will be the line name with _convert
appended.
9. Use the Validate Icon and toggle results to check the results of the
substitution.
10. Use MB1 to stretch the columns wide enough view the full result.
Your validation table should look like the following, except the
full path to your SEGY file may be different:
11. If your results look right, close your validation table. If not, make
the necessary changes and refresh you validation table to update
your results.

Building Replica Flows
With the Template built and substitution targets and sources defined, we
are now ready to generate the replica flows belonging to each line in the
PM2000 survey. As seen before, this is accomplished from the Replica
Jobs table.
1. Close the Replica Parameters tab, answering yes to save, and

open the Replica Jobs table.
2. Select the first 3 lines listed and build the flows by clicking MB3 -
> Build. Alternatively, you can use Ctrl B as noted in the MB3
menu to the right side of build. If the flows build properly, you
should see the following:
Note: It is recommended that you build and test using a single line to
confirm parameter substitution. In this example, the first 3 lines are
selected to demonstrate how to build multiple flows simultaneously.

Checking the Build
1. Highlight your first segycvrt Built cell and click MB3 -> Flow
Viewer. The contents of the Flow Viewer window should be similar
to the following:

2. Toggle between the available flow viewing tabs at the bottom of

the window. You may find the Flow HTML tab to be the easiest
to read.
Note the name assigned to this new flow at the top of the flow table:
This flow was treated like a 3D flow and placed in the same line as our
template. For this project, lets treat each sailline as a 2D line and create
a separate 2D line for each Subproject.
Close out your flow window and uncheck mark the Share this Project
toggle at the bottom left side of the Replica Jobs table. You should
receive the following warning dialog:
3. Select Yes and the three flows we built will be deleted
4. Rebuild the same three flows. and bring up the flow viewer for the
first flow again. This time the name assigned to this flow should be
built under its respective replica subproject:
Replica Subproject
For 2D lines, Share this Project should not be check-marked and

each flow will be placed in its own line defined by the Subproject
entry in your Replica Parameters table.
5. Highlight the segycvrt cells for the 3 flows you have built, click
MB3 and select Submit. This brings up the Submit Job GUI.

6. In the Submit Job GUI, make sure local is highlighted for hosts
and click Submit.
7. While a job is in the running state place the cursor over it. You
should receive information about your job such as:
Your job status should update interactively and end with Completed if
your job ran normally. If this is not the case, view the job.output using
the steps indicated below, fix the problem, and resubmit the flows.
View the Job Log

After a job is submitted, you can access the job log (formerly job.output)
by highlighting the cell of the job of interest and using either Ctrl V or
MB3 -> Log Viewer. You can also double click on the cell to launch the
log viewer.
Alternatively, if you wish to only view the tail, or end of the job log
listing after your job has submitted, you can hold down MB2 on the
status cell to activate a pop-up.
8. Highlight the next 3 lines and click MB3->Build and Submit ->
Local Submit
9. With at least one segycvrt cell highlighted, click the detailed

view icon to acquire statistics concerning each segycvrt job that
has been submitted.
Exercise - Using the Database with SeisSpace Flow Replication:

10. From the Navigator tree, create a new flow called xtracgeom in
Flow Rep class - <Username> / <your initials> PM2000.

11. In the Flow Editor, place the following modules in xtracgeom:
12. Change the following parameters from their default values:
SEG-Y Input:
Type of storage to use: Disk
MAX traces per ensemble: 240
Remap SEGY header values? Yes
Extract Database Files:

Is this a 3D survey?: No
Data Type: Marine
Source Index Method: FFID
Trace Display Label:

Trace label: Extracted Shots
13. Templatize xtracgeom
14. For SEG-Y Input, target Enter DISK path name(s) for
substitution. Define the regular expression to input the SEG-Y
disk dataset associated with each line. You can copy the expression
from the segycvrt flow using Ctrl C and paste using Ctrl V.

15. For Disk Data Output target Output Dataset Filename for
substitution. Define a substitution to append _convert to the line
name (subproject).
16. Hit the Validate icon and examine the results of the substitutions.
17. When you are satisfied the substitutions are correct, close the
validation table and open the Replica Jobs table.
The new flow, xtracgeom, should be listed in the JobStatus dialog. If it

is not, click the refresh icon.
18. Use Build and Submit to locally submit the first 3 jobs.
Accessing the data base
You can launch DBTools in SeisSpace by clicking the Icon or

using Tools -> DBTools
View database values with DBTools
1. When the 3 jobs complete, highlight line PM2000_100106 in the

Navigator Tree, accessible from Navigator tab, and click Tools ->
DBTools.
2. From the DBTools dialog for line PM2000-100106, double click

on the TRC -> CDP attribute to launch the 2D Crossplot. It should

look like the following picture. However, the colors of your

attribute may vary depending on your default colormap;
Remember, when starting a project using SeisSpace Flow Replication,

you must decide how you want SeisSpace to organize the file system
and database via the Share this Project toggle. Be sure to choose the
appropriate method before building flows.

Flow Chaining
We will now run a few flows to demonstrate the flow chaining

capabilities.
Chaining flows together means that a flow will not be submitted until
another flow, or multiple other flows complete successfully. You may
chain regular flows or replicated flows built from templates.
To chain flows together you answer Yes to the Chain this flow?
question in the beginning of the flow. You then type in a flowname or
flownames which must complete successfully before the chained flow
will be automatically submitted for execution.
Chaining Replicated Flows: one template chained to one other template

1. In your <Your initials> PM2000 line create a flow called gain with
the following modules:
2. If your parameters for each module are not visible, use the
following icon to see them:

3. Scroll to the beginning of the flow, toggle Chain this flow to

Yes. Enter segycvrt for the Chain Precursors parameters, so
the chain parameters are the same as:
4. Templatize this flow.
5. Mark Select Dataset from Disk Data Input for substitution.

Drag and drop the Subproject name and add +_convert to
match the output of the segycvrt template.
6. Scroll down to Disk Data Output and mark Output Dataset

Filename for substitution. Create an output dataset appending
+_gain to the Subproject.
7. Save this template.
8. Bring up the RJT (replica jobs table) for this line.
Since we have chained the gain template to the segycvrt template,

lets rearrange our columns in the RJT.
9. Click on the segycvrt column header to move the column to the

left of the gain template. In this order, the job sequence
progresses from left to right, which is a more familiar presentation
for monitoring project status.

10. Highlight the grey flows that have Unknown status in the
following view and locally build and submit all six of these flows.
You should see the gain flows having status of Chained until the
corresponding segycvrt flow completes successfully. Upon
completion the chained flow will automatically be submitted for
execution like the following time captured example:
Chaining Replicated Flows: chaining to replica sequence number
There are cases where you would want a set of replicated flows from the
same template to run in sequence. One example of this is running

Extract Database files on a 3D dataset. Each replicated flow is writing

to the same database, so you need each flow to run to completion, adding
its information to the database, before the next flow starts. You want the
jobs chained together so there is minimal lost time between jobs.
1. Go to your Manhattan 3D line generated from the previous

chapter and edit your SEG-Y Extract flow.
In this case we do not want to chain the very first flow, as we want this
to start the serial flow chaining, so we must add a parameter in our
replica table to indicate this.
2. Initiate the Replica Parameters table for the Manhattan 3D line

and add a new column of type STRING to the end of the table
called Chain.
3. Fill in this new Chain parameter for Seq 2, or Subproject SEG1,

with the value false, and Seq 3-10 with the value of true. Do not
use quotation marks or apostrophes.
4. Save your Replica Parameters Table:
5. Back in the flow editor for your SEG-Y Extract template, target
the Chain this flow parameter for substitution, populate this
parameter by dragging and dropping the chain replica. If you do
not see the Replica Parameters on the right hand side of your
Navigator GUI, open it with the following icon:
6. Target Chain Precursors for substitution and fill the substitution

parameter as follows:
Above is the proper syntax for indicating previous sequence numbers.

Sequence number(s) must always be surrounded by square brackets [].

7. Validate to ensure the syntax is correct. Items such as unmatched

quotations marks will be indicated. If you typed everything
correctly, your validation should look like the following:
8. Initialize the Replica Jobs table for Manhattan 3D and locally

build and submit the remaining jobs. All the sequenced flows
should be chained and they should run sequentially one after the
other, as this example suggests:

Chaining replicated flows: Many jobs to one job
There may be instances where you want many jobs to finish before you can proceed to the next
single job. One example would be Extract Database files to Geometry Spreadsheet for 3D data.
Geometry Spreadsheet is dependent upon completion of all the Extract Database Files to work on
a full database. In this example we will also explain how to delete multiple replicated flows at
once, and how to Disable Replicas.
1. Create a flow under your Manhattan 3D line called Geom.

Spread and populate it with the 3D Land Geometry
Spreadsheet module.
2. Templatize the flow.
3. Specify Yes for Chain this flow?, and parameterize the Chain
Precursors parameter as follows:
Note: You must Templatize a flow to view it in the Replica Jobs table,
but you do not have to specify any substitution parameters.
Deleting Multiple Replicated Flows:

4. Open the Replica Jobs table for Manhattan 3D and mark SEG-
Y Extract cells for Seq 2-10. Click MB3 -> Delete Replica flows
so we can test this flow chaining example.
This is also a handy tool when you need to change the parameterization
of a template and rerun jobs.
5. Locally Build and Submit Seq 2-6, (or Subproject SEG1-5) again
for the SEG-Y Extract template. You should see your flows
chained and submitted one after another, as a result of the previous
serial flow chaining exercise.
Disabling Replicas:
We now have two templates. SEG-Y Extract will be run once for each
swath (Seq 2 - 10), and Geom. Spread will be run once for the entire
survey (Seq 1). We will, therefore, Disable the replicas for the
sequences we wont use.

6. Highlight Seq 0 for SEG-Y Extract and disable this replica by

clicking MB3 -> Enable/Disable Replicas. (Note, this is a toggle,
allowing you to re-enable a replica if necessary)
7. Highlight Seq 2 through 10 for the Geom. Spread template and

disable these sequences.
All the disabled sequences should be greyed out.
8. Try locally building and submitting the Geom. Spread template

using the Seq 1 cell. You should see the following:
The submit failed because SEG-Y Extract was not marked as

completed for all the sequences indicated in Geom. Spreads chained
precursor parameter.
9. Now highlight both the SEG-Y Extract cells for Seq 7-10 and the
Geom. Spread cell for Seq 1. and locally build and submit these
flows.
Geometry Spreadsheet should now run once the last SEG-Y Extract
flow completes.
10. Exit out of the Geometry Spreadsheet GUI.

The job status of your Replica Jobs table should now look like:

Reading data from other lines / projects
In this example we will create a new set of 2D lines in a different project

In these new lines, you will read the datasets data from the 2D lines we
created in the beginning of this chapter.
1. Create a new project called Flow Rep read- <user initials>.
2. Create a subproject under this project called Set-2 <your

initials>-PM2K
Create a flow under this new line called read data-ano. line
Your new area, line, and flow should look similar to the following in
your navigator tree:
3. Populate your read data-ano. line flow with the following

modules:
4. Templatize this flow. (T icon)
Now build a replica table which contains the same line numbers as our
workshop for the suffix, and SET2- for the prefix.

5. Click Tools ->Replica Editor to initiate a replica table for this

new line.
6. Click MB3 -> Add rows to add 12 new rows.
7. Highlight the Subproject cells for all the rows and click MB3 ->
Fill column.
8. Populate the String with SET2- (without the quotes) and hit the
+ for that row.
9. Populate the number range with 100106, increment of 606.

Blank the Sep, End, and Incr fields, and hit the + icon for
that row. Your String fill GUI should now look like:
10. Click OK.

11. Add another STRING column called Linename to the end of the
replica table and populate it with the 6 digit line name (100106
incrementing by 606).
12. Save the Replica table.
13. In the flow editor, edit your read data-ano. line template,
marking the Disk Data Input Select dataset parameter for
substitution and fill this with an expression which will identify the
area and lines you created in the beginning of the chapter. It will be
similar to the following with your area name substituted for Flow
Rep class - U:
Flow Rep Class - U | PM2000_+r.Linename | PM2000_+r.Linename+_convert
Note the spaces before and after the pipe | symbol.
14. Mark the Disk Data Output Output Dataset Filename

parameter for substitution and fill it with the following equation:
15. Use the Validate icon to check your substitution parameter results.
They would be similar to:
16. Close the validation table and open the Replica Jobs table for this
new set of lines.

17. As we are reading data from other 2D lines and creating a new set
of 2D lines, uncheck Share this Project and click Yes to the
Possible Stranded replicas message.
18. Locally build and submit the first three replicas. The flows should
run, reading data from the other lines, and complete normally. If
they do not, check the job.output (MB3 ->Log Viewer) for clues to
the problem, fix the problem, and resubmit the flows.
Once these jobs have completed normally, you will have successfully
built and submitted flow replicated jobs reading input data from a
different project.
NOTE: Datasets can be read from different projects within a given

DATA_HOME. However, datasets cannot be read across separate
DATA_HOMEs. This is because each DATA_HOME may have its own
config_file defining secondary data partitions that might not be mounted
across all the necessary hosts in your network.

Guidelines for Success with Flow Replication
When used appropriately, the flow replication tools described in this

class can significantly improve efficiency and management of large
seismic projects.
With experience, these tools can make all aspects of the processing task
faster, easier, more efficient, and therefore, more profitable. More can
be accomplished by fewer people, in less time, and with fewer errors
when repetitive tasks are performed by the computer rather than the
analyst.
But just as flow replication can assist the analyst, it can also impede
progress, and in the worst case, force large scale reprocessing if an
incorrect parameter is used. Flow Replication enables the analyst to
generate and submit large numbers of jobs in a very short period of time,
but automation doesnt guarantee quality if parameter checking and
strict quality control procedures arent followed.
The impact of a parameter error is compounded by the number of jobs

submitted before the error is discovered.
Recommendations for Success
1. Do all geophysical testing, then build and confirm that you have a
sensible processing sequence.
2. Test each flow that will be used as a Template BEFORE you build
a bunch of production flows with it.
3. Make no changes to the Template, no matter how minor, without

re-testing.
4. After production begins, the Template must never be altered.
5. Avoid including interactive tools in replicated flows when running

mass-scale production processing jobs. For example, use caution
when displaying data with Flow Replication. Every flow
submitted containing Trace Display will attempt to produce a
display.
6. Establish a naming convention for datasets, parameter tables, and

velocities before starting production.

7. Check on available disk before mass-submitting.
8. Do not change the Share this Project toggle after production

begins. If you do, you will receive the following warning message:
If you click Yes, all processing generated before this switch is toggled
will be removed.
9. Do not mark parameters for substitution which will alter the menu.
A good example of this would be the TYPE of mute parameter in
the Trace Muting module. Changing the parameter from Top to
Surgical alters the parameters under the menu, as seen below:

10. Do not over-automate. Keep substitutions simple to facilitate

checking and problem solving.
11. The use of JavaSeis datasets is covered in a different training class.

However, if you decide to use JavaSeis Datasets in conjunction
with Flow Replication, please follow this procedure:
If you use Flow Replication to build a series of jobs that will write to the
same output JavaSeis dataset, please heed the following information.
In the JavaSeis Data Output menu:
Set the Create/recreate dataset at runtime (deleting any existing

version:? parameter to No. Use the Create button from the Create/
recreate dataset NOW, deleting existing versions (UNATTEMPTED)
parameter to do a quick sanity check of the output dataset framework.
After the jobs are built, edit the first replica flow and change the Create/
recreate dataset at runtime (deleting any existing version:? parameter to
YES. Submit this first job to the queue. This first job creates or recreates
the framework for the output JavaSeis dataset during the initialization
phase. When this first job moves to Running; status, then and only then
should you submit other replicas that will write to the same JavaSeis
dataset.
Summary
This course is designed to familiarize you with the use of SeisSpace
Flow Replication for large scale production processing projects. If the
tips covered in this Guidelines for success section are followed, a user
can expect a measurable increase in productivity and throughput.


SS FlowRep NoCover

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SS FlowRep NoCover

Enviado por

Direitos autorais:

Formatos disponíveis

Production Processing with

SeisSpace Flow Replication

Part No. 200002A June 2007

Landmark Graphics Corporation

SeisSpace Flow Replication Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Ultimate Goal:. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Flow Replication Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Flow Replication Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

SeisSpace Flow Replication Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Line List and Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Acquisition Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Begin the Workshop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Flow Chaining. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Reading data from other lines / projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-35

Guidelines for Success with Flow Replication . . . . . . . . . . . . . . . . . . . . . . . . . 2-39

Landmark Production Processing with SeisSpace i

ii Production Processing with SeisSpace Landmark

In this chapter, you will learn about:

o The SeisSpace Flow Replication Components

o The procedure for replicating flows

o Descriptions and locations of files generated by Flow

Landmark Production Processing with SeisSpace 1-1

SeisSpace Flow Replication is a flow replication, job submission, and

Project management with SeisSpace Flow Replication utilizes the

1-2 Production Processing with SeisSpace Landmark

Landmark Production Processing with SeisSpace 1-3

1-4 Production Processing with SeisSpace Landmark

Flow Replication Procedure

Design a processing sequence as a series of flows.

Landmark Production Processing with SeisSpace 1-5

Flow Replication Components

Flow Replication is integrated into the SeisSpace user interface. We will

In this example, we have obtained SEG-Y shots of the Manhattan 3D

1. Start a SeisSpace session, and highlight the

4. Highlight your Manhattan 3D project, and click MB3 -> New -

1-6 Production Processing with SeisSpace Landmark

As of version 2003.19.1, SeisSpace modules can be used with Flow

Landmark Production Processing with SeisSpace 1-7

You will receive the following warning message:

This is what we refer to as Templatizing the flow.

7. Click on Templatize. Your flow will now contain bullets in front

1-8 Production Processing with SeisSpace Landmark

Note the asterisk in front of the Flow name:

8. Save your flow using File->Save or the following icon:

Guidelines for substitution:

Landmark Production Processing with SeisSpace 1-9

Importing ASCII file to Replica table:

9. With the SEG-Y Extract flow highlighted, click Tools ->

A replica table should appear. If it contains the following message, click

1-10 Production Processing with SeisSpace Landmark

We now need to populate our replica table with the columns of

12. Repeat Step 11 to create FFID_Range, Min_ILINENO and

Landmark Production Processing with SeisSpace 1-11

MB1 to drag them to the desired order. Once complete, your

13. Highlight all your cells as shown below:

1-12 Production Processing with SeisSpace Landmark

15. We dont want to import our header information, so indicate you

Landmark Production Processing with SeisSpace 1-13

1-14 Production Processing with SeisSpace Landmark

We have toggled three parameters for substitution in the first two

Landmark Production Processing with SeisSpace 1-15

parameters names. These selected parameters are also highlighted in

Before we proceed, we need to explain how to create these substitution

Substitution Naming Conventions