Version 2010.3.1
of the
TIBCO OpenSpirit® Adapter for Petrel
(Formerly OPAA 2010 SP4)
Release Notes
Release Date: March 18, 2011
The TIBCO OpenSpirit® Adapter for Petrel (TOAP) provides seamless access to more
than 12 OpenSpirit-enabled data stores, including GeoFrame®, Finder®,
OpenWorks®, and KINGDOMTM.
End users can access data
across multi-vendor and cross-disciplinary data stores and applications in a
single step, without the need to learn multiple user interfaces. Petrel users
can now be liberated from the mundane and time-consuming task of searching for
the right data to load into Petrel.
Since the acquisition of OpenSpirit Corp by TIBCO Software our product names have changed. The Ocean Petrel Application Adapter (OPAA) was renamed to TIBCO OpenSpirit Adapter for Petrel, and will appear so in future releases of this product.
Overview
This release of the
TIBCO OpenSpirit Adapter for Petrel contains all fixes from previous versions and
service packs and can be installed as an update to any previous OPAA 2010 or as
a standalone install. TOAP 2010.3.1 must be run with OpenSpirit runtime version
3.2.1 or higher. It offers enhanced workflow possibilities and ease of use for
both new and existing customers.
Release
Highlights
- Improvements in OpenSpirit attribute refresh and OpenSpirit data key relinking
- Greatly improved workflows for users migrating to OpenWorks® R5000 from OpenWorks® 2003.12.
- Atribute refresh and key relinking imporved to include seismic and interpretation stored in Petrel subfolder structures.
- Improved Petrel project access time after attribute refresh.
- Improved performance of the OpenSpirit data manager.
- Provided a better workflow to clear unwanted OpenSpirit keys.
Notable
Resolved Issues - TOAP 2010.3.1
(OPAA 2010 SP4)
- Fixed problems writing back 2d interpretation to OpenWorks® 2003.12 where the interpretation crosses more than one 2d SeisWorks 2003.12 project. Details: Due to 2d SeisWorks devkit limitations, interpretation can only be written back to one 2d SeisWorks project at a time. A dialog for selecting a specific 2d SeisWorks project was implemented to more easily identify 2d seimic target projects for OpenWorks® 2003.12 workflows. If multiple 2d SeisWorks projects are used in one TOAP session, write-back jobs must be broken down by 2d SeisWorks 2003.12 project and submitted separately. Even with this fix some workflows writing back 2d interpretation to OpenWorks® 2003.12 remain problematic. TIBCO OpenSpirit® runtime version 3.2.3 or higher is required (25674, 25355).
- Fixed a problem sending 3d horizons from Petrel to ArcGIS as an OpenSpirit data selection event (25708).
- Fixed a problem browsing collections that caused error messages when connecting to OpenSpirit (25569).
- Fixed a problem recognizing 3d volumes that exist in subfolders when relinking keys (25435).
- Fixed a problem saving extended attributes for 3d seismic horizons after closing and reopening the Petrel project (24420).
- Fixed a problem getting the correct Sesimic Reference Datum from OpenWorks R5000 when re-importing 3d seismic horizons (25686).
- Fixed a problem updating attributes when Refresh All Attributes is selected for non-seismic horizons (25706).
Notable
Resolved Issues - OPAA 2010 SP3
- Fixed a problem where no replacement velocity dialog was presented to the user when refreshing a checkshot, horizon, or fault (24876).
- Fixed a problem where OpenSpirit extended attributes for 3D Horizons were lost after saving, closing, and reopening a project (24420).
- Fixed a problem with special handling of well picks when using save to external (25079).
- Fixed a problem that caused Java heap space errors when exporting a large group of wells to OpenWorks 2002.12 (24998).
- Fixed a problem displaying all 2d seismic lines and datasets in the data manager when the lines and datasets existed in multiple folder levels in the petrel tree (25357).
- Fixed two problems with coordinate system recognition and conversions when selecting specific coordinate systems from the Petrel list (25383, 25420).
- Fixed a problem where a 2d or 3d horizon was renamed with the datastore name in the OpenSpirit data manager after export (25274, 25275).
- Fixed a problem where fault names were not updated in the OpenSpirit data manager when renamed in the Petrel tree (25245).
- Fixed a problem updating the well UWI in the logs and tops tabs of the OpenSpirit data manager after changing the parent well UWI in the Petrel tree (25203).
- Fixed a problem applying the proper color to a point object imported as a GIS event from ArcMap (25281).
- Fixed a problem checking for null values when exporting faults (24992).
- Fixed a problem importing Horizon Fault Boundaries that contain null values (24930).
- Fixed a problem where GUI displays were unreadable when large or medium font settings were applied (25395).
- Fixed a problem with inconsistent results when refreshing all attributes for 3d and 2d horizons, faults, and surfaces (25394).
- Fixed a problem where the log curve name did not match between the Petrel tree and the OpenSpirit data manager after refreshing all attributes (25373).
Notable
Resolved Issues - OPAA 2010 SP2
- Fixed a
problem that prevented an end-user to do work in a Petrel project if a
live-link volume was displayed upon save and close of that project
previously. The subsequent opening of the project attempted to get data
via live-link, but the project was not yet connected to OpenSpirit. This
caused the project to hang indefinitely (24943, 24961).
- Fixed a problem identifying and displaying OpenSpirit attributes for wellbores in subfolders greater than two levels deep (24972).
Notable
Resolved Issues - OPAA 2010 SP1
- Fixed a
performance problem opening Petrel project when OPAA is installed.
Provided an option to load the OpenSpirit attributes on Petrel objects
when connecting to OpenSpirit, rather than project open (24542).
- Fixed a
problem with being unable to import shared checkshots from a GeoFrame data
store in Petrel 2010.1. Now allowing an option to replicate the checkshot
on import as a workaround to Ocean/Petrel Issue 1723 (24699).
- Fixed a
problem listing the right data source after refreshing 2d horizon
properties (23225).
- Fixed a
problem deleting existing 2d lines when subsequent 2d line imports matched
existing lines imported with 2d horizons (23782).
- Fixed a
problem exporting non-seismic grids to GeoFrame (24601).
- Fixed a
problem with the index serializer that caused wellbore attributes to be
incorrect in the Well Manager (24419).
- Fixed a
problem mapping well symbols (24337).
- Fixed a
problem parsing the Petrel custom WKT string properly (24766).
- Fixed a
performance problem importing faults (10259).
- Fixed a
problem leaving some files still existing after uninstall (23564).
- Fixed a
performance problem building indexes for project with a large number of
log curves (24782).
- Fixed
migration problems from SIS plug-in to OPAA (24586, 24814, 24272, 24652,
23855).
Notable
Resolved Issues - OPAA 2010
- Exporting
2d seismic horizons into a target project that already contains portions
of that horizon may invalidate the existing horizon set. To that end, we
have disabled the export functionality of 2d seismic horizons in this
release. Export of 2d seismic horizons into an empty target project
functions as expected with OPAA 2009 SP2. (23748)
- Fixed a
problem saving migrated keys after the project is closed. (23750)
- Fixed a
problem requiring the default Petrel folders (Wells, Seismic, Well Tops 1)
to exist in the tree prior to import (23224).
- Improved
performance when opening Petrel projects with migrated markers (23751).
- Fixed a
problem importing fault point sets (23611).
- Fixed a
problem when deleting seismic from Petrel (23522).
- Fixed a
problem sending and receiving contours as GIS events (22919).
- Fixed a
problem sending well bottom and surface locations as GIS events (23637).
- Fixed a
problem sending and receiving objects with Z values as GIS events (22911).
- Fixed a
problem supporting Schlumberger Well Known Text strings for coordinate
systems (21973).
- Fixed a
problem with invalid compression factors when exporting 3d volumes in
Brick format (22422).
- Fixed a
problem displaying correct survey name for 3d seismic horizons in the
multiple export dialog (23165).
- Fixed a
problem sending mixed polygon/polyline features as a GIS event (22917).
- Fixed a
problem with match and merge after marker deletion (23547).
- Fixed a
problem allowing refresh from external option on 2d horizons existing
somewhere other than the default location in the Petrel tree (23119).
- Fixed a
problem sending and receiving faults as GIS events (23126).
Certified
Operating Systems and Prerequisites
- TIBCO OpenSpirit
Adapter for Petrel functions on any Operating System
certified to run Petrel 2009.2 Sep 11, 2009 or Petrel 2010.1 Apr 24, 2010 or Petrel 2010.2 Oct 28, 2010.
- Prerequisites
that must be installed on the System running the OpenSpirit Ocean Petrel
Application Adapter are
- Petrel
2009.2 Sep 11, 2009 or Petrel 2010.1 Apr 24, 2010 or Petrel 2010.2 Oct 28, 2010
- OpenSpirit
v3.2.1 or higher
Known
Issues
The following are the most
significant known issues at the time of the release of Version 2010 SP3.
- In
very rare cases, roundtriping of cropped 3D volumes from Charisma (import
to Petrel from Charisma, realize, crop, export to Charisma, import, and
realize again) causes the loss of amplitudes when realizing to a 32bit
format (8 and 16 bit are okay). Fixed in Petrel 2010.2.
- If
a 2d horizon GIS event is sent to ArcMap where placeholder datasets still
exist in Petrel, the geometries will be sent twice and appear as duplicate
lines in ArcMap (Ocean/Petrel Issue 1031).
- After
upgrading from OPAA2010 to OPAA2010 SP1 errors may appear in the Petrel
message window "Specified cast is not valid." These can be
ignored, and only exist the first time Petrel is opened subsequent to the
OPAA upgrade. The errors are not displayed when OPAA2010 is uninstalled
before the service pack is applied.
- Importing
2d seismic DEPTH datasets displays both the dataset and a placeholder in
the Petrel tree.
- Export of
data to Petra, GeoFrame, and Kingdom expects a password to be entered.
Cancel the resultant User Setup Wizard or run through and set passwords if
appropriate.
- Empty
"One-way time 1" log is created under wellbores when a wellbore
with a shared checkshot is imported and the activate checkshot on import
option is selected. A workaround is to turn checkshot replication on via
the Options dialog (Ocean/Petrel Issue 1723).
- Cursor
tracking events are not received by Petrel when sent from the OpenSpirit
ArcGIS Extension 2010.
- Unable to
migrate markers from OSP v2.9x to v3x due to improper key in source (Ocean
Petrel Issue 979). Fixed with Petrel 2010 and OPAA 2010.
- 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).
- 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.
- 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
time shift, phase rotation, and amplitude scale factor, which are all
defined in the KingdomSuite Survey Management Mistie dialog, may have been
applied.
- Kingdom8.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.
- Microsoft
Windows Uniform Naming Convention syntax is not supported when entering a
configuration file custom location on installation.
- 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.
- A change
in Petrel 2010 causes the directional survey calculation method to always
fall back to linear (Ocean/Petrel Issue 1612).
- When
deleting a well pick in Petrel 2010 an error is logged in the message
dialog. The delete completes as expected.
- Issues
migrating unrealized 2d lines from previous Petrel versions (Ocean/Petrel
Issue 1636).
- OpenSpirit
keys for markers are not honored after moving data using the Petrel
Reference Project Transfer tool. OpenSpirit has worked around this issue
by populating a new column in the marker spreadsheet with the OpenSpirit
key.
- If 2d
lines were imported into Petrel 2009.x from an OpenWorks 2003.12 datastore
configured in OpenSpirit 3.2.0 or higher, the shotpoint array is not
accurate. To resolve this issue, reimport the 2d lines using OPAA 2010.
- If
multiple 3d seismic horizon properties are imported into Petrel from the
OpenSpirit Horizon Properties tab, including the primary Z property, the
primary Z property loses its OpenSpirit datakey. To resolve this issue,
either broadcast from the Horizon tab, or broadcast only the primary Z
property from the Horizon Properties tab.
- When a 2d
horizon is imported into a custom folder (not the OpenSpirit default),
subsequent refresh of that horizon will place a duplicate 2d horizon in
the OpenSpirit default Interpretation folder.
- Cannot
install both 32 bit and 64 bit versions of OPAA on the same machine.
- When
importing 2d horizon properties, the primary Z property is considered part
of the geometry, and therefore is not listed as a property in the Petrel
message log on import.
- The WKT for the MENTOR: TIMBALAI:N.W.Borneo RSO Timbalai system is incorrect and should not be used.
- Exporting 2d horizons export all the lines for the associated survey. Subsequent export of related 2d datasets results in duplicate 2d lines.
- Deleting the Well Tops 1 node from the Petrel tree yields an unknown error (Ocean/Petrel Issue 1880).
- Upgrading to OPAA 2010 SP3 means that OpenSpirit properties will no longer be sent when objects are broadcast as GIS events.
- Sending horizon data to Petrel and ArcGIS as a data selection event from the OpenSpirit data selector produces an error. Fixed in OpenSpirit ArcGIS Extension 2010.
- The ampersand and the less than character cause problems when the GISAttributeSchema.xml file gets parsed upon startup of Petrel.
Technical
Support
Please refer to the following
resources for OpenSpirit information:
OpenSpirit
Ocean Petrel Application Adapter is designated with U.S. Department of Commerce
Export Control Classification Number 5D992.b.1