TIBCO OpenSpirit^® Version 3.2.3 Update
Release Notes
April 1, 2011

TIBCO OpenSpirit v3.2.3 is a Master and Satellite release and is intended to be installed as a new installation. Migration of configuration and user information from previous v3.x installations can only be run during new installations. Alternatively, the installation may update existing v3.2.0 or v3.2.1 or v3.2.2 installations.

Master and Satellite installations are available on all supported platforms.

Release Highlights

• Added Support for Create, Read, Update, Delete for PPDM 3.7
• Added Support for SMT Kingdom 8.6
• Added Support for Recall 5.3 on Linux
• Added Support for Petra 3.4.1.0 on Windows

Data Connectors

GeoFrame

• Fixed a problem copying 2d seismic into the GeoFrame (IESX) data connector where datasets had fewer traces than their associated 2d lines. (25663)
• Fixed a problem copying 2d seismic data into GeoFrame (Charisma) data connector where the Z index value was not rounded to the nearest whole number. (24317)
• Fixed problem inserting really large 2d lines into the Geoframe (IESX) data connector. (22514)

Kingdom

• Added support for Kingdom 8.6.
• Fixed a problem where the error message contains symbology if one or more 2d datasets are missing when copying 2d Horizons to TKS8.6 (64 bit). (26016)
• Fixed the problem where Kingdom crashes when displaying attribute HorizonGrid1dProperties for '2D Horizon Property' in the new Data Selector. (24437)

OpenWorks 2003.12

• Fixed a problem calculating the correct NumTraces attribute for very large 3d volumes (6800x6000). This fix makes it possible to copy these large volumes because the seismic validation checks are now successful. (25673)
• Fixed a problem returning 2d/3d seismic horizon data if the min/max values are NaN instead of the SeisWorks null value. (25520)
• Fixed a problem where the SeisWorks 2d master project name is truncated at 8 characters; the maximum is 10 characters. This only involves workflows when a SeisWorks 2d project is created; no affect for read/only workflows. (25432)
• Improved performance when inserting 2d lines from any client application (Copy Manager, Petrel Export to OW2003.12). The SeisWorks SMS files are now only rebuilt once instead of after each newly inserted 2d line. (25287)
• Fixed a problem displaying all HorizonFaultBoundarySets (e.g. OpenWorks fault polygon sets) in the DataSelector when the HorizonName is one of the displayed columns. Some rows were not previously displayed if multiple HorizonFaultBoundarySets were associated to the same OpenWorks surface. Displaying the HorizonName column resulted in a table join between the EpiInterpretation_HorizonFaultBoundarySet and EpiInterpretation_Horizon. (25107)
• Fixed a problem reading traces from 32-bit integer seismic datasets. These datasets can now be sent to the TIBCO OpenSpirit viewers and the ScanUtility can now generate live trace coverages. (24675)
• Fixed a problem where NullPointer exceptions occurred when scanning 16 and 32 bit datasets from OpenWorks 2003.12 if using SDE mode and the SampleMin and SampleMax attributes were selected. (24577)
• Fixed a problem where data entities that have an association to surfaces (e.g. HorizonGrid2d, non-seismic grids, HorizonFaultBoundarySet, HorizonPointSet) are filtered out when doing table joins if the OpenWorks surface has a stratigraphic column that is not "UNKNOWN". Those entities are no longer filtered out. (24440, 24441)
• Improved performance and reduced memory usage when processing (both read and write access) 2d seismic data. (21385, 23428)
• Improved SeisWorks project validation processing so it detects and skips over "bad" SeisWorks 2d projects if the 2d line catalog is corrupted. (24289)
• Fixed a problem when connecting to an OpenWorks project created with the Project Default CRS coordinate system. (24324)
• Fixed a problem where issuing a query with WellType in the WHERE clause (eg. SELECT Identifier from EpiWell_Well WHERE WellType = 'OFF_SHORE')returned zero rows when valid rows should have been returned. (24985)
• Corrected some Reference Value Service (RVS) mappings for ShapePropertyType when mapping to OpenWorks 2003.12. The delta time shape property types should be mapped to 'isochron' and the delta depth shape property types should be mapped to 'isopach'. They were previously mapped to 'unknown'. (24948)
• Fixed problems inserting lease information into OpenWorks if the last character after truncation is a 'space' character. (24112)
• Added additional units to the OpenWorks and Posc unit catalogs to allow logs with those units to be imported into Petrel. (22523)

OpenWorks R5000

• The OpenWorks R5000 data connector has been modified so the DataSelector no longer shows "empty" 2d horizons on the Horizon tab. These are the rows that have a Grid1dSet shape type and no 2d survey origins. The seismic horizon headers with no 2d line associations are no longer returned. (25765)
• Fixed a problem returning 2d/3d seismic horizon data if the min/max values are NaN instead of the SeisWorks null value. (25520)
• Improved performance displaying 2d datasets scoped to a large number of 2d navigation rows in TIBCO OpenSpirit's New Data Selector. (24727)
• Modified the OpenWorks R5000 data connector to look in the WellHeader table first for SpudDate and CompletionDate. If not present then look in the WellDate table. (24898)
• Corrected some Reference Value Service (RVS) mappings for ShapePropertyType when mapping to R5000. The delta time shape property types should be mapped to 'isochron' and the delta depth shape property types should be mapped to 'isopach'. They were previously mapped to 'unknown'. (24948)
• Fixed problems inserting lease information into OpenWorks if the last character after truncation is a 'space' character. (24112)

Finder

• Fixed a performance problem displaying data from Finder in the well tab of the data selector where a spatial filter defined by the well's location attribute or the wellbore's bottomlocation attribute is used. (24635)
• Added the Create WellBore PathXYOffsetCRS parameter to the Finder Data Source configuration panel. This parameter should be checked when using the CopyManager to copy data from Finder projects whose wells cover a large geographic area that cannot be represented with a single map projection system. OpenSpirit needs a map projection system to copy directional survey information. Checking the Create WellBore PathXYOffsetCRS parameter tells the Finder data connector to ignore the map projection setting in the Finder project (which may be incompatible with the well's geographic location) and create a UTM system appropriate for the well's geographic location. This change should allow more directional surveys to successfully copy from Finder. (24993)

PPDM

• Added Create Read Write Delete (CRUD) support for PPDM 3.7
• Enhanced the PPDM data connector to recognize the 'nad83', 'nad27', 'wgs84' non-EPSG code coordinate system identifiers during read. (24969)

Recall

• Added support for Recall 5.3 on Linux.

Petra

• Added support for Petra 3.4.1.0 on Windows.
• Added support for coordinate systems using the European Stereographic projection method. (25694)
• Fixed a problem where only one well log got copied into Petra when copying two well logs with the same name and the log name is not UpperCase. (25563)
• Fixed a problem where the Petra data connector returned NULL for Total Depth Type. It now returns the string 'Total Depth'. (25238)
• Fixed a problem returning values for the PickValueMD attribute for well pick if its parent bore had no values for the total depth and bottom location. (24350)
• Fixed a problem where the ground elevation is missing and elevation datum is incorrect in target Petra project if the wellbore DepthDatum is 'GroundLevel' in the source project. (25250)

SEGY

• Fixed a problem interpreting time or depth vertical systems when a CRS key for each existed for the same SEGY. (25621)
• Fixed a problem where the SEGY data connector misnumbered inline/xline positions pin raw SEGY files. (25165)
• Fixed problem in the SEGY data connector for trace data exceeding the limits of the 2d line's navigation data. (22270)

SDE

• Fixed problem if no row-id was defined for an ArcSDE layer. Also fixed an associated problem with corrupted SDE layers that caused the SDE data connector to be unusable. (25114)

Tools & Utilities

Coordinate System Transforms

• Fixed a problem in the interpretation of Well Known Text (WKT) for geographic transforms using the Position_Vector and Coordinate_Frame methods. This caused large errors (100s of meters) when importing or exporting data through the TIBCO OpenSpirit Adapter for Petrel (formerly OPAA) to projects with different datums requiring use of the Position_Vector or Coordinate_Frame shift. Creation of WKT from OpenSpirit projects is not affected, so Petrel projects created with WKT generated from OpenSpirit systems do not cause errors. (25997)
• The ESRI WKT SystemExchanger was changed to generate correct WKT for oblique mercator systems. (25974)
• Added the ability for Petra data connectors to now support coordinate systems using the European Stereographic projection method. (25694)
• Fixed a logic error in the comparison of geodetic datums which caused two different, predefined datums using the same ellipsoid to be considered equivalent. (25709)

OpenSpirit v3.2.2 - Release Notes

GeoFrame

• Added support for configuring Geoframe data server to default the project password in the data store configuration panel. (20848)
• Fixed a problem returning extents of GeoFrame nonseismic grids with negative row or column increments. (22404)
• Fixed a problem getting surface units for certain Charisma projects with a rare condition. (22730)
• Fixed a problem returning extents of GeoFrame nonseismic grids where the binset index system has been shifted from normal. (23786)
• Fixed a problem creating GeoFrame nonseismic grids where the binset index system has been shifted from normal. (23846)

Kingdom

• Fixed a problem where copying a small survey with a sub-set volume from a source into a larger survey in the target fails. (22403)
• Fixed a problem where the survey name was inappropriately appended to the horizon name when copying horizons if both source and target were Kingdom. (22709)
• Fixed a problem where seismic volume names are truncated to 20 characters. (22710)
• Fixed a problem where Petrel hangs after sending a 3D volume from a Kingdom8.5 data store if the seismic data file for the volume is missing. (23452)
• Fixed a non-seismic grid copy problem where data looks incorrect in Kingdom after exporting from OPAA when TopLeft is not the extent origin. (22211) The solution also requires SMT 8.5 SP1 or higher.
• Added coordinate system mappings which allows for scanning to the project's geographic system. In some (unusual) situations, it could affect coordinate transformations, since it makes it possible to skip datum shifts through WGS84 if the source and target datums now match. (23785)

OpenWorks 2003.12

• The OpenWorks 2003.12 data connector now returns 0 for the RunNumber if the database contains -1 (indicating a composite log). (22177)
• Fixed a problem in the OpenWorks 2003.12 data connector if the client was inserting a FaultPolyline that contained 64, 128, 192 (or any number that was evenly divisible by 64) number of points. OpenWorks 2003.12 has a limitation that a fault segment cannot contain more than 64 points so OpenSpirit must split the FaultPolyline into multiple fault segments before saving in the database. (22277)
• Fixed a problem accessing OpenWorks 2003.12 seismic files from SeisWorks projects when they belong to different OpenWorks projects. (22425)
• Fixed a problem with the OpenWorks 2003.12 data connector so that it now returns as many of the "good" seismic datasets as possible if it encounters a "bad" seismic dastaset. (22437)
• Fixed a problem with null values for Well Log Trace Data for the OpenWorks 2003.12 data connector. (22664)
• Fixed a problem in the OpenWorks 2003.12 data connector inserting Horizon Fault Boundaries if the Points attribute was created using only XY values but with a 3d coordinate reference system (CRS). (22971)
• Improved performance in the OpenWorks 2003.12 data connector returning Origin Values, Origin Types, and Number of Grids for 2d horizons and Origin Values and Origin Types for faults. (23147, 20708)
• Improved performance when reading 2d lines in the OpenWorks 2003_12 data connector. (23428)
• Added mappings for OpenWorks Stereographic70 projection, as well as some datums that are used exclusively in areas which also use this projection. Please note that the projection mapping is only good for the limited area of its historical usage. Outside those bounds, the difference between the OpenWorks and ESRI implementations may become intolerable. (24016)
• Fixed a problem in the OpenWorks 2003.12 data connector when retrieving the ActualExtent attribute. The inline/crossline ranges are now correct if the volume is not fully populated. (24095)
• Fixed a problem inserting lease information into OpenWorks if the last character after truncation is a 'space' character. (24112)
• Fixed a problem in the OpenWorks 2003.12 data connector returning HorizonFaultBoundary (e.g. OpenWorks fault polygons) XYZ data. Data is filtered out if it is unplottable. (23347)
• Added additional well status codes (22535, 23128, 23858)

OpenWorks R5000

• The OpenSpirit data connector for OpenWorks R5000 no longer replaces special characters (e.g. blanks) with underscores for 3d seismic dataset and seismic horizon names. (22192)
• Fixed a problem exposing the association between the OpenWorks R5000 surface and the seismic horizons. (22680)
• Fixed a problem in the OpenWorks R5000 data connector creating fault polygons for an R5000 interpretation project (IP). (23558)
• Fixed a problem in the OpenWorks R5000 data connector so that it now saves the Horizon Interpreter and DataSource values when creating non-seismic grids instead of always defaulting to the first five characters of the unix userid. (23859)
• Fixed a problem in the OpenWorks R5000 data connector creating 3d volumes if InlineStart, InlineEnd, InlineDelta, XlineStart, ZlineEnd, XlineDelta are not specified. The ranges now default to the associated 3d survey's ranges if the ranges are not specified on the insert. (23999)
• Fixed a problem in the OpenWorks R5000 data connector so that it is possible to create multiple seismic horizon properties for the same horizon and PropertyType (e.g. multiple AMPLITUDE grids). However, because this would violate the R5000 natural key for seismic horizons the second PropertyType will be named AMPLITUDE1 and the third AMPLITUDE2 and so on. This allows copy workflows to succeed when copying seismic horizons from vendor stores that support multiple property types for the same horizon (e.g. GeoFrame) to OpenWorks R5000. (24032)
• Fixed a problem in the OpenWorks R5000 data connector so that it is now allowed to return the 2d Horizon Properties attribute instead of always returning null. (24055)
• Added additional well status codes (22535, 23128, 23858)

Finder

• Fixed a problem with null values for Well Log Trace Data for the Finder data connector. (22663)
• Added additional well status codes (22535, 23128, 23858)

Petra

• Added write support for TVD/TVDSS logs for the Petra data server. (22023)
• Fixed a problem where an exception is thrown if an invalid well bore list (.WSN file) is accessed in the DataSelector. If the WSN file is invalid, instead of throwing exception, we now give the warning and move to the next well bore list (.WSN file). (22238)
• Fixed a problem where the Petra data connector automatically truncates well and bore identifiers if the input values exceed the maximum length. (22617)
• Fixed a problem with null values for Well Log Trace Data for the Petra data connector. (22662)
• Fixed a problem where updating the Bore/Well Aliases without a value for Common Name sets the Bore/Well Name to null. (23666)
• Fixed a problem writing deviation surveys in Petra if the first element of MD is not 0 and no Azimuth/Dip supplied. (23771)
• Fixed problem in the Petra data connector that filtered out picks with no measured depth for queries using a where clause containing the primary key attribute. (23808)

Tools & Utilities

Shared Services, Processes, and Events

• Fixed a problem when using attributes of type Unit in where clauses. (22097)
• Fixed a problem where if a secondary desktop existed for a Windows account, OpenSpirit would launch multiple Executor Server processes, orphaning previous Executor Server processes. (22453)
• Fixed a problem where an Executor process might not get restarted if a prior incarnation of the same Executor process was forcibly killed. (23669)
• Fixed a problem when connecting to machines with multiple IP addresses. A change was made to give preference to IPv4 addresses. (23792)

Scan Utility

• Fixed a problem in the Scan Utility so it no longer has a problem with live trace coverages for 3d volumes if the volume is not fully populated along the Z axis. The Scan Utility tool will now retrieve a horizontal slice that falls within the actual Z range. (24186)

Administrator Tools

• The "Admin Desktop" menu item in the OpenSpirit Launcher --> Configuration has been renamed to "OpenSpirit Desktop" because besides just the administration tools, the new OpenSpirit Desktop now supports the new Data Selector, Copy Manager, and other new tools. (22230)
• When used with OSP runtime v3.2.2, administrators can use the new User Manager to limit users to "import only" rights for OPAA 2010. (22964)

OpenSpirit v3.2.1 SP1 Update - Release Notes

GeoFrame

• Added 3x performance improvements to Charisma seismic write functionality. (21339)
• Added CDP and SP filter to remove noise from CDP and SP positions when creating IESX 2d lines. (21468)
• Added Linux 2.4x and SunOS 5.10 to the list of valid operating systems for GF 43. (21795, 21747)
• Fixed a problem returning attribute property MinValue, MaxValue, and DataUnit values in same units as HorizonGrid2dPropertyAccessor values if the Grid's unit is different than the unit corresponding to the Grid's measurement in the Display unit system. (20976)
• Fixed a problem with projection scale factors in GeoFrame. (21858)

Kingdom

• Added functionality to adjust Fault Z values to sea level and negative going down if in depth domain. (20505)
• Fixed a problem where the Kingdom data server generates a Java crash log at shutdown. (21662)
• Fixed a problem where a unusual string is displayed in a Copy log file when copying TWT well logs from IE44 to Kingdom 8.5 64bit. (21509)
• Fixed a problem with pick location if the bore elevation is null. (21325)
• Fixed a problem where min/max sample doesn't match with float array values returned from the data connector. (21092)

• Fixed a problem where the starting point of MD/TVD should be 0.0 instead of elevation when creating two-point MD/TVD array for straight bore which has no deviation survey. (22001)

OpenWorks 2003.12

• Fixed a problem with improper handling of multiple dir.dat entries and restricted permission to SeisWorks directories. (22328)
• Fixed a problem with scrambled grid data due to wrong internal orientation when retrieving OpenWorks 2003.12 non-seismic grids and SeisWorks 2003.12 seismic grids where the 3d survey has orientation of X-axis: InLine.  (21876)
• Added functionality to generate a better error message in the Copy Manager log if 3d surveys and 2d lines fail to copy to OpenWorks 2003.12. (21964)
• Added a few additional well status codes to the Finder and OpenWorks (2003 and R5000) data connectors. (21845)
• Fixed a problem in the OpenWorks data connector where inserting a well failed if the value for LeaseNumber already existed in the OpenWorks LEASE_MASTER table, and a value for LeaseName did not exist in the database. (21999)
• Fixed functionality to no longer create a two point path when both TD and Bottom Z values are null. (21829)
• Fixed a problem where seismic horizon queries failed if non-conforming data (e.g. 1E37 * 1000) was accidentally written to a horizon. (21774)
• Added the PathXYOffsetCRS column to the WellBore table. The PathXYOffsetCRS defines the coordinate system from which the PathXOffset, PathYOffset, and PathAzimuth columns are referenced. When inserting/updating a WellBore, applications may also specify a value for the PathXYOffsetCRS, indicating the coordinate system from which the PathXOffset, PathYOffset, and PathAzimuth values are referenced. If PathXYOffsetCRS is null on insert/update, the data connector will assume the values are referenced from the project table Coordinate System, as before. (21705)

OpenWorks R5000

• Added a few additional well status codes to the Finder and OpenWorks (2003 and R5000) data connectors. (21845)
• Fixed a problem in the OpenWorks R5000 data connector where a log indexed in time would not display properly in the 3d viewer. (21150)
• Added functionality to the Data Source Configuration panel that allows users to select the District Field from a list. The district field is no longer user editable.  (21497)

Finder

• Added a few additional well status codes to the Finder and OpenWorks (2003 and R5000) data connectors. (21845)
• Fixed problem computing Pick ValueTVD for Finder. (21854)

Petra

• Added read/write support for Petra native entities CalibData, CalibData1, MoProdDef, MoProdData, and GridHeader. (21664, 21665)
• Added relationships to the native Petra model. (21661)
• Fixed a problem inserting null values for the interpreter field in the Petra data connector. (21948)
• Fixed a problem where Petra native model query "select * from logname" or "select * from PetraProject" produces exception. (21666, 21667)
• Fixed problem in not inserting/updating the BotLat, BotLon, SurfLat and SurfLon attributes for a well properly. (21856)
• Fixed a problem where updating 'PickSource' nullifies 'Interpreter'. (21851)
• Fixed the problem where well bores fail to copy from into Petra when PathDip and PathAzimuth are NULL. (21962)

PPDM

• Added KB to the PPDM reference value catalog. (21579)

EPOS

• Updated the EPOS unit catalog with additional units for EPOS 3.38. (21655)

SEGY

• Fixed a problem recognizing volumes with forward or backward slashes in the volume name when copying into SegY. (21340)

Installation and Configuration

• Fixed a problem checking out a license when migrating from a previous version using silent install. (21597)

Tools & Utilities

Shared Services and Events

• Fixed a problem with memory corruption when recreating coordinate systems. (21671)
• Fixed a linking issue by replacing the bundled runtime Linux library "lib\Linux_i386_32\re4\gcc346\libOpenSpiritImpl.so.1" (21972)

Administrator Tools

• Added better cleanup for deleted data sources. (20171)
• Fixed a problem saving the configuration of a Petra data source when closing out of the desktop with the Window Close icon. (21471)

Certified Operating Systems - v3.2.3

• Sun Solaris
• SunOS 8 (Satellite only)
• SunOS 9 (Satellite only)
• SunOS 10
• Linux
• Red Hat Enterprise Linux WS release 3 (Taroon Update 4)
• Red Hat Enterprise Linux WS release 4 (Nahant Update 4)
• Red Hat Enterprise Linux Server release 5 (Tikanga)
• Windows XP (32 & 64 bit)
  • ArcMap Extension - ArcMap
    • ArcMap 9.3 SP1
    • SDE 9.3 SP1
    • Note: The ArcMap Extension as bundled in the OpenSpirit runtime installation will be retired in OpenSpirit version 3.3.0. TIBCO OpenSpirit ArcGIS Extension 2010 is currently available as a separate product download. The new extension supports ArcGIS 10.
  • Excel Adapter
    • Microsoft Office 2003
    • Microsoft Office 2007
• Windows Vista (32 & 64 bit) - See Known Issues
• Windows 7 (64 bit)
• FLEXlm 10.8.0.7 on Solaris, Windows, and Linux Certified Operating Systems above

Certified Data Stores

OpenWorks/SeisWorks

• OpenWorks and SeisWorks 2003.12 running on Solaris 8 using Oracle 8.1.7.4
• OpenWorks and SeisWorks 2003.12 running on Linux RHEL WS3.0 Update 4 using Oracle 9.2.0.4.
• OpenWorks R5000.0.2.3 running on Solaris 10 using Oracle 10.2.0.4
• OpenWorks R5000.0.2.3 running on Linux RHEL Server release 5 using Oracle 10.2.0.4

GeoFrame/IESX/Charisma

• GeoFrame, IESX and Charisma 4.2 and 4.3 running on Solaris 8 & 9 using Oracle 9.2.0.6
• GeoFrame, IESX and Charisma 4.2 and 4.3 running on Linux RHEL WS3.0 Update 4 using Oracle 9.2.0.6
• GeoFrame, IESX and Charisma 4.4 running on Solaris 10 using Oracle 10.2.0.3
• GeoFrame, IESX and Charisma 4.4 running on Linux RHEL Server release 5 using Oracle 10.2.0.3
• GeoFrame, IESX and Charisma 4.5 running on Solaris 10 using Oracle 10.2.0.3
• GeoFrame, IESX and Charisma 4.5 running on Linux RHEL Server release 5 using Oracle 10.2.0.3

Finder

• Finder 9.3 running on Solaris 8 using Oracle 8.1.7.3
• Finder 9.5  running on Solaris 9 using Oracle 8.1.7.3
  **newer versions of Oracle that support Finder should also be OK, but have not been certified

SEGY

• The OpenSpirit "Managed" SEGY server running on Solaris 8 and Solaris 10 and Linux RHEL Server release 5.

Kingdom

• SMT Kingdom 8.4 Build 1491 (32 bit) running on Windows XP (32 bit)
• SMT Kingdom 8.4 Build 1519 (32 bit) running on Windows XP (64 bit) & Vista (64 bit)
• SMT Kingdom 8.5 Build 45 (32 bit) running on Window XP (32 bit) & Vista (64 bit)
• SMT Kingdom 8.5 Build 45 (64 bit) running on Window XP (64 bit) & Vista (64 bit)
• SMT Kingdom 8.6 HF2 Build 314 (32 bit) running on Window XP (32 bit)
• SMT Kingdom 8.6 HF2 Build 314 (64 bit) running on Window XP (64 bit), Vista (64 bit) & Windows 7 (64 bit)

Petra

• Petra 3.4.1.0 (32 bit) running on Windows XP (32 bit and 64 bit) & Windows 7 (64 bit)

PPDM

• PPDM 3.7 running on Oracle 9i
  Newer version of Oracle that supports PPDM should also be OK, but have not been certified

ArcSDE Culture

• SDE 9.3.1 SP2 on Oracle 10.2.0.3
  Newer version of Oracle that supports SDE should also be OK, but have not been certified

Recall

• Recall 5.1 running on Linux RHEL WS release 3 Update 4 & WS release 4
• Recall 5.2 running on Linux RHEL WS release 3 Update 4 & WS release 4 and Server 5
• Recall 5.2 running on Solaris 10
• Recall 5.3 running on Linux RHEL WS release 3 Update 4 & WS release 4 and Server 5

EPOS (Geolog)

• EPOS 3.38 running on Linux RHEL Server release 5

Known Issues

The following are the most significant issues known at the time of the release of v3.2.3. The FAQ area contains an up to date complete list of all known problems. The FAQ area can be found by going to the support section of the OpenSpirit web site (www.openspirit.com/support).

ArcMap Extension

• Sending projected grids as a GIS grid selection event does not work properly at this time.
  Workaround: Re-project the grid to lat/long and resend.

CopyManager

• Cannot copy from OpenWorks/SeisWorks to OpenWorks/SeisWorks where the source includes projects from the same data store configuration as the target.
  Workaround: Create a mirror data store configuration to use as the target. Please contact support@openspirit.com if you need assistance with this workflow.
• When copying well or interpretation data into OpenWorks R5000, if the incoming data is assigned to a private interpreter who is not owned by the unix account running the data connector, then the well or interpretation data cannot be copied. Interpreters inserted by the OpenSpirit copy process are, by default, private interpreters.
  Workaround: To address this issue, the interpreter can be set to public, or the unix account could be granted Manage access on the target project.
• Copy jobs built with v31x or v3.2.0 will not work with v3.2.2 and higher. Workaround: change the XML to select the project using the following format instead of referencing projectSets:
  <projectSelection>
  <projectIds>
  <projectId dsin="IE_42" dst="GeoFrame_4" proj="IE_CLOUDSPIN_42"/>
  </projectIds>
  </projectSelection>
• If path azimuth values for a directional survey is missing in the source database and copied to another data source (e.g. Petra, OpenWorks, Finder), the values for the copied path azimuth might be a few degrees off. The work around is to go into the source database (e.g. Finder, Petra, OpenWorks) for which the azimuth north type values is missing and set it accordingly before copying.

3D Viewer

• Images are either not displayed or displayed in a squashed manner depending on graphics card version, graphics driver, and Microsoft patch version.

Data Connectors

• Recall - A problem exists in the Recall data connector where Well depth data values (eg. Elevation, WaterDepth, TotalDepth) are treated as values in meters regardless of what the actual unit may be in the database. Depth values stored in meters in the Recall database are handled properly. Note the log curve depth values (TraceIndex, TopIndex, BottomIndex) are handled properly regardless of if the values are stored in feet or meters.
• Kingdom - Receive an error (Unable to open seismic file for writing ) when trying to copying 2D datasets into Kingdom 8.6. Issue exists for TKS8.6, TKS8.5 works okay. (SMT TFS 52215 is filed to address this issue.)
• Kingdom - No value for completion date for wells copied into Kingdom 8.6 64bit. Issue exists for TKS8.6 64 bit only. TKS8.6 32 bit works okay. (SMT TFS 52229 is filed to address this issue.)
• Kingdom - Cannot create slice volumes, and cannot create or display brick volumes in Kingdom projects
• Kingdom - Problem saving non-seismic grids into TKS8.5. Grids are lost after the data connector is shut down. Issue exists for only TKS8.5 - 64bit.
• Kingdom - The data connector for Kingdom 8.5 (64-bit) Oracle project will not start if OpenSpirit is installed under "Program Files(x86)". The workaround is 1.) install OpenSpirit in a directory without "()". 2.) Install Oracle 11 Win64 Client.
• OpenWorks 2003.12 -The OpenWorks 2003.12 data connector will avoid a possible corruption problem associated to accessing/creating data in multiple SeisWorks 2d projects and display an appropriate error message like the following: Due to SeisWorks devkit limitations, it is not possible to create 2d seismic files in a SeisWorks 2d project if another SeisWorks 2d project has already been accessed in the same process. Data has already been read from or written to SeisWorks 2d project (swproj1) and a write request to a different SeisWorks 2d project (swproj2) was requested. This request cannot be honored because the OpenWorks 2003.12 data connector will become corrupted and all SeisWorks data access will fail. Possible workarounds: 1) shutdown the OpenWorks 2003.12 data connector after accessing the first SeisWorks 2d project. 2) use different OpenWorks 2003.12 data store installations for each SeisWorks 2d project (assuming the SeisWorks 2d projects are associated to two different OpenWorks projects).
• OpenWorks 2003.12 - Out of memory error occurs when importing to Petrel multiple horizons from multiple SeisWorks projects that are associated with thousands of 2d lines which are also on multiple SeisWorks projects.
• OpenWorks 2003.12 -During copy workflow, the TVDSS value in the OpenWorks 2003.12 data connector does not appear to get populated. Stopping and restarting the dataserver will allow the attribute to post. Fixed in OpenWorks R5000.
  
• GeoFrame - when a seismic survey is referenced to a Local Coordinate System which is different from the Display Coordinate System of the project, the survey Coordinate System is not honored.
• Finder - There is a problem copying path azimuth values for a directional survey from/to Finder if the azimuth north type value is missing in the database to/from another data source (e.g. Petra, OpenWorks). The values for the copied path azimuth might be a few degrees off. Workaround: go into the source database (e.g. Finder, Petra, OpenWorks) for which the azimuth north type values is missing and set it accordingly.
• Some polylines are missing when both 2d and 3d faults are copied into TKS84.  Issue fixed with TKS85. Workaround: copy 2d and 3d faults in separate copy jobs.

Windows Vista

• OpenSpirit Master installation are not supported at this time, only Satellite installations.
• Vista security "locks down" C:\Program Files which prevents some Desktop Admin tools from updating changes.
  Workaround: Install into a directory other than C:\Program Files

General

• When installing on 64bit Windows platforms, do not install in the C:\Program Files directory.  The default (C:\Program Files (X86)) should be selected, or any other custom location that is not C:\Program Files.

• Grid transfers should be limited to 5 million cells ( ~2300x2300) or less.  If a grid of more than 5 million cells is required,  the grid should be resampled to a coarser cell size in order to reduce the number of grid cells to less than 5 million.

• Broadcasting SLICE and BRICK volumes from the 3D Volume tab in the DataSelector to the Excel Adapter when 3D Volumes are toggled to “Listen” causes only one record to be received by Excel. 
  Workaround: Broadcast the related 3D Survey(s) from the 3D Survey tab and toggle the Excel Adapter to “From 3D Seismic Survey select.”

• The Azimuthal_Equidistant projection method (used in Guam and other islands) in Petra is mapped to the Azimuthal_Equidistant projection method in ArcMap. Some preliminary tests suggest that this mapping only works for the predefined systems in the EPSG database (namely the aformentioned Guam projection). Usage outside those areas is not recommended. The projection method will be disabled in future releases until a suitable implementation can be found.

• When 3d volumes are selected for live trace coverage scanning and the job is saved to an XML file (to be used for command-line processing), the volumes are not saved in the XML file. 
  Workaround: The user must go through the user interface in order to do 3D Volume live trace coverage scanning.

Technical Support

Please refer to the following resources for OpenSpirit information:

Web Support	www.openspirit.com/support
FAQ's	www.openspirit.com/support/faqs
E-mail Support	support@openspirit.com

OpenSpirit v3.2.3 is designated with U.S. Department of Commerce Export Control Classification Number 5D992.b.1