Receiver Gather File Format Rev 1 6-1
Receiver Gather File Format Rev 1 6-1
I NDUS T R I ES
Proprietary Information
7-Aug-12 Version 1.6-1
REVISION HISTORY
Rev Date Author Description
1.0 27-Jan-06 JT, MEM, WG, Initial.
SB
1.1 6-Mar-06 JGT Added epoch shot time in 2nd 32-byte shot block. Moved
shot based data from miscellaneous block to new 2nd shot
block.
1.2 30 Jun 06 JGT Added “First break analysis” as a selection regarding the
“source of final receiver information” (Trace header block
#4).
Modified “Shot status flag” (Trace header block #3) to
include “Bad – Operator specified” and “Bad – Failed T0
QC test”.
Added a new Extended Header Block #3.
Added a External Header Definition Block in the front of
all external headers that define the data contained in the
external headers.
1.3 19 Oct 06 JGT Added Clock Drift entry to Extended header #2.
1.4 09 May 07 SKB Added new Trace header extensions 7, 8 and 9 that define
the instrument test configuration parameters.
1.5 30 May 2008 SKB, MEM Increase size of all clock drift related fields to 64 bit.
Add an option to collection type to signify guard banded
collection
Split extended trace header 3 into two separate trace
header extensions, one with shot time and drift values, the
other with guard band information and the remainder of
what was previously in trace header extension 3. Added
shot preplan and final information to the external header.
Added definitions for the field variations when the data is
time sliced.
1.5-1 24 Nov 2008 MEM Document corrections and clarifications. Merged file
system hierarchy and naming conventions to this
document.
1.6 29 Nov 2011 SKB Added fields for Trace Count Within File (TH#1, Bytes
22-25), External Shot ID (TH#4, Bytes 13-16). Orientation
Matrix Version Number (TH#7, Bytes 25-28), and
Gimbaling corrections applied flag (TH#7, Bytes 29).
1.6-1 21June2012 SKB Document correction. RU Channel number in the channel
set descriptor byte 31, Trace Edit code in Trace Header
byte 12, and Sensor Type in Trace Header 1, byte 21, were
not fully documented.
ii Proprietary Information
FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
TABLE OF CONTENTS
1 PURPOSE .............................................................................................................................................. 1
2 GLOSSARY ........................................................................................................................................... 1
3 CONSTRAINTS .................................................................................................................................... 1
1 PURPOSE
The purpose of this document is to describe a custom receiver gather file format for Fairfield.
Fairfield Industries retains the right to change this document at any time and does not guarantee it to be
100% accurate, however every effort will be made to insure that it is both accurate and complete.
2 GLOSSARY
List all terms and abbreviations.
SEG Society of Exploration Geophysicists
Epoch Refers to Unix Epoch Time in micro-seconds (i.e. 00:00:00.000000 UTC on 1 January 1970)
3 CONSTRAINTS
4 RECORD FORMAT
A receiver record header is written before each remote unit gather record and will consist of a number of
General Header blocks, Channel Set Descriptor blocks, Extended Header blocks and External Header
blocks. A receiver record will contain data associated with a single remote unit and all shots associated
with a single shot line and may contain multiple shot lines. When the receiver data is written in continuous
(fixed time sliced) form, some of the fields in the header blocks will vary or simply be zeroed. These
differences will be noted. The following diagram depicts the structure of the Receiver Gather Record. It is
intended to show the order of the headers and data fields within the record. The definitions of each field
can be found in subsequent sections.
FA I R F I E L D Proprietary Information 1
INDUSTRIES
2
32 Bytes 32 Bytes 32 Bytes x n 32 Bytes x n 32 Bytes x n
7-Aug-12
Channel Set
General Header General Header Extended Header External Header
Descriptor Data
Block #1 Block #2 Block #1 - n Block #1 - n
Block #1 - n
340 Bytes 340 Bytes 340 Bytes 340 Bytes 340 Bytes 340 Bytes 340 Bytes 340 Bytes 340 Bytes
Header
Header
Header
Header
Header
Header
Header
Header
Header
Proprietary Information
Trace 1 Trace 2 Trace n Trace 1 Trace 2 Trace n Trace 1 Trace 2 Trace n
20 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes 32 Bytes
INDUSTRIES
FA I R F I E L D
Version 1.6-1
Version 1.6-1 7-Aug-12
The first 128 bytes of data on a tape consists of ASCII characters and constitutes a storage unit label.
The following notes are included to clarify the use of some of the above fields.
• The Storage unit sequence number (bytes 1-4) is a unique integer that indicated
the order in which the current storage unit was written from the source data set.
• The Serial number field (bytes 51-62) contains what is commonly referred to as
the reel number.
• Bytes 69-128 collectively make up the Storage set identifier.
• The External label name (bytes 69-80) contains the user specified area string.
• The Recording entity name (bytes 81-104) is made up of three fields; crew
number, recording system ID, and job name (i.e. “108,0,DeepWaterJob”).
FA I R F I E L D Proprietary Information 3
INDUSTRIES
7-Aug-12 Version 1.6-1
Modifications from the standard Fairfield SEG-D Rev. 2 format are depicted in red.
There are two general header blocks that describe the data that is contained in each receiver record file.
1-2 2 BCD File number (0-9999). Set to FFFF when the file
number is greater than 9999. The expanded file
number is contained in bytes 1-3 of General
Header Block #2.
11 1 BCD 1st shot point or time slice last two digits of year
12-13 1-1/2 BCD 1st shot point or time slice Julian day in year
14-16 3 BCD 1st shot point or time slice UTC time (HHMMSS)
4 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
18 1 - Undefined (0)
The channel set descriptor block follows the SEG-D Rev 2 convention. There may be multiple channel set
descriptor blocks if auxiliary data is recorded within the same file.
FA I R F I E L D Proprietary Information 5
INDUSTRIES
7-Aug-12 Version 1.6-1
11 ½ Binary Unused
6 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
This block contains information relative to all of the data contained in this file.
This block contains information relative to all of the data contained in this file.
0 – normal
1 – storage full (ran out of memory)
2 –power loss (ran out of battery life)
3 – reboot (by command)
0 – control board
1 – atomic
2 – ovenized
3 – double ovenized
4 – disciplined
FA I R F I E L D Proprietary Information 7
INDUSTRIES
7-Aug-12 Version 1.6-1
0 – not decimated
1 – decimated data
This block contains miscellaneous data related to this file. All binary data contained in this block is
unsigned.
10-13 4 Binary First shot line written to this file (set to 0 for
continuous)
14-17 4 Binary First shot point written to this file (set to 0 for
continuous)
8 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
19-22 4 Binary Last shot line written to this file (set to 0 for
continuous)
23-26 4 Binary Last shot point written to this file (set to 0 for
continuous)
This block contains decimation filter coefficients. The number of these blocks depends on the total number
of filter coefficients required as stated in the Extended Header Block #2 (bytes 23-26) above.
The first external header 32-byte block will contain information that describes the contents of the remaining
external header blocks. Below is a description of that block. All binary data contained in this block is 32-bit
unsigned.
FA I R F I E L D Proprietary Information 9
INDUSTRIES
7-Aug-12 Version 1.6-1
The remaining external header blocks contain preplan location, final location, navigation, and energy
source information relative to each shot point.
0 – Undefined
1 – preplan
2 – as shot
3 – post processed
0 – normal
1 – Bad – Operator specified
10 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
32 1 - Reserved (set to 0)
The remaining blocks for each shot will contain the external header data written in a raw manner as it was
received by the recording system. The following example depicts a typical Concept Systems navigation and
Syntron GCS90 energy source setup.
The Concept User Header 7 header description consumes the first 16 bytes, the Concept User Header 7
Hydronav data tag consumes next 176 bytes and the Concept User Header 7 GCS90 data tag consumes next
832 bytes or more depending on how many guns are used. A typical header is 2416 bytes which rounds up
to 76 32-byte headers (2432 bytes) needed to store the raw navigation headers for each shot. Please refer to
the Concept System’s User Header 7 document, which describes the format of this data.
Thus for the example headers described above, the total size of the external header data that will be
required to store all of the data associated with the shots contained in this receiver oriented file can be
calculated as follows:
Assume that we have 400 shots per line and 10 shot lines.
400 shots per line x 77 32-byte blocks per shot = 30,800 blocks per line x 10 lines = 308,000 blocks
Plus one block for the external header block descriptor = 308,001 blocks x 32 bytes = 9,856,032 bytes
A 20-byte trace header and a number of 32-byte trace header extension blocks are attached to the beginning
of each trace record.
1-2 2 BCD Tape file number (two byte, four digit, BCD).
These bytes must be set to FFFF when the
Extended File Number (bytes 18, 19 and 20) is
used.
FA I R F I E L D Proprietary Information 11
INDUSTRIES
7-Aug-12 Version 1.6-1
00 – Not defined
01 – Hydrophone
02 – Vertical geophone
03 – Inline geophone
04 – Cross-line geophone
05 – Other horizontal geophone
06 – Vertical accelerometer
07 – Inline accelerometer
08 – Cross-line accelerometer
09 – Other horizontal accelerometer
12 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
10 - Geophone, X
11 - Geophone, Y
12 - Geophone, Z
13 - Geophone, Horizontal, North
14 - Geophone, Horizontal, East
21 - AUX, Ground Force
22 - AUX, True Reference
23 - AUX, Mass Accelerometer
24 - AUX, Baseplate Accelerometer
This block defines shot location parameters. All binary data contained in this block is unsigned.
Description
Byte Number Number of Bytes Data Type
Shot Mode Continuous Mode
FA I R F I E L D Proprietary Information 13
INDUSTRIES
7-Aug-12 Version 1.6-1
Description
Byte Number Number of Bytes Data Type
Shot Mode Continuous Mode
0 – Undefined
1 – preplan
2 – as shot
3 – post processed
0 – Undefined
1 – Vibroseis
2 – Dynamite
3- Air gun
32 1 - Reserved (set to 0)
This block defines timing information associated with this shot/time slice. All binary data contained in this
block is 32-bit unsigned.
This block defines additional information associated with the data contained in this trace. All binary data
contained in this block is 32-bit unsigned.
1-4 4 Binary Pre Shot Guard Band (ms) (set to 0 for continuous)
14 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
0 – not clipped
1 – digital clip detected
2 – analog clip detected
0 – normal
1 – Bad – Operator specified
2 – Bad – Failed T0 QC test
This block defines receiver location parameters. All binary data contained in this block is 32-bit unsigned.
FA I R F I E L D Proprietary Information 15
INDUSTRIES
7-Aug-12 Version 1.6-1
1 – preplan
2 – as laid (no navigation sensor)
3 – as laid (HiPAP only)
4 – as laid (HiPAP and INS)
5 – as laid (HiPAP and DVL)
6 – as laid (HiPAP, DVL and INS)
7 – post processed (HiPAP only)
8 – post processed (HiPAP and INS)
9 – post processed (HiPAP and DVL)
10 – post processed (HiPAP, DVL and INS)
11 – first break analysis
16 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
This block begins the remote unit instrument test configuration parameters
0 = No Filter
1 = Apply Filter
FA I R F I E L D Proprietary Information 17
INDUSTRIES
7-Aug-12 Version 1.6-1
This block continues to define remote unit instrument test configuration parameters
18 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
This block continues to define remote unit instrument test configuration parameters
The following diagram depicts the organization of the Storage Unit Label and Receiver Gather Records on
Tape media.
FA I R F I E L D Proprietary Information 19
INDUSTRIES
7-Aug-12 Version 1.6-1
128 Bytes
EOF
EOF
EOF
EOF
EOF
Storage Unit Receiver Gather Receiver Gather Receiver Gather
Label Record 1 Record 2 Record n
Tape Organization
20 Proprietary Information FA I R F I E L D
INDUSTRIES
Version 1.6-1 7-Aug-12
This section defines the directory structures and file naming conventions used when the destination media
contains a file system.
Data acquired from a single receiver point can become quite large. The data output generation supports
writing the data to multiple files where each file will contain a portion of the acquired data. Entries are
made in the headers (see 32-byte Extended Header #2) that depict this (i.e. file 1 out of 2). This concept is
carried further when a file system is involved. For example, the data for receiver point 5056.0 was split into
N portions due to the total size of the data set. The file names used on the file system would be 5056.0.0
for the first portion of the data, 5056.0.1 for the second, 5056.0.2 for the third, and so on until 5056.0.N is
reached.
Each receiver point file will be organized as a Fairfield Receiver Gather file format as defined in the
FORMAT DEFINITION section of this document.
A storage label file will be created for each tape that is written to the file system. The name of these files
will be “StorageLabel_<serial#>.<index>” where the <serial#> is the Serial number field as defined in the
Storage Unit Label section and <index> is an incrementing number starting at 0 that increments for each
repeated instance of the same file name should one occur.
For example, if the Serial Number field of the Storage Label is 163, the first file for this serial number
would be “StorageUnit_163.0”, the second would be “StorageUnit_163.1”, and so on.
The data in this file will be formatted as described in the Storage Unit Label section of this document.
FA I R F I E L D Proprietary Information 21
INDUSTRIES