Chinaunix首页 | 论坛 | 博客
  • 博客访问: 3049884
  • 博文数量: 144
  • 博客积分: 10056
  • 博客等级: 上将
  • 技术积分: 2603
  • 用 户 组: 普通用户
  • 注册时间: 2006-12-13 14:20
个人简介

互通有无,共同提高。

文章分类

全部博文(144)

分类: LINUX

2011-11-18 11:06:36

Landmark R5000.8 $OWHOME下的联机帮助文档有:/docs97.9M,主要为pdf格式;/help521M,主要为html网页格式,包括几个视频文件;其它十几个应用模块的相应文档。

 

其中docs涉及OpenWorks工区、数据管理及应用集成;help介绍DecisionSpace DesktopDSD),即一种可视化、解释、建模桌面环境。

 

下面给出几个截图:

 

这是OpenWorks帮助文档导航书签

 

 

这是DSD帮助文档导航书签

 

 

 

这是联机文档附带的几个视频:

 

 

 

以下视频听写文本,由山定子听写,罗斌老师校对:

 

Getting Started with DecisonSpace Desktop

Getting around the workspace

1. Using the Interface
    2. Working with Windows
    3. Working with Drag and Drop
    4. Loading and Displaying Data
    5. Using the Inventory Task Pane
    6. Basic Interpretation

 

1. Using the Interface

 

Verbatim Recording
Welcome to DecisionSpace Desktop 5000.8. This Getting Started video introduces new and experienced users to concepts and interface you throughout the software.  For the experienced user, you know there is a change in the software’s Look & Feel.

 

In this release, we’ve provided new functionality to allow you to select from two different interface palettes, Dark and Light.

 

The dark interface is a default look, but you can quickly switch to light by clicking the Window menu, and selecting Light. You can switch back at anytime during your session. When you end your session,   the Look you’re using becomes default look thereafter until switched again.

 

DecisionSpace Desktop contains many of the same components as you become familiar within other Linux and windows applications.

 

There's a common menu bar. A horizontal tool bar that can be displayed on one to three rows, or it can be torn off to float on your desktop.

 

There's a status bar at the bottom of the window. On the left and right sides of the window are task bar tabs containing additional functionality within task panes.

 

In the center of the window is the workspace.  This customizable workspace is made up of tab tiles that contain views.  Display here are three of the four views --cube, map and section.

 

To the left, there is a vertical tool bar that holds functionality for the active view.  If we switch between views, you can see that there are tool bar changes to reflect the options available for that view.  Only one view and one vertical tool bar is active at a time. Active view is an important concept in the DecisionSpace? Desktop, so let’s discuss it in more detail.

 

There are visual indicators in several places throughout the desktop to communicate what views are active. Orange is a colour indicator and tags are used to describe the view. Notice the tile of the view sets upon is outlined in orange when it is active, and so is the view’s tab.  Also any open task pane’s title bar will contain the name of the active view.   So will some of the dialog boxes within the software as you open them to select, load or work with data in the view.

 

We recommend you begin to learn the software by using the Workflow Catalog.

For this demo, we switch to the Light interface. The Workflow Catalog task bar tab is active as it is indicated by the orange tab. By clicking and expand the entire tree icon, we see familiar tree structure which contains actions and information grouped by categories of workflows.

 

We’ll use Structural Interpretation, and within this category there are sub-category nodes.

 

We’ll use Fault Interpretation for our example.  We recommend that as a new user you go through each workflow from the top-down. Within Fault Interpretation are two workflows: Fault Interpretation On Seismic Slice Data, which is an action node, and QC Display, which is a discussion node.

 

First we’ll do the action workflow. We’ll click MB1 on Select Seismic Data.  Notice the tool tip describing the action the system will take. Notice at the bottom panel of the task pane has instructions regarding this node.  In this case, we are instructed to click this node again to select the seismic volume for this project.

 

The reading pane has embedded hyperlinks, which when clicked, take you to online help pertaining to the steps in this workflow. Discussion nodes,like QC Display, also contains hyperlinks to online help.

 

If you are looking for specific workflows or actions, type the word in the Search Field and click the Magnifier icon.  The first reference will locate the item in the workflow catalog; click the Binoculars icon to find next instance, and click the Next icon to go to the previous instance.  One last icon to mention is the Hover icon, which when clicked, automatically expends and collapses its various nodes as you move your cursor across; click it again to turn it off.

 

 

2. Working with Windows

 

Verbatim Recording:
This movie quickly introduces you to use Tabs and Windows. DecisionSpace Desktop software recognizes geologic and geophysical interpretations often require multiple- workflows that integrate with preferred applications and data within and across domains.

 

Therefore this software allows you to open and work within multiple- windows at once. We’ll learn more about the simplicity of using these windows, but also watch for specific features that can improve your session.  The software uses a numbering system to track both windows and tabs, as you can see our session launch with our first window 1.

 

If we would either launch another instance of the application or create another window using the File- New Window option, or launch new map view from the Inventory tree, the system would consecutively number each window. Now close window 1.

 

I have an option to dock this window, which would mean docking the map tab to window 2, or to close I will choose to close without docking.

 

From window 2 or opening a New Window, notice the window is numbered 6 because the system has tracked my opening five other windows since starting the session.

I used a single map view for these examples, but I could have opened each window with a separate view. I’ll start with the session manager while I select to open my session with the single map view.

 

Now use File menu to open my next set windows. By opening several windows, I can separate and mount additional monitors or work with different project data in each one. Then, if I decide I need space for additional applications, I can regroup the tabs onto a single window by closing and docking the windows on any of the other windows.

 

How to open a new map tab from the File—New Tab menu.  If too many tabs displaying in the tile, a set of scroll back and forward arrows are up here.  I have an additional way of opening new window on the fly from the existing tab.  Here I want to make my map’s depth tabs into a separate window. I click on the tab, and using my left mouse button MB1; I drag the tab above my entire window and position it underneath the other window to have a better view.

 

Notice since this was a tab within the window, and I am now making a separate window, it becomes child of the previous window and it is noted as such by 1.1 sequential numbering on the title bar.

 

We still have the relationship of the tabs in window 1 as you can see when you create a slice to display in section view.  I use a crossline selection icon on the tool bar, pick my area, and click the middle mouse button MB2.

 

Now I have two map views: one on a separate window, and the other still attached on my first tile.  I want to now display time domain for a map view, I select the upper map view tab, and then click the select domain dropdown box and select my time domain.

 

An easy way to adjust tabs and tiles is by using the Tab Manager, or I could move the columns and rows. I can rename a tab, or I can close the individual tabs and tiles.


    3. Working with Drag and Drop

 

Verbatim Recording:
This movie introduces you to use Drag and Drop within the DecisonSpace Desktop.  You’re probably familiar with the concept of drag and drop in object from other applications.  But you’ll see how  dragging large group of files into views or tables within DecisonSpace Desktop saves you time.


You must be setup to use all three buttons.  The left button is called the MB1. The middle mouse button, sometimes scroll wheel, is MB2; and the right mouse button is MB3. MB1 and MB2 are used to throughout the software for dragging and dropping.


Quickly stated, MB1 is to use to drag and drop a single file into a view or a table. MB2 is to use to drag and drop multiple files instantaneously.   Let’s look at the two main tree structures used in the software, Inventory and Select Session Data.


The Inventory tree works between data items and views when the dragging and dropping is involved. Here I’ll drag a single horizon into my cube view using MB1.


Now I’ll select multiple continuous faults by highlighting them with the Shift key and MB2, and then dragging the group into the view.  The Select Session Data dialog box works this way as well with dragging objects into the views; however, I can also drag files from table to table, or directly back into the Inventory tree.


    4. Loading and Displaying Data


Verbatim Recording:

This movie introduces you to use Loading data to your session. DecisonSpace Desktop has a number of data loaders available for many parts of the application.
Loading data items is often based on where you are in your workflow.

 

We are going to quickly look at the main methods for loading data. Data is one of your company’s greatest assets that can be  intimidating when first viewed in entirety.  That’s why the DecisonSpace Desktop software, in conjunction with the OpenWorks, allows your project managers to define and specify data for each project in use. This is where our session begins.

 

I have two separate instances of the application opened in order to demonstrate the relationship between project data and a session.  Here is a session manager prior to launch and here is a launched session after clicking the OK button.

 

I was assigned a district and a OpenWorks project. After that I’ll choose specific data for my session. As you can see I have a number of choices my interpretation project.

 

Since all data encompasses all of these projects, it might seem quicker to select it and then drill down once in the application, but choosing all data may load data items not necessary for this interpretation. Unless you are looking for regional project view, all data is probably more than you need for your session.  I’ll choose project specific to my interpretation that also loads my survey automatically.

 

While the quickest and most convenient way to load data is through the Inventory tree, the green plus sign allows you to quickly choose from the most recently used list or from the option More Data Types. You may not have a list of items as this is one of your fist sessions.  However, More Data Types is a fast way to open the selected session data dialog box without leaving the Inventory tree.

Let’s look at loading another data item to our session. Remember active view is very important.  As we load data, we need to keep in mind what we were in and also what domain we were in. Here are the main cube view in Depth domain.

 

Notice my data item is in blue text. I’m going to use recently used horizon data type. Because I have a large number of horizons to choose from, I’ll use the table tool to sort my list by the Attribute parameter.   I select my depth horizon in displaying cube view. Now I’ll switch to map view; change my domain to time and select my time horizon. It displays in map view.

 

I’ll load faults in another way from the Inventory tree. I highlight the data type Fault in clicking the MB3. I’ll select Add Faults to Session Data from the popup menu.

 

I want several of these faults, so I hold down my shift key and select them in the table. With the faults highlighted, I don’t have to hold the shift; I can just drag the group using my middle mouse button, MB2, and drop the faults into the cube view.

 

The Inventory tree uses the right mouse button,MB3, for various operations; I select my seismic data and click MB3.  I’ll load new inline probe to my display.

Although I’ve been using the Inventory tree to load my data, you can see the data is being loaded for the select session data dialog box. This is the storage container for your data items. The reason is started with the Inventory tree is because selection is more specific and limited, so it is not to be overwhelming. But there will be times when you want to see all your data types at once in order to make selections and to add it.

 

I can open the Select Session Data dialog box from the file menu, or click the Select Session Data icon. This time I want to load wells.

 

I’ll select the Well List data type. Select my wells; I’ll drag my data item to my cube view. I used all wells from my selection because I know its data items, but we recommend you avoid  using all wells unless you know the full extend of the well list.

 

A powerful feature for the select session data dialog box is the ability to control aspects of an object to display parameters at the same time you’re loading it into a view.

 

Here I will select several faults using the shift key and dragging and dropping with MB2 into my view. I can choose to uncheck, the visible box, next each fault and click Apply to see the changes, or I can use the combination of this dialog box and the inventory tree to set my display.

 

Using the select session dialog box I can choose various parameters depending on the data item to apply.

 

A third convenient method for loading data is an I-Set feature, and an interpretation set allows you to organize and quickly load project data you use most often. It’s a list of data items you place in customized folder using the tool’s tab Interpretation Set option, or want to see both inventory task pane and the I-Set task pane at the same time for this demonstration, I’ll use MB1 to move my task pane below the inventory tree so we can watch it build.

 

To demonstrate the speed with which loading data using I-Set has, I select the load data session icon on the tool bar.

 

Now with the single click I loaded all the data items used in our previous examples.

 

By creating an I-Set, you can make a large groups data objects available for yourself, others in any sessions within the project.

 

The last data loader we’ll use is the interpretation task pane. I’ll use the same data items I’ve used in previous examples. Notice nothing is loaded in the inventory tree yet.  I open the interpretation task bar tab and the interpretation task pane displays. First I’ll select Horizon Interpretation to load my horizons. I’ll click the sample data loader icon on task pane and now I select the horizons. Using MB2 or dragging and dropping them into my map view and click OK to close the dialog box. Next I’ll click the Fault Interpretation icon and then select the sample data loader.

 

I’ll select my fault in MB2 and drag and drop. As you can see there are other data types in the interpretation task pane to choose from, but it is more limiting than the previous data loaders that are using the interpretation task pane assumes you will do more than load data items. You’ll also add and interpret them. 

 

Again your workflow will eventually determine the preferred method for loading data to your session.  DecisonSpace Desktop allows you to build your confidence and select your methods as you learn with the software.


    5. Using the Inventory Task Pane

 

Verbatim Recording:
This video introduces you to use Inventory task pane. For those you who are experienced DecisonSpace? Desktop users, you’ll notice that the Inventory Tree has new look and feel.  This incorporates the latest techniques in  usability design. The same functionality exists, but with the reduced needs for horizontal scrolling and increased ability to quickly scan for data using visible and color-bar coded objects.

 

When we initially launch DecisonSpace Desktop, the Workflow Catalog task pane is opened by default. We’ll click the Inventory task bar tab to open the Inventory task pane. The task pane contains navigation tree which can contain large data list that are already loaded from one of the data loaders, the workflow catalog. Select session data, the quick data selector, the interpretation task pane, or an interpretation set.

 

Data types make up the inventory tree, containing within the data types  are data items. For this quick demonstration, we’ll only view items within data types faults, horizons and 3D survey. Refer to the online help regarding individual data types, such as Frameworks, wells and any other data type you want more information about.

 

By default, the application displays all assets. But look at the map view, which is also the active view, and the data displayed. Since we now may want all these faults displayed as we progress our interpretation, we’ll hide most of these by toggling off the visibility indicator next to them.

 

Here I have a long list of faults, so it’s easier to use my right mouse button, MB3, on faults, and then select hide all, and then select each data item to display. Watch the map view as I make my display selections.

 

Let’s discuss how the active view and the Inventory tree work together. I have been displaying data known in the map views, so now let’s see how adding another view in this case cube view works. I hid all the individual faults in the Inventory Tree, so that no data is displayed. Notice the map view is the active view. Now select the single fault to display.

 

  It displays in map view but not in cube view. I select cube view now and you can see the indicator is gray, or toggled off for the same fault. The fault is there because I loaded all the data into the session, but I can’t choose to display the data based on the view on main.

 

Now toggle the same fault ON to display in cube view. Displaying data in a view main involves more than simply toggling on the indicator in the inventory tree. If you can’t see a horizon for instance, you may want to determine whether other criteria have been met, such as the main compatibility, or the surveys are loaded, your datum, or what the display order is.

 

DecisonSpace? Desktop is domain specific. You can choose either time or depth when starting a session. When the desktop opens, the domain is displayed in the select domain pull down box. Time is annotated as two-way time (TWT); depth is annotated as TVD or TVDSS.  If you’re in correlation view, there are others.

The previous example used only depth data. Now switch my domain to TWT and load the inventory tree with mixed domain data. I’ll use the quick data loader by clicking the green plus sign on the inventory task pane. The drop-down shows my most recently used items, and I choose to add faults.

 

The select session data dialog box for faults opens. By adding data from the inventory tree using the quick data selector, I can specify what data type items I want to select from. Since we worked with this fault and depth previously, let’s now view it in the time domain created data item.

 

Remember I’m still on map view, indicated by the orange tab and by the title bar on the dialog box. I’ll click OK. We’re viewing the fault in a map view in time now; but it will be nice also view the data in 3D.

 

I’ll click on the Cube view tab to make it active and click the depth data type item and now this fault is displayed in both a time indicated in black text and depth indicated by blue text domain.

 

Although the inventory tree looks simple, it is actually quite powerful. By click on any data item using MB3, we can add or load and display objects. Using the same fault as an example, notice the choices I can make regarding this fault.

Let’s click Edit. The interpretation task pane that was previous closed opened. We’ll double check that we’re in interpretation mode.  I’m now in fault interpretation that fast. All the points in fault in edit mode as shown by the red points. If I move my cursor over the object or fault, I can then begin to edit individual segments. If I’ll click MB3 well over the object, I have multiple options for working with this fault.


    6. Basic Interpretation

 

Verbatim Recording:
This movie introduces you to use the Basic Interpretation concepts and DecisionSpace Desktop interface. Provided with a rich arrays of interpretation tools that help you to get the most study of your project data. First, the Workflow Catalog, which was demonstrated in the introduction movie, contains several interpretation workflows. Second, the on-line help system is to design to quickly give you a step-by-step procedure used to set up and complete your interpretation.

 

We’ll begin with the simple horizon interpretation. We’ll use the default type layout to pick in the section view.  and we’ll do our review in the map in cube views.  The first question we might ask ourselves as a new DecisionSpace Desktop interpreters is what I have got to work with.   We opened the new session with 3D surveys, but we haven’t selected our seismic data yet. We’ll start with loading the seismic data from the select session dialog box. We’ll collapse our two task panes so only a view is displayed, and we’ll arrange our tabs. Let’s take a quick look at what seismic data we’ve loaded. One way is to use the section from this dialog box. Using the inline tab, we select the line number to start our review, and we’ll use the step control tool to quickly look at our data by entering 10 as our incremental value. We step through until we get to the end.

 

Now we want to look at our seismic data from a cross line orientation. We start at a line number as step through quickly. Now let’s see how quickly you can interpret a horizon in the simple data area using the same data set and pick this blue event.

 

First we open Horizon Interpretation and click the create new horizon icon. The system automatically loads horizon using the default name. We want to set the Onset value to Maximum since our amplitude is positive. And let’s double check the interpretation mode is toggled on. Notice though a Shortcut Keys in the task pane used to interpret it, we are going to select and pick in both directions on our horizon using the control key plus MB1 and click. We’ll save our interpreter’s horizon value to the OpenWorks data base. We’ll use special tracking tool in the interpretation pane called area track to extend our interpretation.  We’re going to use entire survey and we’ll accept the rest of the defaults.  After area track is finished, we close the window, and we’ll review in the map view.

 

Let’s display the new horizon using the inventory tree visual control toggle. We see how we can easily and quickly interpret simple horizon.  Since we finish with our horizon demonstration, we’ll remove it from our display. During the data review, we’ve noted the number of faults in a 180 to 2000ms range. In the section view, we’ll select a section from list line 100 to work within the inline orientation. For this data we’re going to pick fault segments on every fifth inline using even increments to enable us to quickly return to particular fault segments later.

 

Changing the color map can highlight the details of interest. You may want to select a different color bar to more easily see what you want.  We’re going to pick these faults and later interpret a horizon through them. Here we see a number of faults. We’ll pick one to interpret. First we enter a fault interpretation and create a fault. We can change name for ease identification and it appears on our fault table. We’ll pick our first fault segment by clicking MB1, releasing the mouse button and clicking again at the end of the fault segment with MB2 to complete the fault segment. Step forward five and pick our segment again. We’ll continue picking and step in it until we no longer clearly see our fault.   We’ll back up review our picks and pick in the opposite direction until we don’t see it. We’ll return to our studying inline.  We see additional faults, there, there and there.

 

So let’s create most of all faults to pick. We’ll start the counter at 2 and then enter 4 as a number to create. Click Generate Fault Names.   Notice fault created are displayed in fault table and we are in interpretation mode. With fault 02 selected, we’ll pick in the same manner done previously.

 

Now we step through picking our fault segments. Basically, we continue picking  and editing until we are satisfied that we have picked all of our faults.  We’ve picked on one inline. So we now want to complete the cross line pick.  We choose this play as pierce points.  We turn on visibility and we see our fault. Next we want to go to cube viewto quality control our fault picks.

 

We will return to line 100 to pick the third fault.  We’ll do several edits along the way until we’ve picked all of the faults.

 

In this example we want to review our fault picks so we can display them in map view. From the inventory tree we’ll use MB1 and select all our faults, and then using MB3, we’ll select hide, show selected, which automatically displays in this map view all of our picked faults. Now we can use cube view for our final quality control review. We’ll select all of our faults again in the inventory tree, and display them in the cube view. We’ve added a number faults to data set. This time we’ll going to do our horizon interpretation between faults. We’ll select horizon interpretation and quickly create a new horizon. We pick the horizon between the fault segment using MB1 and then MB2 to end it. We go to the other side of the fault segment and do the same thing. We continue doing this until we’ve picked between all of our fault segments. DecisionSpace Desktop contains a number of tools, such as correlation tool, to help you with picking a horizon with fault segments. Let’s check map view. We’ll turn on all of our faults. We haven’t area where we are not seeing faults so we want to now select a cross line section. We click MB2 to open the cross line and then we click the section’s tab. Now we’ll see our cross line section with our pierce point. We go back to our inline orientation and pick up starting point at 100 and increment by 5, and we’ll pick it again. We’ll continue picking the horizon and step in through it until we finish it. You can always re-pick the segment if necessary. Now we’ll return to our horizon and map view to check our seed points.  Now we go to the cube view for a final quality control. Now we’re going to use powerful tool for our fault to horizon called ezTrackerPlus, located on the tool’s menu.

 

We’ve selected our seismic volume and on the horizon control tab, we’ll select the Block at Faults option. Switch to the Tracking tab. We accepted faults and click Run ezTracker Plus. We’ll turn off our seed points to demonstrate our final horizon and review it in cube view, zooming in.

##################

Bugs of Landmark R5000.8 and a few debugging tips
http://blog.chinaunix.net/uid-124509-id-61960.html

阅读(13295) | 评论(1) | 转发(0) |
给主人留下些什么吧!~~

perfectswpuboy2015-01-17 13:58:37

大师,可否请教下R5000.8的相关问题呢。。。