Skip to content

Common Reflection Element (CRE) Gather stacking and interpolation using adaptative pretitive error filters (PEF) and Very Fast Simulated Annealing (VFSA) global optimization

License

Notifications You must be signed in to change notification settings

Dirack/creGatherStack

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Common Reflection Element (CRE) Stack

This package uses Pretictive Adaptative Error Filters (PEF) interpolation and Very Fast Simulated Aneeling (VFSA) global optimization.

Developed to Madagascar package, version 3.0.

Github release License: GPL v3 Madagascar Build Status

Interpolated CRE Gather

This an example of a CRE stacked section.

This is a package with several C programs and SConstructs adapted to the Madagascar seismic processing package. The mains objective of those programs is to obtain the zero offset section using CRE stacking. The main advantage of the CRE stacking is that allows to get the macrovelocity model and stacked section without the NMO velocity analisys. And it can be used in a velocity inversion process, such as tomography algorithms, in order to get the depth velocity model.

The CRE stack process is done defining the seismic traces that belong to the CRE trajectories in a seismic data cube (seismic data organized in CMP x Offset X Time coordinates) for each (m0, t0) pairs in the stacked section. The set of seismic traces that belong to a CRE trajectory form a CRE Gather. The stacking throughout this CRE gathers using the CRE traveltime approximation and the assignment of this amplitude summation to the (m0,t0) pairs in the stacked section is the core of the CRE stacking process.

Interpolated CRE Gather

This is an example of a CRE gather and the CRE stacking curve (in yellow).

CRE stack uses Very Fast Simulated Anneling (VFSA) global optimization

As explained above, a set of seismic traces that belong to a specific CRE trajectory form a CRE Gather. Those trajectories are defined for each (m0,t0) pairs in the stacked section and for a given RNIP and BETA parameters from the zero offset Common Reflection Surface (CRS) process. These parameters are extracted from the seismic data cube using Very Fast Simulated Anneling (VFSA) global optimization algorithm.

For more details about VFSA, please look at the VFSA package repository

CRE stack uses Predictive Adaptative Error Filters (PEF) interpolation:

CRE stack also needs increased CMP data sampling through Predictive Adaptative Error Filters (PEF) interpolation. This happen because the CRE traveltime aproximation is derived from geometric considerations in a constant velocity model in the neighborhood of a normal ray and the sources (s_i) and receivers (r_i) in this geometry are distributed assimetrically along the aquisition surface because of the reflector's curvature. Besides that, the reflection rays in the CRE gather have the same reflection point and are associated with the same normal ray defined by RNIP and BETA parameters (look at the Figure bellow, an schematic representation of a CRE gather geometry).

Development setup

  • Madagascar package (3.0)

  • VFSA package (1.1.1)

You need to have the actual Madagascar package stable release installed on your computer. Please follow the Installing Madagascar page in the official documentation. You can install Madagascar automatically from Shell Script using program madagainstall from Shellinclude library.

You also need programs sfvfsacrsnh and sfnhcrssurf from version v1.1.1 of vfsa package. Please install them in your local version of Madagascar before using this package.

Installation

After Madagascar installing process, you need to install the programs of this repository in your local Madagascar user's directory. You can compile and install it as any other Madagascar program. Usually, Madagascar keeps the path of your local copy source files in the $RSFSRC environment variable. You can show that on a bash terminal using 'echo' command:

~$ echo "$RSFSRC"

And Madagascar will install executable files on your $RSFROOT directory. You can show that environment variable with 'echo' too:

~$ echo "$RSFROOT"

Madagascar stores user programs in $RSFSRC/user directory. So, you can create a new directory or put this repository inside that directory. In this repository, such as every user's repository in Madagascar, we have a compilation SConstruct that compile the C programs. Run 'scons' on your $RSFSRC/user/creGatherInterpolation repository to compile it:

~$ scons

And run 'scons install' in the top directory of your local Madagascar installation (the directory path in your $RSFSRC variable):

~$ sudo scons install

If you have any doubt about this process, please reffer to the Madagascar oficial documentation in Adding_new_programs_to_Madagascar

Usage example

A few motivating and useful examples of how that product can be used. For more examples and details, please refer to the Wiki.

We also have many SConstruct examples in this repository in the experiments directory

Release History and Versions

This package version is referenced in VERSION.md file, and you can see the complete release history in our wiki or in the CHANGELOG.md file.

Meta

main page

Rodolfo Dirack – @dirack[email protected]

Distributed under the GPL3 license. See LICENSE for more information.

Contributing

In order to contribute with this project you should follow the list of steps bellow, please check out "How to contribute with this project?" in our Wiki for more details.

  1. Create an issue to your request or choose an issue already defined
  2. Fork this project in https://github.com/Dirack/creGatherStack/fork
  3. Create a branch for your contribution (name it using gitflow)
  4. Do clear commit messages (a title with 50 characters and two paragraphs of text)
  5. Push your contribution to this repository
  6. Create a new Pull Request with a clear description of your contribution
Important: The commit history should be clear, with commit mesages around one or two paraghraps describing your modifications. Pull Requests with unsatisfactory commit history will be rejected.