![]() |
||||||||||||||
![]() |
|
|||||||||||||
![]() |
||||||||||||||
Software Release Notes |
|
|||||||||||||
|
What's New in 5.3.14
Russian Text Click Here
General Changes: · Two new parameters added to the tomography to define the distance between the picks. These values are used to do smoothing of the delta V values (or change in velocity) before it is applied to the velocities. Using a larger number will produce more smoothing, a smaller number less smoothing. These new parameters can be found on the Tomography Processing page of the GUI · Tomography program will now output a segy file of delta V values (or change in velocity). This will enable the user to see the change in velocity that was created at anypoint in the model. The file will be created in the project directory and will be named deltav.segy. A value less than one means the tomography has slowed the velocity down and a value greater than one has sped the velocities up.
· Removal of Epsilon and Delta parameters from Anisotropy option. Using one epsilon/delta pair is effectively using a constant eta value, which can be accomplished using the eta file input.
Bug Fixes: · The time frequency pairs (depth frequency pairs in PSDM) could cause aliasing problems at the bottom of the section. That has been fixed. · There was a stair step effect on the bottom of the data when not using time frequency pairs. · The SGI executables had a bug that caused the job to hang after a certain number of traces had been processed. · The SGI executables were outputting blank traces. · Run times have been improved. The previous version of 5.2.13 was not keeping the nodes busy as it should have. · The GCI dataset functionality was updated for changes to byte locations and scalars on the source / receiver xy’s and cdp xy’s. · A bug in using the cdpx/y byte locations for Paradigm input was fixed. Previously it would report the cdp x/y’s as negative numbers in the log file. · The raytracer was updated so that the anisotropy parameters will work when using the eikonal method. · The Output Map Area option (outmap) was not functioning properly. · The Despike parameter information was not being output at the end of the log file.
Additions to GUI: · Updates were made to allow for better display on SGI platform. · Fixes were made to release the java memory to prevent the GUI from hanging. These fixes will also help alleviate the problem of window titles not being cleared out when a new, non-related window is opened. · Windows have been modified so that they are easier to resize if necessary. This includes dragging the corner out to open window wider. · Selecting New from the Files Drop down menu will automatically open the parameter entry page. · The items under the Views drop down menu are now always active. There is no longer the need to do File->New before using the Views menu. · Updates were made to the Tomography GUI. New parameters to define the distance between the picks were added to the Processing page. · Epsilon and Delta parameters taken out of PSTM and removed from Processing Page on PSTM GUI. To See 5.3.14 Full Release Notes Click Here. To See 5.3.14 Full Release Notes in Russian Click Here.
What's New in 5.2.13 Russian Text Click Here General Changes: · Addition of Variable Velocity functionality in PSTM. · Updates to Converted Wave functionality in PSTM · Addition of HiDef PSTM Option · Tsunami is now available for the IBM Bluegene platform. · Calculation of the azimuth for the traces has been added to the function that builds the trace.db instead of the extended trace.db function. Bug Fixes: · A test was put in for reading of velocity file to make sure it is a fully populated rectangle. Previously, the velocity file was checked for constant increments, but not to verify that all inlines had the same number of xlines. This would cause incorrect velocities to be read, or the program to crash. · Bugs were fixed in the Aperture pairs and Aperture angle parameters. · Azimuth limits fix. Azimuth info will now be stored in the trace.db even if extended trace.db option is not turned on. Also the azimuth limit parameters can now be negative. For example, to specify an azimuth range of 40 degrees, centered about zero (north), the min/max azimuth would be input as –20/+20. · The Paradigm dataset functionality was updated. · The GCI dataset functionality was updated. · The Hi Def PSTM had a bug in the setting of the anti alias filter which resulted in problems in the imaging. · If the inline distance and xline distance were different, then the Smooth Velocity utility had them reversed. This has been fixed. Additions to GUI:
· Ability to turn off the Change Tracking Comments in parameter file has been updated. It is now a check box. If the box is checked the tracking comments are off. · Variable Velocity parameters added to Variable Velocity Tab in PSTM. · HiDef PSTM Option added to HiDef Option Tab in PSTM. *Please Note: These parameters are only active if you have a license for the HiDef PSTM in your $TSUNAMI directory. · Converted Wave Parameters have been moved to the Converted Wave tab in PSTM · OBC parameter added to the PSTM / PSDM Input page for use with Floating Datum options. · Changes to GUI have been made for the Bluegene platform. If using the IBM Bluegene platform, you must have .bluegene file in your $TSUNAMI. GUI will use this to set correct node.db file and executables. · Updates were made to allow for better display on SGI platform.
To See 5.2.13 Release Notes in Russian Click Here.
What's New in 4.18.12
· The Ability to Run in Converted Wave Mode has Been added to the PSTM Files Page. · The Ability to Output Angle Gathers has been added to the PSTM/PSDM Output Page. · Ability to Turn Off the Change Tracking Comments in the Parameter File. Located under Parameter drop down menu
General Changes: · New FocusDbFind script allows for spaces in DSOUT File Names ·· Angle Gathers Added to PSTM / PSDM · Converted Wave Added to PSTM · Smooth Velocity Program Added
Bug Fixes: · A bug was fixed that would crash the software if all of the static shifts were negative. This would happen if the reference elevation was completely below the topography surface. · A bug was fixed in the software for creating the extended trace.db. If the user did not supply the geometry parameters (dxpil,dypil.dxpxl,dypxl) then the src/receiver locations in the trace.db were wrong, as were the number of src/rcvr locations in the trace.db. So the geometry plot would be wrong. · Changed maxt in program to match mxtime output by GUI · Aperture angle fix. Was not working correctly in 4.16.10 · A bug was fixed that would cause the logfile to hang when the last offsets output were empty. · A bug was fixed in the paradigm file type. When entering the byte location for headers, the 1 was not being subtracted out of it. · Smute was not working correctly. · Fixed outmap so that it won’t be used with just a few traces (ie. Synthetic datasets) · Changed large negative number for migrated dist. when no traces contribute to output offset to 999999999. The large negative number was making the screening process more difficult when doing the stack · The interpolation of the velocity model when using the 2D crooked line feature has been improved and made more accurate. This was a problem when the model did not start at the same place as the seismic input data, and also when the line was very crooked. · A bug was fixed in the software that had to do with the mute at the top of the section when using the floating datum. The output was clipped a bit deeper than it needed to be. · A bug was fixed that occurred when the velocity model does not extend to the edge of the seismic and there was a floating datum in use. · The interpolation in the floating datum generation has been improved. A progress bar has also been added to this step. · For the Smooth Velocity Module. When setting the desired max z derivative, the parameter was not being output as it should have. · A bug in PSDM / PSTM using DSOUT files has been fixed. The DSOUT files with 16 bit integer and with an odd number of samples in the trace were not being read correctly. · A test for the input parameters has been added. The dxpxl, dypxl now needs to be consistent with the xlspc, if the xlspc is input as a parameter.
|
||||||||||||||
![]() |
||||||||||||||
![]() |
||||||||||||||