Notable Resolved Issues SP2

• Fixed a problem with match and merge on surfaces. (22891)
• Fixed a problem importing polygon features from SDE datastores. (22857)
• Fixed a problem with Save to external functionality when saving depth faults to a Charisma datastore. (21818)
• Fixed a problem importing 3d Seismic horizons from OpenWorks 2003.12 datastores into Petrel. (21848)
• Fixed a problem where checkshots were not activiated on both the wellbore owning the checkshot and those wellbores sharing the same checkshot. (21781)
• Fixed a performance problem when importing faults from OpenWorks 2003.12 datastores. (22849, 22982)
• Fixed a problem exporting slice volumes to OpenWorks 2003.12 datastores. (22072)
• Fixed a problem importing wells using a specified global user file. (21722)
• Fixed a problem exporting non-standard log curve mnemonics from Petrel to Geoframe. OpenSpirit will honor LogNameToLogMnemonic.xml mapping for log curves that do not have an OpenSpirit key. If the original log curve was imported to Petrel via OpenSpirit, the subsequent export of that log curve will honor the original log kind stored by OpenSpirit. (22093)
• Fixed a problem exporting non-seismic grids to Kingdom8.5. (22513)
• Fixed a problem importing depth and time faults with the same name but different origins. (22956)
• Fixed a problem importing time and depth horizons simultaniously into a selected subfolder. (22562)
• Fixed a problem where export dialogs did not display parent objects where appropriate. (21955)
• Fixed a problem where attribute grids imported from a Charisma datastore displayed incorrectly. (22362)
• Fixed a problem renaming Well Tops folder in Petrel after connecting to OpenSpirit. (22850)

Certified Operating Systems and Prerequisites

• OpenSpirit Ocean Petrel Application Adapter functions on all Operating Systems that Petrel 2009.2 Sep 11, 2009 functions on.
• Prerequisites that must be installed on the System running the OpenSpirit Ocean Petrel Application Adapter are
• Petrel 2009.2 Sep 11, 2009
• OpenSpirit v3.1.4 or higher

Known Issues

The following are the most significant known issues at the time of the release of Version 2009 SP2

• Unable to migrate markers from OSP v2.9x to v3x due to improper key in source (Ocean Petrel Issue 979).
• OPAA depicts holes in GIS polygons as its own polygon.  The polygon representing the hole does not appear as a hole to the user (Ocean/Petrel Issue 1046).
• LastModifiedDate (LMD) for a Petrel Marker not updated when modified (Ocean/Petrel Issue 568)
• OpenSpirit Properties not displayed in Settings for Horizons. OpenSpirit Properties are displayed in Settings for the associated Horizon Property (Ocean/Petrel Issue 828).
• Blank place-holder is created in the Petrel Input Tree when importing 3D Seismic Volumes.
• Does not support drilling targets.
• On export of seismic data, if the Petrel SRD does not match external project's SRD, a warning is issued to note difference; the export of the data is still performed.
• The Settings dialog for the Process OpenSpirit cursor tracking does not display.  There are no settings for this process.
• NAD27 transformation methods listed twice in details dialog.
• When exporting from Petrel to GF4.4, the resultant trace start and trace end are different from the original (fixed in OSP v3.1.5).
• Issue when exporting modified markers from Petrel to Kingdom (fixed in OSP v3.1.5).
• Cannot use concatenated license servers (Requires patch to OSP Runtime for v3.1.x.  Contact OSP Support).
• Short_Time unit cannot be set to “s” (Ocean/Petrel Issue 1184)
• Unable to export WellType to Kingdom data store.
• Importing 3d Volumes into Petrel from a Kingdom8.4 data store yields wrong results.  Traces appear replicated (issue resolved in Kingdom 8.5).
• Exporting CheckShots from Petrel to a Kingdom data store does not account for any difference in Velocity Datum (SMT Issue 27012).
• Only one well log curve version can be exported from Petrel to Kingdom8.4 because the Kingdom data connector does not support multiple log curve versions.
• When exporting to a Kingdom data connector from Petrel, no matter what interpreter is selected in the Export dialog, the data will always be associated with the Author used to run the Kingdom data connector.
• The horizon grid “Origin Name” field is not exported when performing an export to a Kingdom project.
• When upgrading Petrel projects from an older version to Petrel 2009.2 with the OpenSpirit Ocean Petrel Application Adapter (OPAA), the user is prompted to convert any existing keys upon connection to OpenSpirit.  Keys are tags for data items, stored in Petrel, that point back to an OpenSpirit data connector.  The process of conversion changes the old keys to keys appropriate for OPAA access and validation.  Check shot keys are not converted or validated.  Thus, when importing matching check shots with the OPAA, they will populate the Petrel project and appear as duplicates.  Deleting the old check shots is a typical workaround.
• Duplicate points are discarded when importing fault polylines into Petrel. Petrel considers a point to be a duplicate if the X, Y, and Z values match any point on the fault, even points on different fault segments (Ocean Petrel Issue 1251).
• The “Skip” option must be selected when exporting log curves and well picks from Petrel to an OpenSpirit data source that does not support check shot creation.
• Accessing 3d seismic data via a live link in Petrel from a Kingdom project with an incorrect seismic path setting will cause Petrel to hang.
• The min/max sample values shown in the DataSelector may not match the min/max sample values shown in Petrel because the values in the DataSelector do not necessarily reflect the min/max values of the raw seismic data.  The timeshift, phase rotation, and amplitude scale factor, which are all defined in the KingdomSuite Survey Management Mistie dialog, may have been applied.
• Kingdom 8.4 data connectors return KB Elevation as Seismic Reference Datum (SRD).
• Kingdom data connectors do not support last modified date. As a result, Match and Merge timestamps comparisons cannot be established to indicate which data source has been updated most recently.
• Re-importing faults multiple times from a Kingdom data source occasionally produces a lost connection error in the Petrel message log. Shut down and restart the Kingdom data connector to reestablish the connection.
• Exporting faults to a target data store that contains matching parent objects, such as 2d lines or 3d surveys, causes the fault key to update, but not the parent (2d line or 3d survey).  Thus there is a mismatch between parent and child sources after export.  Caution should be used when exporting faults.
•   Cannot import non-primary Z properties for 2d seismic horizons from Geoframe data stores.
• Microsoft Windows Uniform Naming Convention sysntax is not supported when entering a configuration file custom location on installation.
• The default folders in the Petrel tree (Wells, Seismic, Well Tops 1) must exist or OPAA will throw an error upon import.
• Cannot export 3d seismic horizons to an OpenWorks R5000 data store where the horizon name already exists (issue resolved in OpenSpirit v3.2.2).
• The OpenSpirit data key for non-primary Z 2d seismic horizon properties does not get updated upon export.

Technical Support

Please refer to the following resources for OpenSpirit information:

Web Support	www.openspirit.com/support
E-mail Support	support@openspirit.com

OpenSpirit Ocean Petrel Application Adapter is designated with U.S. Department of Commerce Export Control Classification Number 5D992.b.1