We are pleased to announce the release of Tsunami A2012.  This version of the Tsunami software contains new PSTM, PSDM, RAYS and SMTH modules as well as several Tsunami developed plugins for the INTViewer.  The latest versions include several new features to enhance performance as well as results.  

We would also like to take this opportunity to announce our updated website.  We hope that you find this website more clear, concise and ultimately easier to use.

PSTM                                                                                                  

A2012 version pstm_6.0

New Performance Feature

To keep the higher performance compute nodes busy, PSTM now caches seismic input traces on the compute nodes. By default it uses /tmp, however in the node list file you can specify another name for the scratch directory.

The scratch directory needs to have at least 10 G of scratch space. The PSTM application will check that it can write to the scratch directory, and that there is at least 10 G of space.  If either of these tests fail, it will abort.  The logfile will list all nodes that fail this test.

When the job checkpoints, the compute nodes must sync up at that point so, they are all on the same trace. Some nodes may go idle while this happens.

In order for the user to know when the checkpoint will occur, the software will put the trace number for the checkpoints in the logfile at the beginning of the job.

New Merge Survey Weights Parameter

Tsunami allows the use of trace weights to minimize the acquisition foot print, and to make the amplitudes more consistent in the migration output.  These trace weights are stored in the trace database (trace.db).  This new parameter allows the use of trace scaling weights from previous trace databases, so the amplitudes will match when doing a survey merge. This allows you to merge surveys without having to re-migrate the combined datasets.

When the old trace database file parameter is detected, the program will look first for traces in this file, and use those weights, before calculating new weights for new traces not in this file.  The weight from the old trace.db, is then added to the current trace.db file, so the datasets can be cascaded forward. If additional data is then added to the dataset, the current trace.db file will then become the old trace.db file, and the weights can then be reused again. 

New fields were added to the trace.db for this new functionality.  Due to this, the previous version trace.db is not compatible with pstm_6.0 and vice versa.  The trace.db will be regenerated if the program detects a trace.db generated from another version.  

This parameter can be found on the Processing Tab under Amplitude Scaling.  The parameter name is oldtrcdb and its input is the direct path to the desired old trace.db file.  There is no default value.

Floating Datum Enhancement

PSTM will now output the floating datum static in the same byte location as the static in the input data headers.  These will be placed in the output file regardless of outputting at final or floating datum.

Azimuth Update

The azimuth of the traces in the trace.db file have been changed to match the azimuth specified for HTI azimuth file, and for the TTI azimuth orientation.   The orientation is that 0 azimuth points parallel to the xlines, towards increasing inlines, and 90 azimuth points parallel to the inlines, towards increasing xlines.

Variable Velocity Fix

A bug fix was put in place to resolve a mismatch of headers in variable velocity migrations.

Balanced Offsets Fix

When using balanced offsets on very large datasets, the memory was not being released after the calculation of the offsets.  This caused the job to not have enough memory to start. 

Converted Wave Fix

The time/ frequency pairs will now be ignored when doing converted wave.  A bug caused an error message to be given in this situation.

 

 

PSDM                                                                                                           

A2012 version psdm_6.0

New Performance Feature

 

 To keep higher performance compute nodes busy, PSDM now caches travel times and seismic input traces on the compute nodes. By default it uses /tmp for the scratch directory, however in the node list file you can specify another path name for it to use.

 The software will put a small amount of travel times on the compute nodes to start the job. It will then stream seismic traces and travel times to the compute nodes continuously while the job is processing.

 It is recommended that there is room on disk for approx 25% of the travel times. The software will print in the logfile what percentage of travel times will fit into memory, and what percent will fit on disk.

 Approximately 100-200 gig of disk can be used for this caching process.

 When the job checkpoints, the compute nodes must sync up at that point so, they are all on the same trace. Some nodes may go idle while this happens.

 The software will put the trace number for the checkpoints in the logfile at the beginning of the job, so the user knows when offsets will be output, or the job checkpointed. 

Floating Datum Enhancement

PSDM will now out put the floating datum static in the same byte location as the static in the input data headers.  These will be placed in the output file regardless of outputting at final or floating datum.

1/t Scaling Bug Fix

The 1/t scaling parameter (sphdiv) in psdm_5.8.sp1 was not behaving correctly. A positive number makes the
amplitudes decrease as a function of depth and a negative number increase as a function of depth. The parameter in psdm_5.8.sp1 was doing the opposite. The 1/t scaling has been fixed in psdm_6.0.  It is advised that before running any large job, you run a few small tests to ensure that you have the desired scaling.  Previously, the 1/t scaling parameter was limited to integer values.  It will now properly use floating point values.

2D  Crooked Line Fix

Using the 2D crooked line option will now ignore the delta x, y values when calculating the xline spacing.  It will just use the xline spacing parameter.

Memory Bug Fix

An issue regarding the limit on how much memory the master node can allocate was addressed, as well as a bug that caused problems when not keeping all offsets in memory.

 

 

RAYS                                                                                                             

A2012 version rays_5.10

Using Both Smoothed and Unsmoothed Velocity Models

 The raytracer now has the ability to use both smoothed and unsmoothed velocities for travel times generation.

 In Kirchhoff migrations, we have to smooth the velocity model to minimize the ray scattering when calculating the travel times. This smoothing is a rather subjective process, and the downside of it is inaccuracies in the velocity model. Smoothing the model changes the velocities, and changing the velocities causes changes in the image, and changes in the depth position of the events.

 With the new raytracer, we optionally allow the use of two models: a smooth one, which is used for calculating the ray paths, and an unsmoothed one, which is used to calculate the travel times. This increases the accuracy of the ray tracer, and allows events to be positioned more accurately.

 The benefits include:

• Uses smooth velocities for calculating the ray paths to minimize ray scattering
• Uses unsmoothed velocities for calculating the travel times, minimizing the velocity distortion from the smoothing
• Minimizes the subjective nature of how much smoothing is enough, or too much
• Images better under salt and around high velocity contrasts

The option to input the unsmoothed velocity model can be found on the files tab.  Parameter name is velunf and the value is the direct path to your desired unsmoothed segy velocity model.  The 2 velocity models may also be used in the smoother utility.  In this case, for the raytracer, you would specify the velocity block file created in the smoother as well as the 2 input velocity models. 

New Parameter

The visv0 parameter has been added to distinguish between V0 and Vvertical for TTI anisotropy.  This is found on the input tab.

 

 

SMTH                                                                                                             

A2012 version smth_5.9

2 Modes of Smoother

The smoother will now operate in two separate modes. 

Mode 1 outputs the smoothed version of the velocity and a block file that can be supplied to the ray tracer. The block file can be isotropic, anisotropic (both VTI and TTI) and can be a combination of both smoothed and unsmoothed velocities as required.

In Mode 2, the user inputs a single segy file, no block model is created and the output is a smoothed segy file.  The input is not limited to velocities but can be a segy file of eta values, deltav, etc.

The switch for smoother mode can be found at the top of the files tab.

Median Method of Smoothing

Median method of smoothing velocities has been introduced in the new release, which will remove anomalously high and low velocities. Median smoothing can be used in Mode 2 only.  Median smoothing is better for smoothing RMS, and non velocities. The average smoother is better for reducing the derivatives in interval velocity models. 

This parameter is found on the Options tab and is only active when Mode 2 has been selected.  The parameter name is avesm= 0. Default is to use the average smoother (avesm= 1).  The user will need to supply operator lengths for this method.  Calculate operator lengths is not available with the median smoothing method.

 

Using Both Smoothed and Unsmoothed Velocity Models

The raytracer now has the ability to use both smoothed and unsmoothed velocity models for travel time calculations.  If you are starting with an unsmoothed model, specify it as both the input velocity file and the unsmoothed velocity file in the smoother utility.  This will generate your smoothed output velocity model for use in the raytracer, as well as store the unsmoothed model information in the block model.  If using this method, you would then specify your new, smoothed velocity model, your original, unsmoothed velocity model and your block file from the smoother in your raytracer parameter file.

 

 

TOMO                                                                                                   

A2012 version tomo_5.8

New Trace.db Format

The Tomography program has been updated to use the new trace.db format.

 

 

GUI

Floating Datum Byte Size

A toggle has been added so that the byte location for the floating datum static may be defined as 2 byte or 4 byte.  Parameter name is dtmtyp.  Default is 4 byte or dtmtyp= 0.  This parameter can be found in the Floating Datum section of the Input tab on both PSTM and PSDM.

Smoother Name Change

The Smooth Velocities option on the GUI start up window has been changed to Smooth Utility

Output Floating Datum Bug Fix

The GUI was previously outputting the output at floating datum option as outfltdatum when it should have used the name outfltdtm.  This has been corrected in the A2012 GUI.

Tomography Travel Time Bug Fix

The GUI would not allow a single file for the travel time and seed horizon files.  When a user tried to accept the parameters an error message would pop up. This is now working correctly.

 

INTViewer                                                                                                          

INTViewer 4.3

Tsunami Plug ins Released

Tsunami is pleased to release several of our in house designed plug ins for the INTViewer.  Plug ins released in this version are:

• Plug in PWaveConversion. Users can generate a starting S-wave model with indexed P-wave and gamma files.
• Plug in Load from ASCII.  Users can convert ASCII files containing laterally varying velocity or gamma files to SEGY.
• Plug in VariableVelocityPicker.  Users can display gathers from variable velocity migrations and pick the velocities that best flatten the migrated events.
• Plug in VariableVelocityAnanlysis. Users can create an updated velocity model using picks from the VariableVelocityPicker Plugin.
• Plug in AutoPicker II.  Auto-pick horizons on gathers for input into Tomo.  Residual moveout on depth migrated.Plugin Floating Datum Correction.This plugin reads in a trace.db file and extracts the floating datum values. Once floating datum is known for each trace, it is applied. To save the new dataset, use the INTViewer menu item File->Save seismic datas
• Plugin Horizon Depth Correction. Users can correct a horizon's depth values when the horizon is picked on a seismic dataset which has had specific interval velocities applied or when the horizon is in time and a depth conversion is desired.
• Plugin Horizon Interpolation. This allows the user to input a horizon and select either 2D or 3D interpolation between the user picked points.
• Plugin Horizon Polygon Edit.  Quality control tool for horizons. The input consists of 2 horizon files and a polygon file. The user defined polygon encloses a questionable area on a horizon.  Data points within the polygon are removed allowing the user to focus only on the questionable area for repicking.
• Plugin  Horizon  Slice.  This plugin takes the seismic dataset and horizons in the currently selected window as input and uses this input to create a "flattened" region above and below each horizon. This slice data is then displayed in an INTViewer window. Once saved, indexed and transposed it can then be displayed in a Map window to view each horizon time slice.
• Plugin Horizon Strike and Dip.  The plugin takes the input horizons and calculates the strike and dip values. These values are output to a separate strike file and dip file for display or use in other applications
• Plugin Seismic Time to Depth Conversion. Convert a seismic dataset from time to depth or from depth to time using a user input velocity model.
• Plugin Velocity Model Update. The user is able to delineate an area using either 1 (flood) or 2 horizons (top/bottom) per area and replacing the velocity within that area with a user defined velocity.
• Plugin Velocity Resample.  The Velocity Resample plugin allows the user to input a 2D or 3D velocity model and change the increment of the Inline and/or Xline.
• Plugin Velocity WellTop Updater.  The plugin creates a deltav mapping so the velocity for the seismic can be adjusted to the known horizon from the welltop
• Plug in Angle Mute.   Apply an angle mute to seismic gathers, calculated by using the RMS velocity model.

All of the plug-ins have detailed help files that can be ac  cessed either through the Help->Help Contents on the menu bar or by clicking the Help button on the individual plugin's dialog box.

Instructions for installing the new plug ins can be found here on our support portal.  Should you have questions about installing the plug ins or on any of our new features, please feel free to contact our friendly support staff at any time.

 

Release Notes

---

Overview

I am pleased to announce our new release of Tsunami software, the Tsunami B2011 suite. This suite contains new versions of PSTM, PSDM, and Tomography. Details on the changes are contained herein.

 

I have been asked a few times now, what Tsunami is planning for upcoming releases. For our INTViewer customers, you will be pleased to know that we are planning our next release to contain new plug in tools developed for versions 4.0 and greater of the INTViewer. Our new Autopicker tool that has been under beta testing for some time and a semblance builder will be presented in the C2011 release. Additionally, we are planning the release of a new Rays and Smoother tool, though the date is not yet set. If you are not a current user of the INTViewer or you are just interested in what other tools are under development, please let your account representative know. They will be happy to show you more. sales@tsunamidevelopment.com

 

We are continuing to expand our support content for our customers. In May we added a support button to our homepage. Users can now submit a support request from any page on our website. This also means that our old support ticketing system is now defunct and has been removed from the site altogether.

New support content is being added to our support portal every month at support.tsunamidevelopment.com. Some information is only available to customers, and those users will need to log in to see all the features it offers. If you forgot your password, no worries. You can request a reset link quickly and easily from the log in screen.

 

I want to take a moment to highlight two of the great benefits of the support portal for our customers. We are taking the more commonly asked questions and converting them into forum topics with detailed explanations and pictures, where possible, to make finding solutions fast and efficient. Users can interact with these support documents and let us know when more information is needed. It’s a great way to make support more powerful. Also, customer’s support request history is maintained and easily reviewed by the user or our support geophysicist. If a customer has an issue similar to something in the past the support representative can review this information to provide a timely solution. As we are supporting more companies around the globe, using the support portal or support@tsunamidevelopment.com means that we can deliver the excellent customer support you expect.

 

Before I sign off on this update, I also have to pass on news of our newsletter, lunch & learns, and the new support phone number. Starting in May Tsunami began sending out a monthly newsletter with information on new features, tools, and upcoming events. Speaking of events, we have begun hosting periodic Lunch N Learns in our Houston, Tx office. Look for these to start showing up in Europe late this year. If you are not getting the newsletter or you want to know about upcoming events before they happen, email Melanie Blind melanie.blind@tsunamidevelopment.com. Finally, Tsunami Support has a new direct number! +1 713-900-2099 will call our support staff directly, no fancy queues or numbers to press. If we are there, we will answer the phone, but if we are not please leave us a voicemail. It will be emailed to entire group, and someone can get back to you quickly.

 

Happy migrating,

 

 

Jaclyn Cribley

Operations Director

Tsunami Development

 

 

---

 

General

In the latest release users will see a change to the structure of the INTViewer installers. Inside the release will be a directory named INTViewer and under that a directory called releases which will contain multiple version of the latest INTViewer as well as supporting files. Users may install which ever version of the viewer they wish. Newer versions will support more plug ins as they are released. The viewer will only work for Tsunami customers with a current license. Please contact your sales representative if you have questions.

 

PSTM new features

 

The newest release of Pre-Stack Migration software is PSTM 5.9.

Data Preparation

 

In the previous release of the Tsunami Suite, A2011, we released the data preparation features in our depth migration software. This release of Tsunami B2011 brings these same features to our Pre-Stack Time Migration. These processes are applied before the migration.

•Amplitude Scaling computes and applies a time variant scaling function defined by a 1/t scaling power. For example, enter a parameter value of 2 to scale the input trace by 1/t2.
•Filters applies a Bandpass frequency filter defined by low cut/high cut frequency pairs. Enter values for zero pass frequency and full pass frequency to define the high cut and low cut ramps.
•AGC automatically applies an AGC operator length defined by the Window Length parameter.

Converted Wave algorithm changes

Many changes were made to our algorithm for converted wave applications to improve the image quality. Most of these changes involve improvements to the underlying algorithms and will be transparent to the user. New variable velocity options allow variation of gamma and of both P-wave and S-wave velocities together. Previous versions used a single gamma function. The new release allows use of a spatially varying gamma field. We feel that the updates give an image of superior quality to the results produced by other tools on the same data.

 

Input data in PP and PS time is now supported and can be selected on the user interface.

 

A new utility has been added in the INTViewer to generate an S-wave model from a P-wave model and a gamma file. SEGY models can be generated from ASCII input files. This utility will work with gamma, velocity and eta data and is implemented in the INTViewer. plug in names

 

For information on installing INTViewer plug-ins refer to the support article built into the INTViewer help.

PSTM Enhancements

1/t **n changes

In previous versions the user could only supply positive integers for this variable. The program will now accept negative and positive integers.

PSDM Enhancements

The latest release of PSDM is 5.8.sp1.

Output at Floating Datum

This option, when selected was not properly outputting data as expected. This has been corrected.

 

TOMO Enhancements

The latest release of PSDM is 5.7.sp1.

Error: Negative Slowness

Users reported receiving the error “Negative Slowness” in the log file. This error was the result of a miscalculation which has been corrected.

---

GUI new features

Data Prep Tab

The data prep tab was added to support the new features of PSTM discussed earlier.

Geometry tab now has Check Coordinates

Traditionally PP data  causes the data to fail the geometry check. There is an option on this tab to skip the geometry check, which will prove useful when you working with the converted wave application. 

Converted Wave Tab

The Converted Wave Tab now has Domain of Input Seismic, choices are PP or PS, and  the VP/VS (Gamma) Velocity Model user option.

Variable velocity tab

The Variable Velocity tab now has  a new Function option of Gamma (VP/VS) and a Function option of P-Wave & S-Wave velocities.

Changes to GUI

Internationalization bug

When the OS has been set to a language that uses commas rather than periods in representing a floating point number, numerous problems occur in setting parameters, both in the user interface and the INTViewer.  The Tsunami start up script has been modified to resolve this issue.

Geometry Map / trace.db

When the trace.db file is read, any shots or receivers falling outside the defined INLINE / XLINE boundary were assigned a shot number of zero. If  a shot zero was detected, the geometry map failed with the error, “XXX.” This has been corrected.

Data Prep tab

1/t scaling has been moved from the Processing tab and is now a user supplied value as described above.

Known Issues

Updates for known issues are maintained on our support portal at support.tsunamidevelopment.com. This is a list of known at this time.

TOMO Travel Time Files

 

The GUI says it will take a single file for the travel time and seed horizon files.  However, the user interface is only accepting a list of files. The work around is to supply a file list for the travel times.

Output at floating datum in PSTM

In the user interface on the Output tab, there is a parameter to output at the floating datum. At this time this feature works in PSDM but is not functional in PSTM. A solution is under development for the next release of PSTM, and if any user desires a beta version in advance, please contact Tsunami at support@tsunamidevelopment.com.