TIBCO OpenSpirit Adapter for Petrel Release Notes. Software Release July 2014

Transcription

1 TIBCO OpenSpirit Adapter for Petrel Release Notes Software Release July 2014

2 ii Important Information SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE. USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME. This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc. TIBCO, OpenSpirit, TIBCO OpenSpirit Adapter for Petrel are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries. All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only. THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM. THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME. THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES. Copyright TIBCO Software Inc. ALL RIGHTS RESERVED. TIBCO Software Inc. Confidential Information

3 Contents iii Contents Contents... iii Preface...iv Typographical Conventions... v Connecting with TIBCO Resources... vii How to Join TIBCOmmunity... vii How to Access All TIBCO Documentation... vii How to Contact TIBCO Support... vii Release Notes... 8 New Features... 9 Release Changes in Functionality Release Deprecated and Removed Features Release Migration and Compatibility Release Closed Issues Known Issues... 17

4 iv Preface Preface The TIBCO OpenSpirit Adapter for Petrel provides seamless access to more than twelve OpenSpirit-enabled data stores, including GeoFrame, Finder, OpenWorks, and KINGDOM. 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. The TIBCO OpenSpirit Adapter for Petrel is designated with U.S. Department of Commerce Export Control Classification Number EAR99.

5 Preface v Typographical Conventions The following typographical conventions are used in this manual. Table 1 General Typographical Conventions Convention Use TIBCO_HOME ENV_HOME OSP_ HOME code font bold code font Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The default value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco. Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. An environment home directory is referenced in documentation as ENV_HOME. The default value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco. TIBCO < ProductName > installs into a directory referenced in documentation as OSP_HOME. The default value of OSP_HOME depends on the operating system. For example on Windows systems, the default value is C:\Progam Files\OpenSpirit. Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example: Use MyCommand to start the foo process. Bold code font is used in the following ways: In procedures, to indicate what a user types. For example: Type admin. In large code samples, to indicate the parts of the sample that are of particular interest. In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable disable]

6 vi Preface italic font Key combinations Italic font is used in the following ways: To indicate a document title. For example: See TIBCO ActiveMatrix BusinessWorks Concepts. To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal. To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C. Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q. The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances. The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result. The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

7 Preface vii Connecting with TIBCO Resources How to Join TIBCOmmunity TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to How to Access All TIBCO Documentation After you join TIBCOmmunity, you can access the documentation for all supported product versions here: How to Contact TIBCO Support For comments or problems with this manual or the software it addresses, please contact TIBCO Support as follows. For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site: If you already have a valid maintenance or support contract, visit this site: Entry to this site requires a user name and password. If you do not have a user name, you can request one.

8 8 Release Notes Release Notes Check the TIBCO Product Support web site at for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request one. You must have a valid maintenance or support contract to use this site. Topics New Features Changes in Functionality Deprecated and Removed Features Migration and Compatibility Closed Issues Known Issues

9 Release Notes 9 New Features This section lists features added since the last major release of this product. Release The following are new features in Release Release is compatible with Petrel 2014.x. Added support for import of Stratigraphic Column to either the Well Tops folder or the Stratigraphic Chart Folder via OpenSpirit Data Selection Events. Export and Refresh from external are not supported yet. Enabled update (save to external) of well logs with an OpenSpirit datakey. Enabled update (save to external) for 2d horizons with an OpenSpirit datakey. Added option to skip over well picks whose associated horizon is not already in the well top folder s stratigraphic hierarchy. Provided a firewall exemption script in the Adapter s installation directory as goby to setup firewall exemption rules.

10 10 Release Notes Changes in Functionality This section lists changes in functionality since the last major release of this product. Release The following are changes in functionality in this release. Fractional shotpoint values will be preserved in the SEGY file for 2d datasets. User-defined properties are being used to store the OpenSpirit attributes for well logs. These user-defined properties can be displayed in Petrel s log attribute spreadsheet. Several of the OpenSpirit attributes for well logs are now mapped to pre-defined Petrel properties: o TraceVersion will be mapped to log version o DataSource will be mapped to log source o TraceProcess will be mapped to log type The OpenSpirit WellVelocity s Source attribute is added to the list of attributes in the OpenSpirit Properties tab for Checkshots. The OpenSpirit SpudDate attribute for wellbore is now mapped to Petrel s predefined property Spud date. The OpenSpirit WaterDepth attribute has been added to the list of user-defined properties for borehole on import. The OpenSpirit attribute Strat column name has been removed from well picks because a pick may be associated with a horizon that s in multiple strat columns. The export dialog for 3d volumes and 2d datasets no longer allows overwrite if the volume/dataset has a match in the export project. The Petrel 2d dataset s CDP array will be populated with trace numbers instead of shotpoint values if the dataset had been imported from OpenWorks. The Petrel Adapter s version, the OpenSpirit Runtime client and master versions will be added to the history record for all the data types on import. In the OpenSpirit Settings dialog, the Restore to Defaults for the If missing azimuth north reference option is to NOT assume any, which will result in data not being able to import. Users have to make an explicitly decision on what to assume. Using the msi will install the Adapter for all users. Option to select a single coordinate transform has been removed from the OpenSpirit Settings dialog since Petrel has been supporting compound transforms for several releases now.

11 Release Notes 11 2d horizons without any primary geometry can now be imported into Petrel. The Z values will be set to 0 for time and Petrel project SRD for depth.

12 12 Release Notes Deprecated and Removed Features This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features. This section also lists features that are removed (if any). Release In the OpenSpirit Settings dialog, the option to create stratigraphic column upon import of well picks has been removed because they may be associated with more than one stratigraphic column. If users had that option checked from previous release, they will get a warning dialog when connect to OpenSpirit.

13 Release Notes 13 Migration and Compatibility This section explains how to migrate from a previous release to this release and version compatibility. Release There are no migration procedures issues in the release; the previous version of the Adapter will be uninstalled during the new installation procedure. Release is compatible with any operating system certified to run the following Petrel versions: Petrel Prerequisites that must be installed on the System running the Adapter are: Petrel OpenSpirit Runtime The following table describes the TIBCO OpenSpirit Adapter for Petrel version compatibility matrix: OpenSpirit OpenSpirit 4.0.0, 4.0.1, Petrel 2010.x 20.0.x Petrel 2011.x 20.0.x Petrel 2012.x Not Supported OpenSpirit Petrel 2013.x Not Supported Not Supported Petrel 2014.x Not Supported Not Supported Adapter version

14 14 Release Notes Closed Issues The table in this section list issues that were closed in the named releases. Closed in Release CR # Summary Dip and azimuth for exported picks were not correct. Cannot create Petrel coordinate system if the project coordinate system name has "<" and ">" characters Removed the? Icon next to the logging level Cannot send all the 3d seismic horizon properties together into Petrel. We should print out when the processing of Data Selection event is done, no matter what the logging level is. TOAP should catch incompatible format exception for processing coordinate system. We should not allow "save to external" for pointsets since export is not supported Horizon property color is not being preserved Map well log attributes to predefined Petrel properties, if they exist. Like to add the "source" attribute for WellVelocity to the OSP Properties tab. Add option to skip over picks whose associated horizon is not in the strat column. Add WaterDepth to the list of attributes for wellbores on import. Incorrect display if the actual 2d dataset's starting time is not the same as the possible minz. Cannot connect to OpenSpirit if the OSP coordinate system key in the project is bad. When connect to OSP, we should always check that the Petrel project coordinate system matches that of the OpenSpirit system key Handling of concatenated transform.

15 Release Notes 15 Closed in Release CR # Summary Since Petrel can support compound transforms, no longer need option to select a single transform. Seeing "Cross-thread operation not valid" when accessing 2d/3d horizons in Petrel Using TOAP msi does not install for all users When creating user-defined properties for borehole, marker, and logs, one single property definition will be created per property instead of one per property per Petrel project The Timbalai systems are not being compared properly Discrepency on the default for "missing azimuth north reference" between the "Restore to Default" and the User Guide Add the TOAP version, the OSP client and master version to the history of each imported data type. Re-sending well pick after well bore UWI is updated does not show match and merge dialog. Like to use OW trace number in place of CDP in Petrel when importing 2d seismic via TOAP "List data before matching" option not working properly Non-seismic grid property failed to import if the data extent is smaller than the possible extent. Why is the 3d survey not showing up in the grouping list for 3d seismic horizons? 2d/3d horizon property values are not being unit converted properly. The right Petrel property template is not being used for 2d/3d horizon properties. The "timeshift" was not being applied to the time values when "save to external" is selected for checkshot. Multiple versions of CAL and CALI are not being named properly. Need to move the well log custom attributes to user-defined properties. Well log template in subfolder is not being honored when new curves are imported.

16 16 Release Notes Closed in Release CR # Summary Clicking on Ok button in the Settings dialog resulted in error if Petrel had not been connected to OpenSpirit Not able to import 2d horizons without primary geometry If comment is not in the configuration file, do not update the comment field on import. This allows clients to preserve their Petrel comments According to the SEGY specification, the Adapter should be generating big endian SEGY file Cannot load 2d datasets with "\" in the line name Need a better message when we can't send GIS event for 2d survey. Wells created with Petrel Well Engineering tools failed to transfer via OpenSpirit Preserve fractional shotpoint values Need indication that Data Selection event button has been pushed. Client would like to have Save to External enabled for log data type. The "state" symbol will be '?' instead of '=' for checkshots in the match and merge dialog since checkshots do not have history records in Petrel. Check for comments in the Adapter's configuration file before overwriting it with the comments from the external data sources on import. Do not allow overwrite for exporting 3d volume instead of showing errors. Petrel Petrel CCC CCC Well path was zigzagging when displaying it in time domain. Overwriting wellbore does not seem to overwrite correctly.

17 Release Notes 17 Known Issues The table in this section lists known issues in this release. Key OI 2452 PI OI 1031 OI 1046 OI 568 OI 1184 SMT Issue OI 1251 Summary/Workaround If copy a live-link 3d volume from a reference project to a working project using Reference Project Tool, user must first connect to OpenSpirit; otherwise, Petrel will crash. Importing multiple versions of the same well log kind will result in multiple global well log templates being created. 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. Importing 2d seismic DEPTH datasets displays both the dataset and a placeholder in the Petrel tree. The Adapter depicts holes in GIS polygons as its own polygon. The polygon representing the hole does not appear as a hole to the user. LastModifiedDate (LMD) for a Petrel Marker not updated when modified. Blank place-holder is created in the Petrel Input Tree when importing 3D Seismic Volumes. The Adapter does not support drilling targets. The Settings dialog for the Process OpenSpirit cursor tracking does not display. There are no settings for this process. The NAD27 transformation methods are listed twice in details dialog. Short_Time unit cannot be set to s Unable to export WellType to Kingdom data store. Exporting CheckShots from Petrel to a Kingdom data store does not account for any difference in Velocity Datum. Only one well log curve version can be exported from Petrel to Kingdom because the Kingdom data connector does not support multiple log curve versions. When exporting to a Kingdom data store 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. 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. 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.

18 18 Release Notes Key OI 1636 OI 2839 CR CR CCC CCC Summary/Workaround 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 Kingdom Suite Survey Management Mistie dialog, may have been applied. Kingdom data connector does 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. 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. Issues migrating unrealized 2d lines from Petrel 2009 or earlier versions. 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. Workaround: Either broadcast from the Horizon tab, or broadcast only the primary Z property from the Horizon Properties tab. 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. If the original coordinate system of the 3d survey is not compatible with the Petrel project coordinate system, clicking on the survey/volume will cause numerous error dialogs to pop up. There's warning sign by the OpenSpirit plug-in in the Ocean Plug-in Manager dialog about "Initialization time" being too high. The current threshold set by Petrel is 1 second. Any plug-in that slows down Petrel startup time by more than 1 second will have this warning sign. The OpenSpirit Adapter takes 1.5 seconds to initialize. When loading data via the Petrel Studio index, the load dialog shows that user can load properties associated with their 2d horizons as well. Currently, when 2d horizons are scanned using the TIBCO OpenSpirit Scan for Studio, 2d horizon properties are not captured due to performance issues. Therefore, checking the "loading 2d horizon properties" toggle still will not load any 2d horizon properties into Petrel using the Studio index. The number of navigation lines shown for the 2d survey's Statistics tab may not match the actual navigation lines in the Petrel tree. Under some circumstances, the global well log template names may have strange numbering.

19 Release Notes 19 Key CCC CCC CR CR CR Summary/Workaround OpenSpirit attributes whose values are null for 2d/3d horizons, are lost, once the Petrel project is saved. Stratigraphic Chart does not have the "OpenSpirit Properties" tab in its Settings dialog to list the OpenSpirit attributes. Problem exporting markers whose name has the single quote (') character. Need to rename in order to export. After exporting logs from the Adapter's Data Manager, the logs will be reordered in that tab and the selection after the export would not reflect what was exported. Missing TraceVersion when exporting logs via OpenSpirit to Studio database. CR = OpenSpirit Issue OI = Ocean Issue must be fixed by SIS in Ocean API CCC = SIS Customer Care Center Issue must be fixed by SIS PI = Petrel Issue must be fixed by SIS in Petrel