JavaSeis Dataset Introduction11 SeisSpace Tools Reference

Other Docs
Known Problems
Search Page
JavaSeis Dataset Introduction
In traditional seismic processing systems only the rst axis of
the seismic data, the number of traces per sample, is xed.
The second axis, the number of traces per frame, is allowed
to vary, although the maximum number of traces per frame is
usually known. The third axis, the number of frames per
volume, is usually undened except in the parameterization
of imaging algorithms. The fourth and fth axes are usually
undened.
The JavaSeis framework provides a global view of a seismic
dataset. It imposes the requirement that, although the
number of axes may vary from 3 to 5, each axis must be well
dened. A well dened axis must have a known number of
elements. Knowing the number of elements along each axis
allows you to easily perform operations such as moving sets
or subsets of the data from disk to memory and back,
transposing data in distributed memory, and applying
algorithms that require known data size such as a 3-
dimensional Fourier transform. In practice the number of
elements along any axis can be padded somewhat with no ill
effects. This is useful because the exact number of elements
is not always known at every stage of processing.
JavaSeis datasets reside on disk and are designed to improve
the efciency of processing large 3D data volumes in parallel
on Linux clusters.
The SeisSpace software includes three primary processes to
create, read, write and sort JavaSeis datasets:
JavaSeis Data Input,
JavaSeis Data Output, and
JavaSeis Sortmap Create*.
JavaSeis Parallel Sort
There is also a graphical fold-map tool available from the
MB3 options menu of the Navigator which shows the extents
and population of the selected JavaSeis dataset.
There are also specialized tools to manipulate JavaSeis
datasets:
JavaSeis Dataset Introduction12 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
JavaSeis Data Match-inserts JavaSeis data into a ow
by merging frames when both datasets share the same
framework.
JavaSeis Data Combine-inserts JavaSeis data into a
ow by creating a new framework that is a superset com-
bining the input frameworks. and data.
Data Context Editor-congure or modify the framework
associated with a JavaSeis dataset.
Finally, there is a tool to scan existing ProMAX datasets and
create a JavaSeis framework, JavaSeis Framework Create.
The SeisSpace implementation of the JavaSeis input and
output routines are based on the work published on the
www.javaseis.org website.
JavaSeis datasets use a uniform description of "regular" or
"near-regular" seismic data. A dataset can be viewed as an
"N-dimensional" array where the lengths of the dimensions
of the array are known and the dimensions are uniformly
sampled. The array for a "regular" dataset is completely lled.
The array for a "near-regular" dataset has "holes" where data
are missing. A "fold-map" is available to show the dataset
population.
JavaSeis uses the generic terms "Frame", "Trace", and
"Sample" to describe a 3 dimensional "cube" of data. The term
"Volume" is used to identify a 4th dimension which is
typically a grouping of "Frames" (or ensembles). When a
dataset is created, specic trace headers are selected to be
assigned to each of these dimensions.
For example, prestack 3D CDP gathers would have 4
dimensions, and the Volume, Frame, Trace, and Sample axes
would have the names "In-Line", "X-Line", "Offset-Bin", and
"Time". 3D marine sail lines can also be viewed as a 4
dimenional array with axes "SailLine", "Station", "Channel",
and "Time". For 3D pre-stack data, 4 dimensions covers most
cases.
The Volume, Frame and Trace dimensions must be dened
by INTEGER header values. The Trace Dimension is a simple
counter as in Channels per shot, or Offsets per CDP, or
Crosslines per Inline. NOTE that the 3rd dimension
ensembles are not sorted by the Trace designation.
Typical data organizations for 3D pre-stack data include:
JavaSeis Dataset Introduction13 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
CMP gathers,
with axis names "InLine, CrossLine, Offset_bin and
Time",
SOURCE gathers,
with axis names "SailLine, Source, Channel and Time",
RECEIVER gathers,
with axis names "SailLine, RcvrLine, Source and Time"
OFFSET_BINS,
with axis names "Offset Bin, Inline, CrossLine and Time"
There is one supported data organization for post 3D post
stack data:
STACK, with axis names "InLine, X-Line, Time"
CMP-organized data
For the CMP case all the traces with the same ILINE_NO
header are gathered into a Volume. Within that Volume,
ensembles (or Frames) are made containing all the traces
with a common XLINE_NO, where there are CDP_FOLD
traces per XLINE_NO. (NOTICE that the OFFSET_BIN
designation is used as the denition of differenting the traces
in the ensemble, but the traces are not OFFSET_BIN ordered)
JavaSeis Dataset Introduction14 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
Source-organized data
For the SOURCE case, all the traces with the same S_LINE
number are gathered into a Volume. Within that Volume,
ensembles (or Frames) are made containing all traces with a
common SOURCE, where there are SHOT_FOLD traces per
SOURCE (notice that the CHAN designation is used as the
SEQ_NO
x x x x x
I
L
I
N
E
_
N
O

1
XLINE_NO
x x x x x
x x x x x
For a CMP dataset;
4th dimemson = Volume - ILINE_NO
3rd dimension = Frame - XLINE_NO
The 2nd dimension is SEQ_NO or the number of traces per CDP (maximum)
and is generally referred to by OFFSET_BIN.
4 dimensional - CMP/CDP dataset
(OFB_NO)
I
L
I
N
E
_
N
O

2
I
L
I
N
E
_
N
O

3
JavaSeis Dataset Introduction15 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
denition of differenting the traces in the ensemble, but the
traces are not CHAN ordered).
Stack-organized data
For the STACK case, ensembles (or Frames) are made
containing of all traces with a common ILINE_NO, where
there are NUM_XLINES traces per ILINE_NO (Notice that the
XLINE_NO designation is used as the denition of
SEQ_NO
x x x x x
S_LINE
SOURCE
x x x x x
x x x x x
For a SOURCE dataset;
4th dimemson = Volume - S_LINE
3rd dimension = Frame - sOURCE
The 2nd dimension is SEQ_NO or the number of traces per SHOT (maximum)
and is generally referred to by CHAN.
4 dimensional - SOURCE dataset
(CHAN)
S
_
L
I
N
E


3
S
_
L
I
N
E


2
S
_
L
I
N
E


1
JavaSeis Dataset Introduction16 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
differenting the traces in the ensemble, but the traces are not
XLINE_NO ordered).
General Usage
JavaSeis datasets rst need to have their frameworks created
and then they are populated with trace data. The dataset
axes are dened and the boundaries of those axes are set
when the dataset framework is created. Sort orders "map
les" are constructed in a separate step and saved with the
JavaSeis dataset.
ILINE_NO
XLINE_NO
For a CMP dataset;
4th dimemson = Volume (Not used)
3rd dimension = Frame - ILINE_NO
The 2nd dimension is XLINE_NO or the maximum number of CDPs per
3 dimensional - STACK dataset
x x x x x x x x x x x x x x x x x x x x x
ILINE_NO
JavaSeis Dataset Introduction17 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
JavaSeis datasets also include a second matching N-
dimensional array used to hold the trace headers.
JavaSeis Terminology
A summary of JavaSeis dataset nomenclature:
dataset - a regular or near-regular collection of seismic
traces that corresponds to a multi-dimensional array of
data samples.
axis - one of the 3, 4, or 5 dimensions of a JavaSeis
dataset.
range -start, end, increment triplets that describe the
sampling of a dataset axis.
Hypercube - A collection of Volumes
Volume - A collection of traces with something in com-
mon and has the largest stride in memory.
Volume Header - denes unique volumes in the seismic
data.
Frame - the "Primary Sort Order" equivalent of the Jav-
aSeis dataset.
Frame Header -denes unique frames (ensembles).
Trace - the number of traces to expect per 3rd dimension
ensemble of a JavaSeis dataset.
Sample - trace samples in the JavaSeis dataset. In terms
of array indexing, the Sample index is the rst Fortran
dimension, or the last 'C' dimension, and has unit stride
in memory.
regular - a data where all 4 dimensions have known
names and ranges, and all the traces exist.
near-regular - a data where all 4 dimensions have
known names and ranges, but some traces do not exist.
Internally, JavaSeis builds a set of data structures that are
used in reporting the size and state of an existing dataset to
job logs. A quick description of these values:
Dataset Axis Names - The JavaSeis names for each axis.
Dataset Axis Sizes - The dimensions or length of each
axis.
JavaSeis Dataset Introduction18 SeisSpace Tools Reference
Other Docs
Known Problems
Search Page
Axis Data Origins - Floating point value for the start of
each axis.
Axis Data Deltas - Floating point Increment between val-
ues on each axis. For a 3D CDP dataset, these values
would be the separation between InLines, CDP spacing,
offset spacing, and time sample rate, and are taken from
the 3D binning geometry.
Axis Logical Origins - Integer value for the start of each
axis. For CDP datasets, these values are set to the start-
ing ILINE_NO, XLINE_NO, SEQ_NO, and sample num-
ber.
Axis Logical Deltas - Integer value dening the separa-
tion between "Logical" values along each axis. For 3D
CDP datasets, these values would be the INLINE_NO
increment, XLINE_NO increment, SEQ_NO increment
(always 1) and sample increment (always 1).
These JavaSeis data structures are not used in the ProMAX
system, but are used by parallel JavaSeis processes (such as
regularization or time migration) to dene processing grids.
JavaSeis writes information to ProMAX primary storage and
has options as to where to write trace data in seconday
storage.
After the framework is created, any data written must have
an identical header catalog or the job will fail.