SMT Kingdom Troubleshooting Manual

©2010 Seismic Micro-Technology, Inc. / www.seismicmicro.com

KINGDOM Software Release Notes for Version 8.5 Service Pack 2

September 30, 2010

The KINGDOM™ Software and all of its components – 2dPAK®, 3dPAK®, 2d/3dPAK®, EarthPAK®, LoadPAK®, DirectPLOT®, VuPAK®, SynPAK®, TracePAK®, ModPAK®, AVOPAK®, PAKnotes®, CGMPAK®, LogPAK®, and VelPAK® - are registered trademarks of Seismic Micro-Technology, Inc. (SMT), The KINGDOM Company™. KINGDOM Data Management™, KINGDOM DM Catalog Builder™, KINGDOM 1D Forward Modeling®, KINGDOM Illuminator™, KINGDOM Seeker™, KINGDOM GeoModeling™, and KINGDOM Colored Inversion™ are trademarks of Seismic Micro-Technology, Inc. (SMT), The KINGDOM Company™.

General Installing KINGDOM 8.5 SP2

• KINGDOM 8.5 SP2 utilizes the latest Microsoft technology and requires Microsoft .NET Framework 4.0 and other system components. These components will be automatically installed during the KINGDOM installation if not already installed.

For this reason, your current version of KINGDOM 8.5 must be completely uninstalled before installing version 8.5 SP2.

The KINGDOM installer will automatically uninstall for you and then will proceed with the installation of 8.5 SP2 and required components.

• Microsoft SQL Server Express is now automatically installed with KINGDOM unless it is unchecked during installation

Notes

• Always back up each project before opening it in a new release.

• KINGDOM 8.5 is available in 32-bit and 64-bit versions:

o The 32-bit version will hereafter be referred to as “The KINGDOM Software 32-bit” or “KINGDOM-32."

o The 64-bit version will hereafter be referred to as “The KINGDOM Software 64-bit” or “KINGDOM-64."

• KINGDOM-64 requires the use of a SQL Server Express, SQL Server, or Oracle database.

For more details see the SMT Planning Guide available on the View Resources tab of the Installation Manager. The Planning Guide is also included as a section in the Installation Guide.

• KINGDOM-32 and KINGDOM-64 can run standalone on a 64-bit system running Windows XP Professional, Windows Vista, and Windows 7 with a USB sentinel plug. Parallel port sentinel plugs are not supported on this platform. Contact your marketing representative at 713-464-6188 or [email protected] if you need a USB plug.

Software Download Capability

• SMT offers an electronic download capability to obtain this new release via the Internet. Log in to your My Account. Once logged in, click on Downloads and select Latest Release. This will take you to the release page where you can either download the software or select to have a DVD shipped. If you choose get a DVD, SMT will ship to the address that we have in our Customer

KINGDOM Software Release Notes for Version 8.5 SP2

September 2010 p. 1


Support system. If you do not have a My Account or cannot locate your My Account login information please contact your local SMT support team to obtain a login.

Compatibility

• KINGDOM 8.5 SP2 will not install on: o Windows XP unless Service Pack 2 or later has been installed. o Windows 2000.

• Users may see error 19 while applying Web Feature Keys when running KINGDOM for the first time with a standalone license on Vista. This can happen when Vista's User Account Control (UAC) is turned on. The default for UAC is enabled. The workaround is to use the right mouse button menu option "Run As Administrator" when starting KINGDOM the first time.

• SQL Server Users please note: KINGDOM GeoModeling requires SQL Server 2005 SP3 or SQL Server Express 2005 SP3

Oracle Users

• KINGDOM is certified on Oracle versions 8.x through 10g.

• KINGDOM versions 8.5 and later requires Oracle users to have CREATE VIEW System Privileges. Your Oracle DBA may need to add this privilege for each Oracle user before you can open or create KINGDOM projects.

• Some versions of Oracle do not work with applications installed in directories that contain parentheses. If you are using Oracle as your KINGDOM project database and you are installing KINGDOM 32-bit on a 64-bit operating system, you will need to do one of the following:

o Install KINGDOM in a folder without parentheses. (e.g. C:\KingdomSuite). o Install a version of Oracle that does work with parentheses or install patch 5059238 for

Oracle client 10.2.

Oracle and SQL Server users

• The 8.5 SP2 version of KINGDOM requires that tables be added to the data model. When a project is opened for the first time with 8.5 SP2, the Oracle or SQL Server user must have create table system privileges in order to successfully upgrade the project with the new tables.

• If your Oracle or SQL Server user can create projects, then you have create table permissions. If your user profile does not have the required permissions, you will get an Insufficient Privileges error message when opening the project. Contact your database administrator to modify the user profile.

SQL Server Express Users

• If you install and run SQL Server Express on the same machine as KINGDOM, we recommend Windows XP Professional x64 Edition SP2, Windows Vista 64 SP1, or Windows 7 on a workstation with a minimum of 4 GB of physical memory. Also note that performance can be substantially improved for large projects by adding additional RAM.

• KINGDOM 8.0 and prior cannot open SQL Server Express projects. After a project is converted to SQL Server Express, only KINGDOM 8.1 and later can open the project.


September 2010 p. 2



September 2010 p. 3

Access to SQL Server Express Migration in a Multi-user Environment

• If multiple users are going to access the SQL Server Express projects, you should install SQL Server Express on a network accessible machine. You cannot specify to install SQL Server Express on a different machine than the one you are logged into. Determine the machine to house SQL Server Express, and install the application from that machine with the SMT Installation Manager on the KINGDOM Software DVD or from the downloaded installer.

Using SQL Server Express Management Tools in a Networked Environment

• If you have installed SQL Server Express on a networked server, you must run the SQL Server Express Management Tools from that server in order to make projects portable or reattach portable projects.

Performance Considerations

• KINGDOM-32 on a Windows x64 Edition can access 3GB of physical RAM, which significantly improves performance for large projects. KINGDOM-64 can access 128 GB of physical space and 8 terabytes of address space.

• Application of any XP theme can cause serious performance problems. If you are using the XP “look and feel,” please review the Microsoft discussion at http://support.microsoft.com/?kbid=319740#kb4.

• Follow these steps to adjust the Windows settings for best performance: 1. Exit all running applications. 2. Right-click on the My Computer icon. 3. Select Properties from the menu. 4. Click the Advanced tab. 5. Click the first Settings button in the Performance box. 6. Click the Adjust for Best Performance radio button. 7. Click OK in both open dialog boxes.

• Users can view memory usage and availability by using the hot key combination Alt+Ctrl+M when

KINGDOM is running and has the active focus.

NOTE: If you have Windows Live Search installed, the keyboard shortcut Ctrl+Alt+M may bring up the Windows Live Search Tool instead of the KINGDOM memory dialog box.

Windows 7 KINGDOM 8.5 has passed testing on Windows 7 with no known outstanding issues. As with any new operating system there are a multitude of configurations with respect to security settings, up-to-date device drivers and mix of loaded software applications. If you should experience issues as always please contact your local SMT support team for assistance. Windows 7 and BMC’s AppSight Black Box When KINGDOM 8.5 was released, AppSight version 7.5 did not support Windows 7. If you are running KINGDOM on a Windows 7 system, SMT will not install AppSight when KINGDOM 8.5 SP2 is installed. BMC, the AppSight vendor, has released AppSight 7.5.02 which is compatible with Windows 7 systems.

http://support.microsoft.com/?kbid=319740#kb4



September 2010 p. 4

If AppSight is needed to troubleshoot a KINGDOM issue, SMT Technical Support will ask you to download and install AppSight from My Account. SMT KINGDOM 8.5 Hardware Configuration Recommendations Guide Note: The document below represents good faith estimates by SMT on customer hardware needs. Every customer environment is different and evolving. We strongly recommend that customers work with their IT departments and SMT consulting services to define their actual hardware needs. The information below is purely a guideline and not meant to be authoritative. SMT currently recommends the following basic configurations:

• Operating System: Windows XP Professional x64 SP2, Windows Vista x64 SP1, or Windows 7. (The OS must be specified because many vendors ship new workstations with Vista x32 as the default OS).

• KINGDOM Software 64-bit version When buying a new 64-bit workstation with a 64-bit OS, please determine your minimum configuration based on the following: Project Size KINGDOM x64 Version KINGDOM x32 Version Large Regional Projects 16 GB RAM Not Recommended Quad Core CPU Large Projects 8 GB RAM 4 GB RAM Quad Core CPU Two Dual Core CPUs Small Projects 4 GB RAM 4 GB RAM One Dual Core CPU One Dual Core CPU On a 64-bit workstation with a 64-bit OS running KINGDOM x64 Version, KINGDOM can potentially access up to 128 GBs of RAM and 8 TBs of virtual memory, depending on the amount of RAM on the workstation. On a 64-bit workstation with a 64-bit OS running KINGDOM x32 Version, KINGDOM can potentially access up to 3 GBs of RAM, depending on the amount of RAM on the workstation. This significantly increases the amount of accessible RAM using a 32-bit OS. How do I determine which hardware configuration is needed? Recommended Disk Drives

For KINGDOM projects stored on the local workstation or on a network file server, KINGDOM currently recommends the following:

• Project data is stored on the local workstation: 15,000 RPM SAS drives are recommended for the workstation.

• Project data is stored on a file server: 7,200 RPM SAS drives are sufficient for the local workstation.



September 2010 p. 5

Recommended RAM The following chart has formulas for estimating RAM required for a given project. The sample project used for this example is a Large Regional Project. However, you can use the formulas to determine your hardware requirements for any project.

Sample Large Regional Project Formula

Data Object Description MBs of RAM Required Example MB Total

Time Slice Display (In Lines * CrossLines * 4) / 1,000,000

(9300 *11400 * 4) / 1,000,000 = 424.08

Horizon Display 50 MBs is total RAM used 1 or many horizons = 50.00

GRID Display (Number of cells *4) / 1,000,000 (100,000,000 cells) * 4 = 400.00

Contour Display 4.5 * (contour files size) ((File size of 16.645MB) * 4.5) = 74.90

Vertical Seismic View Display traces * samples * 4 (9300 * 3246 * 4) /

1,000,000 = 120.75

Surface Picks load into memory .0016 MB each (1,000,000 Surface Picks) *

.0016 = 1600.00

Well data load into memory 0.00643 each (357,607 wells) * .00643 = 2299.41

Sum 4969.15 4.9

Data Object Computation RAM Required Example MB Total

Grid Gridding ((Number Cells ) * 4 + 4 * (number of input points)) / 1,000,000

100,000,000 * 4 + (4 * 103,020,000)) / 1,000,000 =

812.08

Contour Contouring a Horizon

((4 * 2 * 10,000) + (4 * Horizon bins)) / 1,000,000

((4 * 2 * 10,000) + (9300 * 11,400*4)) / 1,000,000 = 424.16

Contour Contouring a Grid

((4 * 2 * 10,000) + (4 *Grid cells)) / 1,000,000

((4 * 2 * 10,000) + (9300 * 11,400 * 4)) / 1,000,000 = 424.16

Max of the Above 0.8

Additional memory recommended MB Total

Seismic Caching Ram Cache (number of lines to cache) *

traces * samples * 4 10 * ((9300 * 3246 * 4) / 1,000,000) = 1207.51

Tiff Display sizes vary estimate 500.00

Shape files Display ~2 * sum of file sizes (*.shp file) estimate 200.00

Sum 1907.51 1.91

Memory Required 7.7GB



September 2010 p. 6

Based on the above chart, the peak RAM requirements for this project would be 7.7GBs if the user only displayed one window. However, if the user displayed 2 grids, 5 vertical seismic views, 2 horizons and 2 time slices we would need an additional 800MBs + 600MBs + 848MBs bringing the peak RAM requirements to 9.9 GBs. The actual peak memory usage would be during the grid creation. Since the amount of RAM required for this project is over 8 GBs, it is considered a "Large Regional Project" and one should purchase hardware accordingly. It is important to remember, this is only an example scenario. Please contact your IT department and/or SMT consulting services to define hardware needs for your environment. Video Cards Please refer to Appendix B for Video Card Requirements. Development and testing for VuPAK was done utilizing Nvidia Quadro FX3700, FX3800, FX4600 & FX5200 Video Cards with 512MB and 768MB of memory.

License Server for Network Users

• KINGDOM 8.5 SP2 requires license server version Sentinel LM 8.0. This is the same version since the release of KINGDOM 8.0. Users of previous versions of the Sentinel LM license server must upgrade to Sentinel LM 8.0. The SMT License Server 8.0 installer will guide you through the upgrade process.

• Sentinel LM 8.0 is backward compatible with older clients. That is, all applications currently running on Sentinel LM version 7.2.0.9 will operate normally.

• If the network license server is running on a computer with the Windows Firewall option turned on, then the computers running the KINGDOM software may have a problem connecting to the license server. If this situation occurs, set the Windows Firewall option to OFF on the computer running the network license server or create an exception.

Regional Settings

The regional settings for Windows must be set to use a period instead of a comma for the decimal point. The default in many European countries is to use a comma. To change the regional settings, follow these steps:

1. Exit all running applications. 2. Click Start > Settings > Control Panel > Regional and Language Options. 3. Click Customize next to the regional setting. 4. If the Decimal symbol is a comma, then click the drop-down arrow beside Decimal symbol and

select period. 5. Click OK and OK again on the original window.



September 2010 p. 7

Enhancements KINGDOM

Auto SSE (Automatic SQL Server Express)

• KINGDOM now offers a new SQL Server Express (SSE) option to make your projects more easily portable. The Auto SSE option moves the project database files into the project folder. KINGDOM then automatically attaches and detaches the database files when you open and close the project making your project automatically portable. You can move or copy the project without any tools or special operations.

• When MS Access projects are opened in KINGDOM, you will be presented with the option to convert these projects to any available database that KINGDOM supports. You can select from Auto SSE (automatic portability) or Manual SSE (original implementation using a tool to make projects portable) in addition to SQL Server and Oracle.

• If you had previously migrated projects to SSE, you will be prompted with the option to convert those projects from Manual SSE to Auto SSE at the time that they are opened.

• Some initial system configuration may be required if you want to use the Auto SSE option in a networked environment and will be sharing these projects with other users. This configuration is described in detail in the on-line help under Help > The KINGDOM Software Help Topics > Database Administration > Microsoft SQL Server Express as the Project Database or by clicking the Connection Requirements link on the migrate message box.

EarthPAK KINGDOM 8.5 SP2 debuts major new EarthPAK Advanced functionality for the geoscientist and engineer. Please note that due to limitations in Microsoft Access this new functionality is only available for SQL Express, SQL Server, and Oracle-based projects.

Perform Sophisticated Volumetrics Analyses • Incorporate structure, isopach, and property grids.

• Simultaneously analyze multiple layers, each with different properties.

• Perform “what if” analysis on an individual layer by varying fluid types and contacts.

• Analyze geological uncertainty through Monte Carlo and Sensitivity Analysis.

Forecast Recoverable Reserves • Analyze multiple production profiles in multiple cross plots.

• Forecast production into the future and tie with Volumetrics.

• Generate composite forecasts using multiple segments.

• Aggregate or normalize production data using group wells and perform analysis at the entity level.

• Create forecast templates and run in batch mode.



September 2010 p. 8

Assess Economic Viability • Create scenarios for economic cases.

• Input production, ownership, product pricing, OPEX and CAPEX to compute before and after tax cash flow.

• Compare projects with various economic indicators.

• Print or save cash flow summaries, and export full monthly cash flow table to Excel.

Extensive documentation, including a glossary, is available in the online help.

KINGDOM Colored Inversion KINGDOM Colored Inversion transforms seismic reflectivity data to relative acoustic impedance data. It enables interpreters to pick true changes in impedance that represent geology that matches well log data, not just picking horizons based on processing reflections. KINGDOM Colored Inversion requires a separate license. Known Issue with Colored Inversion: Under the ‘Apply to Volume’ tab, if ‘Invert Selected’ is pressed without selecting a volume an exception error message may be given. If it is, press ‘Continue’, select the volume you require, and then press ‘Invert Selected’ and the processing will proceed. [43574]

Bug Fixes in this Update (Reference numbers in parentheses) The following problems have been fixed with this update. We recommend that the update be installed if you are experiencing one of the listed problems. Service Packs and Hot Fixes by nature do not have the full certification of releases; therefore we highly recommend that you back up your projects before updating KINGDOM. KINGDOM updates are inclusive. Any problems fixed with previous Service Packs and Hot Fixes are included in the current Service Pack or Hot Fix.

KINGDOM • KINGDOM now automatically populates the Database login form with the named database

instance in the <project>.xml file rather than relying on the Microsoft Master Browser list,. (328198)

• Standalone sentinel plugs may now be easily moved between customer computers. (329110) • KINGDOM will now migrate projects from Access to Oracle, SQL Server or SQL Server Express

when Regional Settings is not English US. (284746)

• Improved performance when displaying and scrolling large shape files. (330656)

2d3dPAK • Posting a borehole note no longer hangs KINGDOM for projects with large number of wells.

(319116) • Recalling a saved map will now display fault polygons. (322430) • KINGDOM no longer crashes when loading wells in Geographix Ascii 3 format, provided to client

by Drilling Info. (322987)



September 2010 p. 9

• The user can now move or delete a SEG Y file after import is complete without exiting KINGDOM. (324047)

• Improvements were made for well load time. The performance issue when displaying tops for wells on the base map has been resolved. (324653)

• Performance has been improved when importing Logs> Multiple LAS logs into a project with a large number of wells. When the user selects the drop down list to select a well, the well list no longer takes a long time to open. (330585)

Tunnel O • Transfer of horizon data between Landmark and SMT via Tunnel O no longer shifts inlines and

crosslines by -1. (324728)

AVOPAK • Adding gathers to a new or existing gallery using the digitize line method no longer fails with a

"No gather to load" message. (320766)

VelPAK • Velocity data imported from KINGDOM now covers field area as expected. The data is correctly

listed when selected. (304532) • Under certain circumstances loading horizon data that does not have an associated fault polygon

set into a model as an XYZ (control point) data type could produce an error message. This has been fixed, and it is no longer necessary to associate a fault polygon set with a horizon to avoid the error. (314560)

• An issue with the VelPAK screen failing to display or being slow to open has been fixed. (318732)

TracePAK • The Time <> Depth Conversion option in TracePAK now places the converted cube in the correct

vertical position. (252498) • When generating "Average velocity" 3D volumes from a T-D Curve, the first pair of points in the

Time/Depth curve is normally depth =0.0 and time= 0.0 (seconds). Since Time/Depth = 0/0 at this point, the current logic sets this velocity value to 0.0. Later on the Time<>Depth conversion finds this zero value and gives an error message. (RTI 332463)

KINGDOM Service Packs and Hot Fixes are inclusive and include any problem fixes provided in previous Service Packs and Hot Fixes.



September 2010 p. 10

KINGDOM Software Release Notes for Version 8.5 Hot Fix 7

July 6, 2010

The KINGDOM™ Software and all of its components – 2dPAK®, 3dPAK®, 2d/3dPAK®, EarthPAK®, LoadPAK®, DirectPLOT®, VuPAK®, SynPAK®, TracePAK®, ModPAK®, AVOPAK®, PAKnotes®, CGMPAK®, LogPAK®, and VelPAK® - are registered trademarks of Seismic Micro-Technology, Inc. (SMT), The KINGDOM Company™. KINGDOM Data Management™, KINGDOM DM Catalog Builder™, KINGDOM 1D Forward Modeling®, KINGDOM Illuminator™, KINGDOM Seeker™, and KINGDOM GeoModeling™ are trademarks of Seismic Micro-Technology, Inc. (SMT), The KINGDOM Company™.

The following problems have been fixed with this update. We recommend that the update be installed if you are experiencing one of the listed problems. Service Packs and Hot Fixes by nature do not have the full certification of releases; therefore we highly recommend that you back up your projects before updating KINGDOM. KINGDOM updates are inclusive. Any problems fixed with previous Service Packs and Hot Fixes are included in the current Service Pack or Hot Fix.

Bug Fixes in this Update (Reference numbers in parentheses)

2d/3dPAK

• While using the 3D Hunt feature, the VSD update no longer blinks repeatedly. (322051)

• Active fault surfaces were not properly displayed in time slices. Intersection points only were displayed. (325405)

• When loading additional seismic data types into an existing 2D survey, horizon and fault interpretation may be lost if the incoming data extends the 2D line. Under these conditions users will be notified and can choose to 1) continue the seismic import only within the limits of the existing survey, 2) allow the 2D survey extension and redefine the survey limits, or 3) cancel the data loading process. An option is also available to skip the current survey's import and proceed to the next 2D line when "Import Multiple 2D SEG Y Files" is used. The choice to load only the incoming data type within limits of the existing 2D survey will ensure that any interpretation for that survey is preserved. (326629)

• Poor performance was observed while adjusting mistie settings in multi-author environments using Oracle. Performance has been improved. (326668)

VuPAK

• The unexpected display of horizons outside the VuPAK area of interest has been fixed. This corrects the inaccuracy and also improves performance when loading and displaying large horizons in VuPAK. (325334)

KINGDOM Service Packs and Hot Fixes are inclusive and include any problem fixes provided in

previous Service Packs and Hot Fixes.





June 8, 2010




KINGDOM

• Users who edit color bars will be presented with a Save dialog when editing is complete. Changes are now saved in a consistent manner. (315752)

• An intermittent crash when editing color bars has been resolved. (318164)

• When attempting to open a KINGDOM session file that uses an obsolete author name, the following error message appears: “The session file that you are trying to open is a different author's session file and cannot be opened”. Following this message you now have the option to open the session file. (319742)

• An intermittent crash when importing Geographix wb2 and wb3 wellbase has been fixed. (322001)

• Importing Geographix wb3 files sometimes resulted in the creation of spurious wells if the wb3 file included especially long Remarks Table (RT) records. (323326)

• The deviation survey computation method specified by the user during Geographix wb3 file import was not saved. When the deviation survey was later viewed, a different computation method was displayed. (323326)

• Improved performance when saving log settings and closing projects with large well log collections. (323412)

• Improved performance in KINGDOM projects with a significant number of culture shape files. (323587)

• Improved performance when creating or editing a work tree. (324125)

• Improved performance for users whose KINGDOM work trees load slowly. (324126)

2d/3dPAK

• Improved performance when creating a grid based on a zone attribute. (302649)




• Users can now consistently generate an Illuminator volume using 32-bit KINGDOM. Users were sometimes receiving the error message “KINGDOM could not create the specified Illuminator volume. There is not enough contiguous RAM to create the Illuminator volume”. (318168)

• Incorrect borehole projection to vertical displays for some projection distances has been fixed. (319430)

• Issues with digitizing correct 2D arbitrary lines across some 2D surveys have been resolved. (320545)

• While picking a horizon using 3D Seeker or 3D Seeker+ with the survey also open in VuPAK, some users received an error “Unable to enlarge file (file name) by increment yyyy. The file is currently locked”. The horizon is no longer locked. (320919)

• An intermittent crash when generating automatic fault polygons for a horizon is resolved. (322060)

• The author of a grid now has full edit and delete control at all times. (322206)

• The list of KINGDOM survey data types that appears in the surveys data type management dialog is now alphabetical. (323413)

• When multiple 2D SEG Y files are imported, a single survey that contains spikes in the trace data will no longer adversely affect the remaining surveys. Previously, subsequent SEG Y files were not imported correctly. (323461)

• Intermittent KINGDOM crashes when exporting formation top XYZ data from a grid has been fixed. (324049)

• An issue with horizon autopicking on a horizon processed by horizon snap has been fixed. (324457)

EarthPAK

• Improved performance when calculating volumetrics using polygons. (312308)

• Some zone attribute cross plots displayed no data after a filter was applied. (322631)

• Improved performance when performing log calculations. (323266)

1D Forward Modeling • Exporting gathers from 1DFM directly to the AVOPAK Gallery is done in CDP to Receiver format

instead of SP to Rec. This caused the offset distance to be 2X what it should have been - thus the distance was doubled. (323524)

• When gathers are exported from 1DFM to SEGY, the units flag is now put in the binary header (feet or meters) (323524)

• When gathers are exported from 1DFM to AVOPAK, the units (feet or meters) are read from the project and are exported correctly. (323524)

VelPAK • The default workflow "Interval Velocity v Depth to Middle of Layer.xml" has been corrected. The

second depth conversion step now correctly references the current event. (319882)




VuPAK

• Faults viewed in VuPAK did not become transparent when set. Fault surfaces became black instead of transparent and objects behind the fault were not visible. (291886)

• In some circumstances, the user was unable to pick horizons in the currently active VuPAK area of interest if a grid outside the active area was turned on. (323409)

• Mouse wheel zoom performance in VuPAK has been improved. (323410)

Tunnel O

• The shot point numbers of 2D surveys imported from a Landmark project using Tunnel O now match the original shot point numbers. (322546)


KINGDOM Software

Release Notes for Version 8.5 Hot Fix 5 May 10, 2010




KINGDOM • Startup performance when opening KINGDOM projects with large well log collections has been

improved. (290026)

DBAdmin • Following installation of KINGDOM version 8.5 Service Pack 1, the DBAdmin tool cannot connect

to the KINGDOM project database server. (320024)




2d/3dPAK

• An accuracy problem for certain MD-INCL-AZIM deviation survey calculations has been resolved. (276982)

• When a saved contour is dragged from the project tree and dropped on a base map, an error message "Loss of data converting_int64()” occasionally appears. (318856)

• The list of KINGDOM authors that appears in the various author selection dialogs is now alphabetical. (319288)

• The session file selection dialog is not wide enough to display the full path and file name of the session file. (319304)

• When session files are used with multi-user KINGDOM projects, an error message “Seismic data type id: xxxx in file: seismicxxxxxxx is undefined." Setting seismic data type to default” appears. (319443)

• Following installation of KINGDOM version 8.5 Service Pack 1, horizon auto update in base map view cannot be activated. (320379)

• When well symbols are imported from ASCII files (*.97, *.wb3, *.asc, etc.) or using Tunnel O or Tunnel L, the well symbol mapping selected during the import process now matches the final result seen in the import report. (320570)

• Users who inadvertently select the main KINGDOM window exit (X) button will see a “Confirm Close” dialog to avoid loss of data. (320842)

• An issue with 3D horizon files being locked after auto picking is aborted has been corrected. An error message “The file xxxx.hzn cannot be deleted as it is currently locked” was displayed. (322132)

• In some KINGDOM projects, when a user activates a fault in a VSD view, the VSD freezes and cannot be panned. (322136)

• Wiggle traces may incorrectly be displayed as vertical lines in VSDs (322154)

EarthPAK

• Performance issues for users who pick formation tops with many windows open have been resolved. (320542)

• Performance issues experienced while displaying the Log Management dialog have been resolved. (322142)






April 21, 2010




2d/3dPAK

• For some projects the error message “Error writing contour” is displayed and the contour file will not be saved correctly. (319918)

• Some contour lines may be missing if "Enable Contouring within a Polygon" option is turned on. This can occur if fault polygons intersect the boundary polygon. (319999)

• Upon opening a session file some windows may not reopen. (320180)

• To ensure that users are warned if they have not saved their session upon exiting KINGDOM, the default for session files has been changed to “Always Prompt”. The new default setting will apply for all projects created after updating to 8.5 Hot Fix 4. It will apply to existing projects only if the *.set file in the author folder is renamed or deleted. (320689)

• When using "Save Tables" on the Survey Management Mistie tab, settings were not saved to the mistie file if the file was open, and TKS was not giving the correct message. (320524)

• Some users experienced intermittent crashes when they opened a session file. (320532)

o Opening a session file and then applying mistie could cause a crash if multiple authors were turned on

o Opening a session file which included a contour within a polygon could cause a crash

• Horizon picking cursor is still shown upon switching from horizon to fault interpretation either using hot keys F7 and F8 or horizon and fault interpretation tool bars. (321262)

• KINGDOM does not use generated time slice volumes created in previous version. (320478)

• Random color bar crashes in a network environment when dragging a horizon onto a base map. (318599)






KINGDOM Software

Release Notes for Version 8.5 Service Pack 1 April 6, 2010


Enhancements

2d/3dPAK

• The Multiple SEG Y Export tool now supports the export of pre-stack gathers and the ability to filter out post-stack AVO data from the list of seismic volumes.

• A hot key for horizon polygon smooth has been added. (303044)

Bug Fixes in this Update (Reference numbers in parentheses) The following problems have been fixed with this update. We recommend that the update be installed if you are experiencing one of the listed problems. Service Packs and Hot Fixes by nature do not have the full certification of releases; therefore we highly recommend that you back up your projects before updating KINGDOM. KINGDOM updates are inclusive. Any problems fixed with previous Service Packs and Hot Fixes are included in the current Service Pack or Hot Fix.

KINGDOM • When renaming (RMB > Rename) an object in the Project Tree, typing the letter ‘q’ opens the

Picking Parameters dialog. (308367) • KINGDOM returns an incorrect value for free disk space when the target disk is larger than 4TB.

(308882) • Toolbar locations are not persistent and some users cannot dock the toolbars side by side.

(312620) • Required KINGDOM 8.5 SQL Server project database schema updates are not implemented if

the user does not have “dbo_owner” permissions. An error message has been added informing users of the required database permissions. Users will not be permitted to attempt to upgrade a project database schema without “dbo_owner” permissions. (317047)

2d3dPAK • When using a completion code template if one assigns the template and accepts that some of the

completion codes in import data are bold, the user gets no errors. If the bold completion codes are re-assigned then an error message is displayed. (254978)

• Arbitrary lines composed of multiple segments display incorrect “True Distance” on the vertical seismic view if the bins are not square. (294465)




• For KINGDOM X64 the ability to act as an administrator and bulk load formation tops for the all authors is restored. (284433)

• Exporting completion dates from the Wells > Spreadsheet results in ordinal numbers, not dates, being exported. (299948)

• Fault data exported from Geographix in Geoquest Card Image 7 format could not be imported into KINGDOM. (301503)

• Depth conversion > Create Average Velocity Map, is creating wrong x,y values for the control point file for some wells. (300893)

• Users cannot select the Well folder in the Project Tree, then type the first character of the well name and have the focus change to the first well in the list that begins with that character. (305240)

• The Author Delete warning message was incomplete and has been corrected. (307035) • Arbitrary lines on surveys with rectangular bins do not post correctly on the base map. (301657) • Some users experienced crashing while contouring a grid with a very complex surface with many

fault polygons. (309871) • After importing wells with longitude between 0 and 1 degrees west and then closing and

reopening the project, KINGDOM changes longitude value to positive which results in the longitude being east of the Greenwich median rather than west. (308403)

• When a user creates an arbitrary line then picks a horizon on an inline -- the picks (seed points) display automatically in the arbitrary line. If the user then increments the inline and makes additional picks - the picks do not appear on the arbitrary line. After shifting the arbitrary line over and back, the picks then appear. (266575)

• In a vertical seismic window displaying color raster seismic with the color bar displayed, if a user uses Ctrl+M on the keyboard to reverse the polarity of the seismic, a trough becomes a peak which shows as positive in the status bar. However, the color that is assigned to it is still a negative value in the colorbar. (266012)

• User enters deviations by MD, TVD, INC, AZI only and clicks calculate, apply and ok. This returns user to the well information screen. When returning to the deviation page, INC and AZI are gone. User adds a new line to the deviation by MD, TVD, INC, AZI but KINGDOM returns an error: "the y column can't contain empty values". User has to delete any calculated data and re-enter ALL the MD, TVD, INC and AZI values for the entire dev survey. (312618)

• GeoQuest Card Image 7 export results in null values in the output file for 2D and 3D depth horizons. (314295)

• Although the length of the guide window is still an important parameter in the use of fill picking, it looks like it is inactive when the "Show a guide window" is inactive. (308935)

• When copying seismic via Share/Copy, if the target disk drive is larger than 4TBs the status bar indicating copy progress quickly moves to “1 second left” and the program looks like it is hung. (316718)

• Import of 2d horizon data fails to import data for lines with non-numeric characters in the line name. (316181)

• Surveys > Survey Management > Mistie “Load Tables” fails to load a mistie table from another project. (316230)

• Misties must be entered by hand after merging seismic volumes to a new master project. The load/mistie table was designed to work across projects but does not. (316230)

• When creating 2d arbitrary lines, the geometry becomes corrupt and the line fails to display properly. (317892)

• Selecting a timeslice to display from the vertical seismic window can cause KINGDOM to crash. (319278)




• Horizon picks are no longer erased when the user switches from manual to erase picking mode without moving the mouse cursor. (303077)

VuPAK • KINGDOM crashes with VuPAK open while nulling contour nodes with the Grid Editor. (313834) • While interpreting in VuPAK the following message may be displayed when selecting

interpretation objects: "Interpretation on previous surface has ended. Please activate a new surface to start a new segment." (304392)

1D Forward Modeling • When a very large vertical scale is used such as 50 inches per second, the tops are not

accurately located on the model. (289198)

AVOPAK • Unable to extract amplitudes on Hilbert transform based attributes. (305346) • Color scales are not retained while scrolling through the gallery. (278998) • The user cannot change Time or Depth easily; only Amplitude gather time is available in

dropdown list. (258050) • Inserting gathers in a gallery that has user defined min and max values set does not honor user

defined min and max. (TFS 31477) • If the user sets a manual range for the colorbar, doing an F5, F6 does not honor the manual

settings. (TFS 30817) • Align Gather output blocks seismic data in KINGDOM X64. (TFS 31616) • Creating a new gather volume using mute and align data conditioning crashes. (TFS 28120)

EarthPAK • Aggregate cumulative production calculation does not include historical yearly production.

(287269)

LogPAK • In a multi-author project, the LogPAK parameters can become unavailable when switching

authors. (291584)

ModPAK • When creating a presentation plot of a model section window with formation tops, the formation

tops are misplaced in print preview. (307788)






March 2, 2010




KINGDOM • KINGDOM crashes when opening some session files: 1) Session files that had a link or path to a

survey that no longer existed in the project; 2) Session files that had multiple vertical seismic windows with a band pass filter applied; 3) In some cases KINGDOM crashed during calculating fault intersections. (311837, 302535, 302841, 305913, 316803)



KINGDOM Software

Release Notes for Version 8.5 Hot Fix 2 February 22, 2010




KINGDOM Data Management and Tunnel O • Installing this KINGDOM Hot Fix will resolve an issue for both Tunnel O and KINGDOM Data

Management as KINGDOM Data Management shares the binaries where the bug was fixed. After transferring wells from an existing Oracle project to a new project, the well logs in the source




project have identical start and end depths. In the target project the well logs are correct. (315193)

2d/3dPAK • When applying time shifts when loading a saved mistie table, the bulk shift is applied incorrectly

to faults and horizons if the user chooses the option to shift faults and horizons. Since this shift should not be applied when loading the mistie table from file, the option has been removed. (315248)

VelPAK • A well will not import into VelPAK after creating a time depth chart for the well in KINGDOM 8.5.

(314214)




February 8, 2010




KINGDOM • One client reported error messages during project conversion from Access to Oracle when

processing the T_ZoneIntervalAV table. (313289) • When editing culture layers, the active layer being edited may change, causing culture to be

added to or deleted from the wrong layer. (313356)

2d/3dPAK • The dropdown list for selecting attributes in a map view currently doesn't auto-expand for list

viewing as on VSD displays. The view of full data type names can be cut short. (29842)




• The sort order in Surveys > Survey Management > Mistie Table doesn't persist after applying a change to a data type's mistie settings. Sort order incorrectly reverts back to default order. (310228)

• A bug was fixed in "Import World Coordinates > 2d By File" that results in incorrect 2d coordinates when importing form SEG-P1 or UKOOA files. (29889)

VuPAK • Unnecessary check boxes are displayed on the Tops > Formation Top Management > Display

and the Faults > Fault Cut Management > Display tabs. The unnecessary text and check boxes have been removed. (312604)


previous Service Packs and Hot Fixes. If you have any questions please contact your local technical support team.

SMT USA & Canada Monday through Friday, 7:30 a.m. to 5:30 p.m. CST Phone: +1 (713) 935-7900 Fax: +1 (713) 464-6440 [email protected]

[email protected]

SMT Latin America (Mexico, Central America, South America) - en español Monday through Friday, 7:30 a.m. to 5:30 p.m. ART Phone: +54 (11) 43438635 Extension 211 & 203 Fax: +54 (11) 43438635 Extension 206 [email protected]

SMT Russia Monday through Friday, 8:00 a.m. to 5:00 p.m. GMT Phone: +7 495 980 89 82 [email protected] SMT Singapore Monday through Friday, 9:00 a.m. to 6:00 p.m. GMT+8 Phone: +65 6220-1089 Fax: +65 6220-1081 [email protected]

SMT UK Monday through Friday, 8:00 a.m. to 5:00 p.m. GMT Phone: +44 (0)20 8240-6525 Fax: +44 (0)20 8240-6526 [email protected]

mailto:[email protected]









Appendix A: Video Cards—Updated Hardware Requirements Two features available in KINGDOM versions 8.3 and later affect video card requirements. Volume co-blending (VuPAK) and shaded relief (2d3dPAK) take advantage of some of the new functions available in updated graphics libraries. Framebuffer Objects, a relatively new extension to OpenGL, is needed to make these two functions display properly. When shopping for a video card, look for a card that has:

• OpenGL 2.1 or higher • DirectX 9.0 or higher • Shader Support 2.1 or higher • at least 512 MB RAM (at a minimum - of course, more is better)

If you are unsure if your video card can meet these specifications, run a test program like OpenGLViewer (included with the DVD, or it can be downloaded from ftp://ftp2.realtech-vr.com/realtechv/pub/glview232.exe [32-bit] or http://www.realtech-vr.com/glview/download.html [64-bit]). For example, in the screen shot below, you can see that this video card with an older driver only has 66%% of the core features needed for OpenGL 2.1.

ftp://ftp2.realtech-vr.com/realtechv/pub/glview232.exe

ftp://ftp2.realtech-vr.com/realtechv/pub/glview232.exe

http://www.realtech-vr.com/glview/download.html




After updating to a new driver, the same video card now supports all features of OpenGL 2.1

VuPAK does not require the latest shader models and GPU functionality, but it does perform best with greater memory and faster processing speeds. However, even a moderately priced or older GPU can support VuPAK if it has shader support and the software running it is up-to-date. Development and testing for VuPAK was done utilizing Nvidia Quadro FX3700, FX3800, FX4600 & FX5200 Video Cards with 512MB and 768MB of memory.




Appendix B: Post 8.4 Release Bug Fixes included in 8.5 Since the release of 8.4 numerous bug fixes have been made to Kingdom-32 and Kingdom-64. These fixes have been made available through 8.4 Hotfix releases. All of these bug fixes are included in the 8.5 Release. KINGDOM releases are inclusive and include any problem fixes provided in previous ServicePAKS and Hotfixes.

KINGDOM Software

Release Notes for Version 8.4 Hotfix 3 October, 2009

The following problems have been fixed with this update. We recommend that the update be installed if you are experiencing one of the listed problems. ServicePAKs and Hotfixes by nature do not have the full certification of releases; therefore we highly recommend that you back up your projects before updating KINGDOM. KINGDOM updates are inclusive. Any problems fixed with previous ServicePAKs and Hotfixes are included in the current ServicePAK or Hotfix.


KINGDOM • One client reported that Kingdom consistently crashed when trying to Import horizons. This has

been fixed. (RTI 304176)

2d/3dPAK Advanced

• When performing 3d seeker + on an inverted data set, the illuminator volume generates but seeker did not work. This problem has been fixed. (RTI 301908)

LogPAK

• The crash when running the “Missing Curve Reconstruction” has been fixed. (TFS 25940)

TracePAK • The reported crash when running “Survey Statistics” has been fixed. (RTI 300620)

KINGDOM Software Release Notes for Version 8.4 Hotfix 2

September, 2009 The following problems have been fixed with this update. We recommend that the update be installed if you are experiencing one of the listed problems. ServicePAKs and Hotfixes by nature do not have the full certification of releases; therefore we highly recommend that you back up your projects before updating KINGDOM. KINGDOM updates are inclusive. Any problems fixed with previous ServicePAKs and Hotfixes are included in the current ServicePAK or Hotfix.





2d/3dPAK • Performance when horizon picking on an arbitrary line has been significantly improved. The

noticeable latency during the picking operation has been eliminated. (RTI 300582) • When updating a time/depth chart with the last depth shallower than the total depth of the well

KINGDOM will extrapolate the time/depth chart to the total depth of the well. (RTI 299529) • Using Math on two maps to add a constant value to a grid would give an error message and not

complete the operation. This problem has been fixed. (RTI 299733) • The latency when selecting a fault to edit has been eliminated. This latency was particularly

noticeable for regional projects. (RTI 300647) • Scrolling performance for both map and vertical seismic windows has been significantly improved

for most projects. The slow scrolling performance was particularly noticeable when base maps had culture displays enabled. The unnecessary redrawing of culture data in map windows was slowing display performance. (RTI 300651)

• Horizon “Polygon Erase” of 2d horizon data has been fixed. One can now delete 2d horizon data with “Polygon Erase”. (RTI 299873)

• The 2D hunt settings no longer get reset to pick in both directions when you change from ‘H’ to ‘F’ to ‘H’ again. (RTI 300884)

TracePAK • A crash reported when running Survey Statistics has been fixed. (TFS 20986)

EarthPAK • “Drill Events>>Show>>Show Type” now permits users to add new DST data types. (RTI 297830)

Tunnel L+ • In one client’s environment, after transferring 2d surveys from Openworks 2003 the KINGDOM

Oracle project would not open. This has been fixed. (RTI 293190) • File permissions for interpretation files transferred to SeisWorks are now defaulted to the

permissions for the current UNIX session. (RTI 300471)

Documents

SMT Kingdom Troubleshooting Manual