Version 2013

ProSource Seismic
Administration Guide
Copyright © 2004-2015 Schlumberger. All rights reserved.
This work contains the confidential and proprietary trade secrets of
Schlumberger and may not be copied or stored in an information retrieval
system, transferred, used, distributed, translated or retransmitted in any
form or by any means, electronic or mechanical, in whole or in part, without
the express written permission of the copyright owner.
Trademarks & Service Marks
Schlumberger, the Schlumberger logotype, and other words or symbols used
to identify the products and services described herein are either
trademarks, trade names or service marks of Schlumberger and its
licensors, or are the property of their respective owners. These marks may
not be copied, imitated or used, in whole or in part, without the express
prior written permission of Schlumberger. In addition, covers, page
headers, custom graphics, icons, and other design elements may be service
marks, trademarks, and/or trade dress of Schlumberger, and may not be
copied, imitated, or used, in whole or in part, without the express prior
written permission of Schlumberger. Other company, product, and service
names are the properties of their respective owners.
An asterisk (*) is used throughout this document to designate a mark of
Schlumberger.

Schlumberger Private - Customer Use

iv ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

Contents
1 Information Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Schlumberger Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

About Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Document Last Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Online Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Typestyle Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Alert Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Contacting Schlumberger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

2 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Purpose of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Who Should Use This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Format of This Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
Overview of ProSource Seismic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Related Reference Materials . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
ProSource Seismic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

3 Post-installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Post-Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

4 Scan/Edit/Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Files Used by Scan/Edit/Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Parameter File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
EBCDIC Overlay File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Starting Scan/Edit/Load job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Starting Scan/Edit/Load Job from User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Contents v

Schlumberger Private - Customer Use

Administration Guide

Starting Scan/Edit/Load Job from Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Reading Large Records from Tape Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Processing Seismic Files/Tapes in Batch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Restarting Scan/Edit/Load Job (Unavailable License) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12
Viewing Scan/Edit/Load Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Displaying the “Set SP equal to CDP” check box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Java Out of Memory Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15
Loading Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15

5 Tape Index Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

About Tape Index Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Starting Tape Index Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Loading Tape Index Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Associate Datastore, Project and Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Select Survey . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
Select Survey CRS from Previously Used CRSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7
Select Survey CRS from All CRSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10
Select Template Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
Index Control File Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
Creating Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Opening Data File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
Header and Delimiter Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Data Field Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
Saving Template File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Select Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
Select Tape Index File(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Remove Tape Index File(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Select Data Override Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18
Validate Input Data and Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
Submit Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20

6 Navigation Loader (2D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Viewing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Control File Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Creating and Saving Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

7 Loading 3D Navigation with Scan/Edit/Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

vi ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Viewing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Control File Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Creating and Saving Control File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

8 Project Scan Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
Project Scanning in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Need for Batch Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Running Job in Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Setting Cron Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Viewing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Troubleshooting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11
Timeout Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

9 Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Data Transfer to Charisma . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Relevant values in SEG-Y headers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Automatically Creating Surveys by OSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Viewing and changing Z-range values in Charisma . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Seismic Export Order Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Viewing Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Sending Data to SEOW via Table View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7
Sending Data to SEOW via GIS View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8
SEG-Y Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Project-to-Project Data Copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Project to ZGY Data Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10
Export to Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-13
Export to Trace Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-15
Navigation Export Order Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Sending Data to
Contents vii

Schlumberger Private - Customer Use

Administration Guide

NEOW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-21
Sending Data to
NEOW via GIS View using Seismic Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22
Navigation Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23
Aliases for
Datum and Spheroid Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24
Managing Export Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Email Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Monitoring Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25
Distributor Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
Job Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26
ProSource Export Jobs Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Updating Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Resubmitting Failed Export Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-27
Cancelling Export Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28
Selecting Device for Export to Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-28

10 User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Setting Up User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2

Creating New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Granting Seismic Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
Granting Project Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Verifying User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Configuring Business Associate Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Creating Person Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Creating Electronic Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5
Creating FTP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6
Creating Physical Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Creating Business Associate Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Creating Group-Person Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8
Creating Application User Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8

11 System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Configuring non WGS-84 Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

Adding a CRS to the Recommended CRS List and Setting Transformation . . . . . . . . . . . . . . 11-3
Managing Custom CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Creating Custom CRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Creating Custom Datum Transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Creating Custom CRS for OpenSpirit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4
Reference Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

viii ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Managing Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Managing Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6
Media and Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Media Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7
Device Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-8
Managing Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Adding Media Definition to Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-9
Modifying Media Definition Stored in Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Deleting Media Definition from Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10
Managing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Adding Device Definition to Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Modifying Device Definition Stored in Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11
Deleting Device Definition from Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12
Archive Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Configuring Output Directory Selection Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Archive Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-13
Managing Bitmap Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Loading Seismic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-15
Managing messaging level for seismic loader logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-17
Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
ProSource Seismic Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-18
Trace Viewer Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19

12 Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2
Spatial Entitlements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Granting Spatial Entitlement to 2D Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3
Granting Spatial Entitlement to 3D Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Attaching Document to Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-4
Viewing Document Attached to Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-5

13 Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

General Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Supported Export Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Recommended Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2
Starting and Stopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Starting Distributor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4
Stopping Distributor from ProSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-5
Contents ix

Schlumberger Private - Customer Use

Administration Guide

Stopping Distributor from Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-6

Configuring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Distributor Log File Name and Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-7
Message Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8
List of Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-8

14 OpenSpirit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Master Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-2
Master/Satellite Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
OpenSpirit Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3
Configuring Secondary User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Creating managed
SEG-Y DataSource . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Preservation of Original Access Dates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-4
Validating OpenSpirit's Access to Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5
Validating ProSource Seismic’s Access to Data Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

15 Command Line Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Generating RODE Image of Original Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-2

Extracting Data from RODE File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Extracting SEG-Y Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Extracting SEG-A/B/C Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-3
Extracting Navigation from SEG-Y File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Mandatory Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Optional Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-5
Extracting Trace Headers from SEG-Y File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Mandatory Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7
Optional Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-7

16 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2
KDE Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-2

Appendix A seismic_loader.properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

x ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 1 Information Resources

In This Section

Schlumberger Product Documentation ......................................................... 1-2

About Schlumberger ............................................................................. 1-2
Document Last Updated........................................................................ 1-2
Typestyle Conventions .......................................................................... 1-2
Alert Statements .................................................................................. 1-2
Related Publications.............................................................................. 1-3
Technical Support ................................................................................. 1-4
Contacting Schlumberger ............................................................................ 1-4

Information Resources 1-1

Schlumberger Private - Customer Use
Schlumberger Product Documentation

Schlumberger Product Documentation

About Schlumberger is the leading oilfield services provider, trusted to deliver superior
Schlumberger results and improved E&P performance for oil and gas companies around the world.
Through our well site operations and in our research and engineering facilities, we
develop products, services, and solutions that optimize customer performance in a
safe and environmentally sound manner.

Document Last April 2015

Updated

Online Documentation is provided in the following electronic formats on the Schlumberger

Documentation product CD:
• PDF files
• Online help
You must have a PDF reader installed to read the PDF files.

Typestyle The following conventions are observed throughout this guide:

Conventions
• Bold text is used to designate file and folder names, dialog titles, names of
buttons, icons, and menus, and terms that are objects of a user selection.
• Italic text is used for word emphasis, defined terms, and manual titles.
• Monospace text (Courier) is used to show literal text as you would enter it, or
as it would appear onscreen.

Alert Statements The alerting statements are Notes, Cautions, and Warnings. These statements are
formatted in the following style:

• • • • • •
Note: Information that is incidental to the main text flow, or to an important
point or tip provided in addition to the previous statement or instruction.

• • • • • •
Caution: Advises of machine or data error that could occur should the user fail
to take or avoid a specified action.

1-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Schlumberger Product Documentation

• • • • • •
Warning: Requires immediate action by the user to prevent actual loss of data
or where an action is irreversible, or when physical damage to the
machine or devices is possible.

Related All documentation resources are available from the Information Management (IM)
Publications Start Page:
URL: http://<hostname>:<port>/imadmin/suite/index.html in which
you supply the appropriate hostname and port data.
The following publications are additional resources for information about ProSource
Seismic
Table 1-1 Related Publications

Document/Resource Description
ProSource Release PS_ReleaseNotes.pdf
Notes Provides an overview of the release of the ProSource
Suite, new features, system requirements and last-
minute product information.
Available on the ProSource installation DVD and
accessible after installation from the IM Start page.
ProSource Seismic PSS_AdminGuide.pdf
Administration Guide Provides information on administrative workflows and
tasks for ProSource Seismic.
Available on ProSource installation DVD and accessible
after installation from the IM Start page.
ProSource Seismic Provides detailed information on ProSource Seismic end-
Online Help user workflows.
Accessible from ProSource Help menu, help buttons in
the relevant interface windows, and also by right-clicking
on features and selecting Help from the pop-up menus.

Information Resources 1-3

Schlumberger Private - Customer Use
Contacting Schlumberger

Contacting Schlumberger

Technical Support Schlumberger has sales and support offices around the world. For information on
contacting Schlumberger, please refer to the information below.
For Technical Support for SIS software:
• Schlumberger Support Portal:
http://support.software.slb.com/Pages/Overview.aspx
• Customer Care Center e-mail: [email protected]
• Phone Support:
- SIS Support (main)
http://support.prod.software.slb.com/pages/SupportContacts.aspx

1-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 2 Preface

In This Chapter

Purpose of This Document .......................................................................... 2-2

Who Should Use This Document ............................................................ 2-2
Format of This Document...................................................................... 2-2
Overview of ProSource Seismic.................................................................... 2-3
Related Reference Materials ........................................................................ 2-4
ProSource Seismic Documentation ............................................................... 2-6

Preface 2-1
Schlumberger Private - Customer Use
Purpose of This Document

Purpose of This Document

This document provides information about ProSource* Seismic components, which
are used in order to perform and/or monitor data loading and exporting, such as
Scan/Edit/Load, Navigation Load, Export Order Wizard, Project Scanner,
Project-to-Project and Distributor. It describes administrative tasks for
ProSource Seismic and gives instructions for the corresponding workflows. It also
gives guidelines for using ProSource Seismic scripts and command line utilities.
Additional information about individual components is provided in the ProSource
Seismic online help, which is accessible from ProSource Help menu, help buttons in
the relevant interface windows, and also by right-clicking on features and selecting
Help from the pop-up menus.

• • • • • •
Note: An asterisk (*) is used to designate a mark of Schlumberger.

Who Should Use This document is primarily intended for use by data managers, data loaders and
This Document administrators, who are loading and QC-ing the data, configuring, maintaining and
troubleshooting ProSource Seismic.

Format of This You may be required to use the UNIX command line interface. This interface is
Document documented in Courier font using the following typographic conventions:
• The prompt root# precedes entries that must be made while you are logged on
as a superuser.
• The prompt % precedes commands that can be entered when you are logged on
as a regular user.
• System output is shown in regular weight font (like this).
• User input is shown in bold font (like this).
• Values that are site-specific are shown in oblique angle font (site-specific prompt:
your response.

The command line interface indicates default values within brackets and followed by
a colon ([VALUE]:). You can accept a default value by clicking Enter or, if you
want to use a different value, you can enter it after the colon and click Enter. When
a command line prompt is shown without a response, the default value should be
selected by clicking Enter.

2-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Overview of ProSource Seismic

Overview of ProSource Seismic

ProSource Seismic is an archive management system for 2D and 3D seismic data,
which is used to perform the following tasks:
• Scan seismic data from input files and/or tapes:
- Pre-stack data in SEG-Y, SEG-A/B/C/D formats
- Post-stack data in SEG-Y and ZGY formats

Catalogue the metadata scanned in the ProSource Seismic database and store the
seismic data in the archive storage area.
• Load navigation data into the ProSource Seismic database.
• Scan IESX, Charisma or SeisWorks projects, transfer metadata, including spatial
data, to the ProSource Seismic database and store the seismic data in the archive
storage area.
• Browse, select and export data from ProSource Seismic to projects in IESX,
Charisma or SeisWorks datastores, as well as to disk/tape. Project-to-project
copying between datastores, such as IESX to IESX and IESX to Charisma, can also
be performed.
Figure 2-1 illustrates the general ProSource Seismic data flows.

Fig. 2-1 General ProSource Seismic Data Flows

Preface 2-3
Schlumberger Private - Customer Use
Related Reference Materials

Related Reference Materials

Additional sources of information include the following:
• UKOOA P1/90 Post Plot Data Exchange Tape 1990 Format
The document can be found on the OGP Geomatics Committee web site (http://
www.epsg.org/Exchange/P1.pdf [the web link accessed on 08/2011]).
This document contains detailed description of the UKOOA P1/90 file format for
2D and 3D navigation data.
• Coordinate Transformation Services
The document can be found on the Open GIS Consortium, Inc. web site (http://
www.opengis.org/docs/01-009.pdf [the web link accessed on 08/2011]).
This document contains detailed description of codes for coordinate
transformation systems and well known text keywords.
• OpenSpirit documentation
The OpenSpirit Corporation makes its documentation publicly available for
download from its web site (http://www.openspirit.com/docs [the web link
accessed on 08/2011]).
The documentation set includes Release Notes, User Guide and Developer Guide.
You will also find OpenSpirit documentation in the $OPENSPIRIT_HOME/docs/
User directory.
• ProSource Administration Guide
This manual includes information about server administration and account
management, as well as troubleshooting tips.
• SEG RODE Format Record Oriented Data Encapsulation, Society of Exploration
Geophysicists, 1996.

The document can be found on the SEG web site (http://www.seg.org/

documents/10161/77915/seg_rode.pdf [the web link accessed on 08/2011]).
This document describes the RODE format standard developed by the SEG
Technical Standards Committee.
• SEG-Y, Society of Exploration Geophysicists, 2002.

The document can be found on the SEG web site http://www.seg.org/documents/

10161/77915/seg_y_rev1.pdf [the web link accessed on 10/2011]).
This document describes the SEG-Y Data Exchange format standard developed by
the SEG Technical Standards Committee.
• SEG-A/B/C, Society of Exploration Geophysicists, 1967.

The document for SEG-A/B can be found on the SEG web site http://
www.seg.org/documents/10161/77915/seg_a_b_ex.pdf [the web link accessed
on 10/2011]).
The document for SEG-C can be found on the SEG web site http://www.seg.org/
documents/10161/77915/seg_c.pdf [the web link accessed on 10/2011]).
These documents describe the SEG-A/B/C Digital Tape formats standard
developed by the SEG Technical Standards Committee.

2-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Related Reference Materials

• SEG-D, Society of Exploration Geophysicists, 1996.

The document can be found on the SEG web site http://www.seg.org/documents/

10161/77915/seg_d_rev2.pdf [the web link accessed on 10/2011]).
This document describes the SEG-D Field Tape standard developed by the SEG
Technical Standards Committee.

Preface 2-5
Schlumberger Private - Customer Use
ProSource Seismic Documentation

ProSource Seismic Documentation

The ProSource Seismic product documentation includes a combination of Portable
Document Format (PDF) files and ProSource Seismic Online Help.
• PDF files:
- ProSource Installation Guide
- ProSource Seismic Administration Guide
- ProSource Seismic Release Notes

• ProSource Seismic Online Help

2-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 3 Post-installation and Configuration

In This Chapter

Post-Installation Tasks ................................................................................ 3-2

Post-installation and Configuration 3-1

Schlumberger Private - Customer Use
 Post-Installation Tasks

Post-Installation Tasks
You need to complete the tasks listed in this section to finalize ProSource Seismic installation. For each task,
references to the appropriate documentation are provided.
For upgrade scenarios, you may already have carried out one or more of the steps below, during the previous
installation. If this is the case, you do not need to repeat them. However, it is strongly recommended to verify
the steps to make sure that the system is properly configured.
1 If you are planning to use project-related (OpenSpirit based) workflows, make sure that OpenSpirit has
been properly installed and configured. For more details on its installation, refer to the appropriate section
of the chapter “Installing Third-Party Applications” in the ProSource Installation Guide. For more details
on OpenSpirit configuration, refer to Chapter 14, “OpenSpirit,” on page 14-1.
2 Make sure that corresponding parameters are correctly set in the Seismic workflow within the IM
Administration Console:
• Seismic OpenSpirit tab
• General tab
Make sure that this task is completed before proceeding further. For more details, refer to the topic
“Configure Seismic” in the IM Administration Console Online Help (Home>Manage
ProSource>Manage Seismic>Configure Seismic).
3 Create and configure ProSource user accounts, if not done. Make sure that at least one ProSource user
has been configured to receive or submit export jobs. This can be carried out using the Business
Associate branch of the ProSource Seismic tree. For more information, refer to Chapter 10, “User
Administration,” on page 10-1.
4 Make sure that at least one staging project exists in ProSource to support the Tape Index loading
workflow. For more details on creating staging areas, refer to the section “Home > Manage Seabed
Databases and Projects > Creating a Staging Area” of the IM Administration Console Online Help.
5 Make sure that you have reviewed the seismic_loader.properties file and set configuration
parameters, as required for your site/setup. For more details on particular configuration parameters, refer
to the corresponding sections of this document:
• “Displaying the “Set SP equal to CDP” check box” on page 4-14
• “Archive Area” on page 11-13
• “Managing Bitmap Storage” on page 11-15

•
Note:A new file is created for fresh installations. In upgrade scenarios, the
original file is preserved by the ProSource installer for reference, and can
be found in the old $SEISMAN_HOME/config directory. An example of the
file is given in Appendix A, “seismic_loader.properties,” on page A-1.

6 Make sure that archive folders have been created as required (if this option was set during the previous
step). For more information, refer to Chapter 11, “Archive Folders,” on page 11-13.
7 Make sure that distributor configuration parameters have been correctly set as required for your site/setup.
Start the Scan/Edit/Load component to populate distributor parameters, if required. For more information,
refer to Chapter 13, “Distributor,” on page 13-1.
8 Make sure that the following processes and daemons are up and running:

3-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Post-Installation Tasks

• ProSource Server (for further details, refer to Chapter 3, “Server Management” of the ProSource
Administration Guide).
• Distributor (for more information on configuring, starting and stopping the distributor, refer to Chapter
13, “Distributor,” on page 13-1).
• OpenSpirit services (for more information, refer to Chapter 14, “OpenSpirit Services,” on page 14-3).
9 Make sure that ProSource Seismic preferences have been configured correctly. You can access and
configure the preferences by selecting Edit>Preferences from the ProSource main menu and then by
clicking the Prosource Seismic tab.
For more information on configuring seismic preferences, refer to Chapter 11, “ProSource Seismic
Preferences,” on page 11-18.
10 Make sure that trace viewer preferences have been configured correctly. You can access and configure the
trace viewer preferences by selecting Edit>Preferences from the ProSource main menu and then by
clicking Trace Viewer tab.
For more information on configuring trace viewer preferences, refer to Chapter 11, “Trace Viewer
Preferences,” on page 11-19.
11 Run at least one export job. For a detailed walkthrough on export jobs, refer the ProSource Seismic
Online Help (Home>End User Interface>Exporting Data>Export Workflow in a Nutshell).

Post-installation and Configuration 3-3

Schlumberger Private - Customer Use
Post-Installation Tasks

3-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 4 Scan/Edit/Load

In This Chapter

General Description .................................................................................... 4-2

Overview ............................................................................................. 4-2
System Requirements ........................................................................... 4-3
Files Used by Scan/Edit/Load ...................................................................... 4-4
Parameter File ...................................................................................... 4-4
Template File ....................................................................................... 4-4
Properties File ...................................................................................... 4-5
EBCDIC Overlay File ............................................................................. 4-7
Log File ............................................................................................... 4-7
Starting Scan/Edit/Load job......................................................................... 4-8
Starting Scan/Edit/Load Job from User Interface..................................... 4-8
Starting Scan/Edit/Load Job from Command Line.................................... 4-8
Reading Large Records from Tape Devices ..................................................4-10
Processing Seismic Files/Tapes in Batch ......................................................4-11
Restarting Scan/Edit/Load Job (Unavailable License) ....................................4-12
Viewing Scan/Edit/Load Log .......................................................................4-13
Displaying the “Set SP equal to CDP” check box...........................................4-14
Troubleshooting ........................................................................................4-15
Java Out of Memory Error ....................................................................4-15
Loading Scenarios ...............................................................................4-15

Scan/Edit/Load 4-1
Schlumberger Private - Customer Use
General Description

General Description

Overview The Scan/Edit/Load component is designed to handle the following data:

• Pre- and post-stack seismic data in SEG-Y format.
• Pre-stack field formats that include SEG-A, SEG-B, SEG-C and SEG-D (multiplexed
and de-multiplexed).
• Post-stack seismic data in ZGY (uncompressed) format.
• 3D navigation data.

SEG-Y data
The Scan/Edit/Load is used to:
• Scan input SEG-Y files or tapes, generate metadata, statistics and geometry.
• Edit the input SEG-Y data, if required.
• Load the data into the system:
- Load the metadata, statistics and geometry into the ProSource Seismic
database. The loaded data can then be viewed in the Seismic branch of the
ProSource tree.
- Save SEG-Y data to the designated disk storage area.

• • • • • •
Note: In case of disk files being scanned and catalogued, by default the files are
not copied to the storage area, references to the original files are created
instead. Option to copy the original files to the storage area is also
available.

Field formats
The procedure for scanning and loading field formats is similar to the procedure
used for loading SEG-Y data, with the following important differences:
• The following inputs are supported for loading:
- Tapes in native field formats
- Disk files in RODE encapsulated field formats
- Disk files in native SEG-D format

• Default templates are provided to display general header information. The

functionality to create and edit templates for modifying field format header data is
not supported.
• Field data read from tape are cataloged and stored on disk as RODE encapsulated
disk files (tape images).
• No shape information is generated from field format data.

4-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

ZGY data
The procedure for scanning and loading ZGY format is similar to the procedure used
for loading SEG-Y data with the following important differences:
• Only disk files in ZGY format can be loaded.
• Since the ZGY format does not contain Textual, Binary and Trace headers (which
are specific for SEG-Y format) the information scanned from ZGY files is
reformatted to simulate standard SEG-Y Textual, Binary and Trace headers for
displaying purposes only. For this reason, the Scan/Edit/Load always uses the
provided default header templates when processing ZGY data.
• The functionality to create and edit templates for modifying ZGY header data is
not supported.
• The Scan/Edit/Load does not reformat or copy ZGY files during loading. A
reference to the original ZGY disk file is created and cataloged in the database.

Figure 4-1 illustrates the Scan/Edit/Load data flow.

Fig. 4-1 Scan/Edit/Load Data Flow

System To run the Scan/Edit/Load component, the ProSource Seismic environment must
Requirements be set and the ArcSDE server must be running, as described in the ProSource
Installation Guide.

Scan/Edit/Load 4-3
Schlumberger Private - Customer Use
Files Used by Scan/Edit/Load

Files Used by Scan/Edit/Load

This section describes the files used by the Scan/Edit/Load and includes information
about the following topics:
• "Parameter File" on page 4-4
• "Template File" on page 4-4
• "Properties File" on page 4-5
• "EBCDIC Overlay File" on page 4-7
• "Log File" on page 4-7

The Scan/Edit/Load includes an option that allows you to choose location for the
following files:
• Log file (*.log)
• Parameter file (*.par)
• Template file (*.sgyfmt)

When you create a scan/edit/load job, you can specify an output directory for these
files or let the files be generated in the central location.
- If you select Redirect Logs to Output Directory, the files will be saved to
the specified output directory.
- If you do not select Redirect Logs to Output Directory, the files will be
saved to $PS_EXTERNAL_DIR/logs/pss/import folder.

Parameter File The parameter file is used to store scan/edit/load job parameters and specify data to
be processed by the job. The Scan/Edit/Load automatically generates the
parameter (*.par) file when Save or Load buttons are pressed in the final Load
panel of the interface. When Load button is pressed, the parameter file is saved and
the job is submitted. When Save button is pressed, the parameter file is generated
without submitting the job.
The parameter file is created with the name specified by the user in the New Scan/
Edit/Load panel of the Scan/Edit/Load interface. The location of the file is defined
as described above.
A parameter file is also generated dynamically by the seismic_loader.csh script. In
this case, the temporary parameter file is created in the directory from which the
seismic_loader.csh script is executed.

Template File Header structure of each input SEG-Y file should be known for the purpose of
metadata scanning and cataloging in the ProSource Seismic database. The header
structure is described by specifying byte positions for different header parameters.
The SEG-Y template files (*.sgyfmt) are used to store header structure
information. Each template includes information on textual, binary and trace
headers. Different templates are used to process input SEG-Y files with different
structure. Only one template file can be specified for a single job, so for all the files
to be processed by the job the single template will be used.

4-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Files Used by Scan/Edit/Load

The Scan/Edit/Load interface can be used to create new header templates and to
edit existing ones. However, if an existing template is associated with a dataset, the
template cannot be edited. For detailed information, see the ProSource Seismic
Online Help.
Similar templates are used for the pre-stack field formats, such as SEG-D
(*.sgdfmt) and for the multiplexed field formats, such as SEG-A, SEG-B and SEG-C
(.sgabcfmt). Default templates are provided for these formats. ProSource Seismic
does not support editing of headers for these formats and hence does not permit
the new templates to be created or default templates to be edited for these formats.
Also default textual, binary and trace header templates are provided for ZGY format.
These templates are used only for displaying information extracted from ZGY files in
the same manner as SEG-Y header information would be displayed. ProSource
Seismic does not support modification of header information for the ZGY format and
hence does not permit the new templates to be created or default templates to be
edited for ZGY format.
The output directory for header templates can be set in the Scan/Edit/Load interface
as described earlier in the beginning of this chapter.

Properties File Default values for the Scan/Edit/Load interface are defined by the properties. The
list of properties and their descriptions can be found in the table below. The
properties are saved in an ASCII file, which is called properties file. The file is
named load_setup.properties and it is located in the $HOME/.seisman
directory. The properties are read from the file and used to pre-populate the Scan/
Edit/Load Utility interface when it is starting. Any changes made to the properties
in the interface are automatically saved in the file.
The properties file contains the following attributes:
Table 4-2 Properties File Attributes

Property Name Description

APP_DATABASE Seabed database name (ORACLE_SID)

APP_PROJECT ProSource Seismic (Seabed) project name

APP_USER ProSource Seismic user name

BINARY_OUT_TEMPLATE Binary header template name for output file

BINARY_TEMPLATE Binary header template name

DEFAULT_DATASET_PROC_PHASE Processing phase

DEFAULT_DATASTORE Datastore name as defined in the ProSource

seismic database

DEFAULT_PROJECT Application project name as defined in the

ProSource Seismic database

EBCDIC_OUT_TEMPLATE Textual (EBCDIC) header template name for

output file

EBCDIC_TEMPLATE Textual (EBCDIC) header template name

Scan/Edit/Load 4-5
Schlumberger Private - Customer Use
Files Used by Scan/Edit/Load

Property Name Description

INPUT_DIRECTORY The full path to the directory, where input file(s)

reside(s)

NAVIGATION_EVENT_OUT_TEMPLATE Navigation file format template name for output

file

NAVIGATION_EVENT_TEMPLATE Navigation file format template name

NAVIGATION_HEADER_OUT_TEMPLATE Navigation file header template name for output

file

OUTPUT_DIRECTORY The directory, where *.log, *.par and *.*fmt files

are to be saved

PREVIEW_NO_OF_TRACES Number of traces for preview

SCAN_NAME Scan name or job name (also used to form log file
name)

TRACE_OUT_TEMPLATE Trace header template name for output file

TRACE_TEMPLATE Trace header template name

USER_DEFAULT_TEMPLATE_DIR The default directory for header templates

WINDOW_H Interface window height

WINDOW_W Interface window width

WINDOW_X Interface window position on the screen Y

WINDOW_Y Interface window position on the screen X

The following is an example of the properties file:

APP_DATABASE=pss_db
APP_PROJECT=prj1_seis
APP_USER=user1
BINARY_OUT_TEMPLATE=DEFAULT_BINARY
BINARY_TEMPLATE=DEFAULT_BINARY
DEFAULT_DATASET_PROC_PHASE=MIG
DEFAULT_DATASTORE=test_datastore
DEFAULT_PROJECT=scan_tests
EBCDIC_OUT_TEMPLATE=DEFAULT_EBCDIC
EBCDIC_TEMPLATE=SRV1_EBCDIC
INPUT_DIRECTORY=/data/pss_test_data
NAVIGATION_EVENT_OUT_TEMPLATE=DEFAULT_NAVIGATION
NAVIGATION_EVENT_TEMPLATE=srv1_Field_Navigation
NAVIGATION_HEADER_OUT_TEMPLATE=DEFAULT_NAVIGATION
OUTPUT_DIRECTORY=/data02/test_data/tmp

4-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Files Used by Scan/Edit/Load

PREVIEW_NO_OF_TRACES=1000
SCAN_NAME=test1
TRACE_OUT_TEMPLATE=DEFAULT_TRACE
TRACE_TEMPLATE=SRV1_Trz
USER_DEFAULT_TEMPLATE_DIR=/local_home/tmp/
Scan_Edit_Load_templates/tests
WINDOW_H=864
WINDOW_W=1425
WINDOW_X=96
WINDOW_Y=146

EBCDIC Overlay If EBCDIC header of the input SEG-Y file has been edited, the Scan/Edit/Load
File generates an EBCDIC overlay file (<survey_name>.EBCDIC.overlay) after the
job has been submitted. The file contains edited EBCDIC header information, which
the Scan/Edit/Load uses for the input file processing.
The file is saved to the location specified in the Scan/Edit/Load interface. Each
EBCDIC overlay file is named after the survey, which the data belong to (for
example, A3Dsurvey.AAA001.sgy.EBCDIC.overlay).

Log File For each job the Scan/Edit/Load writes a log file into the location specified in the
interface as described earlier in the beginning of this chapter. A log file name is
generated by concatenating ‘.log’ to the end of text string specified in the Specify
Scan Name field in the New Scan/Edit/Load panel (for example job1.log).
Each log file contains the following:
• Time the job was started
• The job parameters (as per the corresponding *.par file)
• Processing output and errors, if any
In addition to writing the information in the log file, the Scan/Edit/Load also displays
the information in the progress window. This window opens automatically after the
user submits load job by clicking the Load button. The messaging level can be set
to different values. For more information please see "Managing messaging level for
seismic loader logs" on page 11-17.

Scan/Edit/Load 4-7
Schlumberger Private - Customer Use
Starting Scan/Edit/Load job

Starting Scan/Edit/Load job

A scan/edit/load job can be submitted from the Scan/Edit/Load interface or from
command line.
• "Starting Scan/Edit/Load Job from User Interface" on page 4-8
• "Starting Scan/Edit/Load Job from Command Line" on page 4-8

Starting Scan/Edit/ To start a scan/edit/load job, click Load button in the Load pane of Scan/Edit/Load
Load Job from User window. The job will load data into the database and/or generate a new edited
Interface version of the input SEG-Y file(s) as per the parameters specified while setting up
the job. For detailed information about setting up scan/edit/load jobs see the
ProSource Seismic Online Help.

Fig. 4-2 Example of the Load pane of the Scan/Edit/Load interface

Starting Scan/Edit/ A scan/edit/load job can be submitted from the command line by running the
Load Job from seismic_loader executable. The executable can be run in one of the following
Command Line modes:
• In scan/edit/load mode, it will load data into the database and/or generate a new
SEG-Y file using a previously created parameter file.

4-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Starting Scan/Edit/Load job

• In scan/edit and standalone mode it will read pre-stack field format data from
tape (SEG-A, SEG-B, SEG-C and SEG-D) and generate a RODE encapsulated disk
image of the original tape. In standalone mode, no database is required.

 To run seismic_loader executable in Scan/Edit/Load Mode from a

Command Line
1 Open xterm window from the ProSource Seismic Standalone Launcher.
Environment variable SEISMAN_HOME will automatically be set for the window.

• • • • • •
Note: To run an executable (in this particular case seismic_loader) from a
command line without having to specify path to the executable, the
executable location directory (in this case $SEISMAN_HOME/bin) should
be present in the $PATH environment variable. If the xterm is opened
from the ProSource Seismic Standalone Launcher, the environment
should automatically be set correctly.

2 If you are logged in to the ProSource Seismic server from another machine,
make sure that the DISPLAY environment variable is set properly. Set the
variable, if required. For example:
% setenv DISPLAY <hostname>:0.0
3 Review the command line options and run the following command:

% seismic_loader <parameter_file> <log_file>

For example (assumed that the executable is run from its location, which is
$SEISMAN_HOME/bin):
% ./seismic_loader usera_load1.par usera_load1.log

 To run seismic_loader executable in Standalone Mode from a

Command Line
For information on running the seismic_loader executable in standalone mode
from a command line please refer "Generating RODE Image of Original Tape" on
page 15-2.

Scan/Edit/Load 4-9
Schlumberger Private - Customer Use
Reading Large Records from Tape Devices

Reading Large Records from Tape Devices

There is a known limitation on the maximum record size that can be read from an
individual tape device. Maximum record sizes have been determined for the
following tape devices on Linux.
Table 4-3 Tape Drive Maximum Record Size

Tape Drive Maximum record size (bytes)

DLT 8380 000
IBM 3592 2080 000
Exabyte 8mm 240 000

This limitation should not be an issue for reading tapes in de-multiplexed formats,
which normally would have records of relatively small sizes (compared to the device
maximum).
It could be an issue when reading tapes in multiplexed formats using tape device
such as Exabyte 8mm, which has a small maximum record size. An attempt to read
a record larger than the maximum for that device will generate an error message,
but the application will skip to the start of the next file and continue to read the
remaining data.
Also, this limitation may affect ability to read large-record data from 8mm tape,
which was successfully written on a Solaris workstation, if an Exabyte drive attached
to a Linux workstation is used for reading. Attempts to read this data will generate
an error, if the record size exceeds the maximum record size for the device.

4-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Processing Seismic Files/Tapes in Batch

Processing Seismic Files/Tapes in Batch

A scan/edit/load job can be run in batch mode to process data from multiple disk
files in multiple storage locations, as well as from multiple tapes.
To set up a batch job for loading multiple files from disk the parameter file should
contain the full UNIX paths to all the input SEG-Y data files.
If the input files are to be loaded from multiple tapes, then the total number of
tapes should be specified in the parameter file, as well as the tape stacker capacity
and path to the tape drive. The job will load data from each tape file, one tape at a
time, until the contents of all tapes have been scanned. If the number of input tapes
exceeds the capacity of the tape stacker, the user who submitted the job will receive
an e-mail notification that all of the tapes currently inserted in the stacker have been
scanned and that the tapes containing the remaining files must be inserted into the
stacker. The user then must remove the tapes from the stacker and insert the new
tapes.
Alternatively, the data loading job can be split into two (or more) parts by editing
the number of tapes specified in the parameter file. For example, if a user wants to
load data from ten tapes but the stacker has capacity for only five tapes, two load
jobs could be run. The NO_OF_TAPES parameter in the parameter file must be
changed to specify five tapes rather than ten. The user could then run one load job
for the first five tapes, then another load job for the second five tapes. If the tapes
are not replaced in the stacker within a certain time frame, the load job will fail.
After the appropriate parameter file has been saved, it can be used to start the
scan/edit/load job from command line, as described in "Starting Scan/Edit/Load Job
from Command Line" on page 4-8

Scan/Edit/Load 4-11
Schlumberger Private - Customer Use
Restarting Scan/Edit/Load Job (Unavailable License)

Restarting Scan/Edit/Load Job (Unavailable License)

In some cases, when a user submits a job from the Scan/Edit/Load interface, the
license, required to run the job (SeismicManager_SEGY_Load feature), may be
unavailable. This can occur, for example, if the license server is down or if the
number of concurrent users has exceeded the license limits. In this situation the job
parameters can be saved to a parameter file and the job can be re-submitted from
the command line at a later time.

 To restart a Scan/Edit/Load Job

1 Configure a job, as described in the ProSource Seismic online help.
2 Click Save at the bottom of the Load window, the parameter file
(<scan_name>.par) will be saved to the location specified in the interface as
described earlier in the beginning of this chapter. A header template file will
also be saved to the location and will have the name <scan_name>.sgyfmt.
3 Run the job from the command line, as described in "Starting Scan/Edit/Load
Job from Command Line" on page 4-8.

4-12 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Viewing Scan/Edit/Load Log

Viewing Scan/Edit/Load Log

The Scan/Edit/Load log can be viewed in the progress window that opens
automatically after the user submits a load job by clicking the Load button.

• • • • • •
Note: The messaging level can be changed if required. For more information see
"Managing messaging level for seismic loader logs" on page 11-17.

The log is also saved to a file for each job to the location specified in the New
Scan/Edit/Load pane of the interface as described earlier in the beginning of this
chapter.
The value of the output directory parameter is saved in the parameter file along with
the other job parameters. So if required, the value can be found in the file. In order
to do that, one should look for the OUTPUT_DIRECTORY parameter in the file.
If the job is run from a command line, the log file may be saved to a specific
directory as per the command line parameter specified for the seismic_loader
executable. For detailed information about this file, see "Log File" on page 4-7.
In order to view a log file:
1 Identify its location using above information.
2 Use your preferred command/application in order to view the content of the
file.

Scan/Edit/Load 4-13
Schlumberger Private - Customer Use
Displaying the “Set SP equal to CDP” check box

Displaying the “Set SP equal to CDP” check box

In the Trace Template window of the Scan/Edit/Load interface, there is the “Set
SP equal to CDP” check box. It is unchecked and hidden (not visible) by default. To
control if the check box should be visible, so that users can check/uncheck it, there
is a DUPLICATE_OFFSET parameter in the seismic_loader.properties file.
The file is located in the $SEISMAN_HOME/config directory. This parameter can
be set to the following values to show/hide the check box:
• ENABLE
• DISABLE
For more information on the check box and system behavior depending on the
check box state, please refer to the “Editing Header Templates” section of the
Online Help.

• • • • • •
Note: An example of the seismic_loader.properties file is provided in
Appendix A, “seismic_loader.properties,” on page A-1.

4-14 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Troubleshooting

Troubleshooting

Java Out of In some cases a scan/edit/load job may produce the following error:
Memory Error
java.lang.OutOfMemoryError
For example, it can happen, if there is a large number of traces in the input file
being scanned.
In such cases it is recommended to set a larger value for Java max heap size
parameter.

 To increase max heap size

1 In a text editor open the $SEISMAN_HOME/scripts/loader_setup.csh
script.
2 Find the following line:
${JRE_HOME}/bin/java -Xmx512m
com.slb.sis.seisstream.segy.scan.ui.SetupMain
3 Change 512 to a larger number. For example:
${JRE_HOME}/bin/java -Xmx1000m
com.slb.sis.seisstream.segy.scan.ui.SetupMain
4 Save and close the file.

Loading Scenarios The way in which the data are loaded affects the results. Table 4-4 lists five loading
scenarios and what these scenarios produce.
Table 4-4 : Loading Scenarios

Load Output

Seismic traces with Metadata

navigation in the Archived SEG-Y files/links
headers Shape

Seismic traces without Metadata

navigation in the Archived SEG-Y files/links
headers

Nav files Shape

Archived nav files

Seismic traces Metadata

+ Archived SEG-Y files/links
Nav files Updated Metadata
Shape

Scan/Edit/Load 4-15
Schlumberger Private - Customer Use
Troubleshooting

Load Output

Nav files Metadata

+ Shape
Seismic traces Updated Metadata
Archived SEG-Y files/links

4-16 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 5 Tape Index Loader

In This Chapter

About Tape Index Loader ............................................................................ 5-2

Starting Tape Index Loader ......................................................................... 5-3
Loading Tape Index Data ............................................................................ 5-4
Associate Datastore, Project and Survey................................................. 5-5
Select Template Options.......................................................................5-12
Index Control File Generator ................................................................5-14
Select Data .........................................................................................5-17
Select Data Override Options................................................................5-18
Validate Input Data and Template .........................................................5-20
Submit Job..........................................................................................5-20

Tape Index Loader 5-1

Schlumberger Private - Customer Use
About Tape Index Loader

About Tape Index Loader

Certain metadata is used for cataloging seismic tapes and/or disk files in ProSource
Seismic database. One possible way to obtain the metadata is to scan the tapes/files
and read the required information from the headers. In some cases the metadata is
already available, so there is no need to scan the tapes/files for it.
The Tape Index Loader is a server-side application designed for loading metadata
from input ASCII files into ProSource Seismic database without actually scanning the
tapes/files to be catalogued.
The application interface is used to set up, validate and submit loading jobs. One (or
more than one) input file can be specified for a single job to process. An input file is
a text file formatted in certain way.
The rules/instructions to describe input file format (layout) and define mapping
between data fields in the input file and corresponding database attributes must be
set and saved in a file called template file. The file is used by the application in
order to correctly read the input file and load the data.
Template files are created using the graphical interface. A separate template file is
required for each distinct type of input file format (layout). Only one template file
can be specified for one job, so for all the files to be processed by one job, one
template will be used. In other words, all the files to be processed by a single job
should be formatted the same way.

5-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Starting Tape Index Loader

Starting Tape Index Loader

The Tape Index Loader can be started by directly activating the Tape Index
Loader icon on the ProSource Seismic Standalone Launcher or from a
command line, as described below.

 To Start the Tape Index Loader from a Command Line

1 Open xterm window and ensure that SEISMAN_HOME environment variable is
set correctly. If you open xterm from the ProSource Seismic Standalone
Launcher, the variable will automatically be set for the window.
2 If you are logged in to the ProSource Seismic server from another machine,
make sure that the DISPLAY environment variable is set properly. Set the
variable, if required. For example:
% setenv DISPLAY <hostname>:0.0
3 Enter the following command:
% index_setup.csh

Tape Index Loader 5-3

Schlumberger Private - Customer Use
Loading Tape Index Data

Loading Tape Index Data

The Tape Index Loader workflow is performed from the main window.

Fig. 5-1 Tape Index Loader

The workflow consists of the following basic steps:

1 Associate datastore, project and survey (see “Associate Datastore, Project and
Survey” on page 5-5).
2 Select the template options (see “Select Template Options” on page 5-12).
3 Select the data files (see “Select Data” on page 5-17).
4 Select the data override options (see “Select Data Override Options” on page 5-
18).
5 (Optional) Validate the job setup (see “Validate Input Data and Template” on
page 5-20).
Use this option to run a quick check of your settings before you proceed with
the job.

5-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

• • • • • •
Note: The validation is performed in the background each time you submit a
load job.

6 Submit the job (see“Submit Job” on page 5-20).

• • • • • •
Note: At least one staging project must exist in ProSource to support the Tape
Index Loading workflow. For more details on creating staging areas, refer
to the section “Home > Manage Seabed Databases and Projects >
Creating a Staging Area” of the IM Administration Console Online Help.

Associate Complete the following steps to select a datastore and a project.

Datastore, Project
and Survey

 To Select Datastore and Project

1 Check the datastore name. If you would like to select another datastore, click
Select Datastore. The list of available datastores pops up.

Fig. 5-2 List of Datastore entities

2 Select the correct datastore from the list. If the required datastore is not listed,
you can create a new datastore by clicking Create a New Item icon in the
interface.
3 After you have selected the correct datastore, click OK to close the List of
Datastore Entities window.

Tape Index Loader 5-5

Schlumberger Private - Customer Use
Loading Tape Index Data

4 Check the project name. If you would like to select another project, click
Select Project. The list of available projects pops up.

Fig. 5-3 List of Project entities

5 Select the correct project from the list. If the required project is not listed, you
can create a new project by clicking Create a New Item icon in the interface.
6 After you have selected the correct project, click OK to close the List of
Project Entities window.

Select Survey Complete the following steps to select a survey.

 To Select Survey
1 Select type of the survey from the drop-down list (2D or 3D) and click Select
Survey.
The list of surveys displayed in the selection window corresponds to the
selected type of survey.

5-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

Fig. 5-4 Select Survey

2 Select a survey from the list.

If the required survey is not listed, you can create a new survey by clicking
Create a New Item icon in the interface.
3 After you have selected the correct survey, click OK to close the List of
Surveys window.

• • • • • •
Note: If one of existing surveys was selected, name of the CRS associated with
the survey is displayed in the Survey CRS field.

Select Survey CRS from Complete the following steps to select a CRS for the survey from the list of
Previously Used CRSs previously used CRSs, if required.

 To Select Survey CRS from Previously Used CRSs

1 Select Previously Used option (radio button) in the main window.

Tape Index Loader 5-7

Schlumberger Private - Customer Use
Loading Tape Index Data

Fig. 5-5 Select Previously Used option

2 Click Select Survey CRS icon.

3 Click Search without setting any search criteria to get the entire list of
previously used CRSs or set a search criteria on one or more attributes and click
Search.

5-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

Fig. 5-6 Search CRS

• • • • • •
Note: You can use the % symbol with the LIKE operator as the wildcard for a
string of characters. For example, you can use %UTM%15% with the LIKE
operator for CRS_Name to find such names as
NAD_1927_UTM_Zone_15N.

4 Select a CRS from the list in the top part of the window appeared. The
previously selected transformation will be displayed in the bottom part of the
window.

Tape Index Loader 5-9

Schlumberger Private - Customer Use
Loading Tape Index Data

Fig. 5-7 List of Previously Used CRS

5 Click OK.

Select Survey CRS from Complete the following steps to select a CRS for the survey from the list of all CRSs
All CRSs defined in the system, if required.

 To Select Survey CRS from All CRSs

1 Select ALL option (radio button) in the main window.

5-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

Fig. 5-8 Select All option

2 Click Select Survey CRS icon.

3 Click Search without setting any search criteria to get the entire list of existing
CRSs or set a search criteria on one or more attributes and click Search.

Fig. 5-9 Search CRS

Tape Index Loader 5-11

Schlumberger Private - Customer Use
Loading Tape Index Data

• • • • • •
Note: You can use the % symbol with the LIKE operator as the wildcard for a
string of characters. For example, you can use %UTM%15% with the LIKE
operator for CRS_Name to find such names as
NAD_1927_UTM_Zone_15N.

4 Select a CRS from the list in the top part of the window appeared. Select
appropriate transformation from the list in the bottom part of the window.

Fig. 5-10 List of CRS entities

5 Click OK.

Select Template Complete the following steps to select tape index template options.
Options

 Select Tape Index Template Options

1 Select the Template Type for the job.

5-12 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

Fig. 5-11 Select Template Options

• • • • • •
Note: Only custom templates are currently supported, so it is the only option
available. After you selected the Custom entry from the list, you must
select a previously created template in the Template File field. The
template should match the format (layout) of the input file(s) to be
loaded.

2 To select a previously created template file click the Select Template File
icon. The Open File window displays.

Fig. 5-12 Open File Window for templates

3 Enter the file name or navigate to the file to be used. The selected file name
displays in the File name field. Click Open to select the file.

Tape Index Loader 5-13

Schlumberger Private - Customer Use
Loading Tape Index Data

• • • • • •
Note: If there is no previously created template file matching format (layout) of
the data file(s) being loaded, create a new template using the Index
Control File Generator as per the instructions further below.

4 Click Select output directory icon to pick an output directory. By default the
system is configured to use the List of Archive Folder entities for the
Output Directory selection. Make a selection from the list and press OK. Please
refer to the “Archive Area” section for more information.

Fig. 5-13 List of Archive Folder entities

When the job is submitted, the folder <archive folder>/<the

datastore>/<the project>/<the survey>/tape_index will be
created (if does not exist) and a copy of the template file will be stored in the
folder.

Index Control File The Index Control File Generator is opened from the main Tape Index Loader
Generator window by clicking Select Template Type icon. The Index Control File
Generator is used to create and edit the template files required for loading tape
index data.

5-14 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

Fig. 5-14 Index Control File Generator

Creating Template File Use the following steps to create a template file for a specific input data file format
(layout):
1 Select and open the data file.
2 Define the header and the delimiter options.
3 Define the field numbers/positions and mapping.
4 Save the new template file.
Steps 1-4 are described in details below.

Opening Data File Complete the following steps to open a data file.

 To open a data file:

1 Click the Open Data File button to display a file selection dialog box.
2 Navigate to the location of the data file to be used to create the new template
file.
3 Enter the file name or pick the data file to be used. Click Open.

Tape Index Loader 5-15

Schlumberger Private - Customer Use
Loading Tape Index Data

The data file will be opened and displayed in the Index Control File
Generator window.

• • • • • •
Note: Blank lines in the input files are not supported. The loader will fail, if a
blank line is encountered.

Header and Delimiter Complete the following steps to set the header and delimiter options.
Options

 To define the header and delimiter options

1 Specify the header options in the Header Options pane of the Index
Control File Generator window.

• • • • • •
Note: The Tape Index Loader supports data files without header lines as well as
ones with one or more header line. The header lines should be placed at
the beginning of the file. The lines should be marked with a common
character, which should be the first character of each header line.

2 If the data file contains no header line(s), choose the No Headers option. If
the data file contains one (or more than one) header line, specify the character
used to mark the header line(s) in the Header Record Start Character field
and ensure the Has Headers option is selected.
3 Specify the field and the string delimiter options in the Delimiter Options
pane of the Index Control File Generator window.
The Tape Index Loader supports data files with the fields separated either by
a specific character or by the ASCII tab character. Data files where the fields
are defined by specific start and end column positions are also supported.
If the fields in the data file are separated by the ASCII tab character, select the
Tab Delimited option.
If the fields are separated by a specific ASCII character, specify the character
and select the Char Delimited option.
If the fields are defined by specific start and end column numbers, select the
Pos. Delimited option.
The Tape Index Loader supports character fields in the data file enclosed by
a specific character, such as a double-quote or not enclosed by any character.
If the character fields in the data file are enclosed by an ASCII character,
specify the character in the String Delimiter field. If the character fields in
the data file are not enclosed by any special character, clear the value in the
String Delimiter field.

Data Field Mapping The Tape Index Loader reads input data files line by line. Field numbers/positions
specified in the template file are used to parse each line and extract data values.
The extracted values are written to ProSource Seismic database as per the mapping
defined in the template file. For each template file you must specify field numbers/

5-16 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

positions and create mapping between ProSource Seismic database attributes and
the fields in the data file. The workflow is described below.
It is assumed that the data file has already been opened and the delimiter options
have been specified.
1 Select an attribute to be mapped from the list of available ProSource Seismic
attributes in the Template Field Options>Parameters panel. The record is
highlighted.
2 In the Tape Index File panel, where the data file is displayed, left-click on the
left-most character of the corresponding field and drag the mouse until the
entire field is highlighted, then release the left mouse button. The field should
remain highlighted.
3 Move the mouse over to the selected attribute in the Parameters panel, then,
with the mouse cursor pointing anywhere within the highlighted record, click
the middle mouse button to populate the relevant columns as described below.
If the delimiter option has been specified as Char Delimited or Tab
Delimited, the value for the Column in the highlighted attribute record will be
set to the index number of the field (computed starting from 1 at the left side
of the line).
If the delimiter option has been specified as Pos. Delimited, the start and the
end positions for the field will be computed and displayed in the corresponding
columns of the selected ProSource Seismic attribute record.
Two vertical red lines will appear in the Tape Index File pane to mark the
data field just mapped, so the user can visually control, if the field has been
defined and mapped correctly.
Selecting any attribute, which has already been mapped, will cause the vertical
lines to appear around the corresponding data field. If the delimiter option has
been set to Char Delimiter or Tab Delimiter, the vertical lines will only be
correctly placed for the first line in the data file.

• • • • • •
Note: It is important to correctly define the field delimiter before you start
mapping. If the field delimiter is changed during the mapping process, all
fields are cleared and all mappings must be redefined.

Saving Template File After all the relevant fields in the data file have been mapped, use the following
steps to save the newly created template file:
1 Click Save to activate the file selection dialog.
2 Navigate to the desired directory. Specify a meaningful name for the file being
saved. Click Save to save the file and close the file selection dialog.
3 Select Exit to close the Index Control File Generator window.

Select Data Complete the following steps to select input data files for the job.

Tape Index Loader 5-17

Schlumberger Private - Customer Use
Loading Tape Index Data

• • • • • •
Note: Blank lines in the input files are not supported. The loader will fail, if a
blank line is encountered.

Select Tape Index Perform the following steps to open a data file:
File(s)
1 Click the Add Data File icon.

Fig. 5-15 Select Tape Index File

2 Navigate to the directory containing the file that you want to open.
3 Select the file so that it displays in the File Name field and click Open.
The full path to the file will be displayed in the Path pane of the main Tape
Index Load window.
4 Repeat steps 1-4, if more files should be added for the job.

Remove Tape Index Use the following steps to remove a file from the list of files in the Path pane of the
File(s) main Tape Index Load window:
1 Select the file you want to remove.
2 Click Remove Data File icon.

• • • • • •
Note: The file will be removed from the list only, it will not be physically deleted
from its disk location.

3 Repeat the above steps, if more files should be removed from the list.

Select Data In order for tape index data to be correctly loaded into Seabed, values for certain
Override Options key database attributes should be present in the input file(s).

5-18 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

If the key attribute values are not present in the input file(s), they must be set by
using corresponding drop-down lists available in the Data Override Options
section of the main Tape Index Load window.

Fig. 5-16 Data override Options

The key database attributes are listed in the following table.

Table 5-1 The Key Database Attributes

Attribute Description
Data Format The seismic format of the tapes/files being catalogued
(for example SEG-Y, SEG-D, ZGY-U, etc.).
Data Type The type of seismic data on the tapes/files being
catalogued, such as Poststack or Prestack.
Media Type The media type for the tapes/files being catalogued,
such as Disk or Tape.
Data Stage Processing stage for the data on the tapes/files being
catalogued (for example MIG, RAWMIG, FMIG, FIELD
etc.).
Sort Key The sort key, such as CDP, SP, FF (field file) for 2D or i-
line, x-line, FF for 3D. The value specifies how the data
on the tapes/files being catalogued are sorted.

When the application is started, values in all the drop-down lists are set to
Computed except Data Format, which is set to Custom.
If a value is set to Computed, the program expects that data for the corresponding
attribute will be extracted from the input file(s). The validation process will check if
the attribute is mapped in the selected template. If it is not mapped in the template,
an error message will be reported.
The values in the input file(s) must precisely match case and spelling of the
corresponding reference values defined in Seabed. The validation process will check
that as well and report errors, if any.

Tape Index Loader 5-19

Schlumberger Private - Customer Use
Loading Tape Index Data

If for an attribute a value other than Computed is specified in the Data Override
Options section, it will be global in its scope and will be used for each entry in the
input file(s). Even if values for the attribute are present in the data file(s) and the
attribute is mapped in the template file, the values in the data file(s) will be ignored
and overridden by the value specified in the Data Override Options section.

Validate Input Data Problems with the index data being loaded may cause the load job to fail. If the load
and Template fails, it may be difficult to determine the particular line and filed in the input file that
caused the problem. The load job will fail after the first error, but there may be more
than one problematic line/field in the input file.
For this reason, the Tape Index Loader includes a validation procedure that scans
the input file using the template file specified and reports potential problems to the
user without actually loading any data into Seabed. User can review the warnings
and error messages displayed in a console window. Each warning or error message
is accompanied by the line number in the input file at which the problem has been
identified. The validation is started by clicking the Validate button in the main
window.

Fig. 5-17 Tape Index Validator

Submit Job After you completed setting up a tape index load job, the job can be submitted to
start loading the metadata into the database.
Use the following steps to submit a load job.
1 Click Submit button. If validation failed, the message displays, you will be
prompted to correct the error(s) before resubmitting the load job.

5-20 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Loading Tape Index Data

2 Monitor the console output to verify that the load is successful. Review the log
information when it displays.

Fig. 5-18 Submit Tape Index Job

If any errors occurred during the load operation, the relevant information will
be listed in the log. A log file named like
index_<user_name>_<nnnnnnnnnnnnn>.log will be saved in the
$PS_EXTERNAL_DIR/logs/pss/import directory.
For example index_myuser_1067961383635.log.
3 If necessary, correct the errors identified in the log file and restart the job.

• • • • • •
Note: In addition to the log file described above, the Tape Index Load utility
writes another log file named like transfer<username>.log. The file
is written to the <ProSource external directory>/logs folder.
The file is the most detailed log file.

Tape Index Loader 5-21

Schlumberger Private - Customer Use
Loading Tape Index Data

5-22 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 6 Navigation Loader (2D)

In This Chapter

General Description .................................................................................... 6-2

Viewing Log ............................................................................................... 6-4
Control File Creation ................................................................................... 6-5
Overview ............................................................................................. 6-5
Creating and Saving Control File ............................................................ 6-5

Navigation Loader (2D) 6-1

Schlumberger Private - Customer Use
General Description

General Description
The Navigation Loader provides an alternative method of loading 2D navigation
data when 2D SEG-Y files do not contain navigation data or when SEG-Y trace data
has not been loaded for the lines.
The Navigation Loader loads 2D navigation data from ASCII files to ProSource
Seismic database. The application reads the files according to the rules/instructions
set in the specified control file, then builds a shape and loads the shape to the
spatial layer in ProSource Seismic database.
Included with ProSource Seismic are the control files to support the following
navigation formats:
• UKOOA P1/90
• UKOOA P1/84
• UKOOA P1/76
• SEG SPS
• SEG P1
• GEF

In addition, you can create a custom control file to handle other formats.
The Navigation Loader is invoked from the ProSource Seismic Application
Launcher.
You can submit 2D navigation load job from the Navigation Loader interface by
clicking Submit button in the main window.

6-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

Figure 6-1 illustrates the navigation loading data flow.

IESX IESX
End User Interface
Seicmic Trace
Tree / Table / Map SEOW Data
Charisma Charisma

Seisworks Seisworks

Data Attributes
Including Spatial

Export Job
Info
Project Scan

Database Export

SEG-Y
Scan
Seismic
Optional: if Trace Data
editing needed
or input=tape

Optional: if navigation cannot SEG-Y

SEG-Y Navigation be obtained from SEG-Y; N/A for
Load Project Data

SEG-Y
SEG-Y

Navigation

SEG-Y
SEG-Y FTP

Fig. 6-1 Navigation Loading Data Flow

Navigation Loader (2D) 6-3

Schlumberger Private - Customer Use
Viewing Log

Viewing Log
The load progress window is displayed after a user clicks Submit button in the
Navigation Loader interface. When 2D navigation load job is completed, the log file
is stored in the $PS_EXTERNAL_DIR/logs/pss/import directory. The default
naming convention for the log file is
navigation_<account_name>_<time>.log.
In order to view a log file:
1 Identify its location using above information.
2 Use your preferred command/application in order to view the content of the
file.

6-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Control File Creation

Control File Creation

Overview The Navigation Loader can handle input data represented in standard navigation
formats as well as in custom formats. For a custom format control file has to be
created. There is Navigation Control File Generator tool designed to assist users
with control file creation.
The main steps to create a new 2D navigation control file include:
1 Launch the Navigation Control File Generator
2 Open an input navigation file
3 Set header options
4 Map the fields in the input file
5 Save the control file
The detailed description of the workflow is provided below.

Creating and 2D seismic navigation control file is an ASCII file in XML format. It is recommended
Saving Control File to use the Navigation Control File Generator to create 2D navigation control
files. The tool generates control files based on the input provided trough the
interface. It also contains a panel where the input file is displayed in order to assists
users with the control file creation. The Navigation Control File Generator is
started from the Navigation Loader interface.

 To Create a 2D Seismic Navigation Control File

1 In the Navigation section of the 2D Navigation Load window set the
Navigation Format to Custom and click Create Navigation Control
File icon.
The Navigation Control File Generator window opens.

Navigation Loader (2D) 6-5

Schlumberger Private - Customer Use
Control File Creation

Fig. 6-2 Navigation Control File Generator

2 Click Open button to open a navigation file. File selection window pops-up.
3 Select a navigation file and click Open button. The file is displayed in the
Navigation File panel of the main Navigation Control File Generator
window.

• • • • • •
Note: By default, the first 100 lines of the navigation file are displayed. If
required, specify a different number of lines to be displayed or select All
Lines and refresh the view by pressing Reload the navigation file icon.

4 In the Header Options section select either of the following options:

• No Headers, if there are no header lines in the input file.
• Has Headers, if there is one (or more) header line in the input file.
If selected Has Headers option, also specify how the loader will recognize the
header lines:
• Fixed Length Header Records – select this option, if there is a fixed
number of header lines in the input file. Specify the number.

6-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Control File Creation

• First character starts with – select this option, if each header line in the
input file starts with the certain character. Specify the character.
5 In the Degree Format Options section specify the format for navigation data
represented in degrees:
• DMS Format – for data represented in degrees/minutes/seconds.
• Decimal Format – for data represented in decimal degrees.
6 The Navigation Loader reads input data files line by line. Field start/end
positions specified in the control file are used to parse each line and extract the
data values. The extracted values are associated with corresponding attributes
according to the mapping defined in the control file. For the new control file
you specify positions and create mapping for the fields in the data file. The
workflow is described below.
a. Select a parameter to be mapped from the list in the Parameters panel.
The record is highlighted.
b. In the Navigation File panel, where the data file is displayed, left-click on
the left-most character of the field and drag the mouse until the entire field is
selected, then release the left mouse button. The data field should remain
highlighted.
c. Move the mouse over to the selected parameter in the Parameters panel,
then, with the mouse cursor pointing anywhere within the highlighted
record, click the middle mouse button to populate the relevant fields.

Two vertical red lines will appear in the Navigation File panel to mark the data
field just mapped, so the user can visually control, if the field has been defined
and mapped correctly.
Selecting any attribute, which has already been mapped, will cause the vertical
lines to appear around the corresponding data field.
7 Click Save button, the Save dialog opens. Give a name to the newly created
control file, and click Save button. The file is saved and the dialog is closed.
8 Click Exit to exit the Navigation Control File Generator.

Navigation Loader (2D) 6-7

Schlumberger Private - Customer Use
Control File Creation

6-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 7 Loading 3D Navigation with Scan/
Edit/Load

In This Chapter

General Description .................................................................................... 7-2

Viewing Log ............................................................................................... 7-6
Control File Creation ................................................................................... 7-7
Overview ............................................................................................. 7-7
Creating and Saving Control File ............................................................ 7-7

Loading 3D Navigation with Scan/Edit/Load 7-1

Schlumberger Private - Customer Use
General Description

General Description
3D navigation loading functionality is available in the Scan/Edit/Load interface. It
provides an alternative method of loading 3D navigation data when 3D SEG-Y files
do not contain navigation data or when SEG-Y trace data has not been loaded for
the survey.
The functionality is used for 3D navigation data loading from ASCII files to
ProSource Seismic database. The application reads the files according to the rules/
instructions set in the specified control file, then builds a shape and loads the shape
to the spatial layer in ProSource Seismic database.
Included with ProSource Seismic are the control files to support the following
navigation formats:
• UKOOA P1/90
• UKOOA P1/84
In addition, you can create a custom control file to handle other formats.

• • • • • •
Note: Latitude/longitude loading is not supported at this time.
X/Y fields may contain an implied decimal point that will affect
designations of the Offset and the Length columns.

For more information please refer to “Data with Implied Decimal Point”
page (i.e. Home > Data Loader Interface > Navigation Load > Data with
Implied Decimal Point) of the ProSource Seismic Online Help.

The Scan/Edit/Load is invoked from the ProSource Seismic Application

Launcher. To set up a 3D navigation loading job you should select one of the
following options in the Data Format drop down list of the New Scan/Edit/Load
pane:
• UKOOA P1/90
• UKOOA P1/84
• Custom Navigation

7-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

Fig. 7-1 Example of the New Scan/ Edit/Load pane for 3D navigation load job

You can start 3D navigation load job from the Scan/Edit/Load interface by clicking
Load in the Load pane.

Loading 3D Navigation with Scan/Edit/Load 7-3

Schlumberger Private - Customer Use
General Description

Fig. 7-2 Example of the Load pane for 3D navigation loading

7-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

Figure 7-3 illustrates the navigation loading data flow.

IESX IESX
End User Interface
Seicmic Trace
Tree / Table / Map SEOW Data
Charisma Charisma

Seisworks Seisworks

Data Attributes
Including Spatial

Export Job
Info
Project Scan

Database Export

SEG-Y
Scan
Seismic
Optional: if Trace Data
editing needed
or input=tape

Optional: if navigation cannot SEG-Y

SEG-Y Navigation be obtained from SEG-Y; N/A for
Load Project Data

SEG-Y
SEG-Y

Navigation

SEG-Y
SEG-Y FTP

Fig. 7-3 Navigation Loading Data Flow

Loading 3D Navigation with Scan/Edit/Load 7-5

Schlumberger Private - Customer Use
Viewing Log

Viewing Log
The load progress window is displayed after the job is submitted as described
above. When 3D navigation load job is completed, the log file is stored in the
location specified during the load job setup.
When you setup a navigation loading job, you can specify an output directory for the
log file or let the log files be generated in the central location.
- If you select Redirect Logs to Output Directory, the log file will be saved to
the specified output directory.
- If you do not select Redirect Logs to Output Directory, the log file will be
saved to $PS_EXTERNAL_DIR/logs/pss/import folder.
The default naming convention for the log file is
navigation_<account_name>_<time>.log.
In order to view a log file:
1 Identify its location using above information.
2 Use your preferred command/application in order to view the content of the
file.

7-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Control File Creation

Control File Creation

Overview ProSource Seismic can handle 3D navigation data in UKOOA P1/84, UKOOA P1/90 or
custom formats. For a custom format control file has to be created. There is Event
Template tool designed to assist users with control file creation.
The main steps to create a new 3D navigation control file include:
1 Select input navigation file(s)
2 Launch the Event Template tool
3 Map the fields in the input file
4 Save the control file
The detailed description of the workflow is provided below.

Creating and 3D seismic navigation control file is an ASCII file in text format. It is recommended
Saving Control File to use the Event Template tool to create 3D navigation control files. The tool
generates control files based on the input provided through the interface. It also
contains a panel where the input data can be displayed in order to assist users with
the control file creation. The Event Template tool is started from the Select
Navigation Files pane of the Scan/Edit/Load interface.
For more information on the Scan/Edit/Load interface please refer online help.

 To Create a 3D Seismic Navigation Control File

1 In the Select Navigation Files pane of the Seismic Scan/Edit/Load
interface, click to select a navigation data file.

2 Click in the Templates section. The Event Template window opens.

3 Click on the Select or create a new template icon. Navigation Event

Templates List window pops up.
4 Select an existing template from the list or create a new template by clicking
, and click OK.

5 Assign the correct Parameter Attributes for Line Number, Crossline, SX

and SY (see Figure 7-4).

Loading 3D Navigation with Scan/Edit/Load 7-7

Schlumberger Private - Customer Use
Control File Creation

Fig. 7-4 Example of Event Template Window

a. Select a parameter to be mapped from the list in the Tabular panel. The
record is highlighted.
b. In the Textual panel, where the data file is displayed, left-click on the left-
most character of the field and drag the mouse until the entire field is
selected, then release the left mouse button. The data field should remain
highlighted.
c. Move the mouse over to the selected parameter in the Tabular panel, then,
with the mouse cursor pointing anywhere within the highlighted record, click
the middle mouse button to populate the relevant fields.

6 Click the Save button to save the newly created control file or changes made
to the existing one. You can revert back to the original setting by pressing
Reset button.
7 Click the Close button to exit the Event Template window.

7-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 8 Project Scan Utility

In This Chapter

General Description .................................................................................... 8-2

Overview ............................................................................................. 8-2
System Requirements ........................................................................... 8-3
Properties File ............................................................................................ 8-5
Project Scanning in Batch Mode................................................................... 8-8
Need for Batch Processing..................................................................... 8-8
Running Job in Batch Mode ................................................................... 8-8
Setting Cron Job................................................................................... 8-8
Viewing Log ..............................................................................................8-10
Troubleshooting Jobs .................................................................................8-11
Timeout Error......................................................................................8-11

Project Scan Utility 8-1

Schlumberger Private - Customer Use
General Description

General Description
This section includes information about the following topics:
• “Overview” on page 8-2
• “System Requirements” on page 8-3

Overview The Project Scan Utility scans Geoframe (IESX, Charisma) and OpenWorks
(SeisWorks) projects in order to gather the seismic-related information and populate
ProSource Seismic database with it. Information gathered by the Project Scan
Utility includes the following:
• 2D
- Projects
- Surveys
- Lines
- Datasets
- Amplitude statistics
- Live trace coverage

• 3D

- Projects
- Surveys
- Datasets
- Amplitude statistics
- Live trace coverage

• • • • • •
Note: The scanning process captures spatial information for entities with spatial
content.

A project scan job is configured from the Project Scan Utility interface and
initiated when a user selects the Run option from the Run menu or clicks Run icon
in the Project Scan Utility interface.
Users can also start a scan job from command line, see “Project Scanning in Batch
Mode” on page 8-8. A project scan job should normally be started from the Project
Scan Utility interface. When necessary, it can also be started from command line.
The project scanning data flow is illustrated in Figure 8-1.
When scanning seismic datasets for live trace coverage or amplitude statistics, only
those data in Geoframe or OpenWorks will be scanned, which were modified more

8-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

recently than the corresponding data in ProSource Seismic. This is because scanning
is a time-consuming operation that requires reading bulk trace.

IESX IESX
End User Interface

Tree / Table / Map SEOW

Charisma Charisma

Seisworks Seisworks

Data Attributes
Including Spatial

Export Job
Info
Project Scan

Database Export

SEG-Y
Scan
Seismic
Optional: if Trace Data
editing needed
or input=tape

Optional: if navigation cannot SEG-Y

SEG-Y Navigation be obtained from SEG-Y; N/A for
Load Project Data

SEG-Y
SEG-Y

Navigation

SEG-Y
SEG-Y FTP

Fig. 8-1 Project Scan Data Flow

System The following has to be done in order to be able to run project scans:
Requirements
• The OpenSpirit software should be installed. One or more than one setup may
exist in one system.
• The ProSource installation is properly configured with an OpenSpirit setup using
IMAdmin console. For more information please refer to ProSource Installation
Guide.
• The OpenSpirit setup should be properly configured i.e. Data Source
Configuration has been properly done on the OpenSpirit server (master
installation).
• The OS account to be used for project scans is properly configured for project
access:
• The account (user) has been granted access to the GeoFrame/OpenWorks
project(s) to be used for project scans. For details on granting access to
GeoFrame/OpenWorks project(s) to users please refer to GeoFrame/
OpenWorks documentation.

Project Scan Utility 8-3

Schlumberger Private - Customer Use
General Description

• The account (user) is properly configured with the OpenSpirit setup. The
User Setup Wizard tool can be used for that. Please refer to the OpenSpirit
documentation for more information.

8-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Properties File

Properties File
Scan properties define execution environment (for example: ArcSDE server
parameters, database parameters, etc.) and run mode (for example: implementation
mode, logging details level, etc.) for project scan jobs. The list of properties and
their descriptions can be found in this section (see below).
Project scan properties have to be specified for each scan job. The properties are
saved in an ASCII file. The file is called properties file. By default the properties file
is named project_scan.properties and it is located in the $HOME/.seisman
directory.
If a project scan job is to be run from command line, the properties file to be used
by the job has to be specified as a command line parameter. You can create a
custom properties file to be used for running a project scan job from command line
and save it in desired location.
If a project scan job is to be run from the Project Scan Utility interface, the
properties read from the file are used to pre-populate the interface when it is
starting. Any changes made to the properties in the interface are automatically
saved in the properties file before starting the job.
Each properties file contains the following attributes:
Table 8-1 Project Scan Properties

Property Name Description

ARCSDE_SERVER_NAME The name or IP address of the ArcSDE server machine.
ARCSDE_SERVER_PORT The port number used by the ArcSDE server.
CLASS_NAME Name of Java class to be called by OpenSpirit to run
scan jobs. You should not change the default value.
FILE_NAME The full path to the directory where the job log files are
to be saved and file name prefix. The file name prefix is
usually the name of the datastore the job is run against.
For example, /tmp/OpenSpirit/OSPVM04.
In this example the files will be stored in the
/tmp/OpenSpirit folder and will be named like
OSPVM04_dd_MMM_YYY_hh_mm_ss.log.
IMPL_MODE The implementation mode that identifies which
implementation of the project scan component should
be used by the OpenSpirit software.
The GeoQuestScan is a ProSource Seismic specific
implementation of the OpenSpirit project scan module.
LM_LICENSE_FILE The license server specification for accessing the source
datastores.
A license server can be defined by a text string like
port@host, where port is port number and host is the
host name or IP address of the machine where the
license server is running. For example
[email protected] or 27001@my_host.
Multiple specifications can be specified by separating
each with a colon.

Project Scan Utility 8-5

Schlumberger Private - Customer Use
Properties File

Property Name Description

LOG_FILE The name of the project scanner log file. The name can
also include the full path to where the log file will be
saved. If no path is included, the file will be created in
the same location as specified by the FILE_NAME
LOG_FORMAT The format of the project scanner log file, which can be
either TEXT or XML.
LOG_LEVEL The logging detail level of the project scanner log file,
which can be one of the following: SEVERE, WARNING,
INFO, CONFIG, FINE, FINER or FINEST. The SEVERE
level will log the most activity and FINEST will log the
least.
PASSWORD The password of the ProSource Seismic user.
PRESERVE_TIMESTAMPS Specifies if the timestamps of the seismic files found in
the project datastores (such as IESX, Seisworks,
Charisma) are to be preserved. The value can be TRUE
or FALSE.
SCAN_DATASTORE_TYPES The source datastore type, which can be one of the
following GeoFrame_4, OpenWorks_2003,
OpenWorks_R5000. Multiple types can be specified,
each separated by a comma.
SCHEMA The name of the target ProSource Seismic project.
SDE_AUTHENTICATION_TYPE The value can be either Regular or
OperatingSystem. Regular is for internal
authentication and OperatingSystem is for external
authentication.
SDE_CONNECTION_TYPE The value can be either NotDirectConnect or
DirectConnect. NotDirectConnect is the normal SDE
connection via the SDE daemon and DirectConnect
means that you will need to have an Oracle client
installed on the machine you are connecting from.
The SDE_AUTHENTICATION_TYPE and
SDE_CONNECTION_TYPE support ESRI's direct connect
which connects to Oracle directly and does not go
through the SDE demon.
SEABED_DATASTORE The name of the ProSource Seismic database
(TWO_TASK).
SPLASH_ICON_NAME The path to the image file used for the ProSource
Seismic splash screen.
TIMESTAMP_TEMP_PATH Specifies the location for the temporary files, if
PRESERVE_TIMESTAMPS is set to TRUE. A special
directory can be created for this, so all the files in this
directory can be deleted, if the scan job fails. The files
are automatically deleted, when the scan job is
successful.
USER_NAME The name of the ProSource Seismic user.

8-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Properties File

The following is an example of the properties file:

ARCSDE_SERVER_NAME=192.23.9.192
ARCSDE_SERVER_PORT=4721
CLASS_NAME=com.slb.sis.seisstream.project.scan.SSFeatureStore
FILE_NAME=/tmp/OW2003
IMPL_MODE=GeoQuestScan
[email protected]\:[email protected]\:1700@192.
23.9.223\:[email protected]\:[email protected]
LOG_FILE=scan.log
LOG_FORMAT=TEXT
LOG_LEVEL=FINEST
PASSWORD=r^eD
PRESERVE_TIMESTAMPS=FALSE
SCAN_DATASTORE_TYPES=GeoFrame_4,OpenWorks_2003,OpenWorks_R500
0
SCHEMA=pp
SDE_AUTHENTICATION_TYPE=Regular
SDE_CONNECTION_TYPE=NotDirectConnect
SEABED_DATASTORE=pss111s
SPLASH_ICON_NAME=/images/tw_splash.jpg
TIMESTAMP_TEMP_PATH=/home/psadmins/.seisman/timestamp
USER_NAME=pss

Project Scan Utility 8-7

Schlumberger Private - Customer Use
Project Scanning in Batch Mode

Project Scanning in Batch Mode

This section includes information about the following topics:
• “Need for Batch Processing” on page 8-8
• “Running Job in Batch Mode” on page 8-8
• “Setting Cron Job” on page 8-8

Need for Batch Project scan jobs can be run in batch mode. In UNIX environment you can schedule
Processing batch jobs to run automatically at a preferred time by setting up cron jobs.
Project scan jobs can be scheduled to run at times, when the network traffic is low
or at a time that is convenient for the normal operations of your company. When a
limited number of licenses is available for the source datastore (GeoFrame,
OpenWorks), batch jobs can conserve the number of licenses that are used at one
time, thus minimizing any interruption to interpretation activities. Some scanning
activities, such as histogram generation, may use significant network bandwidth.
Batch jobs can help to reduce the load on the system during times of peak usage.
You create the batch file from the Project Scan Utility by selecting the appropriate
processing options, selecting Save As from the File menu and then selecting a
directory and a file name for the batch file.
Batch files store such information as which seismic volumes/data sets should be
scanned and whether live trace coverage and statistics should be included in the
scan. See the Online Help for the detailed batch file setup procedures.
The Project Scan Utility saves the batch file in the directory with the file name
you specify in the Save Input Batch Script window displayed when you select
File>Save As from the Project Scan Utility menu. The batch files are saved as
XML files.

Running Job in To run a project scan job from a UNIX command line, you must run the
Batch Mode scan_project.sh script with the properties file and the batch file specified as the
command line options. The following example illustrates the required syntax:
scan_project.sh -propertyFile <path>/<property_file> -
batchFile <path>/<batch_file>

Setting Cron Job Project scan jobs can be scheduled to run automatically at regular time intervals.
In UNIX environment the crontab functionality can be used for that. To set up a
cron job, there must be:
• A crontab file, which lists the scripts to be run and defines time schedule for each
of the scripts
• A script, which would contain actual command to start the project scan job as
described above. The crontab file would define the run schedule for the script.

For more details on setting cron jobs, please refer to the operating system
documentation.

8-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Project Scanning in Batch Mode

 To Create a crontab File

1 Log in to the machine where you would like to set up the cron job as a user
with appropriate administrator permissions.
2 If required, set the command line environment for the vi editor.
root# setenv EDITOR vi
3 Open the crontab file for editing.
root# crontab -e
4 Add a line to the crontab file to specify the time and frequency the cron job
should be run. The following example shows how to schedule the cron job be
run at 11 p.m. every Thursday:
0 23 * * 4 <path>/cron_scan.csh
5 Exit from the vi editor.
6 Check that the command you added to the crontab file is correct.
root# crontab -l
For additional information about crontab, enter man crontab from a UNIX
command line.

 To Create the cron Job Script Referenced by the crontab File

1 Open a text editor and save a new file, use the name you used for the cron job
script in the crontab file.
2 Add the following lines to the new file:
#!/bin/csh -f
<full path to the file>/scan_project.sh -propertyFile
<path>/<property_file> -batchFile <path>/<batch_file>
3 Save the new file and close the text editor.

• • • • • •
Note: Ensure that the path and file name you used in the crontab file matches
the path and file name you use for the cron job script.

Project Scan Utility 8-9

Schlumberger Private - Customer Use
Viewing Log

Viewing Log
For each project scan job a log file is created in the directory specified either in the
Log File Directory field in the Project Scan Utility interface or in the batch file, if
the scan job is run in batch mode. Log files record all of the system activities that
occur during each project scan, including error messages. Consequently, the log files
can be used for troubleshooting project scans.
When a scan job is run from the Project Scan Utility, a Project Scan Progress
window displays all of the scan activity. This information will be included in the log
file. When the scan job is complete, an information window displays the directory
path and name for the log file. If the scan job is run from a command line, the
scanner script will display the same information when the scan job is complete. Each
log file is written to the directory specified as a text file named like
<datastore><date><time>.log. An example is shown below:
R5000_Dyce_14_Sep_2011_10_40_21.log.

8-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Troubleshooting Jobs

Troubleshooting Jobs

Timeout Error The following error occurs when the time to start server process exceeds the time
specified in the OpenSpirit.properties file.
*** ERROR (FailedOperationException) while retrieving
information for project '<project>':

Solution
1 Stop the OpenSpirit server.
2 In the <OpenSpirit_HOME>/classes/OpenSpirit.properties file add
or edit the following property:
openspirit.servers.UserServer.startupTimeOut=<seconds>
For example, the value for <seconds> can be set to 300 (5 minutes)
3 Restart the OpenSpirit server.
4 Rescan your project.

Project Scan Utility 8-11

Schlumberger Private - Customer Use
Troubleshooting Jobs

8-12 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 9 Data Export

In This Chapter

General Description .................................................................................... 9-2

Overview ............................................................................................. 9-2
System Requirements ........................................................................... 9-3
Data Transfer to Charisma..................................................................... 9-4
Seismic Export Order Wizard ....................................................................... 9-7
Viewing Related Information ................................................................. 9-7
Sending Data to SEOW via Table View ................................................... 9-7
Sending Data to SEOW via GIS View ...................................................... 9-8
SEG-Y Export........................................................................................ 9-9
Project-to-Project Data Copying............................................................9-10
Project to ZGY Data Export ..................................................................9-10
Export to Tape.....................................................................................9-13
Export to Trace Viewer.........................................................................9-15
Navigation Export Order Wizard..................................................................9-21
Sending Data to NEOW ........................................................................9-21
Sending Data to NEOW via GIS View using Seismic Selector ...................9-22
Navigation Export ................................................................................9-23
Aliases for Datum and Spheroid Names .................................................9-24
Managing Export Jobs................................................................................9-25
Email Notifications ...............................................................................9-25
Monitoring Jobs...................................................................................9-25
Updating Jobs .....................................................................................9-27

Data Export 9-1

Schlumberger Private - Customer Use

General Description

General Description
This section includes information about the following topics:
• “Overview” on page 9-2
• “System Requirements” on page 9-3
• “Client user i.e. user account on the machine where ProSource client is running is
properly configured with OpenSpirit User Setup Wizard. For that the OpenSpirit
client kit must be installed on the machine. Please refer to the OpenSpirit
documentation for more information.” on page 9-4
• “Data Transfer to Charisma” on page 9-4

Overview ProSource Seismic was designed to export seismic trace data using the Seismic
Export Order Wizard (SEOW). With the SEOW you can export/copy data loaded
from the corresponding sources to the following destinations:
• SEG-Y (disk file, tape or FTP)
• ZGY file (disk file, FTP)
• SEG-A, SEG-B, SEG-C and SEG-D (RODE encapsulated disk file, SEG-D disk file,
tape or FTP)
• a datastore project
- IESX project
- Charisma project
- SeisWorks project
ProSource Seismic can also export navigation data using the Navigation Export
Order Wizard (NEOW). Both the NEOW and the SEOW consist of a series of
panels displaying various options, depending on the source of the data set and the
output destination.
Figure 9-1 illustrates the following copy/export operations, which can be performed
with seismic data using the SEOW:
• SEG-Y to project (yellow line): Copies SEG-Y trace data from ProSource Seismic-
managed SEG-Y files to IESX, Charisma or SeisWorks projects.
• Project to project (red line): Copies project data between projects in the same
datastore as well as projects between different datastores.
• Project to SEG-Y/ZGY-U (green line): Copies project data from IESX, Charisma
or SeisWorks datastores to SEG-Y/ZGY-U (3D only) files on various media, such
as tapes and disks and FTP (only disk file and FTP for ZGY).

The orange lines illustrate SEG-Y-to-SEG-Y exports performed by the SEG-Y Exporter.
The thick pink line illustrates flow of metadata and export order parameters.
Metadata is transferred both to and from the Browse/Select/Export user interface
(ProSource), whereas the export order parameters are transferred to the database
and to the export module. Exports are controlled by the Distributor, which polls the

9-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 General Description

database for new export orders and determines the proper exporter (software
module) to which each order should be sent for further processing.

IESX IESX
End User Interface

Tree / Table / Map SEOW

Charisma Charisma

Seisworks Seisworks

Data Attributes
Including Spatial

Export Job
Info
Project Scan

Database Export

Seismic
Scan
Seismic
If SEG-Y Trace Data
editing needed
or input=tape

Optional: if navigation cannot

SEG-Y SEG-Y/
Navigation be obtained from SEG-Y; N/A for ZGY-U
Load Project Data

SEG-Y/
SEG-Y ZGY-U

Navigation

SEG-Y/
ZGY-U
SEG-Y FTP

Fig. 9-1 Export Data Flow

System The distributor must be running for the export jobs to be executed. For detailed
Requirements information about the distributor please refer to the Chapter 13, “Distributor,” on
page 13-1.
In addition to that the following has to be done in order to be able to run seismic
export to projects:
• The OpenSpirit software should be installed. One or more than one setup may
exist in one system.
• The ProSource installation is properly configured with an OpenSpirit setup using
IMAdmin console. For more information please refer to the ProSource Installation
Guide.
• The OpenSpirit setup should be properly configured i.e., Data Source
Configuration has been properly done on the OpenSpirit server (master
installation).

Data Export 9-3

Schlumberger Private - Customer Use

General Description

• The OS account, which is used for starting the distributor (normally it would be
the account used for ProSource installation/administration) is properly configured
for project access:
• The account (user) has been granted access to the GeoFrame/OpenWorks
project(s) to be used for export-to-project workflows. For details on granting
access to GeoFrame/OpenWorks project(s) to users please refer to
GeoFrame/OpenWorks documentation.
• The account (user) is properly configured with the OpenSpirit setup. The
User Setup Wizard tool can be used for that. Please refer to the OpenSpirit
documentation for more information.
• Client user i.e. user account on the machine where ProSource client is running is
properly configured with OpenSpirit User Setup Wizard. For that the OpenSpirit
client kit must be installed on the machine. Please refer to the OpenSpirit
documentation for more information.

Data Transfer to For successful data transfer from ProSource Seismic to Charisma certain
Charisma conditions should be met:
• The increment factor for in-lines/x-lines must be a positive value, as 3D
surveys with decrementing in-lines/x-lines are not supported by Charisma.
• The first and the last shotpoint numbers must be integer values. If fractional
SP values are found in the source SEG-Y dataset, they will be renumbered by
OSP to non-fractional numbers upon transfer to Charisma.
• Shotpoint increments must be positive integer values.
• CDP numbers must be integer values.
Also when transferring seismic data from ProSource Seismic to Charisma it is
important to make sure that Z-range (time or depth) is set properly for the target
survey in Charisma, so the corresponding header values in the seismic files are
within the range. If the values in the files are out of range specified for the survey,
the data transfer will fail with the message, like the one below:
PostStack2d was not copied due to an error
Caught StoreException copying a 2D Dataset. Reason:
'JNISeismicSection::createSeismicSection(): Caught exception,
osic_SeismicInterface::createSeismicSection() - Charisma Section
create failed - Section vertical extent is incorrect.' Detail:
'com.openspirit.osp.Osi.Exceptions.DevKitException:
JNISeismicSection::createSeismicSection(): Caught exception,
osic_SeismicInterface::createSeismicSection() - Charisma Section
create failed - Section vertical extent is incorrect.'
COMPLETED
2012-08-01 11:14:51 CDT
219110
CopySync job completed
---------------- Copy Job Summary ---------------
LineGeometry2d: 1/1 [ 1 Copied or Matched ]
LineGeometry2dSet: 1/1 [ 1 Copied ]
9-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 General Description

PostStack2d: 0/1 [ 1 Failed During Copy ]

-------------------------------------------------
THESE ITEMS FAILED TO COPY:
-------------------------------------------------------
The Scan/Edit/Load interface (or another application suitable for the purpose) can
be used to view values in seismic headers. The data should be checked, verified and
corrected or re-processed, if required. If the data are ok, then the target survey
parameters need to be changed in Charisma to accommodate values in in the files.
If new surveys in Charisma are created automatically during data transfer, then
corresponding OSP parameters for automatic survey creation should be changed
accordingly. More detailed information on these topics is provided below.

Relevant values in SEG- The parameters to check in SEG-Y headers are:

Y headers
• Number of Samples
• Sample Rate
• Delay Recording Time (aka First Sample Offset in ProSource table view)
The Delay Recording Time will show the minimum time or depth for the traces in
the seismic file. The maximum value can be calculated using the following formula:
((No_of_Samples – 1) * Sample_Interval) + Delay_Recording_Time

Automatically Creating A new survey can be automatically created by OSP when transferring data to a
Surveys by OSP Charisma project. Parameters for automatic survey creation are defined in the
runGeoFrameServer.sh script. The script is located in the $OSP_HOME/bin.
Below is an example of the file content related to Z-range (time or depth) definition:
OSIC_NEW_SURVEY_MIN_TIME_MS=-200; export
OSIC_NEW_SURVEY_MIN_TIME_MS
#OSIC_NEW_SURVEY_MIN_TIME_MS=0; export
OSIC_NEW_SURVEY_MIN_TIME_MS
OSIC_NEW_SURVEY_MAX_TIME_MS=10000; export
OSIC_NEW_SURVEY_MAX_TIME_MS
OSIC_NEW_SURVEY_DELTA_TIME_MS=2; export
OSIC_NEW_SURVEY_DELTA_TIME_MS
OSIC_NEW_SURVEY_MIN_DEPTH_FT=-200; export
OSIC_NEW_SURVEY_MIN_DEPTH_FT
#OSIC_NEW_SURVEY_MIN_DEPTH_FT=0; export
OSIC_NEW_SURVEY_MIN_DEPTH_FT
OSIC_NEW_SURVEY_MAX_DEPTH_FT=65000; export
OSIC_NEW_SURVEY_MAX_DEPTH_FT
OSIC_NEW_SURVEY_DELTA_DEPTH_FT=13; export
OSIC_NEW_SURVEY_DELTA_DEPTH_FT
The parameter names are quire self-explanatory. Edit the parameters as required.
For more details please refer OSP documentation.

Viewing and changing In Charisma values defining Z-range can be viewed and edited using the “Survey
Z-range values in Create/Edit” dialog (for more details please refer to GeoFrame documentation):
Charisma
Data Export 9-5

Schlumberger Private - Customer Use

General Description

9-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

Seismic Export Order Wizard

You can export partial or entire post stack data sets (2D/3D surveys and 2D lines) by
sending the data to the GIS View and then to the Seismic Export Order Wizard
(SEOW) via the Seismic Selector or directly to the SEOW.
The following workflows are described below in order to give few examples of how
the ProSource end user interface can be used for data selecting, viewing and
sending to the SEOW/GIS View:
• selecting data and viewing the related information
• selecting and sending the data to the SEOW
• selecting and sending the data to the SEOW via GIS View
These examples are focused on 2D lines, but the same techniques can be applied to
the other types of seismic entities, i.e. 2D/3D surveys, datasets, etc.

• • • • • •
Note: Data will not be copied to the destination application if the dataset name is
longer than allowed in the destination application. The dataset without
survey or line shape can be sent to the SEOW. However, if there is no
shape in the selected dataset, the dataset cannot be exported to Project
(IESX/Charisma/SeisWorks).

Viewing Related Complete the steps outlined below to select 2D lines and view the related
Information information.

 To Select 2D Lines and View the Related Information

1 In the ProSource Tree, select Seismic>Project or Seismic
Datastore><survey_name>>Lines.
The associated lines appear in the right pane.
2 Select all/some of the lines in the Name column and right-click to select
Related Information from the menu. The Related Information dialog box
opens.
3 Double-click the Post Stack Datasets option or any other option as required.

Sending Data to Complete the following steps to select 2D lines and then send the data to the
SEOW via Table Seismic Export Order Wizard.
View

• • • • • •
Note: 2D seismic lines and/or 3D surveys can be sent to SEOW only via the
Seismic Selector. Seismic datasets can be sent directly from the ProSource
Tree or from the Table View to SEOW by right-clicking on the selected
(highlighted) dataset(s) and then Send To -> Seismic Export Order
Wizard.
Data Export 9-7

Schlumberger Private - Customer Use

Seismic Export Order Wizard

 To Select 2D Lines and Send the Data to the SEOW using Seismic
Selector
1 In the ProSource Tree, select Seismic>Project or Seismic
Datastore><survey_name>>Lines. The associated lines appear in the
table view opened in the right pane of the main ProSource client interface
window.
2 Select all/some of the lines in the Name column and right-click to select Send
To>Seismic Selector from the menu. The ProSource Seismic - Seismic
Selector dialog box opens.

Fig. 9-2 Seismic Selector Window for 2D Lines started from Table View (note
the window header)

From here you can press the Export Seismic button to continue the SEOW
workflow to complete setting up the export job and submit it. For more information,
refer to the ProSource Seismic Online Help.

Sending Data to Complete the following steps to select 2D lines and send the data to GIS View.
SEOW via GIS View

 To Select 2D Lines and Send the Data to the GIS View

1 In the ProSource Tree, select Seismic>Project or Seismic
Datastore><survey_name>>Lines. The associated lines appear in the
right pane.
2 Select all/some of the lines in the Name column and right-click to select Send
To>GisView from the menu.
3 Use ProSource tools to draw a selection polygon around the lines in the GIS
View. The polygon can have simple or complex shape and can include entire
lines or their parts.
9-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

4 Right-click on the polygon and select Send To>Seismic Selector. The dialog
box opened contains surveys and 2D lines/segments.
5 Click Export Seismic to start the SEOW with the lines/segments selected as
defined by the selection polygon.

• • • • • •
Note: You can use the same instructions for selecting 2D lines and 2D/3D
surveys and sending the data to the GisView. If number of the output
SEG-Y files exceeds 100, an alert is given.

Fig. 9-3 Seismic Selector Window for 2D Lines started from GIS View (note
the window header)

SEG-Y Export

Description The SEOW can be used for exporting SEG-Y trace data from ProSource Seismic
SEG-Y storage area to a local disk area, device media (e.g. tape), an FTP site or to
projects in IESX, Charisma and SeisWorks datastores.
A SEG-Y export job is submitted after the job setting is complete, when a user clicks
Submit from the Export Order Wizard (depending on the type of export that has
been configured). The data flow for the SEG-Y Export is shown in Figure 9-1.

Data Export 9-9

Schlumberger Private - Customer Use

Seismic Export Order Wizard

Limitations Depending on the export order destination application, some values may have
character length limitations. Table 9-1 specifies the character length limits for 2D
data and Table 9-2 specifies the character length limits for 3D data.
Table 9-1 : Character Length Limits for 2D Data

Character Length Limits for . . .

Destination
Application
Survey Names Line Names Dataset Names

IESX 254 characters 255 characters 20 characters

Charisma 16 characters 20 characters 16 characters

Seisworks 40 characters 30 characters 9 characters

Table 9-2 : Character Length Limits for 3D Data

Character Length Limits for . . .

Destination Application
Survey Names Volume Names

IESX 254 characters 20 characters

Charisma 16 characters 16 characters

Seisworks 40 characters 256 characters

Project-to-Project Besides exporting SEG-Y trace data from the storage area to projects in IESX,
Data Copying Charisma and SeisWorks datastores, ProSource Seismic allows users to copy project
data from projects in one datastore to projects in another (or same) datastore.
A Project-to-Project job is submitted after the job parameters setting is complete,
when a user clicks Submit from the Export Order Wizard interface (depending
on the type of export that has been configured).
Please refer to the “Limitations” on page 9-10 for information on character length
limits in different systems for different seismic entity names.

Project to ZGY Data Use the following procedure to do a standard export of project data to ZGY:
Export
1 Select the desired 3D survey under project datastore.
2 Right-click and select Send To>Seismic Selector.

9-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

Fig. 9-4 Seismic Selector

3 Select the desired datasets available for the 3D survey selected.

4 Click on Export Seismic to send to Seismic Export Order Wizard.
5 Specify information about the recipient.

Fig. 9-5 Recipient Information

6 Select the Output Destination as ZGY-U.

Data Export 9-11

Schlumberger Private - Customer Use

Seismic Export Order Wizard

Fig. 9-6 Output Destination

7 Specify the Output Directory and click Next.

Fig. 9-7 Output Directory

8 Click Finish to view the export job summary.

9-12 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

Fig. 9-8 View Job Export Summary

9 Review the export job summary and click Submit.

Fig. 9-9 Job Export Summary

Export to Tape There are some specific steps to be done in order to configure and run an export to
tape job.
1 Make sure that the corresponding entry exists in the Media table for the media
type you are going to use for the export job.
Data Export 9-13

Schlumberger Private - Customer Use

Seismic Export Order Wizard

Administrator must create one entry for each media type in order to define it in
the system. For more details on setting a media in the system please refer to
the “Managing Media” on page 11-9.
2 Make sure that the corresponding entry exists in the Devices table for the tape
drive you are going to use for the export job.
Administrator must create one entry for each device in order to define it in the
system. For more details on setting a device in the system please refer to the
“Managing Devices” on page 11-11.
3 Select your data and start the SEOW. Going through the workflow select Mail
in the Delivery Method field.

Fig. 9-10 Selecting Delivery Method

4 Select the Media type as required. For more details on setting media types in
the system please refer to the “Managing Media” on page 11-9.
The export recipient must have a physical address defined. For more details on
creating users and setting various types of user-related information in the
system please refer to the “User Administration” on page 10-1.

9-14 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

Fig. 9-11 Selecting the Media Type

5 After the export order is submitted, administrator must update the job record
to change the status from ‘SUBMITTED DEFERRED’ to ‘SUBMITTED’ and specify
the output device. For additional information, see “Selecting Device for Export
to Media” on page 9-28.

Export to Trace The Trace Viewer option is available for seismic file entities, which are children of 2D
Viewer or 3D Datasets: SEG-Y entities in the TreeView, TableView, or FormView. When you
are logged directly into a project account, (i.e. no control by entitlements), you can
select and view a seismic file with the trace viewer. However, if you are logged into a
secure interface, the Trace Viewer option will be disabled, and you will not be able to
view a seismic file with the Trace Viewer.

• • • • • •
Note: The Trace Viewer process can be launched on ProSource server and by
default Trace Viewer application will be displayed on the ProSource server
host. Use the following options to access the Trace Viewer:

• You can access the Trace Viewer application on your desktop. Run the X
Window server (like Hummingbird®/OpenText® Exceed®, Cygwin/X, etc.)
on your desktop and redirect the Trace Viewer window to the user display by
configuring preferences for Trace Viewer. For more information on
configuring the trace viewer preferences, refer to Chapter 11, “Trace Viewer
Preferences,” on page 11-19.
• You can access the Trace Viewer application on ProSource server host. The
following example is for VNC® software but any other appropriate
application can be used.
- Run the VNC® Server on ProSource Server host.
Data Export 9-15

Schlumberger Private - Customer Use

Seismic Export Order Wizard

- Run the VNC® client from the client machine (to ProSource Server host) to get
direct access to the Linux environment where the trace viewer can be launched
by default.
Use the following procedure to view a SEG-Y file:
1 Select the desired SEG-Y file in the TreeView, TableView, or FormView.
2 Press the right mouse button and select Send To and then Trace Viewer.
You may send only one SEG-Y file at a time to the trace viewer.

Fig. 9-12 Launch Trace Viewer

Use the following procedure to do a standard export of trace data to get only data
covered by entitlements:
1 Select the desired Files: SEG-Y entity.
2 Select Send To and then select Seismic Export Order Wizard.

9-16 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

Fig. 9-13 Launch Seismic Export Order Wizard

Data Export 9-17

Schlumberger Private - Customer Use

Seismic Export Order Wizard

3 Specify information about the recipient.

Fig. 9-14 Recipient Information

4 Select the new delivery method named TRACE VIEWER.

Fig. 9-15 Output Directory

This option will only be available if the Output Destination is SEG-Y. The
Representation option will be disabled and ORIGINAL option will be
selected by default. Click Next.

9-18 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Seismic Export Order Wizard

5 Provide the Output Directory (default value can be set in the ProSource
Seismic preference tab) and Display Host option to show Trace Viewer, then
click Finish.

Fig. 9-16 Local Copy

6 Review the export job summary and click Submit.

Fig. 9-17 Job Summary

7 Monitor the export job the same as a normal export process, from Submitted
to Finished.

Data Export 9-19

Schlumberger Private - Customer Use

Seismic Export Order Wizard

8 When the export job is finished, you should be able to see the Trace Viewer.

Fig. 9-18 Trace Viewer

9-20 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Navigation Export Order Wizard

Navigation Export Order Wizard

Navigation export workflow is accomplished with the Navigation Export Order
Wizard (NEOW). Navigation can be exported either for entire 2D line(s) / 3D
survey(s) or just for their part(s). Full export is done by sending selected survey(s)/
line(s) from a ProSource view (Table View, Row View, GIS view) directly to the
NEOW. Partial export (also called sub-setting) is performed by sending the data
from a ProSource view to the Seismic Selector first and then calling the NEOW
from the Seismic Selector interface. It is possible to make spatial selection in the
GIS View, before sending data to the Seismic Selector. Also the Seismic
Selector can be used to create/modify selection polygon(s).
The following workflows are described below in order to give few examples of how
the ProSource end user interface can be used for navigation data export.
• Selecting and sending the data to the NEOW
• Selecting and sending the data to the NEOW via GIS View using Seismic Selector

Sending Data to Complete the following steps to select 3D survey(s) or 2D line(s) and send the data
NEOW directly to the Navigation Export Order Wizard.

 To Select 3D survey(s) or 2D line(s) and Send the Data to the NEOW

1 In the ProSource Tree, select one or more 3D survey by navigating to
Seismic>Project or Seismic Datastore>Project>3D Surveys.
Similarly, you can select one or more 2D lines by navigating to
Seismic>Project or Seismic Datastore>Project>2D Survey>Lines.
The survey(s)/line(s) appear in the right pane.

• • • • • •
Note: Alternatively, you can use corresponding topics under the
Supplementary Info node.

2 Select all/some of the survey(s)/line(s) and right-click to select Send

To>Navigation Export Order Wizard from the menu.

Data Export 9-21

Schlumberger Private - Customer Use

Navigation Export Order Wizard

The Navigation Export Order Wizard dialog box opens.

Fig. 9-19 Navigation Export Order Wizard

• • • • • •
Note: From here, you can continue the NEOW workflow to complete setting up
the export job and submit it. For more information, refer ProSource
Seismic Online Help.

Sending Data to Complete the following steps to select 3D survey(s) or 2D line(s) and send the data
NEOW via GIS View to the Navigation Export Order Wizard via GIS View using Seismic Selector.
using Seismic
Selector

 To Select 3D Survey(s) or 2D line(s) and Send the Data to the NEOW

via GIS View using Seismic Selector
1 In the ProSource Tree, select one or more 3D survey by navigating to
Seismic>Project or Seismic Datastore>Project>3D Surveys.
Similarly, you can select one or more 2D lines by navigating to
Seismic>Project or Seismic Datastore>Project>2D Survey>Lines
The survey(s)/line(s) appear in the right pane.

• • • • • •
Note: Alternatively, you can use corresponding topics under Supplementary
Info node.

2 Select all/some of the surveys/lines and right-click to select Send

To>GisView from the menu.

9-22 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Navigation Export Order Wizard

3 Use ProSource tools to draw a selection polygon on top of the survey(s)/line(s)

in the GIS View. The polygon can have simple or complex shape and can
include entire survey(s)/line(s) or its part(s).
4 Right-click on the polygon and select Send To>Seismic Selector. The
Seismic Selector starts showing selected survey(s)/line(s).
5 Click Export Navigation to start the NEOW with the survey(s)/line(s)
selected as defined by the selection polygon.

Fig. 9-20 Seismic Selector Window for 3D Survey

• • • • • •
Note: From here, you can continue the NEOW workflow to complete setting up
the export job and submit it. For more information, refer ProSource
Seismic Online Help.

Navigation Export The NEOW can be used for exporting navigation data from ProSource Seismic
database to a local disk area, an FTP or SFTP site in UKOOA P1/90 format. A
navigation export job is submitted after the job setting is complete, when a user
clicks Submit from the Navigation Order Wizard.
Data Export 9-23

Schlumberger Private - Customer Use

Navigation Export Order Wizard

The UKOOA exporters generate output files as per UKOOA P1/90 specification. The
files have the following bare minimum of information in header fields:
• Survey Name
• UKOOA format version of the file (which is P1/90)
• Coordinate System and Transformation details
Complete the following steps to select 3D survey(s) or 2D line(s) and send the data
directly to the Navigation Export Order Wizard.

Aliases for The H1400 and H1500 fields of the UKOOA header contain datum and spheroid
Datum and names for the storage and the output coordinate systems respectively. If the length
Spheroid Names of datum and/or spheroid name is not as per the UKOOA P1/90 specification then
the values are truncated to meet the specification.
An option is provided to allow users to specify shorter names for datum and
spheroid names which will be used to generate the UKOOA header. The following file
is used to define aliases for datum and spheroid names:
$PS_HOME/ext_app/psx/Seabed_Utilities/config/ukooa_alias.txt
Example of the file content:

9-24 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Managing Export Jobs

Managing Export Jobs

Email Notifications When an export job is submitted, the appropriate users will be notified by e-mail.
The recipients of these notifications are specified in the Recipient Information
panel in the Seismic Export Order Wizard. By default a notification will also be sent
to the owner of the account used to submit the export job, even if another recipient
has been selected in the Recipient Information panel. The users listed in this
panel are defined in the ProSource Seismic Business Associate tree and all have
access to the same project.
You can have these e-mail notifications sent to other users, such as administrators,
by setting the corresponding parameters in the ProSource Seismic tab of the Edit
Preferences window in the ProSource interface.
You can specify multiple e-mail addresses by separating each address with either a
comma (,) or a semi-colon (;). For example:
email1,email2,email3
.

Fig. 9-21 Edit Preferences window

Monitoring Jobs Progress and status of export jobs can be monitored using the following:
• “Distributor Log File” on page 9-26
• “Job Log File” on page 9-26
• “ProSource Export Jobs Tree” on page 9-27

Each export job generates an export order summary, which is e-mailed to the
person, who submitted the export job from the Seismic Export Order Wizard. This
summary includes such information as the date and time for the export job, the
name of the person submitted the export job, the delivery method and destination
for the output.

Data Export 9-25

Schlumberger Private - Customer Use

Managing Export Jobs

Distributor Log File The progress of an export job execution is recorded in the distributor log file. You
can use OS command for viewing the log file or you can view the file from the
ProSource tree.

 To View the Distributor Log File Using OS Commands

1 Locate the file. For more details on the distributor log file location please refer
to the “Distributor Log File Name and Location” on page 13-7.
2 Use your preferred command/application in order to view the content of the
file.

• • • • • •
Note: You can find information on how to view the Distributor Log File from the
ProSource Tree by referring to the topic ‘Viewing Log Files’ within the
ProSource Seismic Online Help.

• • • • • •
Note: More than one distributor process can be running in the system against
different Seabed projects

Each time an export job is run, new information is added to the distributor log file. If
you want to start a new log file without information from previous export jobs, you
must restart distributor before running the new export job. The Distributor will then
create a new log file when it processes the export job.
To change the default name and/or location of the distributor log file refer to the
“Distributor Log File Name and Location” on page 13-7.
To change the messaging level (i.e. how much details are included into the log file)
refer to the “Message Level” on page 13-8.

Job Log File The details of an export job execution are recorded in the job log file. The file is
located in the job log directory, which name is equal to the export job ID.

• • • • • •
Note: The system assigns to each job a random number, which is known as job
ID. All the jobs can be listed using the “ProSource Export Jobs Tree”,
that can be used to find out the job ID of the submitted job. You can find
information on how to view the Job Log File by referring to the topic
‘Viewing Log Files’ within the ProSource Seismic Online Help.

Based on the job type the job log directory will be created in one of the following
sub-folders:
• <ProSource External Directory>/logs/pss/export
• <ProSource External Directory>/logs/pss/openspirit

If the job is setup for the OpenSpirit data transfer (Project Copy/Loader), the
parameter files that the Distributor creates for the export job will be stored in the
directory along with the job log file.
9-26 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Managing Export Jobs

• • • • • •
Note: OpenSpirit log files are in html format, so use your preferred web browser
to view those.

ProSource Export Jobs After an export order is submitted, the job is added to the EXPORT_JOB table and
Tree can be seen in the Export Jobs node in the ProSource tree. The Status attribute
indicates the current status of the export job, (see the topic Job Status Tracking
within the ProSource Seismic Online Help for further details).

Updating Jobs A user can update an export job based on his account privileges.
By default ProSource Seismic provides the following roles in order to manage and
control access to the database and use of the administrative privileges:
• SEISMIC_MANAGER
• SEISMIC_MANAGER_ADMIN
Each of the roles provides users with different privileges for updating export jobs
from ProSource tree.
User accounts the SEISMIC_MANAGER role was granted to (end users) have the
following privileges:
• Resubmit an own export job
• Cancel an own export job
• Update the status of an own export job

User accounts the SEISMIC_MANAGER_ADMIN role was granted to (administrators)

have the following privileges:
• Resubmit any export job
• Cancel any export job
• Update the status of any export job

• Assign output device to any export job

The procedures associated with these account privileges are listed below:
• “Resubmitting Failed Export Jobs” on page 9-27
• “Cancelling Export Jobs” on page 9-28
• “Selecting Device for Export to Media” on page 9-28

Resubmitting Failed Failed export jobs can be resubmitted from ProSource Seismic tree. To resubmit any
Export Jobs export job, you must be logged on to ProSource with an account that has
appropriate administrative privileges. If you are logged on with an account that does
not have the administrative privileges, you will be able to resubmit only jobs
submitted using this account.

 To Resubmit an Export Job

1 Navigate to the Export Jobs node under the ProSource Seismic tree.

Data Export 9-27

Schlumberger Private - Customer Use

Managing Export Jobs

2 Search for a specific export job or on the Export Jobs node, click to list all
the submitted export jobs. If prompted to log on to the database, enter your
login information.
3 Ensure that the export job you want to resubmit is selected and then check the
status of the job (see “ProSource Export Jobs Tree” on page 9-27 for
information about checking export job status).
4 If the job status shows that the job failed (see the Table , “After an export order
is submitted, the job is added to the EXPORT_JOB table and can be seen in the
Export Jobs node in the ProSource tree. The Status attribute indicates the
current status of the export job, (see the topic Job Status Tracking within the
ProSource Seismic Online Help for further details).,” on page 9-27) right-click
the job in the tree and select Send To>Resubmit Export Job from the
menu.
5 Click Yes when prompted to confirm that you want to resubmit the job.
If you are logged on to ProSource with an account that does not have required
administrative privileges and you are attempting to resubmit a job, which was
originally submit using another account, an error message will display. The
message will state “You may only resubmit jobs which you created”. In this
case in order to be able to resubmit the job, you must log on with an account
that has required administrative privileges or with the account, which was used
to submit the job. If the job was successfully re-submitted, a message will
display to confirm that the job was re-submitted.

Cancelling Export Jobs Export jobs can be cancelled from the ProSource interface. To cancel any export job,
you must be logged on to ProSource with an account that has appropriate
administrative privileges. If you are logged on to ProSource with an account that
does not have the administrative privileges, you will be able to cancel only the jobs
submitted using this account.

 To Cancel an Export Job

1 Navigate to the Export Jobs node under the ProSource Seismic tree.

2 Search for a specific export job or on the Export Jobs node, click to list all
the submitted export jobs. If prompted to log on to the database, enter your
login information.
3 Ensure that the export job that you want to cancel is selected. Right-click the
job in the tree and select Send To>Cancel Export Job from the menu.
4 Click Yes when prompted to confirm that you want to cancel the job.
If you are logged on to ProSource with an account that does not have required
administrative privileges and you are attempting to cancel a job, which was
originally submit using another account, an error message will display. The
message will state “You may only cancel jobs which you created”. In this case
in order to be able to cancel the job, you must log on with an account that has
required administrative privileges or with the account, which was used to
submit the job. If the job was successfully cancelled, a message will display to
confirm that the job was cancelled.

Selecting Device for If an export job is setup to output data to a media, the job status initially is set to
Export to Media SUBMITTED DEFERRED and the job is ignored by the distributor. A user with

9-28 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 Managing Export Jobs

appropriate administrative privileges must then assign an output device to the job.
See also “Seismic Selector” on page 9-11.

 To Select a Device for the Export Job

1 Navigate to the Export Jobs node under the ProSource Seismic tree.

2 Search for a specific export job or on the Export Jobs node, click to list all
the submitted export jobs. If prompted to log on to the database, enter your
login information.
3 Ensure that the export job that you want to update is selected. Use ProSource
interface controls to enter edit mode. The Remarks, Device and Status
attributes for the selected job will become editable.
4 Click the Device attribute field. Picklist button should be available on the right
side of the field.
5 Select a device from the list and click OK.
6 Click the Status attribute field. Picklist button should be available on the right
side of the field.
7 Select Submitted status from the list.
8 Click Save. The device will be assigned to the job. The Distributor will pick and
submit the job next time it polls the database for submitted jobs.

Data Export 9-29

Schlumberger Private - Customer Use

Managing Export Jobs

9-30 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use

 10 User Administration

In This Chapter

Setting Up User Accounts...........................................................................10-2

Creating New User Account ..................................................................10-2
Granting Seismic Roles.........................................................................10-2
Granting Project Access .......................................................................10-3
Verifying User Account .........................................................................10-3
Configuring Business Associate Information.................................................10-4
Creating Person Profile.........................................................................10-5
Creating Electronic Address ..................................................................10-5
Creating FTP Address...........................................................................10-6
Creating Physical Address.....................................................................10-7
Creating Business Associate Group........................................................10-7
Creating Group-Person Association .......................................................10-8
Creating Application User Association....................................................10-8

User Administration 10-1

Schlumberger Private - Customer Use
Setting Up User Accounts

Setting Up User Accounts

Follow these steps to set up user accounts. Refer to the IM Administration Console
documentation for additional information.

Creating New User Complete the following steps to create a new ProSource user.
Account

 To Create a New User

1 Log in to the IM Administration Console using account with appropriate
administrative privileges.
2 Click the Users button in the main navigation pane.
3 Click the Create button to create a new user account.
For more details please refer to the ProSource Administration Guide.

Granting Seismic By default ProSource Seismic provides the following roles in order to manage and
Roles control access to the database and use of the administrative privileges:
• SEISMIC_MANAGER
• SEISMIC_MANAGER_ADMIN
The roles are created at the time of installation.
The SEISMIC_MANAGER_ADMIN role provides the following administrative
privileges:
• Edit and delete seismic entities
• Resubmit any export job
• Cancel any export job
• Update status of any export job

• Assign output device to any export job

• • • • • •
Note: A user who was granted the SEISMIC_MANAGER role (but not the
SEISMIC_MANAGER_ADMIN) can resubmit, cancel or update only own
export jobs (but not the jobs submitted by other users).

Complete the following steps to grant ProSource Seismic roles to a user. It is

assumed that you are logged in to the IM Administration Console using account with
appropriate administrative privileges.

 To Grant ProSource Seismic Roles

1 Select a user from the list, and click the Role button to display the list of roles
already assigned to the user.
2 Click the Add button to display a list of available roles.

10-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Setting Up User Accounts

3 Select either the SEISMIC_MANAGER or the

SEISMIC_MANAGER_ADMIN role to be granted to the user.
4 Specify the Start Date and the End Date, if the usage of the role by this user
is to be restricted to a specific date range, then click OK. If usage of the role is
not to be restricted, leave the fields blank. The selected role should now be
displayed in the list of assigned roles.

Granting Project Complete the following steps to grant project access to a user. It is assumed that
Access you are logged in to the IM Administration Console using account with appropriate
administrative privileges.

 To Grant Project Access

1 Select a user from the list, and click the Objects button to display the list of
objects already assigned to the user.
2 Click the Add button to display a list of available objects.
3 Select the Seabed Project tab to display the list of available projects. This list
includes both projects and secure project interfaces.
4 Select the project or secure interface to which the user is to have access and
click OK.

• • • • • •
Note: Do not select a secure interface at this step unless the data entitlement
functionality will be used. If you grant secure interface, the user will be
able to see only those data entries (such as surveys and lines) that he was
entitled to. For the user in order to be able to see the data entries, an
entitlement operation must be performed explicitly through the ProSource
interface by an administrator, who has access rights to the project.

5 Specify the Start Date and the End Date, if the access rights of this user are
to be restricted to a specific date range, then click OK. If access to the project
is not to be restricted, leave the fields blank. The selected project should now
be displayed in the list of assigned projects.

Verifying User Complete the following steps to log in to ProSource with the newly created/
Account configured user account and verify if the role(s) and/or project access have been
granted correctly.

 To Log into ProSource Seismic

1 Restart the ProSource client or add a new connection for the user.
2 Connect to the project to verify that access has been granted correctly.

User Administration 10-3

Schlumberger Private - Customer Use
Configuring Business Associate Information

Configuring Business Associate Information

The business associate (BA) model is used to manage information about business
associates and the relationships between them. Some BA entities are used by
ProSource Seismic:
Table 10-1Business Associate Entities Used by ProSource Seismic

Entity (Topic Name) Description

Application Users The link between a ProSource Seismic database login
account and a ProSource Seismic user profile. This
association is required for all users who want to submit
export jobs.
Group person The relationship between users, logical group and user
roles. There are two user roles available for ProSource
Seismic users: Exporter and Member. A user with the
Exporter role can create export orders. A user with the
Member role can receive export orders but not create
them. Users who want to create and receive export
orders must have both roles.
Groups The logical group to which a user is assigned. Users can
belong to multiple groups, regardless of whether they
are assigned the Exporter or Member role.
Person The ProSource Seismic user profile, which should be
created for all ProSource Seismic users.
Electronic The e-mail address to which export order summary
Addresses reports are to be sent. The e-mail address specified for
this association will display in the Email field of the
Recipient Information window in the Sesimic
Export Order Wizard interface. (Optional)
FTP Addresses IP address or machine name for an FTP destination.
This is required if an export order is to be output to FTP.
This address will be used if a user selects the FTP
option in the Output Destination window of the
Seismic Export Order Wizard interface. (Optional)
Physical Addresses The physical address to which data should be shipped.
This address will be used if a user selects the MAIL
option in the Output Destination window of the
Seismic Export Order Wizard interface. (Optional)

The following associations are not required by ProSource Seismic:

• Activity Roles
• Alias
• Associate Types
• Association Roles
• Business Associates
• Business Titles

10-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring Business Associate Information

• Company
• Company Person
• Telephonic Addresses
• Valid Alias Sources
• Valid Associations
The following business associate procedures require that you log on to ProSource
using account with appropriate administrative privileges.
• “Creating Person Profile” on page 10-5
• “Creating Electronic Address” on page 10-5
• “Creating FTP Address” on page 10-6
• “Creating Physical Address” on page 10-7
• “Creating Business Associate Group” on page 10-7
• “Creating Group-Person Association” on page 10-8
• “Creating Application User Association” on page 10-8

Creating Person Complete the following steps to create a Business Associate Person profile.
Profile

 To Create a Person Profile

1 Navigate to Business Associate>Person in the ProSource Seismic tree.
2 Click the Create Person icon in the tree. The Create Person window displays
on the right side of the ProSource interface.
3 Enter a value for the Unique identifier.
4 Enter values for the First name and the Last name.
5 Select a Person type from the picklist. If you are not already connected to the
database, you will be prompted to do so.
6 Optionally enter values for the following attributes:
• Business title code: An abbreviation that identifies business title of the
person. You can select a code from the picklist.
• Remarks: Enter any remarks.
7 Click Save to save the person profile.
8 Close the Create Person window.

Creating Electronic Complete the following steps to create an electronic address.

Address

User Administration 10-5

Schlumberger Private - Customer Use
Configuring Business Associate Information

 To Create an Electronic Address and Associate it with a Person

1 Navigate to Business Associate>Reference>Electronic Addresses in the
ProSource Seismic tree.
2 Click the Create Electronic Address icon in the tree.
The Create Electronic Address window displays on the right side of the
ProSource interface.
3 Enter or select values for the following attributes (the required attributes are
marked in red, all the other attributes are optional):
• Name: Enter a name for the address. This is used for descriptive purposes
only, such as “Primary e-mail.”
• Address text: Enter the e-mail address.
• Electronic address type: Select an address type from the picklist. If you
are not already connected to the database, you will be prompted to do so.

• • • • • •
Note: The address type should be e-mail.

• First name: From the picklist select the user name to associate with this
address. Selecting an item in this picklist will automatically populate the Last
name field. This picklist displays business associate persons.
• Remarks: Enter any remarks.
4 Click Save. Close the window.

Creating FTP Complete the following steps to create an FTP address.

Address

 To Create an FTP Address and Associate it with a Person

1 Navigate to Business Associate>Reference>FTP Addresses in the
ProSource Seismic tree.
2 Click the Create FTP Address icon in the tree.
The Create FTP Address window displays on the right side of the ProSource
interface.
3 Enter or select values for the following attributes (the required attributes are
marked in red, all the other attributes are optional):
• Name: Enter a descriptive name for the address.
• Address text: Enter an IP address or server name to be used for the output
destination for export orders. If no port number is specified, the default one
will be used for establishing the FTP/SFTP connection to the remote host. If
you need to specify port number explicitly, the format of the entry should be
<IP address>:<port number>, for example 136.254.62.131:21.
• Connect user id: Enter a user ID that allows write access to the FTP
destination.

10-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring Business Associate Information

• Directory path name: Enter the directory path where files should be
copied on the destination FTP site.
• First name: From the picklist select the user name to associate with this
address. If you are not already connected to the database, you will be
prompted to do so. Selecting an item in this picklist will automatically
populate the Last name field. This picklist displays business associate
persons.
• Remarks: Enter any remarks.
4 Click Save. Close the window.

Creating Physical A physical address is a physical location such as a building, plant, site, campus or
Address post office box. Complete the following steps to create a physical address.

 To Create a Physical Address and Associate it with a Person

1 Navigate to Business Associate>Reference>Physical Addresses in the
ProSource Seismic tree.
2 Click the Create Physical Address icon in the tree.
The Create Physical Address window displays on the right side of the
ProSource interface.
3 Enter or select values for the following attributes (the required attributes are
marked in red, all the other attributes are optional):
• Name: Enter a descriptive name for the address.
• Line1 text through Line3 text: Enter the street address, including P. O. Box
or suite number, if relevant.
• City name: Enter the name of the city.
• State province code: Enter an abbreviation for the state or province, such
as TX for Texas.
• Postal code: Enter the postal code for the physical address.
• Country code: Select a country code from the picklist. If you are not
already connected to the database, you will be prompted to do so.
• First name: From the picklist select the user name to associate with this
address. Selecting an item in this picklist will automatically populate the
Last name field. This picklist displays business associate persons.
• Remarks: Enter any remarks.
4 Click Save. Close the window.

Creating Business A logical group may equate to an actual business entity, such as a company or
Associate Group department, or it may be a completely arbitrary group, such as all people within a
department who have a birthday in May. ProSource Seismic uses this system to
control who can submit export orders and for whom users can submit export orders.

 To Create a Logical Group

1 Navigate to Business Associate>Groups in the ProSource Seismic tree.

User Administration 10-7

Schlumberger Private - Customer Use
Configuring Business Associate Information

2 Click the Create Group icon in the tree.

The Create Group window displays on the right side of the ProSource
interface.
3 Enter or select values for the following attributes (the required attributes are
marked in red, all the other attributes are optional):
• Group name: Enter a name for the group.
• Group type: Select a group type from the picklist. If you are not already
connected to the database, you will be prompted to do so.
• Remarks: Enter any remarks.
4 Click Save to save the group record. Close the window.

• • • • • •
Note: The new group name will not be listed in the tree until you clear results
and re-query the database.

Creating Group- You can associate a person within a group with the Member role, the Exporter
Person Association role or both. A person with the Member role may receive export orders. A person
with the Exporter role may submit export orders for all members of all groups of
which he is a member. It is likely that you will want to create two associations:
Exporter and Member.

 To Create a Group-Person Association

1 Navigate to Business Associate>Group Person in the ProSource Seismic
tree.
2 Click the Create Group Person icon in the tree.
The Create Group Person window displays on the right side of the ProSource
interface.
3 Select a group name from the picklist. If you are not already connected to the
database, you will be prompted to do so.
4 Select the First name of the user from the picklist and the Last name field is
automatically populated.
5 Select an association role from the picklist:
- Member to allow the user to receive export orders
- Exporter for the user to create export orders
6 Click Save to save the group-person association to the Dictionary. Close the
window.

Creating The final step is to create an association between a ProSource user and a ProSource
Application User Seismic database account.
Association

10-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring Business Associate Information

 To Assign a ProSource Seismic Login Name to a ProSource Person

1 Navigate to Business Associate>Application Users in the ProSource
Seismic tree.
2 Click the Create Application User icon in the tree.
The Create Application User window displays on the right side of the
ProSource interface.
3 Select the database account from the Login picklist. If you are not already
connected to the database, you will be prompted to do so.
4 Select the name of the person from the First name picklist. This is the user
you created as per the instructions in the “Creating Person Profile” on page 10-
5. The Last name field will be automatically populated.
5 Click Save to save the association between the new database user account and
the business associate person. Close the window.

User Administration 10-9

Schlumberger Private - Customer Use
Configuring Business Associate Information

10-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 11 System Administration

In This Chapter

Configuring non WGS-84 Project ................................................................11-2

Adding a CRS to the Recommended CRS List and Setting Transformation 11-3
Managing Custom CRS...............................................................................11-4
Creating Custom CRS...........................................................................11-4
Creating Custom CRS for OpenSpirit .....................................................11-4
Creating Custom Datum Transformation ................................................11-4
Reference Data .........................................................................................11-6
Managing Values .................................................................................11-6
Managing Permissions..........................................................................11-6
Media and Devices ....................................................................................11-7
Media Attributes ..................................................................................11-7
Device Attributes .................................................................................11-8
Managing Media ..................................................................................11-9
Managing Devices ............................................................................. 11-11
Archive Area ........................................................................................... 11-13
Configuring Output Directory Selection Method.................................... 11-13
Archive Folders.................................................................................. 11-13
Managing Bitmap Storage ........................................................................ 11-15
Loading Seismic Data......................................................................... 11-15
Migration Utility .................................................................................11-15
Managing messaging level for seismic loader logs ...................................... 11-17
Preferences............................................................................................. 11-18
ProSource Seismic Preferences ........................................................... 11-18
Trace Viewer Preferences ................................................................... 11-19

System Administration 11-1

Schlumberger Private - Customer Use
Configuring non WGS-84 Project

Configuring non WGS-84 Project

Each Seabed (ProSource Seismic) project based on a coordinate reference system
(CRS) other than WGS-84, must be properly configured. In this context term
“configuration” means adding essential entries to the Recommended CRS list for
the project and specifying appropriate transformations for the entries in the list.
The following steps should be done to configure a non WGS-84 Seabed project:
1 Check if the WGS-84 geodetic coordinate system (GCS) is in the
Recommended CRS list for the Seabed project being configured. If required,
add the GCS to the list by following the procedure described in the “Adding a
CRS to the Recommended CRS List and Setting Transformation” below.

• • • • • •
Note: This step must be done before running any project scans.

2 Scan the GeoFrame/OpenWorks project, which is to be used for OpenSpirit

workflows.

• • • • • •
Note: The projected CRS of the GeoFrame/OpenWorks project is automatically
created in the Seabed DB when the project is scanned for the first time.
So, after scanning the project you will be able to select the CRS and add it
to the Recommended CRS list. In Seabed each scanned survey will be
associated with the CRS, but at this time the no transformation is set.

3 Make sure that the projected CRS of the GeoFrame/OpenWorks project is in the
Recommended CRS list for the Seabed project being configured. If required,
add the CRS to the list by following procedure described in the “Adding a CRS
to the Recommended CRS List and Setting Transformation” below.
4 Scan the GeoFrame/OpenWorks project.

• • • • • •
Note: At this time in Seabed each scanned survey will be associated with the
transformation set for the survey CRS at step 3 above. Now you should be
able to run all the workflows for the survey.

5 Repeat steps 2-4 for each GeoFrame/OpenWorks project to be used for

OpenSpirit workflows.

• • • • • •
Note: The above procedure is applicable only in cases, when direct
transformation exists for coordinate conversion from the GeoFrame/
OpenWorks project CRS to the Seabed project default CRS. Two step
transformations are not currently supported.

11-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring non WGS-84 Project

Adding a CRS to Please perform the following steps to add a CRS to the Recommended CRS list
the Recommended for the Seabed project being configured and set the transformation for the CRS:
CRS List and
1 Determine what CRS is to be added
Setting
Transformation 2 Find out what datum transformation should be used for conversion from the
CRS to the default CRS of the Seabed project being configured
3 Check if the CRS and transformation definitions exist in the data dictionary, the
Seabed project being configured is based upon. If any of the required
definitions are missing, please add those, before proceeding with the
configuration steps. Mind, that CRS of an interpretation project will
automatically be created in the Seabed DB when the project is scanned for the
first time. For more information on how to define a CRS/transformation in
ProSource please refer to the “Managing Custom CRS” on page 11-4.

• • • • • •
Note: The configuration steps described below are done with the Seabed
dbadmin tool during Seabed project creation or at any time later using
the Set/Edit Recommended CRS dialog (Set Recommended CRS in
project creation mode). For detailed information please refer to Seabed
documentation.

4 Add the CRS to the Recommended CRS list

5 Select the datum transformation to be used for the CRS from the drop down list
6 Click Update button

System Administration 11-3

Schlumberger Private - Customer Use
Managing Custom CRS

Managing Custom CRS

If ProSource Seismic does not include a predefined coordinate reference system
(CRS) that you want to use, you can define required custom CRS in the system. This
may be needed for scanning/loading or export operations, which require CRS
selection.
This section includes the following instructions:
• “Creating Custom CRS”
• “Creating Custom Datum Transformation”
• “Creating Custom CRS for OpenSpirit”

Creating Custom Complete the following steps to create a custom CRS in ProSource.
CRS

 To Create a Custom CRS in ProSource

Identify the Coordinate Reference System (CRS) parameters.
If the CRS has not been defined in ProSource, define it in the system. For more
information, see “Manage Coordinate Systems” section in the ProSource
Administration Guide.

Creating Custom Complete the following steps to create a custom datum transformation in ProSource.
Datum
Transformation

 To Create a Custom Datum Transformation in ProSource

Identify the Coordinate Reference System (CRS) parameters. Based on that define if
the datum transformation is required for the CRS.

• • • • • •
Note: If the CRS is based on datum, different from the one, which is used for the
default CRS definition, then datum transformation is required.

If the datum transformation has not been defined in ProSource, define it in the
system. For more information, see “Manage Coordinate Systems” section in the
ProSource Administration Guide.

Creating Custom Complete the following steps to create a custom CRS for OpenSpirit.
CRS for OpenSpirit

11-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Managing Custom CRS

 To Create a Custom CRS for OpenSpirit

1 Identify the Coordinate Reference System (CRS) parameters.
2 If the CRS has not been defined in ProSource, define it in the system. For more
information, see Manage Coordinate Systems section in the ProSource
Administration Guide.
Print and save the Well Known Text (WKT) of the Projected Coordinate System
(PCS) and its transformation to WGS84.

• • • • • •
Note: The Well Known Text and its transformation to WGS84 is the first piece of
information you will need.

3 If the same CRS (same parameters and not necessarily same name) exist in
GeoFrame, obtain the GeoFrame datum name or press Alt+PrintScreen to
capture the GeoFrame Coordinate System information.
Or, if the CRS does not exist, contact SIS customer support to submit an
InTouch ticket to the GeoFrame and IM Help desks to create a new coordinate
file.

• • • • • •
Note: The GeoFrame datum name is the second piece of information you will
need.

4 Obtain the following Coordinate System parameters from GeoFrame or

OpenWorks/SeisWorks:
• datum name
• spheroid parameters
• transformation parameters
• projection parameters

• • • • • •
Note: The Coordinate System parameters is the third piece of information you
will need.

5 Send the first, second and third pieces of information to OpenSpirit (Tibco)
support. An OpenSpirit representative will determine whether the datum
mapping exists or if there is a need to create a new mapping.
This information is required even if the CRS already exists, because OpenSpirit
might not have all the mappings or because Esri Geographic Coordinate System can
have more than one transformation.

System Administration 11-5

Schlumberger Private - Customer Use
Reference Data

Reference Data

Managing Values Reference values for various attributes are organized under the Reference branch
in the ProSource Seismic tree.
A user having appropriate permissions can use the ProSource Seismic tree nodes to
manage reference values (i.e. add new ones, edit or delete existing ones).

Managing When an administrator grants a user with access to a project, the user will have
Permissions read and write access to all entities within that project. The user will have read-only
access to the reference data in the corresponding data dictionary. The user will not
have insert, update or delete permissions for any reference data because this is
typically managed by a limited number of people.
For details on granting a user with insert, update or delete permissions to reference
data please refer to “Configuring a Data Dictionary” page (i.e., Home > Manage
Seabed Databases and Projects > Configuring a Data Dictionary) of the IM Admin
Console Online Help.

11-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Media and Devices

Media and Devices

You can manage (add, modify or delete) media and devices using the ProSource
interface. You must use a ProSource administrator account with appropriate
privileges. For additional information see the following sections:
• “Managing Media” on page 11-9
• “Managing Devices” on page 11-11

In the ProSource Seismic database there are two reference tables, which are used to
define the devices in the system:
• The MEDIA table stores information on the media types defined in the system.
• The DEVICE table stores information on the devices defined in the system. The
devices are used for export jobs (work orders).

Each record in the DEVICE table references the CODE column in the MEDIA table
for the Media attribute. These two tables are pre-populated during ProSource
Seismic installation. New device and media definitions can be added later. You
should not change the pre-populated records.

Media Attributes Media attributes are stored in the MEDIA table. Each media record includes the
following attributes:
Table 11-1Media Attributes

Attribute Description

Active flag+ a value that specifies whether the media type is

active (1) or not active (0). When set to 1, the
media can be used by a device

Code + a standard abbreviation, mnemonic or short code

that represents the reference value for the media
type

Description a textual description of the media type

Name the full name of the media type

Source the person, company or application that defined or

specified the data (content) for this instance and
who is considered to be responsible for it (such as
POSC, EPSG, API and ISO)

Update date the date of the most recent modification to the

media record

Update user the name of the user responsible for the last
modification to the media record

Media capacity the storage size of the media in gigabytes (GB)

System Administration 11-7

Schlumberger Private - Customer Use
Media and Devices

• • • • • •
Note: The required attributes are marked with + in the above table.

Table 11-2: Example of media type record

Active flag Code Description Name

1 3480 18 track, Storage Storage Tek 3480
Tek

Device Attributes Device attributes are stored in the DEVICE table. Each device record references one
of the media types stored in the MEDIA table. Each device record includes the
following attributes:
Table 11-3Device Attributes

Attribute Description

Active flag + a value that specifies whether the device is active

(1) or not active (0). When set to 1 the device can
be used by ProSource Seismic.

Code + a standard abbreviation, mnemonic or short code

that represents the reference value for the device

Description a textual description of the device

Name the full name of the device

Source the person, company or application that defined or

specified the data (content) for this instance and
who is considered to be responsible for it (such as
POSC, EPSG, API and ISO)

Update date the date of the most recent modification to the

device record

Update user the name of the user responsible for the last
modification to device record

Device file path + the fully qualified UNIX file path for the device
(such as /dev/rmt/1)

Host name+ the name or IP address of the system on which

the device is mounted

Media + the media used by the device; this information

references the R_MEDIA table

Status the status of the device. The allowed values are

ALLOC and FREE. If a device is set to ALLOC
(allocated), it is being used by an export job; when
set to FREE, it is available for use by an export
job.

11-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Media and Devices

• • • • • •
Note: The required attributes are marked with + in the above table.

Table 11-4Example of device record

Active flag Code Device file path Host name Media Status

1 8mm (8500) /dev/rmt/2 163.185.8.182 8mm(8500) FREE

Managing Media Use the procedures described in this section to manage media definitions. The
procedures are organized as follows:
• “Adding Media Definition to Database” on page 11-9
• “Modifying Media Definition Stored in Database” on page 11-10
• “Deleting Media Definition from Database” on page 11-10

Adding Media Definition Complete the following steps to add a media definition to the database.
to Database

 To Add a Media Record to the Database

1 Log on to ProSource with a user account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary
Info>Reference>Media.
3 Click the Create Media icon.
The Create Media panel will display on the right side of the ProSource
interface.
4 Enter the information for the new media.
The required attributes are marked in red. All of the other attributes are
optional. The attributes reflect the columns in the R_MEDIA database table. For
a full description of each attribute, see “Media Attributes” on page 11-7.
5 Ensure that the information for each attribute is displayed in red.
A field value turns red when you click on a different field. If the value of any
field is not red, you will receive an error message when you try to save the
record.
6 Click Save.

System Administration 11-9

Schlumberger Private - Customer Use
Media and Devices

Modifying Media Complete the following steps to modify a media definition stored in the database.
Definition Stored in
Database

 To Edit a Media Record Stored in the Database

1 Log on to ProSource with a user account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary
Info>Reference>Media.

3 In TreeView select to list all records or select , enter your search

criteria in the Search panel and click Search to find records that match your
criteria.
4 When prompted, enter your database connection information and click
Connect.
If you searched for specific media, the media will display in a panel on the right
side of the ProSource interface. If you listed all media that were previously
added to the database, all media will be listed in the panel.
5 Either select specific media from the table view or click Back to see all media in
the tree view. In the tree view you can select specific media items and send
them to the table view.
6 Select the media and click Edit to make all of the attribute fields editable.
7 Edit the media information as required.
The required attributes are marked in red. All of the other attributes are
optional. These attributes reflect columns in the R_MEDIA database table.
After you have changed the contents of a field and clicked on another field, the
value in the field will turn red and the Save button will become active. For a full
description of each item, see “Media Attributes” on page 11-7.
8 Click Save to save your changes.

Deleting Media Complete the following steps to delete media definition from the database.
Definition from
Database

 To Delete a Media Record from the Database

1 Log on to ProSource with a user account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary
Info>Reference>Media.
3 Use the steps described for modifying media in the previous procedure to
search and display the information for a specific media.
4 Ensure that the media you want to delete is selected, then click Delete.
The media information will be grayed out and the record for the media will be
deleted from the database.

11-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Media and Devices

Managing Devices Use the procedures described in this section to manage device definitions. The
procedures are organized as follows:
• “Adding Device Definition to Database” on page 11-11
• “Modifying Device Definition Stored in Database” on page 11-11
• “Deleting Device Definition from Database” on page 11-12

Adding Device Complete the following steps to add a device definition to the database.
Definition to Database

 To Add a Device Record to the Database

1 Log on to ProSource with a user account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary Info>
Reference>Devices.
3 Click the Create Device icon.
The Create Device panel will display on the right side of the ProSource
interface.
4 Enter the information for the new device.
The required attributes are marked in red. All of the other attributes are
optional. The attributes reflect the columns in the R_DEVICE database table.
For a full description of each attribute, see “Device Attributes” on page 11-8.

• • • • • •
Note: You can double-click the Status field to see the current status for the
device. For new devices, this is null until you have saved the device to the
database.

5 Ensure that the information for each attribute is displayed in red.

A field value turns red when you click on a different field. If the value of any
field is not red, you will receive an error message when you try to save the
record.
6 Click Save.

Modifying Device Complete the following steps to modify a device definition stored in the database.
Definition Stored in
Database

 To Edit a Device Record Stored in the Database

1 Log on to ProSource with a user account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary
Info>Reference>Devices.

System Administration 11-11

Schlumberger Private - Customer Use
Media and Devices

3 In TreeView select to list all records or select , enter your search

criteria in the Search panel and click Search to find records that match your
criteria.
4 When prompted, enter your database connection information and click
Connect.
If you searched for a specific device, the device will display in a panel on the
right side of the ProSource interface. If you listed all devices that were
previously added to the database, all devices will be listed in the right panel.
5 Either select a specific device from the table view or click Back to see all of the
devices in the tree view. In the tree view you can select a specific devices and
send them to the table view.
6 Select the device and click Edit to make all of the attribute fields editable.
7 Edit the device information as required.
The required attributes are marked in red. All of the other attributes are
optional. These attributes reflect columns in the R_DEVICE database table.
After you have changed the contents of a field and clicked on another field, the
value in the field will turn red and the Save button will become active. For a full
description of each item, see “Device Attributes” on page 11-8.

• • • • • •
Note: You can double-click the Status field to see the current status for the
device.

8 Click Save to save your changes.

Deleting Device Complete the following steps to delete a device definition from the database.
Definition from
Database

 To Delete a Device Record from the Database

1 Log on to ProSource with an account that has appropriate administrative
privileges.
2 Expand ProSource Seismic tree and navigate to Supplementary
Info>Reference>Devices.
3 Use the steps described for modifying device in the previous procedure to
search and display the information for a specific device.
4 Ensure that the device you want to delete is selected, then click Delete.
The device information will be grayed out and the record for the device will be
deleted from the database.

11-12 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Archive Area

Archive Area
As a part of the data loading workflows (Scan/Edit/Load, Tape Index Load,
Navigation Load) users are required to select an Output Directory in the interface of
the loader being used. The directory will be used as an archive area for the data
being loaded.
Before 2012.1 release of ProSource Seimic, users were able to select any directory
available in the file system. Starting with 2012.1 release, the behavior was changed
(for more details please refer “Archive Folders” section below). Starting with 2012.4
service pack, the behavior of the system can be configured to use either of the
options as follows.

Configuring Output The Output Directory selection method can be defined by setting the
Directory Selection OUTPUTFOLDER_SELECTION property in the seismic_loader.properties
Method file. The file is located in the $SEISMAN_HOME/config directory. Possible values
for the property are described in the table below.
Table 11-5 Output Directory selection property

Value Description
ARCHIVE Default value, the List of Archive Folder entities is
used for the Output Directory selection. For more
details please refer “Archive Folders” section below.
MANUAL File chooser dialog is used for the Output Directory
selection. User will be able to select any available
directory. Output files will be created directly under the
selected directory.

• • • • • •
Note: An example of the seismic_loader.properties file is provided in
Appendix A, “seismic_loader.properties,” on page A-1.

Archive Folders If the system is configured to use the List of Archive Folder entities for the
Output Directory selection, administrator can create a top level output directory
(Archive Folder) and register it in the system through ProSource Seismic user
interface. Administrator can create one archive folder or more.
When a new datastore is created, a new subdirectory is also created under the
selected archive folder.
If data loaders define new project/survey/(line)/<format>, while using
corresponding loader interface, the application will create new sub-directory
structure under the selected archive folder in the fixed pre-defined hierarchy:
<archive folder>/<datastore ID>/<project ID>/<survey ID>/
<dataset ID>/<format>/<seismic filename>
For 3D SEG-Y

System Administration 11-13

Schlumberger Private - Customer Use
Archive Area

<archive folder>/100383/100384/100384/100385/segy/
100395_SM.sgy
For 2D SEG-Y
<archive folder>/100501/100502/100503/100504/100514/segy/
100524_SM.sgy

• • • • • •
Note: In this mode Output Directory is not a free selection. The loader can only
select output directories from the list of archive folders created by the
administrator.

An entry in the list of archive folders is automatically created each time

when rode encapsulated field data are loaded from disk using Seismic
Scan/Edit/Load. This is applicable for SEG-A, SEG-B, SEG-C and SEG-D
workflows. The type of the folder created is RODE. By design the input
data files are not moved to the output folder specified, but the references
to the original files are created in the database and an entry is created in
the list of archive folders.

 To Create an Archive Folder

1 Log on to ProSource with an account that has appropriate administrative
privileges.
2 Navigate to Seismic>System Info>Archive Folder in ProSource Seismic
tree.
3 Click Create Archive Folder icon.
The Create Archive Folders panel will be displayed.
4 Enter the information for the new folder.

The required attributes are marked in red. All of the other attributes are
optional.
5 Make sure that the information entered for each attribute is displayed as red.
A field value turns red when you click on a different field. If the value of any
field is not red, you will receive an error message, when you try to save the
record.
6 Click Save.

11-14 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Managing Bitmap Storage

Managing Bitmap Storage

Loading Seismic When the Scan/Edit/Load is used for seismic data loading, the following two
Data bitmaps are created for each new dataset being added to the database:
• All trace outline
• Live trace outline
The bitmaps are stored in the system for future use in case if more files are to be
added to the existing datasets. The bitmaps can be stored either as BLOBs in the
database or as binary files in the file system. The bitmap storage type is defined by
the BITMAP_STORAGE parameter in the seismic_loader.properties file,
which is located in $SEISMAN_HOME/config directory. By default the
BITMAP_STORAGE parameter is set to DATABASE. If required, the parameter can be
set to FILE. In the latter case the bitmaps will be saved under the
<prosource_ext_dir>/Documents/<instance_name>/<project_name>/
directory in the files named Live_Trace_XPM_<Dataset_ID>.dat and
Dataset_XPM_<Dataset_ID>.dat respectively.
When loading data, the loader reads the BITMAP_STORAGE parameter from the
configuration file and stores the bitmaps as per the value specified. If new seismic
files are added to the existing data sets, the existing bitmaps will be updated (if
required) and stored according to the value specified for the BITMAP_STORAGE
parameter. For example, if the existing bitmaps are stored is in the file tree and the
BITMAP_STORAGE parameter is set to DATABASE, the bitmaps will be moved to the
database. And the other way around, if the existing bitmaps are stored in the
database, and the BITMAP_STORAGE parameter is set to FILE, the bitmaps will be
moved to files.

• • • • • •
Note: The bitmaps can be deleted but only in cases where no data will be added
to the existing data set.

• • • • • •
Note: An example of the seismic_loader.properties file is provided in
Appendix A, “seismic_loader.properties,” on page A-1.

Migration Utility If you have loaded some data into your system and you want to move the bitmaps
from the database to the file tree or vice versa, you can use the migration utility
provided. This utility will move all the bitmaps from one storage type to the other.
Migration utility is invoked by running the script seismic_storage_util.csh
available in the $SEISMAN_HOME/scripts directory.
The script should be executed from the console where SEISMAN_HOME
environment variable is set. The command line options for the utility are listed
below:
• Project name – seismic project for which data are to be migrated

System Administration 11-15

Schlumberger Private - Customer Use
Managing Bitmap Storage

• Project password – password of the project

 To Move Bitmaps from Database to Files:

1 Make sure that the value of the BITMAP_STORAGE parameter in the
configuration file is set to FILE.
2 Run the following command:
seismic_storage_util.csh –u <project> -p <project_pwd>
Bitmaps for every dataset will be moved from database to file storage.

 To Move Bitmaps from Files to Database:

1 Make sure that the value of the BITMAP_STORAGE parameter in the
configuration file is set to DATABASE.
2 Run the following command:
seismic_storage_util.csh –u <project> -p <project_pwd>
Bitmaps for every dataset will be moved from the file storage to database.

11-16 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Managing messaging level for seismic loader logs

Managing messaging level for seismic loader logs

For each load job the Scan/Edit/Load saves the job logs in the corresponding file (for
more information see “Log File” on page 4-7 and “Viewing Scan/Edit/Load Log” on
page 4-13). This log can also be viewed in the progress window, which opens
automatically after the user submits load job by clicking the Load button.
Information displayed depends on the messaging level set by the user.
The messaging level is defined by value of the ALLOW_MESSAGING property in the
$PROSOURCE_HOME/ext_app/pss /config/seismic_loader.properties file. Acceptable
values for the property are YES, NO and DEBUG. By default the property is set to
NO.
You can either set the ALLOW_MESSAGING property in the properties file or
manually set the environment variable of ALLOW_MESSAGING. The environment
variable takes precedence over the properties file value.

• • • • • •
Note: If any invalid value is set in the properties file or the environment variable,
by default the property is set to NO.

• • • • • •
Note: Load jobs can be run from command line or in batch (for more information
see “Starting Scan/Edit/Load Job from Command Line” on page 4-8). If
needed, you can change the property value in the corresponding
parameter (.par) file and run the job. The log file for the job will be output
with the level of details set in the parameter file. If set, the
ALLOW_MESSAGING environment variable takes precedence over the
parameter file value.

• • • • • •
Note: An example of the seismic_loader.properties file is provided in
Appendix A, “seismic_loader.properties,” on page A-1.

System Administration 11-17

Schlumberger Private - Customer Use
Preferences

Preferences

ProSource Seismic Edit the following seismic preferences by selecting Edit>Preferences from the
Preferences main ProSource menu, then clicking the ProSource Seismic tab:

 Mail
The mail preferences are used to send the Summary Report from the Export Order
Wizard.
• Send E-Mail - check box to send email
• SMTP Host - host name or IP address of the SMTP server
• SMTP Port - SMTP port number
• From - address for the email header From field
• CC - one or more addresses separated by commas (,) or semi-colons (;) to send
copy of the Summary Report.

 Exporter
• Default Local Output Directory - path to a directory to be used as a default
value for the Output Directory parameter in the SEOW interface. Seismic
exporters will write output files to this directory (if you do not change it in the
interface while configuring and submitting an export job). The directory must be
accessible for read/write operations from the server where distributor/exporter is
running. Each export job will be run under a user account which was used to start
the distributor. So the user account should have read/write access rights for the
directory.
• Default Local Copy File Prefix - a text string to be used as a default value for
the File-name Prefix parameter in the SEOW interface. This prefix will be added to
the names of the output files (if you do not change it in the interface while
configuring and submitting an export job). The text string should not have OS
specific special characters to avoid conflicts with the file management (copying,
moving, using names in command line, etc.).
• Seismic Manager TWO_TASK - the ProSource database instance
($TWO_TASK)
• Cache Dataset - select this option to retain the values you enter into the various
fields of the Seismic Export Order Wizard. If you launch the Seismic Export
Order Wizard multiple times for the same dataset, values for the parameters in
various panels for the dataset will be retrieved from the cache rather than from
the database. For example, for a dataset, if you specify a value for Bulk Shift or
Z-Range Clipping, next time when SEOW is started for the same dataset, the

11-18 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Preferences

values you had specified will be retained. The cache is cleared upon closing the
ProSource client session.

• • • • • •
Note: If the Cache Dataset option is selected then various parameters for
seismic datasets are cached while the Seismic Export Order Wizard
workflows are executed. As user navigates between different panels of the
interface and makes entries in the fields, the user input is saved in the
cache. If later the SEOW is called for the same dataset(s), then values for
the parameters are retrieved from the cache to be displayed in the
corresponding fields of the interface.

If the Cache Dataset option is disabled then various parameters for

seismic datasets are not cached while the Seismic Export Order Wizard
workflows are executed. As user navigates between different panels of the
interface and makes entries in the fields, the user input is not saved in the
cache. If later the SEOW is called for the same dataset(s), then values for
the parameters are retrieved from the database to be displayed in the
corresponding fields of the interface as user input made in the previous
sessions of the SEOW is not retained.

Trace Viewer Edit the following preferences by selecting Edit>Preferences from the main
Preferences ProSource menu, then clicking the Trace Viewer tab:
Trace Viewer
• Display - specifies where the Trace Viewer interface is displayed. This value
should be specified in a form of <host>:<display> where host is the host
name or IP address of an X server and display is the display number. If an X
server is up and running on the ProSource client system, then the system can be

System Administration 11-19

Schlumberger Private - Customer Use
Preferences

specified as a host. Alternatively, a Linux server can be specified and then a utility
like VNC can be used to access the host and see the Trace Viewer.

• First trace (or field file, in the case of SEG-D/RODE files) to display - First
trace of the range to be displayed in the Trace Viewer by default.
• Number of traces (or field files, in the case of SEG-D/RODE files) to
display - Number of traces to be displayed in the Trace Viewer by default.

• • • • • •
Note: When you are logged on to ProSource as an Administrator, select the
Store settings as the default public preferences option to modify the
public preferences.

• • • • • •
Note: The “First trace/file to display” and “Number of traces/files to display” is
not applicable to SEG-D files.

• There is limitation to the number of traces/records that can be displayed in Trace

Viewer. The table below lists these limitations:

11-20 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Preferences

Data file type Limitation

SEG-Y Range cap of 10000 traces.

SEG-D All records obtainable from the first 4MB of the file.

RODE files Range cap of 100000 records.

System Administration 11-21

Schlumberger Private - Customer Use
Preferences

11-22 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 12 Entitlements

In this Chapter

Introduction ..............................................................................................12-2
Spatial Entitlements...................................................................................12-3
Granting Spatial Entitlement to 2D Data ................................................12-3
Granting Spatial Entitlement to 3D Data ................................................12-4
Attaching Document to Entitlement.......................................................12-4
Viewing Document Attached to Entitlement ...........................................12-5

Entitlements 12-1
Schlumberger Private - Customer Use
Introduction

Introduction
ProSource incorporates a powerful engine to control user access to the data and
functionality of the system. This engine is called the Entitlements Management
System. In addition, access to seismic data can be geographically restricted. These
two features combined, allow full control of data access.

• • • • • •
Note: This chapter is focused on ProSource Seismic specific functionality and
workflows. Before you continue, we strongly recommend that you
familiarize yourself with Entitlements Management concepts and
workflows. Please refer to the ‘ProSource Data Entitlements Guide’ which
provides a thorough introduction to this subject.

12-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Spatial Entitlements

Spatial Entitlements
ProSource Seismic supports entitlements to geographically define subsets of seismic
surveys and lines. Administrators can define a spatial entitlement for a subset of a
3D survey, 3D dataset, 2D line or 2D dataset.
Spatial entitlements geographically restrict the sub-sets of seismic data the users,
whom the entitlements have been granted to, can view/export.
Administrator can view all of the entitlement attributes and spatial information for
any group. Administrator selects an area and entitles it to a specified group. The
processes for granting the spatial entitlement vary, depending on whether the data
is in a 2D or 3D format.
Row level and spatial entitlements used together provide full fine-grained data
access control.

Granting Spatial Complete the following steps to grant spatial entitlement to 2D data.
Entitlement to 2D
Data

 To Grant Spatial Entitlement to 2D Data

1 In ProSource tree navigate to 2D seismic lines (Seismic>Project or Seismic
Datastore><Application_Project><survey_name>>Lines), then right-
click the Lines folder and select Send To>GisView.
The system opens the GisView and displays the lines.
2 Select “create polygon” tool and draw a polygon on top of the 2D survey
restricting certain area within the survey.
OR,
If you want to entitle the entire survey, draw a polygon around the survey.
The system highlights the line segments that fall within the polygon.
3 Right-click the shape displayed and select Send To>Seismic Selector.
The system displays the Seismic Selector for 2D and snaps the polygon to
the segments of the 2D lines in GisView.
4 Click Entitle.
The system opens the Entitlement interface.
5 Enter the following and click OK:
- Name
- Remarks
- The group(s) to be granted spatial entitlement
- Reason (Auditor, Owner, Partner)
- Start date
- End date
The system grants spatial entitlements for the 2D data to anyone in the group.

Entitlements 12-3
Schlumberger Private - Customer Use
Spatial Entitlements

Granting Spatial Complete the following steps to grant spatial entitlement to 3D data.
Entitlement to 3D
Data

 To Grant Spatial Entitlement to 3D Data

1 In ProSource tree navigate to 3D seismic surveys (Seismic>Project or
Seismic Datastore><Application_Project><survey_name>), then
right-click <SurveyName> and select Send To>GisView.
The system opens GisView and displays a survey boundary shape.
2 Select “create polygon” tool and draw a polygon on top of the survey boundary
shape restricting certain area within the survey.
The system displays the polygon on top of the survey boundary shape.
3 Right-click the shape displayed and select Send To>Seismic Selector.
The system displays the Seismic Selector for 3D.
4 Click Entitle.
The system displays the Create Entitlement interface.
5 Select the following and click OK:
- Name
- Remarks
- The group(s) to grant spatial entitlement
- Reason (Auditor, Owner, Partner)
- Start date
- End date
6 The system grants spatial entitlements for the 3D data to anyone in the group
and displays a confirmation message.

Attaching ProSource Seismic allows administrators to attach a document to an entitlement

Document to record to provide additional supporting information about the origin or reason for an
Entitlement entitlement. To attach a document to an entitlement record, perform the following
steps:

 To Attach a Document to an Entitlement Record

1 In ProSource tree navigate to the Entitlements folder
(Seismic>Supplementary Info>Spatial Entitlements>Entitlements),
expand the folder, pick an entitlement and expand it.
2 Right-click on the Documents sub-folder of the selected entitlement. The
system displays a menu.
Select Create Document. The Create Document panel will display on the
right side of the ProSource interface.
3 Enter a Name, select values for the following fields from the picklists and click
Save:

12-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Spatial Entitlements

• Document Format
• Document Type
• Original Path
• Storage Type
The system creates the document record and attaches the document to the
entitlement.

Viewing Document To view a document attached to an entitlement record, perform the following steps:
Attached to
Entitlement

 To View a Document Attached to an Entitlement Record

1 In ProSource tree navigate to the Entitlements folder
(Seismic>Supplementary Info>Spatial Entitlements>Entitlements),
expand the folder, pick an entitlement and expand it.
2 Click on the Documents sub-folder of the selected entitlement to send the
data to table view.
3 Right-click on the name of a document in the table view and select Send To >
Document Viewer.

Entitlements 12-5
Schlumberger Private - Customer Use
Spatial Entitlements

12-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 13 Distributor

In This Chapter

General Description ...................................................................................13-2

Supported Export Jobs.........................................................................13-2
System Requirements ..........................................................................13-2
Recommended Practices ......................................................................13-2
Starting and Stopping ................................................................................13-4
Starting Distributor ..............................................................................13-4
Stopping Distributor from ProSource .....................................................13-5
Stopping Distributor from Command Line ..............................................13-6
Configuring ...............................................................................................13-7
Configuration Table..............................................................................13-7

Distributor 13-1
Schlumberger Private - Customer Use
General Description

General Description
This section includes information about the following topics:
• “Supported Export Jobs” on page 13-2
• “System Requirements” on page 13-2
• “Recommended Practices” on page 13-2

Supported Export The Distributor schedules and controls execution of the export jobs. The Distributor
Jobs periodically polls ProSource Seismic database to determine whether a new export
job record exists and to which exporter the job should be assigned.
Each export job record includes of the following:
• Reference(s) to the dataset(s) to be exported
• Data sub-set identifying information, such as i-line/x-line (3D) or CDPs/shot point
(2D) range
• Data manipulation (edited export), destination and delivery parameters
After the Distributor finds a new export job, it determines which of the following to
open:
• Project Copy/Loader is used to do the following:
- Export SEG-Y trace data to a project (IESX, Charisma or SeisWorks)
- Export project data (IESX, Charisma or SeisWorks) to SEG-Y files
- Export project data (IESX, Charisma or SeisWorks) to another project
- Export project data (IESX, Charisma or SeisWorks) to ZGY files
• Seismic Exporter is used to do the following:
- Export SEG-Y trace data to SEG-Y files on disk or tape media
- Export SEG-Y trace data to ZGY files on disk
- Export raw field data on disk
- Export 3D UKOOA data on disk
- Use FTP/SFTP to transfer files to a predefined destination

System For the Distributor to run, all the required environment variables must be defined as
Requirements described in the ProSource Installation Guide. An xterm started from the
Application Launcher will automatically have all the required environment
variables defined.

Recommended Export jobs are configured using the Seismic Export Order Wizard (SEOW) or
Practices Navigation Export Order Wizard (NEOW). One of the parameters user has to
define Delivery Method.
Local Copy: if delivery method selected is LOCAL COPY, the export files will be
saved to the output directory specified by user while setting up the job. There is
Default Local Output Directory parameter in the ProSource Seismic tab of the

13-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 General Description

Edit Preferences window in the ProSource interface. You may specify a directory
for this parameter and it will be used as default for the Output Directory in SEOW/
NEOW interface.

Fig. 13-1 Edit Preferences Window

The recommended practice is to specify an NFS directory mounted on the machine

running the Distributor. Make sure that the directory has write permissions for users
submitting export jobs. Doing so will prevent export errors.
Mail: when the delivery method selected is MAIL (Output to tape media), you
must ensure that the distributor is running on the machine that has the needed tape
drive connected. If not, shut down the distributor where it is running and restart it
on the machine connected to the tape drive.

Distributor 13-3
Schlumberger Private - Customer Use
Starting and Stopping

Starting and Stopping

This section includes information about the following topics:
• “Starting Distributor” on page 13-4
• “Stopping Distributor from ProSource” on page 13-5
• “Stopping Distributor from Command Line” on page 13-6

Starting Distributor The Distributor is started during installation and configuration of ProSource Seismic.
If it was intentionally stopped or terminated in any other way, it must be restarted to
enable the export functionality of the application.

• • • • • •
Note: Before running the Distributor you must ensure that there is enough disk
space for the intermediate storage of the export job output for SEG-Y to
FTP kind of jobs. In this case, although the export is being transferred by
FTP to a different location, the output SEG-Y files will be temporarily saved
in the scratch directory.

 To Start the Distributor

1 Log on to the ProSource Seismic server using proper account (for example
ProSource Seismic installer/admin account).

• • • • • •
Note: A proper OS account must be used for launching the distributor daemon.
Although it is recommended to use the ProSource installation owner’s
account, it is not mandatory as long as the account is a member of the
same group. The distributor process must be run by an account that:
• is a valid GeoFrame or OpenWorks account that has write access to all
IESX, Charisma, or SeisWorks projects to be used as destinations for
seismic data transfers.
• is registered as OpenSpirit account.
• has read/execute permissions for ProSource directory structure
(usually is a member of ProSource application group).
Refer to “System Requirements” on page 9-3 for more details.

2 Start the ProSource Seismic Application Launcher, if it is not already open

on your desktop.
3 Launch an xterm window.

• • • • • •
Note: The Distributor will fail to start, if the configuration table has not been
populated. In each newly created project the table is empty. It is
automatically populated when the Scan/Edit/Load is run for the first

13-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Starting and Stopping

time. Before starting distributor for a project first time, please make sure
that the configuration table has been populated. For more details please
refer to “Configuration Table”.

4 Start the Distributor for the ProSource Seismic database project account by
running the following command from the xterm window:
% $SEISMAN_HOME/scripts/start_distributor.sh -u <project>
-p <password>

• • • • • •
Note: If you enter the script without any parameters, the script will prompt you
for an account name and password.

After an export job has been processed, the Distributor log file will be written
to the <ProSource External Directory>/logs/pss/distributor
directory.
In addition a directory for the export job log will be created. For more
information on the job log directory and job log file refer to “Job Log File” on
page 9-26.

• • • • • •
Note: You should run only one distributor per project. If the distributor was
stopped from ProSource tree by changing its status, the
start_distributor.sh script will restart the distributor, only if the
status is changed back from STOP to RUN.

• • • • • •
Note: If OpenSpirit is not installed, start the distributor by running the following
command:
% $SEISMAN_HOME/scripts/start_distributor.sh -u
<project> -p <password> -o N

Stopping The Distributor can be stopped from ProSource Seismic tree or command line.
Distributor from
ProSource

 To Stop the Distribution from ProSource Seismic Tree

1 Log on to ProSource with an account that has appropriate administrative
privileges (SEISMIC_MANAGER_ADMIN role granted).
2 Expand the Distributor configuration node by selecting System
Info>Distributor Configuration from the ProSource Seismic tree.
3 Select the Distributor Configuration record (row1) in the tree view. The
configuration information automatically displays in the row view.
4 Click Edit.

Distributor 13-5
Schlumberger Private - Customer Use
Starting and Stopping

5 Change the Status attribute to STOP and then click another field to remove the
focus from the Status attribute. The attribute will then display red and Save
icon will be active.
6 Click Save. If the Distributor is processing an export job, it will stop after the
job is complete.

• • • • • •
Note: Depending on the value of the Status polling interval field in the
Distributor Configuration record, it may take some time for the
distributor process to stop. For additional information about the
Distributor Configuration table, see “Configuring” on page 13-7.

Stopping Complete the following steps to stop the distributor from a command line.
Distributor from
Command Line

 To Stop the Distributor from a Command Line

1 Log on to the machine where the Distributor is running with an account, which
was used to start the distributor or with root account.
2 Find out the process ID of the Distributor.
% ps -ef | grep distributor
3 Use Linux kill command to stop the distributor:
% kill < process ID of the Distributor >

13-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring

Configuring

Configuration Configuration parameters of the Distributor are managed using the Distributor
Table configuration node in ProSource Seismic database.
The configuration parameters can be viewed from the ProSource interface as
follows:

 To View the Configuration Parameters

1 Navigate to the ProSource Seismic>System Info node in ProSource tree.
2 Expand the Distributor configuration node.
3 Select the distributor configuration record (row1) in the tree view. The
configuration information automatically displays in the row view.

• • • • • •
Note: In each newly created project the table is empty. It is automatically
populated when the Scan/Edit/Load is run for the first time.

Distributor Log File The distributor log is written to the file specified by the Log File attribute in the
Name and Location configuration record. If no directory is specified by the attribute, the log file will be
written to the <ProSource External Directory>/logs/pss/distributor
directory.
By default, the log file is named distributor_<host name>_<project
name>.log.<#>, where
• Distributor is the default file name prefix. This can be changed, if required, by
specifying another value for the Log File parameter. For example if the value is
myfile.log, then the file name prefix will be myfile.
• Host name is the name of the machine the distributor is running on
• Project name is the name of the ProSource Seismic (Seabed) project, the
distributor is running against
• <#> is the sequential number (i.e. 0,1,2,3, … etc.). Each time the daemon is
started, the current log file will be marked with 0, the previous log file – with 1,
the one before – with 2 and so on. Maximum number of log files to keep is
defined by the Log maximum number parameter.
You can define name and directory location for the distributor log file by editing the
Log file parameter in the Distributor configuration view using ProSource. For
example:
• If the Log file parameter value is set to /home/amb/distributor.log, the
log file is saved to /home/amb/directory.
• If the Log file parameter specifies just a log file name without a directory path,
the log file will be saved to the default directory as described above.

Distributor 13-7
Schlumberger Private - Customer Use
Configuring

Message Level You may define the message level for the distributor log by editing the Log level
parameter in the Distributor configuration record using ProSource. The allowed
values are listed in the following table:
Table 13-1Log level parameter values

Value Description

OFF turn off logging

SEVERE report failures

WARNING report potential problems

INFO report informational messages

CONFIG report static configuration messages

FINE report tracing information

FINER report detailed tracing information

FINEST report highly detailed tracing information

ALL report all messages

The log becomes progressively more detailed from OFF to ALL.

List of Full list of the distributor configuration parameters is represented in the below table:
Configuration
Table 13-2Distributor configuration parameters
Parameters

Parameter Description Default Value

Job polling interval Time interval in 60000

milliseconds for
distributor to poll
database for new jobs

Job status polling Time interval in 60000

interval milliseconds for
distributor to poll
database for job status
updates

Key attribute Key attribute of job Id

records

Log file Log file name and path distributor.log

(see Distributor Log
File Name and
Location above for
more info)

Log format Format of the log file TEXT

13-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Configuring

Parameter Description Default Value

Log level Level of logging details INFO

(see Message Level
above for more info)

Log maximum number Max number of old log 5

files to keep

Log maximum size Maximum size of the log 50000000

file in bytes

Maximum idle time Maximum time in 60000

milliseconds the
distributor can be idle

Maximum threads in Maximum number of 2

pool jobs in the pool

Minimum threads in pool Minimum number of 1

jobs in the pool

Polled attribute Attribute used by Status

distributor to identify
new jobs

Polled coral entity Table/view used by Export_Job

distributor to poll for
new jobs

Status Current status of RUN

distributor

Status after completion Job status set after FINISHED

completion

Status after failure Job status set after FAILED

failure

Status after polling Job status set after it is READ BY DAEMON

polled by the daemon

Status for polling Job status used by SUBMITTED

distributor to identify
new jobs

Status if cancelled Job status set if the job CANCELLED

was canceled by user

Time interval in 60000

Status polling interval milliseconds for
distributor to poll
database for its status
(Status parameter)

Distributor 13-9
Schlumberger Private - Customer Use
Configuring

Parameter Description Default Value

Status when executing Job status set when the IN PROGRESS

job is sent to the
appropriate exporter

Type attribute Attribute specifying the Export_Type

job type

13-10 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 14 OpenSpirit

In This Chapter

Introduction ........................................................................................14-2
Master Configuration ...........................................................................14-2
Master/Satellite Configuration...............................................................14-3
OpenSpirit Services..............................................................................14-3
Configuring Secondary User Accounts ...................................................14-4
Creating managed SEG-Y DataSource....................................................14-4
Preservation of Original Access Dates....................................................14-4
Validating OpenSpirit's Access to Data Sources ......................................14-5
Validating ProSource Seismic’s Access to Data Sources ...........................14-6

OpenSpirit 14-1
Schlumberger Private - Customer Use
Introduction OpenSpirit must be configured to enable the following workflows in ProSource
Seismic:
• Project scan – scanning interpretation projects (IESX, Charisma, Seisworks),
extracting and storing metadata in ProSource.
• Project export – exporting seismic data from ProSource Seismic to the
interpretation projects (IESX, Charisma, Seisworks), from the interpretation
projects to files, and transferring data between the projects.
Before being able to run OpenSpirit related workflows, configuration and testing of
OpenSpirit needs to be carried out, including data source definition, user
configuration, etc.
Once OpenSpirit has been properly installed and set up, ProSource Seismic can be
configured for OpenSpirit via the IM Administration Console by entering the required
parameters.
OpenSpirit can be set up and configured in different ways, as it supports master and
master-satellite configurations. Both scenarios are described below.

Master If you can access IESX/Charisma and/or SeisWorks projects from the OpenSpirit
Configuration host machine using same Linux account that you use to run the distributor and
ProSource server, then you do not need to deploy a master-satellite configuration.
If this is the case, this usually implies that:
• The OS platform is the same for the OpenSpirit and GeoFrame and/or OpenWorks
host.
• GeoFrame and/or OpenWorks home directory is visible from the OpenSpirit host.
• GeoFrame and/or OpenWorks bulk data directory is visible from the OpenSpirit
host and the user account has read/write access to it.
• The OS user account is a valid account with proper access rights/permissions for
GeoFrame and/or OpenWorks.
If the above conditions are met, please continue reading the comments below on
configuring an OpenSpirit Master only; otherwise, see “Master/Satellite
Configuration” on page 14-3.
For information on configuring different types of data sources with OpenSpirit
master instance, please refer to the OpenSpirit documentation.

• • • • • •
Note:

• If ProSource and OpenSpirit are installed on different hosts, both hosts should be
running appropriate version of operating system.
• If OpenSpirit master is installed on a different host, the directory referred by the
$OSP_HOME needs to be visible/accessible from the ProSource server host.
• Make sure you provide the correct information while configuring your data
sources(s). You can obtain the correct information from a GeoFrame/OpenWorks
xterm by showing environment variable values.

14-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 • You can use GF_PUBLIC account as OpenSpirit query account, but you need to
know the password.
• Directories referred by $GF_PATH, $ORACLE_HOME and $TNS_ADMIN need to
be visible from the OpenSpirit master server.
• If OpenSpirit satellite configuration is not required, you can skip the next section
and refer “Creating managed SEG-Y DataSource” on page 14-4.

Master/Satellite The Master/Satellite configuration would be deployed in the following scenarios:

Configuration
• OpenSpirit Master is installed on a server other than the GeoFrame and/or
OpenWorks host.
• If the GeoFrame or OpenWorks host are only visible via the network (no shared
file system).
The OpenSpirit satellite can be installed with any Linux user account on the machine
where GeoFrame/OpenWorks applications are installed, and the account should
have access to projects of GeoFrame/OpenWorks.
The satellite installation points to the master installation, so connectivity to the
master installation is imperative. Once the satellite instance has been successfully
installed the data sources can be configured for GeoFrame and/or OpenWorks.
For information on configuring a satellite installation please refer to OpenSpirit
documentation.

• • • • • •
Note: Make sure you provide the correct information while configuring your data
source(s). You can obtain the correct information from the OpenSpirit
desktop interface launched on the OpenSpirit master server, if you have
already configured the data source(s) with the master installation or from
a GeoFrame/OpenWorks xterm by showing environment variable values.

OpenSpirit Services Examples of commands to start, stop and check status of OpenSpirit services are
given in the table below. For more information please refer to the OpenSpirit
documentation.
Table 14-3 Commands to start/stop OpenSpirit services

Operation Command
Start OpenSpirit $OPENSPIRIT_HOME/bin/runOSServices.sh start
services if those are
not already running
Check OpenSpirit $OPENSPIRIT_HOME/bin/runOSServices.sh status
services status
Stop OpenSpirit $OPENSPIRIT_HOME/bin/runOSServices.sh stop
services

OpenSpirit 14-3
Schlumberger Private - Customer Use
 • • • • • •
Note: By default all data connectors will be launched on the host which is
running OpenSpirit. However, with a satellite installation the data
connectors associated with the data sources on the satellite must be
started on the satellite machine.

Configuring When you execute project-export workflows, the ProSource client (Seismic Export
Secondary User Order Wizard, to be more exact) needs to obtain information about target projects
Accounts available for selected data source. That information is ultimately obtained from
OpenSpirit server.
All user accounts to be used to run project-export workflows have to be configured
with OpenSpirit. For information on configuring primary and secondary user
accounts refer OpenSpirit documentation.

Creating managed A managed SEG-Y data source is normally a designated directory accessible for
SEG-Y DataSource OpenSpirit and ProSource processes. However it needs to be configured as a data
source in OpenSpirit. Please refer OpenSpirit documentation for instructions.

• • • • • •
Note: Once you use IM Administration Console to configure OpenSpirit
parameters for ProSource the $SEISMAN_HOME/scripts/
seismic_manager.dat file is automatically updated with the
MSEGY_DATASTORE_NAME and MSEGY_DATASTORE_DIRECTORY. Make
sure the MSEGY_DATASTORE_DIRECTORY directory is accessible for read-
write operations for OpenSpirit and ProSource processes. In other words
accounts used to start OpenSpirit and ProSource processes have read-
write permissions on the directory.

Preservation of If you are scanning a project and want to preserve the timestamps of the project
Original Access seismic files (files in the IESX, SeisWorks, or Charisma projects), do the following:
Dates

 To Configure ProSource Seismic to Preserve Timestamps

1 Log in as root on the ProSource server.
2 Change directory to $SEISMAN_HOME/bin directory.
3 Set the file owner to root for restoreinode and restoretime.
root# chown root restoreinode
root# chown root restoretime
4 Set the suid and sgid bits for these files. For example:
root# chmod u+s restoreinode

14-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 root# chmod g+s restoreinode
root# chmod u+s restoretime
root# chmod g+s restoretime
5 Verify in the project_scan.properties file (user home directory/.seisman) that
the following attributes are set as noted below:
• PRESERVE_TIMESTAMPS - Set this to TRUE.
• TIMESTAMP_TEMP_PATH - Set this to a path where temporary files are
to be created.

• • • • • •
Note: You may want to create a special directory for this so that if your scan job
fails, you can delete all the files from this directory. The files are
automatically deleted when the scan job is successful.

• • • • • •
Note: More information about the project_scan.properties file can be found in
the ProSource Seismic Administration Guide.

Validating Before you begin using ProSource Seismic workflows, it is highly recommended that
OpenSpirit's Access you test your access to the OpenWorks or GeoFrame projects through OpenSpirit.
to Data Sources The following workflow validates the access to GeoFrame Datasource using
OpenSpirit.

 To Validate Access to GeoFrame from OpenSpirit

1 Launch OpenSpirit by typing this command:
$OPENSPIRIT_HOME/bin/openspirit.
The OpenSpirit Launcher dialog box opens.
2 Select View > Session Manager to expand the dialog box.
The expanded OpenSpirit Launcher dialog box opens.
3 Select the Sessions tab and click Create to create a new session.
The Session General Properties dialog box opens.
4 Enter the Name and Description, and click Next.
The Session Project dialog box opens. The left side lists of all the available
projects from your previously created datastore.
5 Select all the desired projects from left side and click the right blue arrow to
move the projects to the Session Contents pane and click Next.
The Project Password dialog box opens.

• • • • • •
Note: Make sure you choose a GeoFrame project that contains Seismic Data (2D
and 3D).

OpenSpirit 14-5
Schlumberger Private - Customer Use
 6 Enter the correct password for the project and click Next.
The Project Units dialog box opens.
7 Select your preferable unit system and click Next.
The Coordinate System dialog box opens.
8 Click Select to choose the preferred Coordinate System from the projects and
click Next.

• • • • • •
Note: OpenSpirit will try to start the Datasource server. If you receive an error
message, go to the OpenSpirit log directory and view the log file for the
GeoFrame project that you are accessing. For example,
$OPENSPIRIT_HOME/logs/UserServers/install
install_GF4_GeoFrame_1_cloudspin.log.

9 When the final session wizard opens, click Finish.

10 Navigate to OpenSpirit Launcher and choose the newly created session.
11 Select Tools > DataSelector/CopyManager.
The Data Selector dialog box opens.
12 If the datastore is started, it should show the datastore information. If you
cannot view any data, click Refresh.
13 Navigate to Data Selector and see if you have access to Seismic Data. For
example, 3D Survey.
If you can see all the seismic information from your GeoFrame project, then the
OSP Datastore configuration is properly configured.

Validating To validate access to the GeoFrame or OpenWorks data sources, you will need to:
ProSource
• Use the Project Scan Utility
Seismic’s Access to
Data Sources • View scanned projects
• Export scanned projects

 To Use the Project Scan Utility

1 Connect to the ProSource server and start the launcher:
$SEISMAN_HOME/scripts/standalone_launcher.csh.
The Launcher interface opens.
2 Click Project Scan.
The Project Scan interface opens.
3 Select a data source in the Source Datastore drop down list.
4 Click Connect.
The Set Target Database Connection dialog box opens.
5 Enter the correct values and click OK.

14-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 You are returned back to the Project Scan Utility interface.
6 For Projects, select the Selected Projects option and click Select.
The Select DataSource Projects dialog box opens.
7 Select one or more projects to scan and click OK.

• • • • • •
Note: Make sure the project has seismic 2D and 3D data.

You are returned back to the Project Scan Utility interface.

8 Click Run to start the scan process. Log window opens.
9 Check the log for any errors and close the log window.
You are returned back to the Project Scan Utility interface.
10 Select the 3D Seismic Tab.
11 Click LiveTrace Coverage and then Selected Volumes.
12 If there are no errors, click Select to see the generated live traces. Choose
some and click OK.
13 Select the 2D Seismic Tab.
14 Click Live Trace Coverage and then Selected Datasets.
15 If there are no errors, click Select to see the generated live traces. Choose
some and click OK.

• • • • • •
Note: Since you performed a full scan, you should see some 3D volumes and 2D
datasets. If the data is not visible, check the scan log file.

 To View Scanned Projects

1 Open the ProSource application.
2 Go to the Seismic Tree and connect to the Seismic Project.
3 Select the project you scanned as per above steps.
4 Browse the project and check for the same Seismic information from “To
Validate Access to GeoFrame from OpenSpirit” on page 14-5.

 To Export SEG-Y to Project, Project to SEG-Y, and Project to

Project
1 Open the ProSource application.
2 Go to the Seismic Tree and connect to the Seismic Project.
3 Select one of the scanned projects.
4 Select some 2D lines, right click and Send To > Seismic Selector.
The Seismic Selector dialog box opens.

OpenSpirit 14-7
Schlumberger Private - Customer Use
 5 Click Export Seismic.
The Seismic Export Order Wizard opens.
6 Specify the recipient and click Next.
The Seismic Export Order Output Destination dialog box opens.
7 Select IESX for the Output Destination and click Next.
The Seismic Exporter Order Wizard Choose Project dialog box opens.
8 Choose the destination project, provide the password, and click on Next.
The Seismic Exporter Order Wizard Amplitude Clipping dialog box
opens.
9 Click Finish.
The Seismic Exporter Order Wizard Export Job Summary dialog box
opens.
Check the summary and click Submit.

• • • • • •
Note: For the export job to run, the distributor must be started for the ProSource
(Seabed) project. For details on managing the distributor, please refer to
Chapter 12, “Distributor,” in the ProSource Seismic Administration Guide.

10 Check the Job status from the ProSource Tree by selecting Seismic > Export
Jobs > Export Jobs.
11 Check the distributor logs in case of any error on job status.

14-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 15 Command Line Utilities

In This Chapter

Generating RODE Image of Original Tape ....................................................15-2

Extracting Data from RODE File ..................................................................15-3
Extracting SEG-Y Data..........................................................................15-3
Extracting SEG-A/B/C Data ...................................................................15-3
Extracting Navigation from SEG-Y File .........................................................15-5
Mandatory Arguments..........................................................................15-5
Optional Arguments.............................................................................15-5
Extracting Trace Headers from SEG-Y File....................................................15-7
Mandatory Arguments..........................................................................15-7
Optional Arguments.............................................................................15-7

Command Line Utilities 15-1

Schlumberger Private - Customer Use
Generating RODE Image of Original Tape

Generating RODE Image of Original Tape

The seismic_loader executable can be run in standalone mode to read pre-stack
field format data from a tape (SEG-A, SEG-B, SEG-C and SEG-D) and generate a
RODE encapsulated disk image of the original tape. In standalone mode no
database is required.
To run the seismic_loader executable in standalone mode the
seismic_loader.csh script should be used. The script is located in $SEISMAN_HOME/
scripts directory.

 To run seismic_loader executable in Standalone Mode from a

Command Line
1 Open xterm window from the ProSource Seismic Standalone Launcher.
Environment variable SEISMAN_HOME will automatically be set for the window.
2 If you are logged in to the ProSource Seismic server from another machine,
make sure that the DISPLAY environment variable is set properly. Set the
variable, if required. For example:
% setenv DISPLAY <hostname>:0.0
3 Review the command line options and run the following command:
seismic_loader.csh <input tape device> <SEG format>
<output file/directory> [-multiinput]
where,
• <input tape device> is the address of the input tape drive.
• <SEG format> must be one of the following: SEG-Y/SEG-A/SEG-B/SEG-C/
SEG-D/UNKNOWN. The input format is case sensitive.
• <output file/directory> is the output file name in case of a single file
output or a directory path where output files will be created in case of
multiple file output.

• • • • • •
Note: For a SEG-Y tape, output file(s) will be in SEG-Y format. For a tape in any
other format the output file will be RODE encapsulated.

• [-multiinput] is an optional parameter. When it is specified, all RODE

files separated by double EOF will be read from the tape and written to the
output.
For example (assuming that the executable is run from its location):
% ./seismic_loader.csh /dev/nst0 SEG-C /home/sc/dmc48/
rode/myfile1.rode
You may want to run the command without any options in order to see help
message on the usage of the command line options:
% seismic_loader.csh

15-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Extracting Data from RODE File

Extracting Data from RODE File

The Record Oriented Data Encapsulation (RODE) format was approved by the
Society of Exploration Geophysicists and provides a technical standard for
encapsulating digital exploration data. RODE files may contain encapsulated SEG-Y
or other SEG format trace data. If RODE encapsulated SEG-Y files have to be
imported into the ProSource Seismic database they must first be extracted from the
RODE file where they are archived.

Extracting SEG-Y Complete the following steps to extract SEG-Y data from a RODE file and write it to
Data disk.

 To Extract SEG-Y Data from a RODE File and Write it to Disk

1 Open xterm window from the ProSource Seismic Standalone Launcher.
Environment variable SEISMAN_HOME will automatically be set for the window.
2 Run the RODE-to-SEG-Y script as follows:
seismic_rodeutil.csh <input-rode-file> SEG-Y <output-segy-
file-prefix>
For example (assumed that the script is run from its location):
%./seismic_rodeutil.csh /home/sc/dmc48/rode/myfile1.rode
SEG-Y /tmp/file_
The script will extract SEG-Y file(s) from the RODE file. If the RODE file contains
multiple SEG-Y files, all the files will be extracted. It is not possible to extract
multiple files to a single output file. Each file will start with the prefix ‘file_’ and
will be created in the /tmp directory.

• • • • • •
Note: The seismic_rodeutil.csh script is installed in the
$SEISMAN_HOME/scripts directory by default. Running the script
without any parameters will show help on the script.

For additional information about the RODE format, see SEG RODE Format
Record Oriented Data Encapsulation, published by the Society of Exploration
Geophysicists.

Extracting SEG-A/ Complete the following steps to extract SEG-A/B/C/D data from a RODE file and
B/C Data write it to tape or disk.

 To Extract SEG-A/B/C/D Data from a RODE File and Write it to Tape or

Disk
1 Open xterm window from the ProSource Seismic Standalone Launcher.
Environment variable SEISMAN_HOME will automatically be set for the window.
2 Run the RODE-to-SEG script as follows:
seismic_rodeutil.csh <input-rode-file> SEG-D <tape-device>

Command Line Utilities 15-3

Schlumberger Private - Customer Use
Extracting Data from RODE File

For example (assumed that the script is run from its location):
%./seismic_rodeutil.csh /home/sc/dmc48/rode/myfile1.rode
SEG-D /dev/nst0
The command will extract all SEG-D field files from the RODE file and write the
extracted files to a local tape device called /dev/nst0.

• • • • • •
Note: The tape device should be specified as a non-rewinding device.

The following command will extract a range of SEG-D field files from the RODE
file and write the user-specified range of field files to a local tape device called
/dev/nst0. The field files output will be in the range 101 to 200.
%./seismic_rodeutil.csh /home/sc/dmc48/rode/myfile1.rode
SEG-D /dev/nst0 101 200

• • • • • •
Note: The tape device should be specified as a non-rewinding device.

The following command will extract a range of SEG-D field files from the RODE
file and write the user-specified range of field files to a new RODE file called
/tmp/my_rode_file.rode. The field files output will be in the range 101 to
200.
%./seismic_rodeutil.csh /home/sc/dmc48/rode/myfile1.rode
SEG-D /tmp/my_rode_file.rode 101 200

• • • • • •
Note: The seismic_rodeutil.csh script is installed in the
$SEISMAN_HOME/scripts directory by default. Running the script
without any parameters will show help on the script.

For additional information about the RODE format, see SEG RODE Format
Record Oriented Data Encapsulation, published by the Society of Exploration
Geophysicists.

15-4 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Extracting Navigation from SEG-Y File

Extracting Navigation from SEG-Y File

ProSource Seismic includes a utility that allows you to scan a SEG-Y disk file/tape,
extract navigation from the headers and save it in a UKOOA P1/90 file.

 To Scan a SEG-Y Disk File and Generate a UKOOA P1/90 Disk File
1 Create desired SEG-Y template or pick an existing one. For more details See
“Template File” on page 4-4.
2 Run the seismic_scanutil.csh script with the following options (the
options are described in details further below):
• file (for example /tmp/cloudspin-3D.sgy)
• template (for example /tmp/DEFAULT_TRACE.sgyfmt)
• out (for example /tmp/cloudspin-3D.p190)
• size (for example -1)
• dimension (for example 3)
• program (segy2ukooa)
Sample call (assumed that the script is run from its location):
%./seismic_scanutil.csh –file /tmp/cloudspin-3D.sgy -
template /tmp/DEFAULT_TRACE.sgyfmt -out /tmp/cloudspin-
3D.p190 -program segy2ukooa

• • • • • •
Note: The -program segy2ukooa option should be the last option specified
for the command.

Mandatory The following are mandatory command line options:

Arguments
• -file <input_file> is the complete pathname to the input SEG-Y file.
• -template <SEGY_Template_file> is the complete pathname to the input SEG-Y
template file (required to extract Line/Shot/X/Y information).
• -out <output_file> is the complete pathname to the output UKOOA P1/90 file.

Optional The following are optional command line options:

Arguments
• -metric <yes/no> - specifies if X/Y coordinates are metric or non-metric (default
is yes, if not specified).
• -disk <yes/no> - specifies if input seismic file is on disk (default is yes, if not
specified).
• -z <SEG-Y> - input seismic format (default is 'SEG-Y', if not specified).
• -number <n> - tape file number (Required when input is tape. Default is 1, if not
specified).

Command Line Utilities 15-5

Schlumberger Private - Customer Use
Extracting Navigation from SEG-Y File

• -size <n> - specifies the number of traces to scan (default is -1 i.e. all traces, if
not specified).
• -dimension <2/3> - specifies the type of seismic data represented in the file 2D or
3D (default is 2D, if not specified).

• • • • • •
Note: The seismic_scanutil.csh script is installed in the
$SEISMAN_HOME/scripts directory by default. Running the script
without any parameters will show help on the script.

15-6 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 Extracting Trace Headers from SEG-Y File

Extracting Trace Headers from SEG-Y File

 To Scan a SEG-Y Disk File and Generate a SEG-Y Disk File Containing
Just the Trace Headers (No Trace Data)
1 Create desired SEG-Y template or pick an existing one. For more details See
“Template File” on page 4-4.
2 Run the seismic_scanutil.csh script with the following options (the
options are described in details further below):
• file (for example /tmp/cloudspin-3D.sgy)
• template (for example /tmp/DEFAULT_TRACE.sgyfmt)
• out (for example /tmp/cloudspin-3D_hdr_only.sgy)
• program (segy2truncate)
Sample call (assumed that the script is run from its location):
%./seismic_scanutil.csh -file /tmp/cloudspin-3D.sgy -
template /tmp/DEFAULT_TRACE.sgyfmt -out /tmp/cloudspin-
3D_hdr_only.sgy -program segy2truncate

• • • • • •
Note: The -program segy2truncate option should be the last option
specified for the command.

Mandatory The following are mandatory command line options:

Arguments
• -file <input_file> is the complete pathname to the input SEG-Y file.
• -template <SEGY_Template_file> is the complete pathname to the input SEG-Y
template file (required to extract header information).
• -out <output_file> is the complete pathname to the output SEG-Y file.

Optional The following are optional command line options:

Arguments
• -disk <yes/no> - specifies if input seismic file is on disk (default is yes, if not
specified).
• -z <SEG-Y> - input seismic format (default is 'SEG-Y', if not specified).
• -number <n> - tape file number (Required when input is tape. Default is 1, if not
specified).
• -size <n> - specifies the number of traces to scan (default is -1 i.e. all traces, if
not specified).
• -dimension <2/3> - specifies the type of seismic data represented in the file 2D or
3D (default is 2D, if not specified).

Command Line Utilities 15-7

Schlumberger Private - Customer Use
Extracting Trace Headers from SEG-Y File

• • • • • •
Note: The seismic_scanutil.csh script is installed in the
$SEISMAN_HOME/scripts directory by default. Running the script
without any parameters will show help on the script.

15-8 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 16 Troubleshooting

In This Chapter

Introduction ..............................................................................................16-2
KDE Desktop .......................................................................................16-2

Troubleshooting 16-1
Schlumberger Private - Customer Use
Introduction

Introduction
This section provides information on the known issues you may encounter using
ProSource Seismic and solutions/workarounds for the issues.

KDE Desktop When attempting to launch ProSource Seismic utilities (such as Scan/Edit/Load or
Navigation Load), you may receive the following error message:
“Application Failed to initialize - Panel select files NULL
Pointer exception.”
The problem causing this error message can be resolved by performing the following
steps:
1 In the xterm where you attempted to start the Standalone Launcher utility,
perform the following command:
%env | grep -i gnome
This command will list only those environment variables set in your xterm,
which have name and/or value containing the text string ‘gnome’ no matter in
upper or in lower case.
Gnome is a desktop environment, a graphical user interface that sits on top of
the Linux operating system.
Output from the above command may look like the following:
GNOME_KERRING_SOCKET=<some_value>
GNOME_DESKTOP_SESSION_ID=<some_value>
GNOME_COLORTERM=<some_value>
2 Unset any Gnom-related environment variables using unsetenv command. For
example:
%unsetenv GNOME_DESKTOP_SESSION_ID
%unsetenv GNOME_COLORTERM
%unsetenv GNOME_KERRING_SOCKET
3 Repeat step 1 to ensure that you have unset all Gnom-related environment
variables.
4 From the xterm re-execute the standalone_launcher.csh script.

16-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use
 A seismic_loader.properties

Example An example of the seismic_loader.properties file is given below:

########################################################
# Bitmap storage property
# DATABASE -Store the bitmap in database as a blob
# This is the default value.
# FILE -Store the bitmap in file
########################################################
BITMAP_STORAGE=DATABASE
########################################################
# Folder selection property
# MANUAL -The Output directory selection will be
# through a file chooser.
# ARCHIVE -The Output folder selection will be
# from archive folder list.
# This is the default value.
########################################################
OUTPUTFOLDER_SELECTION=ARCHIVE

########################################################
# Duplicate Offset property
# ENABLE -Show the SP equals CDP checkbox
# DISABLE -Do not show the checkbox.
# This is the default value.
########################################################
DUPLICATE_OFFSET=DISABLE

########################################################
# Messaging property
# DEBUG -Show all the log messages.
# YES -Show error, warning, progress and info messages.
# NO -Show only error and information messages.
# This is the default value.
########################################################
ALLOW_MESSAGING=NO

seismic_loader.properties A-1

Schlumberger Private - Customer Use

A-2 ProSource Seismic Administration Guide

Schlumberger Private - Customer Use