workflows tutorial
DESCRIPTION
traningTRANSCRIPT
EXIT
VelPAK Workflows
Version 8.6
January 2011
EXIT
Trademarks and CopyrightsThis manual was produced by Seismic Micro-Technology Inc.
Version 2.0
July 2010
VelPAK software and documentation was designed and developed by Equipoise Software Ltd. on behalf of Seismic Micro-Technology.
www.equipoise.co.uk Equipoise Software Ltd, 3a Rathbone Square, 28 Tanfield Road, Croydon, Surrey, CR0 1BT. U.K.
The “Galleon” sample data is made courtesy of Shell based on the condition that no Party makes any warranties or representations with respect to the accuracy or completeness of any Data, and no Party shall have any liability to any other Party resulting from the use of the data, all risk relating thereto being on the Party using the data.The following trademarks may appear in this manual.The KINGDOM™ software and all of its components, 2dPAK®, 3dPAK®, 2d/3dPAK®, AVOPAK®, CGMPAK®, EarthPAK®, LoadPAK®, LogPAK®, ModPAK®, PAKnotes®, OpenKINGDOM Domain®, OpenKINGDOM Scout® SynPAK®, The KINGDOM Company®, TracePAK®, Tunnel L+®, Tunnel O®, VelPAK®, VuPAK®, are registered trademarks of Seismic Micro-Technology, Inc. (SMT).
Certain software programs incorporated in KINGDOM are proprietary products copyrighted © 1993 – 2007 by Seismic Micro-Technology, Inc. All rights reserved. Portions of data loading are copyrighted by Blue Marble Geographics. VuPAK includes OpenInventor™ and VolumeViz™ from the Mercury Computer Systems Incorporated. ModPAK includes SHAPES® from XOX Corporation.
Seismic Micro-Technology, Inc. 8584 Katy Freeway, Suite 400 Houston, Texas 77024 U.S.A. Tel: (713) 464-6188 Fax: (713) 464-6440 Internet Address: www.seismicmicro.com E-Mail Address: [email protected] Marketing:[email protected] Tech Support: [email protected]
iii
Tunnel L+ includes OpenWorks® and SeisWorks® Development Kit from the Landmark Graphics Corporation. Tunnel O includes OpenSpirit® FrameWork from the OpenSpirit Corporation. Portions of KINGDOM bitmap graphics are based on GD library by Boutell.Com, Inc. Further information about the company can be found at www.boutell.com. PAKnotes TIFF support is based in part on libtiff. Rock Solid Attributes™ is a trademark of RDSP I, L.P. Solid Attributes™ contains confidential, proprietary, and trade secret information of RDSP I, L.P. This unpublished work by RDSP I, L.P. is ii protected by the laws of the United States and other countries. Additionally, if publication occurs, the following notice shall apply: Copyright ©RDSP I, L.P., All Rights reserved. Microsoft is a registered trademark of Microsoft Corporation. Windows 2000, XP, and XP x64 operating systems, MS-DOS and SQL Server are trademarks of Microsoft Corporation. Oracle® Databases are registered trademarks of Oracle Corporation. OpenWorks, SeisWorks, Interpret 2000 and Interpret 2003 are registered trademarks of Landmark Graphics Corporation. SMT incorporates BMC® AppSight™ Black Box Technology in its software. BMC Software, BMC Software logos and all other BMC Software product and service names are registered trademarks or trademarks of BMC Software Inc. © 2007 BMC Software, Inc. All rights reserved. All other trademarks are the property of their respective holders. ©2007-2009 Seismic Micro-Technology, Inc. All Rights Reserved Worldwide KINGDOM and this manual are both copyrighted and intended for use by a single user or a single computer whose model is authorized by Seismic Micro-Technology, Inc. You are entitled to electronically transcribe KINGDOM CD-Rom to the hard disk of an authorized computer so long as KINGDOM and related software packages are operated on only one computer at a time. You are further entitled to electronically transcribe the CD to other CD(s) for archival storage only. Physical duplication of the KINGDOM software and SENTINEL is expressly forbidden. No portion of KINGDOM software may be incorporated into any other program. No other usage or transcription in any form is allowed without the express written permission of Seismic Micro-Technology, Inc. No portion of this manual may be reproduced, transmitted, transcribed or stored on any information retrieval system, or translated into any foreign language or any computer language in any form and by any means whatsoever without the express written permission of Seismic Micro-Technology, Inc.This document contains confidential
Misuse DisclaimerSeismic Micro-Technology, Inc. makes no representation or warranties of any kind with respect to this manual or The KINGDOM Software Package. Specifically, Seismic Micro-Technology, Inc. disclaims any implied or any other claimed warranties of merchantability or suitability for any particular purpose. Seismic Micro-Technology, Inc. reserves the right to modify. The KINGDOM Software Package and any of the associated user documentation at any time.
Acknowledgments Seismic Micro-Technology, Inc. wishes to gratefully acknowledge the contributions of the many amber software testers in preparing The KINGDOM Software. The enthusiastic Beta Testers, smoke testers, and the SMT Staff greatly appreciate their invaluable feedback and contributions.
iv
EXIT
VelPAK Workflow Wizard
KINGDOM 8.6 1
Main Points
EXIT
Main Points1. Pre-defined workflows can be set up and used with the simplest user intervention for each
or any Event Horizon.
2. Pre-defined Workflows often contain many other ‘nested’ workflows, that is workflows that run other workflows automatically and when required.
3. There is a pre-defined bank of Workflows to select from which can be used to run the major VelPAK processes. There is also a bank of Components which are drawn in to each workflow which contain repetitive routines of work, such as initializing the grids and displaying particular map types.
4. The user can edit the workflows as they wish. These workflows can be saved in the local project directory and will become the default workflows used in that project. The system workflows will not be written over.
5. If there is a workflow stored in the project directory with the same name as the system workflow, the one stored in the project directory will always be the one used in the workflow rather than the system parameter set. This allows the user to change displays and parameters as they wish solely for the selected project while retaining the main system’s integrity.
Quick Start1. Open your project or read data in via the TKS link.
2. Assign the Layer Definitions.
3. Go into the Workflow Module.
4. From the Workflows property grid tab the depth conversion method you want to use and bring it into the Workflow Canvas.
5. From the Nodes property grid tab bring in a ‘Start’ and ‘End’ node.
6. Join your workflow up so that it goes in this order; Start -> Workflow->End
7. Press the Run button on the Workflow.
2 KINGDOM 8.6
The Workflow Screen
EXIT
The Workflow ScreenThe Workflow screen is accessed by clicking on the Workflow Module icon at the top of the VelPAK window.
The default Workflow screen on entry is made up of four canvases (Workflow and three Scratch areas, initially tabbed one behind the other) and a number of fly-outs down the right-hand side of the canvas as shown in Figure 1.1.
Figure 1.1 Workflow Screen
Workflow Canvas TabThis is the main area where you can view, build and run your workflow.
Process Nodes building bricks are dragged from the fly-outs across to this window and arranged in the order the workflow is to process them.
The size of the workflow can be changed using the Tool bar options at the top of the Workflow window.
Scratch Canvas TabsThere are three scratch areas, used to set up rough preliminary workflows or parts of a workflow and to view the internal nested workflows of pre-defined workflows. Each Scratch Canvas works in exactly the same way as the main Workflow Canvas area — that is, data can be saved, run, edited etc.
Saving WorkflowsSaving your workflow will save the processes in your Scratch or your Workflow Canvas window, whichever is active, in one saved file. If you wish to save the process in all the windows, you will need to save them into four separately named files.
KINGDOM 8.6 3
The Workflow Screen
EXIT
Setting up a Pre-defined workflow to runThis aims to make you familiar with the setting up to run the pre-defined workflows.
1. Go into the Workflow tab; a blank screen will be seen as shown in Figure 1.2.
Figure 1.2 Workflow Starting screen
2. Click on the Workflows Property grid tab to the right of the main Workflows screen and pin it out and scroll to the top of it as shown in Figure 1.3.
4 KINGDOM 8.6
The Workflow Screen
EXIT
Figure 1.3 Workflow tab pinned out
3. Use the scroll bar to scroll up and down the Workflow tab.
The Workflows tab is showing you a list of pre-defined workflows under separate headings.
4. Open up the “1 Start Here” branch to find the example workflow ‘Simple Workflow #1.xml’.
5. Drag the ‘Simple Workflow #1.xml’ into the Workflow canvas area.
Notice the comments down the right hand side of the workflow to guide you as to what each node is there for.This workflow is set for a two layer depth conversion.
6. Note the method for each layer - Event 1 is “Curve IntervalVelocity v DepthToMiddle Multi” method and Event 2 “Optimize V0kz Residual Error” method.
Note: These have been selected as standard depth conversions - other ones can be used by selecting them from the Workflows fly out under the Depth branch.
7. Double click on the ‘Initalize All.xml’ in the workflow and this .xml will open up in the Scratch1 canvas as shown in Figure 1.4.
This is an example of a component workflow that the main workflows are made up of, which run tasks repetitive to all workflows.
KINGDOM 8.6 5
The Workflow Screen
EXIT
Figure 1.4 Selecting Workflow node into Workflow Canvas
The Scratch1 Canvas is now showing the nodes of the nested workflow that make up one component of the ‘Simple Workflow #1.xml’ - in this case the ‘Initialize All.xml’. In this case each of the boxes in the Scratch area is a node - not a component workflow - but it is very likely that a component workflow in the top level workflow will have further component workflows nested within it.You can tell the difference between nodes and component workflows because:
a. Nodes do not have the extension .xml following the name.
b. Node boxes are square and not rounded at the corners!
All the nodes in the Initialize All.xml can be found as separate nodes in the ‘Nodes’ flyout.
6 KINGDOM 8.6
The Workflow Screen
EXIT
Joining Nodes1. Click on the bottom of the Event1.xml node and drag the arrowed line that appears from the red
dot to the middle of the top of the depth conversion node as shown in Figure 1.5.
Figure 1.5 Joining the Workflow Nodes
KINGDOM 8.6 7
The Workflow Screen
EXIT
Running a WorkflowFor best effect you would want to detach the Workflow window so you can see what is going on in the Workflow as well as the rest of VelPAK.
1. Detach the Workflow window by pulling the tab away from the main VelPAK window as shown in Figure 1.6.
Figure 1.6 Detaching the Workflow window
2. Open up the Surface module so you can see the resultant surface displays from the workflow actions.
3. Run the Workflow by pressing the Run button at the top of the workflow screen as shown in Figure 1.7.
Figure 1.7 Workflow Run Button
You will notice the nodes in the Workflow canvas go red when they are in progress. In this case there is only one workflow node that contains all the actions that are to be done within this workflow, so the Interval Velocity v Isochron node stays red for some time while VelPAK processes through the nested nodes within it.
Note: The ‘Sooner’ data set does not velocity data within it so the ‘Start Here’ workflow will not work!
Run
8 KINGDOM 8.6
The Workflow Screen
EXIT
Viewing Generated DataWhen your workflow depth conversion has run it will have generated a number of data items for you to review. These are all stored under the relevant event slots in the Model Tree (usually to the left of your VelPAK screen) similar to the Model Tree as shown in Figure 1.8.
Figure 1.8 Model Tree showing contained data
For example:
• Grids - Depth and Velocity grids will be stored under the grid slots of the relevant events.
• XYZ Error values will be stored under the XYZ Error slots of the relevant events.
This data can be viewed in the Surface module by double clicking on the slot in the Model Tree containing the grid or XYZ values you wish to view and then making sure the Surface display is set up such that the contours or XYZ values will be displayed; as described in a previous chapter. Go Here for details.
Exporting the data back to TKSThe Grid data generated in VelPAK can be put back into the main Kingdom project. See section ‘Exporting TKS Data from VelPAK’ for details.
KINGDOM 8.6 9