Académique Documents
Professionnel Documents
Culture Documents
and
Exporting
February 2004
Trademark Notice
3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance,
Active Reservoir Surveillance, ADC, Advanced Data Transfer, ARIES, Asset Development Center,
Asset Development Centre, Automate, Asset Performance, AssetView, Atomic Meshing, Automate, BLITZ,
BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store, Data Manager, DataStar,
DBPlot, Decision Suite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner, DecisionSpace AssetView,
DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace PowerGrid,
DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservior, DecisionSpace TracPlanner,
DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Express3,
DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX,
DFW, DIMS, Discovery, Discovery Asset, Drill-to-the-Earth Model, Drillability Suite, Drilling Desktop, DrillModel,
DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, eLandmark,
Engineers Data Model, Engineer's Desktop, Engineers Link, EOS-PAK, Executive Assistant, ezFault, ezSurface,
ezTracker, FastTrack, FieldWorks, FZAP!, GeoDataLoad, GeoGraphix (stylized), GeoGraphix Exploration System,
GeoLink, GeoProbe, GeoProbe GF DataServer, GeoProbe Integrated, GES, GESXplorer, GMAplus, GRIDGENR,
Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, Landmark, Landmark and Design, Landmark logo and
Design, Landmark Decision Center, LandScape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Magic Earth, MagicDesk, MagicStation, MagicVision, Make Great Decisions, MathPack, MIRA, Model Builder,
MyLandmark, OpenBooks, OpenExplorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire,
OpenWorks, OpenWorks Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PlotView, Point Gridding Plus,
Pointing Dispatcher, PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power Interpretation,
PowerJournal, PowerModel, PowerSection, PowerView, PRIZM, PROFILE, ProMAGIC, ProMAX, ProMAX 2D,
ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, QUICKDIF, QUIKCDP, QUIKDIG,
QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RTOC, Real Freedom, Real-Time Asset Management
Center, Real-Time Asset Management Centre, Real Time Knowledge Company, Real-Time Operations Center,
Real Time Production Surveillance, Real Time Surveillance, RESev, ResMap, RMS, SafeStart, SCAN, SeisCube,
SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisXchange, Sierra, Sierra (design), SigmaView,
SimResults, SIVA, Spatializer, SpecDecomp, StrataAmp, StrataMap, Stratamodel, StrataSim, StratWorks,
StressCheck, STRUCT, Surf & Connect, SynTool, System Start for Servers, SystemStart, SystemStart for Clients,
SystemStart for Storage, T2B, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs,
TOW/cs The Oilfield Workstation, TracPlanner, Trend Form Gridding, Turbo Synthetics, VIP, VIP-COMP,
VIP-CORE, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX,
Web Editor, Web OpenWorks, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect,
WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in Control. Experience the difference, ZAP!,
and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark Graphics Corporation or
Magic Earth, Inc. All other trademarks are the property of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a
commitment by Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any
error that may appear in this manual. Some states or jurisdictions do not allow disclaimer of expressed or implied
warranties in certain transactions; therefore, this statement may not apply to you.
Landmark
Contents
10
14
14
15
18
Curves ...........................................................................................................
18
Grids ..............................................................................................................
22
R2003.12
Contents
iii
Landmark
24
Aliasing .........................................................................................................
26
26
27
27
Filters .......................................................................................................
33
38
43
44
45
45
46
46
46
47
54
54
55
56
61
63
R2003.12
Contents
iv
Landmark
64
64
65
69
70
73
73
74
77
79
80
80
81
82
84
85
87
88
90
91
91
R2003.12
Contents
Landmark
92
93
96
97
98
98
98
99
99
R2003.12
Contents
vi
Landmark
R2003.12
Contents
vii
Landmark
Index ....................................................................................................................
R2003.12
Contents
143
viii
Landmark
Introduction
Overview
In Stratamodel, you can import ASCII and binary grids, well data, and
seismic data. You can convert line data stored in MFDs (Master File
Directories, a storage device used by Z-MAP Plus and some other
Landmark products) to culture data for display. You can also load data
into an attribute model from ASCII files.
You can export ASCII and binary grids and extract attribute data to an
ASCII file, a GLK file, a pseudo log, or a grid. You can extract attribute
values from six adjacent cells and store them in a new field in an
attribute model.
This guide contains the following sections:
R2003.12
Introduction
Landmark
R2003.12
Landmark
R2003.12
Menu Options
OK
Global Exit
Return
enter startow
enter
projectname
click
highlight
select
double-click
triple-click
Landmark
Stratamodel Module
Page
wells
page 6
curves
page 6
grids
page 15
pointsets
page 15
page 24
R2003.12
Data Type
Stratamodel Module
Page
curves
Export Curves to OW
page 18
grids
page 22
Landmark
You can use Pointset Builder to build pointsets from 17 different types
of data.
Menu Option
Suboption
Paleo
Strat Unit Attributes
Strat Unit Isochores
DST/RFT
General
Pressure
Summary
Well
Completion
Fault
Header
Perforation
Pick
Pressure
Surface Elevation
Test
Total Depth
Well Production
Volume Record
Zone
R2003.12
Landmark
wells
curves
grids
pointsets
You can also build pointsets in Pointset Builder from 17 different data
types then export them to Stratamodel. (For more information, see
Building Pointsets on page 24.)
Imported well curves are resampled them to the resolution you desire
when you build your model. In many cases this means upscaling the
curve to one averaged point per layer in the model.
You can import more than one well and log at a time. You can load any
of the logs for multiple wells, or you can have the program show you
the logs common to the wells you have selected. You have control over
the depth units and mode, and you can limit the logs to specified
depths. You can also designate the depth interval.
To get curve data from OpenWorks into Stratamodel, follow these
general steps:
R2003.12
1.
2.
3.
4.
Select the wells when you create a well model. (See Selecting the
Wells on page 47 in Creating Displays.)
Landmark
You can use the tab and arrow keys to traverse this interface.
R2003.12
Landmark
Selecting Wells
Use the Wells panel to choose the wells you want to import.
1.
2.
R2003.12
Once you have selected wells, click Apply Selections. The curves
in the selected well files appear in the Log Curves list.
Landmark
2.
R2003.12
Select one or more logs to import. You can use the selection
buttons below the Log Curves list to help select them.
Landmark
depth
format for data
format options
Options Menu
R2003.12
1.
2.
10
Landmark
3.
Choose the depth range from the next three buttons on the panel:
Total Depth Range imports the entire log curve. This range
may vary between logs.
4.
R2003.12
11
Landmark
5.
R2003.12
12
Landmark
R2003.12
1.
2.
3.
13
Landmark
4.
5.
6.
Optional: To change the default null value, enter a new value in the
In a File, Export Empty or Null Values as field.
7.
Choose whether to use the common well name or the unique well
identifier for the wells name. This choice is offered to help
maintain a distinction between wells, since the OpenWorks
common well name need not be unique.
Length of Well Identifier
SM1 format limits the length of the well identifier to 12 characters.
8.
14
Landmark
R2003.12
15
Landmark
2.
Or the menu
3.
R2003.12
16
Landmark
4.
R2003.12
Selection
5.
Once you select grids and pointsets, click the Import Grids or
Import Pointsets button.
6.
17
Landmark
You can also use the Pointset Builder to export any pointsets you built
with it. (See Building Pointsets on page 24 for more information.)
Curves
Curves that have been imported into Stratamodel and modeled may
have been resampled to fit the resolution of the model. Using Export
Curves to OW, you can export this curve data to compare the curves to
the original or plot them in StratWorks. You can also use Export Curves
to OW to extract a pseudo well that you created in the 3D display and
plot it on a StratWorks section.
To export curves, follow these s
1.
R2003.12
18
Landmark
2.
Match
Button
R2003.12
3.
4.
19
Landmark
5.
Click the name of the OpenWorks well you want to associate to the
selected Stratamodel well. The OpenWorks well name now
appears in the left pane and an asterisk appears to mark the
associated Stratamodel well.
6.
R2003.12
20
Landmark
8.
The Depth Units panel shows the units for the OpenWorks well.
This field is read only. Set the Stratamodel depth units by selecting
them from the SGM Depth Units menu.
9.
R2003.12
21
Landmark
Grids
To export grids from Stratamodel to OpenWorks, follow these steps:
R2003.12
1.
2.
3.
Click the Grid File button and use the file selection box to select a
grid file.
22
Landmark
4.
5.
6.
7.
Click the Geo Name button to select the name of the surface, unit,
fault, etc. The StrataModel Grids to Export panel on the right side
of the dialog box changes its title to OpenWorks Geo-Name and
lists the choices for that grid. Select a name from that list.
8.
9.
Click the Grid Name button. The right-hand panel shows the
available grids that have that type, geo name, and map data set
name. Select a name from that list or enter a new grid name.
10. Click Show Export List button to see what will be exported.
11. Use the buttons below the export list to select grids to export.
12. When you have chosen the grids, click Export Grids.
13. To exit Points and Grids, click File Exit.
R2003.12
23
Landmark
Building Pointsets
The Pointset Builder extracts well data that can be described by points
from the OpenWorks database, which stores data for most Landmark
products. Once the data is extracted, Pointset Builder creates data files
called pointsets from it, extrapolating z values for x, y locations by
calculating them from surrounding points. This data can be used for
surface modeling, data operations, or plotting. Pointsets are sets of x, y,
z values, where the x and y fields indicate the location of the data and
the z field give the value of an attribute.
Many Landmark products create data that can be used for pointsets.
R2003.12
24
Landmark
You can use Pointset Builder to create pointsets from 17 different data
types:
Menu Option
Suboption
Paleo
DST/RFT
OW Surface/Fault Manager
StratWorks Strat Column Editor
General
Completion
Fault
OW Surface/Fault Manager
OW Surface/Fault Manager
StratWorks
Seisworks
Stratamodel
Header
Perforation
Pick
OW Surface/Fault Manager
Pressure
Surface Elevation
Test
Total Depth
Volume Record
Zone
Pressure
Summary
Well
Well Production
R2003.12
25
Landmark
Aliasing
You can use aliasing in the pointset for picks and isochores. For
example, you may know that interpreter AMZ calls the ASAND
formation, ASANDTOP. By aliasing ASANDTOP to ASAND, the
module knows that ASAND and ASANDTOP refer to the same
formation. Therefore, if you dont have an ASAND in a given well, but
you do have an ASANDTOP, ASANDTOP will be included in the
pointset.
Note that all of the profiles for ASAND will be accessed any time you
include profiles, regardless of where they were created.
Pointset Format
The file that Pointset Builder exports for use by Stratamodel looks like
the following:
!ow_point_set
!This file contains data for the L. BALMEI SURFACE.
#X - FIELD
Y - FIELD
SSTVD
WELL NAME
DATA SOURCE
624350.000000,5758380.000000,-7053.201172,1,FLOUNDER-1,JOE
626375.000000,5757515.000000,-6853.197754,2,FLOUNDER-2,JOE
628640.000000,5758140.000000,-7216.395508,3,FLOUNDER-3,JOE
630835.500000,5759084.500000,-6756.055664,4,FLOUNDER-4,JOE
626675.000000,5759125.000000,-7095.562012,6,FLOUNDER-5,JOE
625520.000000,5757835.000000,-6757.345703,7,FLOUNDER-6,JD
WELL ID
The fields are separated by commas and labeled by a header that must
include an identifier (!ow_point_set) that indicates to the program that
it is a pointset and an SSTVD (or MD) field. Once a pointset file is
imported into Stratamodel for viewing, Stratamodel looks for the depth
field (SSTVD or MD) You can display any data in the pointset, and
Stratamodel positions it using the SSTVD or MD field.
R2003.12
26
Landmark
Creating Pointsets
This section explains the general procedure for building pointsets. It
then is broken up by data type to explain the parameters that are
particular to each type.
General Procedure
The procedure for building a pointset follows.
R2003.12
1.
Set the depth units by selecting File Depth Units. The choices
are feet or meters.
2.
3.
4.
27
Landmark
R2003.12
5.
When you have chosen all the Output Specifications, click OK.
6.
From the Pointsets menu, select the data type for building a
pointset.
7.
28
Landmark
In general, the dialog boxes and reasons for selections for data
types are the same. The differences are:
Depending on the data type, some dialog boxes do not have the
panel called Filter Results, which tells how many wells contain
data with the filters you applied and how many of those wells
have duplicate data.
Each data type has different pointset fields that you can select.
You can select multiple fields.
The first step in selecting the parameters for the data type is to
choose the filters from those that are specfic to the data type. For
more information about the use of filters and the filters employed
by each data type, see Filters on page 33.
8.
9.
R2003.12
29
Landmark
11. In the Output Controls panel, choose from a list of Pointset Fields.
These are the actual fields that will be exported. For more
information, see Pointset Fields on page 38.
12. If the selected Pointset fields include any of the Depth z fields, then
the Pointset Creation Option allows you to select what data to
incorporate into the pointset, including picks, StratWorks fault
segments, and SeisWorks fault planes. Aliases apply picks from
surfaces aliased to the selected surface. Aliases are defined in
StratWorks Strat Column Editor.
R2003.12
30
Landmark
R2003.12
31
Landmark
18. Export the pointset: Click OK to export and close the dialog box
or click Apply to export the data, but leave the dialog box open to
make other choices.
R2003.12
32
Landmark
Filters
Generating a pointset that contains duplicate data is a concern if you
are dealing with nondeterministic data forms such as Paleo, Zone
Attribute, Well Test, Drill Stem Test/Repeat Formation Test, Well
Completion, Well Perforation, Well Pressure and Well Production.
Unlike picks and faults which are uniquely identified by an interpreters
initials, non-deterministic data forms have no key fields that uniquely
identify them to the database. By filtering these data forms, you can
uniquely identify the data that you want to map.
For Example:
When creating a Well Test pointset, you may choose to filter by the
Blue Production zone. Since the Blue Production zone is not a key
field, it doesnt uniquely define the pointset. You may have three Blue
Production Zones in your well. When you press the Calculate Button,
the application calculates that 100 wells have a well test in the Blue
Zone. It also calculates that five of these wells have more than one Well
Test in the Blue Zone.
To uniquely identify the points you want, you may choose to select the
Field filter. When you press the Calculate button after specifying that
you only want to see the wells that are in the James Field in the Blue
zone, you find that there are only 35 wells instead of 100. This may
eliminate all of your duplicates.
For Data Forms with only One Formation as Top
Data forms that only have one formation as top do not have to be filtered.
R2003.12
33
Landmark
Deterministic - uses
source priority
Fault
Pick
Surface Elevation
Total Depth
R2003.12
34
Landmark
Suboption
Filters
Comments, if Application
Paleo
Stratigraphic Unit
Genus
Species
Ecozone
Indicated Environment
Stratigraphic Unit
Strat Unit Attribute
Interpretation Method
Interpretation Units
Unit Descriptions
Features to Include
Unit
Column Name
Top Surface
Base Surface
Features to Include
Qualifiers to Include
Confidence Factor
Input Curve
Curve Thresholding
General
Stratigraphic Unit
Test Type
Pressure
Stratigraphic Unit
Test Type
Recorder Number
Summary
Stratigraphic Unit
Test Type
Recorder Number
DST/RFT
R2003.12
35
Landmark
Menu Option
Well
Well Production
R2003.12
Filters
Comments, if Application
Completion
Stratigraphic Unit
Completion Type
Completion Method
Current Status
Fault
Fault Name
Features to Include
Confidence Factor
Header
none
Perforation
Stratigraphic Unit
Perforation Type
Pick
Surface
Features to Include
Qualifiers to Include
Confidence Factor
Pressure
Field
Pool
Stratigraphic Unit
Pressure Type
Field, Pool, and Stratigraphic Unit indicate where the pressures were taken.
Pressure Type refers to the type of test.
Surface Elevation
Elevation Type
Test
Field
Pool
Stratigraphic Unit
Test Type
Total Depth
Volume Record
Zone
Activity Type
Producer or Injector
Production Type
Period Type
Zone
Zone
Field
Pool
Stratigraphic Unit
Operator
Zone refers to the geologic unit or formation where the production information
was recovered. A well production zone
has a single pressure system and does not
communicate with other zones.
36
Landmark
R2003.12
37
Landmark
Pointset Fields
The Pointset Fields (the data Pointset Builder uses to construct the
pointset) are specific to the data type:
Menu Option
Paleo
Strat Unit
Attributes
(called Depth
Fields rather than
Pointset Fields)
R2003.12
Suboption
Pointset Field
Top Depth in MD
Top Depth in TVD
Top Depth in SSTVD
Base Depth in MD
Base Depth in TVD
Base Depth in SSTVD
MD Thickness
TVD Thickness
TST
TVT
Top Depth in MD
Top Depth in TVD
Top Depth in SSTVD
Base Depth in MD
Base Depth in TVD
Base Depth in SSTVD
MD Thickness
TVD Thickness
TST Thickness
TVT Thickness
MD Thickness
TVD Thickness
TVT Thickness
TST Thickness
Curve Sum
Arithmetic Average
Geometric Average
Harmonic Average
Top Depth in MD
Top Depth in TVD
Top Depth in SSTVD
Base Depth in MD
Base Depth in TVD
Base Depth in SSTVD
Unit Name
Comments
Measured Depth
True Vertical Depth
True Vertical Depth Subsea
True Vertical Thickness; dip information required for TVT and TST
input curve required
input curve required
input curve required
input curve required
38
Landmark
Menu Option
DST/RFT
DST/RFT (cont.)
R2003.12
Pointset Field
Comments
Pressure
Recorder Cap
First Init Flow Press
First Fin Flow Press
First Si Press
Second Init Flow Press
Second Fin Flow Press
Second Si Press
Fin Init Flow Press
Fin Fin Flow Press
Fin Si Press
Fin Si BHP
Ihp Mud
Fhp Mud
Surf Choke
Bot Choke
Sampler Press
Press Gradient
Equiv Mud Weight
Formation Pressure
Summary
Potentiometric Surface
Productivity Index
Effective Transfer
Net Productive Interval
Estimated Porosity
Gas Oil Ratio
Estimated Permeability
Effective Permeability
Estimated Damage Ratio
39
Landmark
Menu Option
Well
Well (cont.)
R2003.12
Pointset Field
Completion
Top Depth in MD
Top Depth in TVD
Top Depth in SSTVD
Base Depth in MD
Base Depth in TVD
Base Depth in SSTVD
MD Thickness
TVD Thickness
TST
TVT
Fault
Fault Name
Heave
Vertical Separation
Fault Dip Angle
Fault Dip Azimuth
Repeat Below
MD
TVD
SSTVD
Header
Latitude
Longitude
Latitude BH
Longitude BH
X Coord BH
Y Coord BH
Elevation
Total Depth in MD
Total Depth in TVD
Total Depth in SSTVD
Plugged Back TD in MD
Plugged Back TD in TVD
Plugged Back TD in SSTVD
Perforation
Comments
Latitude at bottomhole
Longitude at bottomhole
X coordinate at bottomhole
Y coordinate at bottomhole
Perforation Density
Perforation Diameter
Top Depth in MD
Top Depth in TVD
Top Depth in SSTVD
Base Depth in MD
Base Depth in TVD
Base Depth in SSTVD
MD Thickness
TST
TVT
40
Landmark
Menu Option
R2003.12
Pointset Field
Pick
Surface Name
Dip Angle
Dip Azimuth
MD
TVD
SSTVD
Pressure
Surface Elevation
N/A
Comments
41
Landmark
Menu Option
Well (cont.)
Total Depth
R2003.12
Pointset Field
Comments
Rat hole diameter
Gas/Oil ratio
% of hydrogen sulfide in oil
Measured Depth
True Vertical Depth
Sub-sea True Vertical Depth
42
Landmark
Menu Option
Well Production
Pointset Field
Volume Record
Volume
Period On
Volume Quality
Zone
Comments
R2003.12
43
Landmark
Each data type uses its own rules to determine the order of the tests.
These rules are the fields in the database the program checks for data.
The following table contains information about the tests:
Menu Option
Suboption
Rule
Paleo
N/A
General
Pressure
Summary
Well
Completion
Fault
N/A
Header
Well Production
Perforation
Pick
N/A
Pressure
Surface Elevation
Create Date
Test
Test Number
Total Depth
Create Date
Volume Record
Volume Start Date and Volume End Date with Create Date as a
fall back
Zone
Create Date
R2003.12
44
Landmark
Importing Grids
Use Import Grids to import external (ASCII, CPS3 binary, and
Z-MAP Plus MFD) surface grids representing sequences of similar
depositional, diagenetic, or structural events into Stratamodel's internal
binary format to build events, horizons, or faults.
A control file is used to define how the external grid is read and
converted into Stratamodel's internal format. If you have more than one
type of grid file to import, you will need to create a control file for each
type.
R2003.12
45
Landmark
Exporting Grids
You can use Export Grids to export grids for use in mapping packages
such as Z-MAP Plus or Radians CPS. You can also use the program
to make a few changes in the grid, such as filling in null areas.
The Export Grids Control File contains the information Stratamodel
uses to export binary (.smg) grids into ASCII .grd files, binary CPS3
.svs grids, and binary Z-MAP Plus MFD files. Stratamodel only
exports the Z values, not the column, row, x or y values. The .grd files
can be read with any UNIX editor, the more command, or cat.
R2003.12
All grids should have the same origin and the same number of grid
rows and columns to be used in the same model. StrataMap can
resample the grids to the same specifications. See the StrataMap
User Guide for more information.
46
Landmark
Grid Format
You must know the grid format, in particular whether it is column or
row oriented, to correctly fill out the Import Grids Control File. This is
because Import Grids reads grids from the x, y origin, either by row or
by column. The information about how your grid is output to the grid
file is usually provided by your mapping package.
Avoiding Errors
Make sure you use the most current values for the grid.
Correct Grid Format for Some Standard Grids
For Z-MAP Plus and Radian's CPS grids, use a column-oriented grid type and
reverse the rows. Program defaults are set for these grids.
Examine the following grid file and the examples that follow to see how
column and row orientation affect the reading of grid values.
R2003.12
-5000
-5020
-5034
-5045
-5055
Record 1
-5004
-5025
-5038
-5046
-5054
Record 2
-5007
-5028
-5040
-5048
-5059
Record 3
-5012
-5030
-5041
-5055
-5065
Record 4
-5020
-5035
-5044
-5060
-5070
Record 5
47
Landmark
-5055
-5045
Rows
-5070
-5060
-5034
-5020
-5025
-5000
-5004
2
1
1
Columns
-5060
-5070
-5045
-5055
Rows
-5004
-5025
-5000
-5020
2
1
1
-5034
3
Columns
R2003.12
48
Landmark
Because of the differences in the way data is placed into a grid between
current mapping packages, you may need to reverse the grid rows,
columns, or both.
Grid Orientation
Changing how the data is read by reversing grid rows or columns does not affect
the original orientation of the grid; it just changes which value is read in first and
how the rest of the values are placed so that the .smg representation of your grid is
positioned accurately.
R2003.12
49
Landmark
The examples below illustrate all the possible combination of grid type
and row-column reversal.
Output File from Mapping Package
-100
-105
-110
-111
-115
-100
-102
-104
-106
-102
-107
-112
-115
-117
-105
-107
-109
-111
-104
-109
-114
-115
-119
-110
-112
-114
-116
-106
-111
-116
-117
-999
-111
-115
-115
-117
-115
-117
-119
-999
Rows
Stratamodels .smg
grid will look like this.
Rows
2
1
Rows
2
1
Columns
R2003.12
Columns
-117
-119
-999
-111
-115
-115
-117
-110
-112
-114
-116
-105
-107
-109
-111
-100
-102
-104
-106
3
2
-115
Columns
50
Landmark
-111
-110
-105
-100
-115
-117
-119
-999
-117
-115
-112
-107
-102
-111
-115
-115
-117
-119
-115
-114
-109
-104
-110
-112
-114
-116
-999
-117
-116
-111
-106
-105
-107
-109
-111
-100
-102
-104
-106
for a
Column-Oriented
Rows
Rows
4
5
Columns
The
R2003.12
Rows
-117
-119
-999
-111
-115
-115
-117
-110
-112
-114
-116
-105
-107
-109
-111
-100
-102
-104
-106
-115
Columns
Columns
51
Landmark
-111
-116
-117
-999
-106
-104
-102
-100
-104
-109
-114
-115
-119
-119
-111
-109
-107
-102
-107
-112
-115
-117
-117
-116
-114
-112
-100
-105
-110
-111
-115
-110
-100
-105
-110
-999
-119
-117
-115
Rows
Rows
2
1
Columns
R2003.12
Rows
Columns
-117
-119
-999
-111
-115
-115
-117
-110
-112
-114
-116
-105
-107
-109
-111
-100
-102
-104
-106
-115
Columns
52
Landmark
-117
-116
-111
-106
-999
-119
-117
-115
-119
-115
-114
-109
-104
-117
-115
-115
-111
-117
-117
-112
-107
-102
-116
-114
-112
-110
-115
-111
-110
-105
-100
-111
-109
-107
-105
-106
-104
-102
-100
Rows
Stratamodels .smg
grid will look like this.
Rows
4
5
Columns
R2003.12
Rows
Columns
-117
-119
-999
-111
-115
-115
-117
-110
-112
-114
-116
-105
-107
-109
-111
-100
-102
-104
-106
-115
Columns
53
Landmark
Importing Grids
This topic contains information about the following subjects:
Required Parameters
To build an Import Grids control file, you need to know the following:
If you need help, click the Help button at the bottom of the window.
R2003.12
54
Landmark
You will need the following information about the grids from your
gridding package:
The Import Grids Control File contains information about the layout of
your external ASCII grids that Stratamodel uses to convert these grids
into the Stratamodels internal binary format (.smg).
If you are starting a new project, you must create a control file. If you
have an existing project, you can use the current control file, create a
new control file from an existing control file, or create a new empty
control file. For more information on control files, see Choosing or
Creating a Control File on page 29 in Introduction to Stratamodel.
R2003.12
55
Landmark
2.
R2003.12
56
Landmark
3.
Enter list of Grid File Names selects the grids for import. The
grids should be in the project directory and should have the same
extensions. Click the Enter list of Grid File Names.
4.
R2003.12
If you are not using the .grd as your grid file extension,
change the File Filter field to your grid file extension and click
the Filter button to display your grid files.
You can select the files individually or select all files in the
directory at once as described in the introduction.
Use the radio push-buttons under the list to add files, select all
the files in the directory or delete files.
57
Landmark
5.
For Enter Grid NULL Value, set the NULL value to be used
while reading your grid data. This option accepts any value that
conforms to the FORTRAN format statement used in Input Grid
Data Format. The value can be negative or positive. If an
exponential format was used in outputting the grids, then any large
null value may be referred to in exponential format here.
R2003.12
58
Landmark
8.
The x and y minimum values define the origin of your grids. These
values can be any real number, but they must be in the same map /
units and map scale.
9.
The x and y increments must reflect the final grid intervals of the
gridding package. If a smoothing operation was performed on the
grid with a corresponding grid interval reduction, the x and y
increments should reflect those values.
Click in the Enter X-Increment/Y-Increment for Grid(s) fields and
enter the increments for the grid.
R2003.12
59
Landmark
10. You must use integers to define the number of rows and columns
of data defined in the 2D grid. To calculate
((Xmax - Xmin)/Xinc) + 1 = number of columns
((Ymax - Ymin)/Yinc) + 1 = number of rows
Click each input field and enter the number of grid columns or
rows.
11. Stratamodel must know how many lines are in the import grid
header, if it exists, so that it knows where to start reading actual
grid data. Stratamodel locates the first values of the data by
reading the first record after the header records.
Click the Enter Number of Header Lines in Grid(s) Files field and
enter the number of header records (number of lines of ASCII text
which is not considered raw data).
12. For Enter Grid(s) Data Format, Stratamodel uses the data format,
expressed as a standard FORTRAN statement, to locate and read
the z data correctly. Each grid file must have the same format.
Refer to Creating Fortran Format Statements on page 49 in
Introduction to Stratamodel for how to use the Create Fortran
Format window.
R2003.12
60
Landmark
You can limit ASCII grids you are importing by row and column or by
x and y values; and/or by z values. If your grids are very large or if you
have a specific area of interest to model, you may want to limit them as
they are imported.
Currently, Stratamodel can import grids up to 999 rows by 999
columns. Large grids demand much more of the hardwares resources;
therefore, the smaller the grids the easier it is to manipulate the displays
and perform operations on the grids.
Rows
1
Old Origin
Columns
61
Landmark
X, Y Limits
Limiting grids by x and y, on the other hand, maintains the original
values throughout. This method also limits the grid at grid rows and
columns even if the x and y value entered is not exactly at a grid node.
The resulting grid is always at least as large as the x and y value
entered.
Procedure
1.
R2003.12
2.
3.
Click the appropriate fields and enter data for limiting your grids
by x, y values or rows and columns. You must be familiar with the
grid to enter meaningful values.
4.
Click OK.
62
Landmark
Importing or Saving
1.
Once you finish entering all the parameters, click the Import
button (in Save and Execute) to import the grids or the Save button
(in Defer Execution) to store the control file for future use.
The Importing and Converting Grids dialog box displays a list of
the converted grids.
2.
You are finished importing grids. You can look at the grids you
imported by using Display SGM Internal Grid File. See Displaying
Internal Grid Files on page 70.
R2003.12
63
Landmark
2.
3.
R2003.12
Toggle to select the type of binary grid you wish to import. Do this
before selecting the grid file names.
64
Landmark
Selecting Files
Be sure you select the Binary Grid File Type before you click Enter
list of Binary Grid File Names, as the list of the grid file names
depends on the selected file type.
Click the Enter list of Grid File Names button to define which grids to
import. The grids should be in the project directory.
Use the filter to find the files if they are not in the project directory.
Selecting files works differently for importing MFDs or CPS3 files.
This is because an MFD can contain multiple files, while a CPS3 is
only one file.
Selecting MFDs
When selecting MFDs, you can either add all the files contained within
the MFD at once or you can unpack the MFD to look at its contents and
select the grids you want.
All at Once
If you know an MFD contains multiple grids and you want to import all
of them, follow these steps.
1.
2.
Select the
file name.
Confirm.
R2003.12
65
Landmark
3.
If necessary, use the buttons below the Current list of File names
selected to delete files from the list.
4.
One at a Time
Follow these steps to add MFDs one at a time.
1.
Either select a file from the Files list and click List MFD button or
double-click the file in the Files list.
Click List
MFD.
R2003.12
66
Landmark
2.
This opens the Select MFD grids dialog box, showing you what
grids are within the MFD file.
Add the grids you want to import. Click the grids in the list, then
click Add or double-click a grid in the list. Double-clicking a grid
selects that grid, but close the Select MFD grids dialog box, and
clicking Add enables you to select multiple grids before you close
the dialog box.
R2003.12
3.
If necessary, use the buttons below the Current list of File names
selected to delete files from the list.
4.
When you have selected all the files you want, click OK to
continue.
67
Landmark
1.
Click the grid in the Files list, then click Add or double-click a file
in the list.
Click Add.
R2003.12
68
Landmark
2.
To delete files from the list, use the buttons below the Current list
of File names selected list.
3.
Importing or Saving
1.
Once you are finished entering all the parameters, click the Import
button (in Save and Execute) to import the grids or the Save button
(in Defer Execution) to store your control file for future use.
The Importing and Converting Grids window displays the
converted grids.
2.
You can look at the grids you imported by using Display SGM Internal
Grid File. See Displaying Internal Grid Files on page 70.
R2003.12
69
Landmark
R2003.12
2.
3.
Use the filter to select the grid file you want to display.
4.
5.
70
Landmark
6.
7.
The NULL value for the grid can be reset to a different value, for
display purposes, by entering a floating point NULL value.
Stratamodel has a default NULL value of 1.0E+30. If you wish to
display your data with the same NULL value as your ASCII grids,
enter that null value.
Click in the NULL substituted in Stratamodel grid field and enter
the NULL value.
8.
R2003.12
71
Landmark
Appearance of Grid
Stratamodel displays data as a column-oriented grid with the origin in the
lower left-hand corner. If your ASCII grids are not column oriented or if you
reversed the rows or columns, the displayed grid appears different than the
original ASCII grid.
Stratamodel displays the grids one at a time. Use the slider bars to
move the view of the file.
9.
R2003.12
72
Landmark
Exporting Grids
This section contains information on the following topics:
R2003.12
73
Landmark
2.
3.
R2003.12
74
Landmark
The Export Grids Control File Grid Names dialog box appears:
4.
Use the filter to add the files you want to export to the list.
5.
6.
R2003.12
75
Landmark
7.
8.
Enter Output Grid NULL Value accepts any value that conforms
to the FORTRAN format statement used in Input Grid Data
Format.
It allows you to set the null value to that used by your gridding
program. The value can be negative or positive. If an exponential
format was used in outputting the grids, then any large null value
can be referred to in exponential format here.
9.
Click the NULL value field and enter the grid NULL value.
10. Enter Output Grid(s) Data Format describes the data format of
the grid files to be output. Stratamodel accepts standard
FORTRAN format statements.
Format of Statement
The parentheses must be included in the field, for example, (10 F15.2).
All grid files using the same control file must have the same
format.
To change the statement, click the Enter Output Grid(s) Data
Format button and change the statement in the resulting dialog
box. See Creating Fortran Format Statements on page 49 in
Introduction to Stratamodel for more information on FORTRAN
format statements.
R2003.12
76
Landmark
11. If you wish to limit the extent of your grids, click the Limit Grids
button and provide the appropriate information. For more
information on setting limits, see Setting Limits on page 42 in
Introduction to Stratamodel.
12. Once you finish making selections, click the Export button (in
Save & Execute) to export the grids or on the Save button (in
Defer Execution) to save the parameters for the control file.
When you export .smg files to CPS3 grids, they are written out in
binary format and appended with a .svs extension. Since the export
extensions are the same as the input grid extension, if you have CPS3
grids already existing in the project, you must rename the files when
you export so you do not overwrite your original grids.
On the other hand, if you export .smg files to Z-MAP Plus .mfd grids,
they are appended with the .mfd extension and a version number, so the
original grid is not overwritten.
R2003.12
1.
2.
Click Enter list of SGM Grid File Names to select the grid files
you wish to export. Use the file filter to select them. For
information on using file filters, see Locating Files with a File
Filter on page 35 in Introduction to Stratamodel.
77
Landmark
3.
Toggle the Binary Grid File Type button to your choice of grid
type
R2003.12
78
Landmark
Destination
Velocity
Model
Seismic
Source
R2003.12
79
Landmark
R2003.12
Click the Projects button to display a list of all the available 3DV
projects:
80
Landmark
2.
3.
Click 3DV File to list the files within the project that are available
for import. You can only import one 3DV file at once, because of
the files size and complexity.
4.
5.
Once you have selected a file, the Start Line and End Line fields
reflect information from the file. To limit the extent of the data to
be imported, enter values between the values listed.
Double-click the appropriate field and enter a new value.
R2003.12
81
Landmark
Before you can load SEGY data you must know the answers to the
following questions:
Questions for Loading SEGY Data
The Landmark program segychk can provide the answers LGC Seismic Loading
needs to the following questions for data Landmark.tod format.
Where are the line and trace numbers in the trace header and what are their
formats?
R2003.12
82
Landmark
Enter the number of samples per trace. If you want to use the value
in the header, leave this field set at 0. For Sierra file types, you
must specify the number of samples per trace.
2.
Enter the sample rate. Leave this field set at 0 to use the header
value.
3.
Enter the maximum time value that you want to import. If you
want to use all the time values, leave this field set to 0. If you enter
a value that actually exceeds the maximum time in your data, the
results are the same but the conversion takes longer. This increased
time is caused by the program trying to convert the values for the
entire range of time specified.
4.
Select the format for the binary file from the menu or choose Get
from Header.
5.
R2003.12
83
Landmark
6.
Enter the distance to add to the x and y header values. The distance
is in feet or meters, depending on your project units.
Sometimes the x and y values in a file are scaled. In such cases, the
header contains a value that the x and ys must be multiplied by to
be correct. Toggling Use Header Coordinate Scalar on instructs
the program to use this value.
2.
R2003.12
Standard
Charisma
Sierra
Western
3.
Use File Name to select the name of the file to import. Click the
button and use the filter to find and select the file.
4.
84
Landmark
R2003.12
1.
2.
3.
Click the 2V2 File List button to pop up a list of all 2V2 files
within the selected project. Because 2V2 data is fairly simple in
format and the files tend to be smaller, you can select more than
one file for import.
85
Landmark
4.
R2003.12
86
Landmark
The Velocity Model converts time data to depth. The velocity model
must be built in TDQ. You have three options for selecting a velocity
model:
1.
2.
R2003.12
87
Landmark
Selecting a Destination
2.
Use the filter to locate and select the Stratamodel project directory,
then click OK.
3.
4.
5.
R2003.12
88
Landmark
5.
6.
R2003.12
Closest Value takes the trace value in the vertical stack closest
to the cell.
89
Landmark
When the import process is complete, the status box reports it and the
Stop Import button changes to read Done. Click Done to close the
status box.
R2003.12
90
Landmark
Saving Parameters
To import a series of files with the same format and settings in different
Stratamodel sessions, use the File Save Parameters button to avoid
resetting the parameters. Next time you bring up LGC Seismic
Loading, the module automatically resets to the saved parameters
unless you delete the parameter file. The file is located in your home
directory with the extension .params_file.
R2003.12
91
Landmark
For all projection methods you can apply a z bias, apply a z scale factor,
and associate a color.
You can load parameters that you have set for other culture data or save
parameters to a file.
Working with MFDs
A good practice is to check your data directory for a file with your MFD name and
the extension .lck or .LCK before using Z-MAP Plus Culture Loader. This is a lock
file for that MFD. If you are using an MFD in Z-MAP Plus or Contouring Assistant
that you simultaneously want to use with Stratamodel, make sure you have detached
the MFD from the other program before running Z-MAP Plus Culture Loader. If
you find a lock file and you are not running one of these other programs, it may be
left over from when a process was killed. Remove it with a UNIX rm command.
R2003.12
92
Landmark
R2003.12
1.
2.
To load MFD files, you must first attach one or more master files
(MFDs).
93
Landmark
Click OK.
3.
Use the button with the three dots to the right of the Input Line file
field to select a file from the .mfd.
4.
From the Master Files list, select the MFD that holds your culture
data. (You can also double-click the MFD and go straight to
step 6.)
MFD Missing from Master Files List
If your MFD does not appear in the Master Files list, you may have a lock file
in your project directory. The lock file has the name of your MFD with the
extension .lck or .LCK. Remove it by using the Unix rm command.
R2003.12
94
Landmark
5.
6.
Click the file name in the List of Member Files to select it.
7.
Click OK. The name of the selected file appears in the field next to
Input Line file.
8.
Use the Associated Grid File button to select the grid that is
associated with the culture data. If you want to drape the data over
a grid, you must select a grid. No grid file is required if you want
to use a projection of None or Flattened.
9.
R2003.12
95
Landmark
14. Optional: To change the name of the .clt file that will be output,
do the following. The default name is default.clt. The program
appends the .clt extension if you do not provide it. If you do enter
the extension, a second extension is not added.
Handling Z Values
To change the appearance of the culture data, select one of the
following options from the Projection Method menu.
Draped drapes the culture data over the grid. (You must specify
a grid.)
R2003.12
Bias suspends the culture data above the model. Enter a value for
the distance above or below the model you want to suspend the
data. (A positive value lays the culture data above, and a negative
value lays it below the model.)
96
Landmark
Choosing a Color
If you are familiar with the color indexes (numbers that indicate a
color), you can enter a number to set the color for the culture data.
Otherwise, click the color square next to the Color field.
Click a color in the palette that appears.
R2003.12
97
Landmark
Saving Parameters
Use this option to save parameters for reuse.
1.
2.
3.
Type a name for the file in the Selection field (after the path). The
name must have the extension .nvp or .NVP.
4.
Click OK.
Loading Parameters
Use these steps to load saved parameters:
R2003.12
1.
2.
Select the directory in which you saved the parameters (or enter
the directory path in the Filter box) and click the Filter button.
3.
Select the file name (with a .nvp extension) from the Files list.
4.
Click OK.
Loading Culture Data from Z-MAP Plus: Saving and Loading Parameters
98
Landmark
Click OK to convert the file and exit the Z-MAP Plus Culture
Loader.
R2003.12
99
Landmark
Menu Options
This topic describes the function of the Attribute Extract/Load menu
options, in order as they appear (with the exception of Attribute Load
Grid).
R2003.12
ATM Load from ASCII File takes an ASCII file from outside
SGM and loads it into the attribute model. You can load one or
more than one attribute into the model at the same time.
100
Landmark
File Types
There are four file types available for loading data ASCII into or
extracting ASCII data from SGM. The file types are named SM1, SM2,
SM3, and SM4. SM1 and SM2 are identical and give the same results
in both Extract and Load.
R2003.12
101
Landmark
2.
Click Input File to Load from to select the ASCII file that is a
source of your data. Use the file filter to locate the file.
3.
Click OK.
4.
Input File Type gives you four choices of formats for the input
file. Choose one from the menu.
For more information about the file types, review File Types on
page 101.
R2003.12
Extracting and Loading Attributes: Loading Attribute Data from an ASCII File
102
Landmark
5.
For SM4 input files only, you can choose to average points. If you
choose to average points, all points falling within a cell are
averaged; if you choose not to average points, only the last point
falling in the cell is used.
6.
The Input File Data Format option instructs the module in how to
interpret the data file. If you have picked the correct input file type
to correspond with your input file, AEL is fairly intelligent about
reading the file and ascertaining the correct format. However, files
that are not right-justified must be formatted in the Create Fortran
Format dialog box.
Whether your file is in the correct format or not, click Input File
Data Format.
AEL attempts to read the file. If it is unable to read it correctly, the
following error message appears along with the Create Fortran
Format dialog box.
In this case you must either correct your file or use the Create
Fortran Format dialog box to format the file.
R2003.12
Extracting and Loading Attributes: Loading Attribute Data from an ASCII File
103
Landmark
R2003.12
7.
In the Input File Null Value field, enter the value used for null in
your input file. Examples of typical null values are -99999,
999999, and 1.0E+31.
8.
If you want to limit the attribute fields you are loading, you can use
X,Y Limits when Loading. The default is not to limit. For
instructions, see Setting Limits on page 42 in Introduction to
Stratamodel.
9.
If you have a large input file or you only want to use part of it, you
can use Input File Record Limits to limit it.
Extracting and Loading Attributes: Loading Attribute Data from an ASCII File
104
Landmark
10. Use Attribute Fields to Load to tell AEL which attributes to load
and where to put them in the attribute model. This entry is
required.
When you select Attribute Fields to Load, two dialog boxes
appear: a standard list box and the New Item for Load Field dialog
box.
Use the Load Fields in Attribute Model dialog box to build a list of
attributes to load. To review how to create a list, see Creating
Lists on page 31 in Introduction to Stratamodel. Instructions on
the other dialog box follow.
11. Use Attribute Model Field to Load into to select an attribute
model field from the attribute model. You will load your attribute
data into this field.
1
2
3
4
5
R2003.12
Extracting and Loading Attributes: Loading Attribute Data from an ASCII File
105
Landmark
6.
The file field is the field in the input file that contains the attribute
you want to load. Although x, y, and z information appear in the
file, the fields that hold that data are not considered in the
selection. So, entering 1 for Load File Field would select the first
attribute field that appears after the x, y, and z fields.
Enter a integer corresponding to the field occupied by the attribute
in the input file, not counting x, y, and z fields.
7.
For SM1 and SM2 formats only, select an option for calculating
the attribute data.
8.
R2003.12
Click Load from the Save & Execute window to load the data to
the attribute model. During the load, a message box appears and
informs you of the status of the load. Once the load is finished,
click Done to close the message box.
Extracting and Loading Attributes: Loading Attribute Data from an ASCII File
106
Landmark
R2003.12
107
Landmark
2.
R2003.12
Select the name of the grid to load using Template Grid Name.
Click OK.
108
Landmark
4.
R2003.12
109
Landmark
5.
Retain values in all cells not loaded keeps the values that
already exist in that attribute field.
Set all cells not loaded to NULL sets the attribute field in
all cells except in the specific layer or sequence to null.
R2003.12
6.
7.
8.
110
Landmark
Once you confirm the load and it has successfully completed, you can
scroll through the information or print it.
R2003.12
111
Landmark
2.
3.
Choose one of the four acceptable formats for the output file.
For more information about the file types, see File Types on
page 101.
4.
R2003.12
112
Landmark
5.
You can limit the attribute model you are extracting to specific
rows and columns, a specific layer, or a specific sequence. Click
Extraction Fields Limits. See Setting Limits on page 42 in
Introduction to Stratamodel for instructions on setting limits.
6.
Use the Extract Fields from Attribute Model dialog box to build a
list of all the attributes you want to extract. To review the
instructions for building lists, see Creating Lists on page 31 in
Introduction to Stratamodel.
R2003.12
113
Landmark
R2003.12
7.
Choose the attribute for your list from the Attribute List dialog box
and click OK.
8.
Once you complete the required fields, click Extract to extract the
data. A message window appears and informs you about the
progress of the extraction. When the data is extracted, click Done
to close the message box.
114
Landmark
Suppose, for example, you plan to drill a well and want to examine the
logs that would be available if you already had a well in that location.
You could extract a pseudo log along the x, y coordinates of the
proposed well to see the results.
Another use for an extracted pseudo log is to verify the results of the
attribute model if you are already fairly sure what the results should be
down the path of the pseudo well.
R2003.12
115
Landmark
2.
3.
For Output Pseudo Log File Extension, enter an extension for the
file that will contain your pseudo log.
4.
For Input File Type, choose the correct type for the file containing
your x, y, z location data. The input file for each pseudo log must
be in its own file.
R2003.12
5.
For Input Z Type choose the correct type for your z values: depth
or elevation.
6.
Use Input Data Format for X,Y,Z to create the Fortran format.
116
Landmark
For information about using the Create Fortran Format dialog box,
see Creating Fortran Format Statements on page 49 in
Introduction to Stratamodel.
7.
Pick the attribute fields you want to extract from the attribute
model. Click Fields to Extract to display a standard list building
dialog box and the Attribute List dialog box.
For instructions about building a list, see Creating Lists on
page 31 in Introduction to Stratamodel.
8.
In the Attribute List dialog box, click an attribute to select it, then
click OK.
9.
Once the list is built, click OK in the Extract Pseudo Log from
Attribute Model dialog box.
10. Use the standard Fortran format dialog box to construct a format
statement for your output file. For instructions on how to use this
dialog box, see Creating Fortran Format Statements on page 49
in Introduction to Stratamodel.
11. Once you have filled out the dialog box, press the Extract button.
A message window appears to advise you of the progress of the
process. When the process is complete, click Done in the message
box to close it.
R2003.12
117
Landmark
R2003.12
118
Landmark
Use the New Item for Attribute Extract Grid dialog box to create
the items to be extracted as a grid.
2.
R2003.12
Click the Attribute to Extract button and select the attribute you
want to use as a grid from the resulting list. Click OK.
119
Landmark
3.
If you choose Event Extract, the next panel of the dialog box,
which provides information about the event, is activated. When
you extract an event, you specify whether you want to view above
the event boundary or below it.
R2003.12
120
Landmark
Just as you would for an event, you must specify whether you
want to see above or below the sequence boundary.
Use the Sequence to Extract slider to choose the event.
Toggle the Where to find Sequence Data button to Above
Sequence Boundary or Below Sequence Boundary.
R2003.12
4.
Press the Output Grid File Name button and enter a name for an
output grid in the Filter box. Click OK.
5.
Click OK in the New Item for Attribute Extract Grid dialog box to
add the item to the list.
6.
121
Landmark
R2003.12
1.
2.
122
Landmark
3.
Select the attributes where you will store data from the adjacent
cells. Click the button and choose an inactive attribute.
Selection
Meaning
Attribute Field for +Column store the data from the cell next to the one in
which the attribute appears (the next one in the
x direction)
R2003.12
store the data from the cell that is above the one
in which the specified attribute appears (the
next one in the z direction)
4.
You can limit the area from which you are getting attributes by
using the Beginning and Ending Column and Row sliders to set
specific rows and columns.
5.
Once you have made your selections, click the Store button to
store the attribute information in the selected attributes. A message
window appears advising you about the progress of the process.
6.
When the process is complete, click the Done button to close the
message box.
123
Landmark
VIP to SGM
Use VIP to SGM to take simulation data from the VIP reservoir
simulator and convers it for use in Stratamodel. This conversion
enables you to compare the upscaled version of the data created in the
VIP simulation with the finer resolution of the Stratamodel model. You
can then spot finer features of the subsurface that are important to the
simulation, but have been averaged out by the upscaling.
1.
R2003.12
124
Landmark
2.
Click the Database button and select a .vdb file from the list. The
.vdb file is the Study created in VIP. Use the file filter to locate
your VIP directory if it is not the one already selected.
3.
Click the Case button and select the VIP case from the list. A case
is a realization that was run as part of a Study (referred to as a
simulation run in StrataSim documentation). Click OK. The case
is the particular simulation run.
4.
Click the Class button and select the array for the VIP data, then
click OK.
R2003.12
125
Landmark
5.
The SGM Model Limits panel shows the limit of the Stratamodel
model.
To limit the model so you can insert the data into specific areas of
the model, click the Change SGM Limits button. Use the sliders
to select the area where the VIP data will be imported.
6.
7.
8.
R2003.12
126
Landmark
R2003.12
127
Landmark
Fault Block 1
(Block 2)
(Block 1)
Event Grid 6
(Horizon 3)
Sequence 3
(Block1-Unit3)
Sequence 6
(Block2-Unit3)
Event Grid 2
(Horizon 2)
Event Grid 5
Sequence 2
(Block1-Unit2)
Event Grid 1
Zone 2
Zone 2
Sequence 5
(Unit 2)
(Unit 2)
(Block2-Unit2)
(Horizon 1)
(Horizon 2)
Event Grid 4
Sequence 1
(Block1-Unit1)
Sequence 4
Event Grid 3
(Horizon 1)
(Block2-Unit1)
(Section 1)
Stratamodel Term
(RESCUE Term)
Stratamodel Term
RESCUE Term
Fault Block
Block
Sequence
BlockUnit
Zone
Unit
These objects are the main building blocks used for constructing both
types of models. This illustration is only a summary of the different
terms used by both models. To learn more details about the RESCUE
model terms, see the documentation at the www.posc.org/rescue
website.
R2003.12
128
Landmark
RESCUE Icon
129
Landmark
R2003.12
130
Landmark
Navigate your directory structure until the .prc file you want appears in
the right pane of this window. Highlight the file name and click OK.
Well Model
Click the Well Model button to display a list of all the well models in
the current project. Select a well model to convert and click OK.
R2003.12
131
Landmark
R2003.12
132
Landmark
Top horizon
Bottom horizon
Sequence Type (onlap, offlap, truncated, proportional, etc.)
Layer parameters such as thickness, offsets, number of layers, etc.
Any other required template or pattern surfaces
Because the Implicit method does not define the individual cell
geometry, this method exports a small, very portable file. For large
models or on machines with little RAM, this is the preferred method.
This setting is the default.
R2003.12
133
Landmark
R2003.12
134
Landmark
R2003.12
135
Landmark
Attribute(s) to export
Use this field to control which cell attributes are exported to the
RESCUE model. Attributes are known as Properties in the RESCUE
model.
When you click the Attribute(s) to export button, the familiar Create/
Select dialog opens and displays a list of all the attributes in the current
project. You must associate each Statamodel attribute with a POSC
RESCUE property before you export any attributes to the new model.
To do this, follow these steps:
1.
2.
R2003.12
3.
4.
136
Landmark
R2003.12
137
Landmark
Highlight all the Fault Blocks and Zones you want to include in your
RESCUE model, and click OK. In our example, we will include Fault
Block 1 and Zones 1 and 2. The Select All Blocks, Unselect All
Blocks, Select All Zones, and Unselect All Zones buttons help you
manage large lists.
R2003.12
138
Landmark
Fault Polygons
Fault polygons (i.e. tiploops) are 3D closed polygons formed by joining
all the triangulated edges of gridded fault surfaces before any surface
extension or fill operation is performed. In other words, fault polygons
or tiploops are the XYZ outline of the original gridded faults before any
extensions were computed. Stratamodel requires that all fault surfaces
are extended; therefore the original surface boundaries are lost.
Reservoir Framework Builder or StrataMap Framework Builder can
generate fault polygons in Stratamodel culture file format (.clt) to be
exported to RESCUE format.
To assign culture files to fault events, use the Fault Polygons button.
When you click the Fault Polygons button the Fault Polygon
Assignment Dialog appears:
If you have an unassigned fault event, None appears to the right of the
fault name. You can use this dialog to assign the culture file (.clt) to the
correct fault event. To assign a culture file:
R2003.12
139
Landmark
1.
2.
3.
Select the correct .clt file in the Get Fault Polygon Culture File
dialog box.
4.
Click OK.
R2003.12
140
Landmark
Export to File
Use this field to name the new RESCUE model file or select an existing
file name and overwrite it when you execute the export with the Export
Full Model button. This field is also used by the Export Attributes
button to update an exising RESCUE model.
Message Level
You can determine the level of detail you want to see in the error
messages by setting the Message Level to one of the following options:
The information from the log file can be useful to help set the
Sequence Geobody Minimum Volume Tolerance field and eliminate
unwanted portions of a sequence.
Values for Sequence Volume Required Before Export
You must generate the Sequence Volume attribute before the RESCUE model can
be exported. This option must be executed at least once per project or after building
the initial Stratamodel framework before you export.
R2003.12
141
Landmark
Save Cntrl-File
Control files (Cntrl-File) contain the parameter settings for all fields
within the POSC RESCUE Export dialog. If you want to save your
settings to be recalled in the future, click this button and assign a name
to the new file.
Export Attributes
This command exports the attributes listed in the dialog to an existing
RESCUE model attribute list. The new attributes are appended to the
existing list using the attribute name and date.
Cancel
Closes the dialog without saving any settings and does not execute the
command.
Help
Opens text files written by the programmer to provide additional
information on the use of this dialog.
R2003.12
142
Landmark
Index
Importing and Exporting Data
Numerics
2V2 data
loading into Attribute Model 85-86
3DV data
loading into Attribute Model 80-81
A
alias
pick data 30, 31
pointsets 26
ASCII file
loading data
extracted from Attribute Model 112-114
into Attribute Model 102-106
selecting
to write attributes to 112
ASCII grids
exporting 74-77
importing 55-63
ATM Extract to Pseudo Log
Formats for x, y, z Data 115
ATM Load from ASCII File
Attribute Fields to Load 105-106
Input File Data Format 103-104
attribute dependence
using template for 107
Attribute Extract Grid
What should be Extracted 120-121
Attribute Extract/Load 100-123
ATM Extract to ASCII File 112-114
ATM Extract to Pseudo Log 115-117
ATM Load from ASCII File 102-106
Attribute Extract Grid 118-121
Get Adjacent Attributes 122-123
menu choices 100-101
Attribute Load Grid 107-111
R2003.12
Attribute Model
extracting data from
to ASCII file 112-114
to pseudo log 115-117
loading data into
from ASCII file 102-106
attributes
extracting data from
to pseudo log 115-117
extracting from Attribute Model
to ASCII file 112-114
extracting from or loading into Attribute
Model 100-123
formats 101
loading a grid into 107-111
loading into model from ASCII file
102-106
loading with seismic data 79-91
choosing attribute 88
retrieving values from a cell and storing them
in new fields 122-123
average
data to be loaded into Attribute Model 106
points
when loading from ASCII file 103
B
binary grids
exporting 77-78
importing 64-69
Index
143
Landmark
cells
calculating composite values in vertical
stacks
from seismic data 89
calculating values for
from seismic data 89
retrieving attributes from 122-123
specifying how to handle cells not loaded
with attribute 110
characters
use of restricted characters (importing well
data) 14
colors
for culture data 97
completion data
filters 36
pointset fields 40
contents
of Stratamodel manuals 2
continuous
averaging 106
conventions
in manuals 3
CPS3 grids
exporting 77
selecting for import 68-69
culture data
choosing color 97
converting for use in Stratamodel 92-99
draping over a grid 96
suspending over a model 96
curves
export to OpenWorks 18-21
select type 21
data
converting culture for use in Stratamodel
92-99
create pointsets from 5
duplicate
creating a pointset with 33
first and last resolution methods 43-44
method for resolving 32
exporting to OpenWorks 18-23
extracting from Attribute Model
to ASCII file 112-114
to pseudo log 115-117
forms
deterministic vs. nondeterministic 33-34
importing from OpenWorks
log curve 6-14
in pointset
select 30
loading into Attribute Model
from ASCII file 102-106
from seismic file 79-91
2V2 85-86
3DV 80-81
SEGY 81-84
OpenWorks
types that can be imported or exported 4
used to construct a pointset 38-43
depth
interval
bounding curve data by 11-12
when outside log values 11
measured, see MD
mode
for importing wells from OpenWorks 12
range
for importing well data 11
true vertical depth sub sea, see TVDSS
R2003.12
Index
144
Landmark
depth continued
true vertical, see TVD
type
for exporting curves to OpenWorks 23
units
for exporting curves to OpenWorks 21
for exporting grids to OpenWorks 23
for importing well data 10
in building pointsets 27
discrete
averaging 106
Display SGM Internal Grid File 70-72
Enter Grid(s) Data Format 70
Enter SGM Grid File Name 70
Null Substituted In SGM Grid 71
drape
culture data over a grid 96
DST/RFT
definition 35
filters 35
pointset fields 39
rules for determining first and last resolution
methods 44
duplicates
first and last resolution methods 43-44
method for resolution 32
resolve by filtering 33
E
Epicenter 127
examples
of grid formats 47-53
explicit cell geometry
bend layer edges 133
clip layer edges 133
export
ASCII grids 74-77
curves to OpenWorks 18-21
grids 46, 73-78
to POSC RESCUE model 127
R2003.12
Index
145
Landmark
formats
2V2 85-86
3DV 80-81
for extracting attributes to pseudo log 115
for grids
Fortran statement 60
for imported grids 47-53
examples 47-53
for importing well data 12
for pointsets 26
for seismic data loaded in Attribute Model
80
SEGY 81-84
G
geoname
for stratigraphic unit 31
Get Adjacent Attributes
Attribute Field for +Column 123
Attribute Field for +Layer 123
Attribute Field for +Row 123
Attribute Field for -Column 123
Attribute Field for -Layer 123
Attribute Field for -Row 123
grids
ASCII
exporting 74-77
importing 55-63
naming 55
associated with culture data 95
binary
exporting 77-78
importing 64-69
type 64
type to export 78
defined by an attribute
extracting from Stratigraphic Framework
Model 118-121
export to OpenWorks database 22-23
exporting 46, 73-78
format
to export 76
to import 47-53
R2003.12
grids continued
header lines 60
import from OpenWorks database 15-17
importing 45-69
increment 59
for importing 46
internal files
viewing 70-72
limiting 61-62
by row and column 61
by x and y 62
loading into Attribute Model 107-111
null value 58, 76
number of rows and columns 60
origin 59
resampling 46
reversing rows and columns
on output 73
rules for importing 46
selecting
ASCII files for export 75
ASCII files for import 57
binary files for export 77
binary files for import 65-69
CPS3 grids 68-69
MFDs 65-67
to be imported
parameters 54
type
column- or row-oriented 58, 75
H
header data
pointset fields 40
headers
filters 36
Index
146
Landmark
import
ASCII grids 55-63
binary grids 64-69
grids 45-69
log curve data
from OpenWorks 6-14
pointsets and grids from OpenWorks 15-17
Import ASCII Grids 55-63
Enter Grid NULL Value 58
Enter list of Grid File Names 57
Enter Number of Grid(s) Columns 60
Enter Number of Grid(s) Rows 60
Enter Number of Header Lines In Grid(s)
Files 60
Enter X-Increment for Grid(s) 59
Enter X-Minimum (origin) for Grid(s) 59
Enter Y-Increment for Grid(s) 59
Enter Y-Minimum (origin) for Grid(s) 59
Import button 63
Limit the Grids 61
Save button 63
Import Binary Grids 64-69
Binary Grid File Type 64
Enter list of Binary Grid File Names 65-69
Import Wells and Curves from OW 6-14
Export Format 12
Export Format Options 13
Log Curves 9
Wells 8
interval
depth
for bounding curve data 11-12
layers
choosing to extract to grid 120
LGC Seismic Loading 79-91
destination for loaded data 88-89
exiting 91
Import Data 90
Seismic Source 80
Velocity Model 87
limit
area affected by template 110
area for retrieving attributes
by rows and columns 123
ASCII grids 61-62
attribute fields
when loading into Attribute Model 104
extracted Attribute Model data
when loading to ASCII file 113
grids
by rows and columns 61
by x and y 62
records
when loading attributes into model 104
location
mode for pointsets 31
log curves
importing from OpenWorks 6-14
selecting
for importing from OpenWorks 9
K
K-Layer trims 135
R2003.12
Index
147
Landmark
manuals
contents 2
conventions 3
MD (measured depth)
definition 12
MFDs
containing culture data
attaching 93
choosing a file from 94
converting 92-99
exporting 78
selecting for import 65-67
mode
depth mode for importing wells 12
model
POSC RESCUE 127
mouse buttons
selecting items with 3
paleo data
filters 35
pointset fields 38
rules for determining first and last resolution
method 44
parameters
for importing grids 54
saving parmaters for converting culture data
98
perforations
filters 36
pointset fields 40
Petrotechnical Open Software Corporation
(POSC) 127
picks
bounding
qualifiers for 29
creation options 30
distinguishing multiple due to reverse
faulting 29
features to include
when building pointsets 29
filters 36
pointset fields 41
Points and Grids
Depth Type 23
Depth Unit 23
exit 17
export data 22-23
Geo Name button 23
Geo Type 23
Get Grids List 16
Get Pointsets List 16
Grid File button 22
Grid Name button 23
import data 15-17
Map Data Set button 23
Show Export List button 23
N
name
pointsets 31
nulls
changing default value when importing well
data 14
filling between noncontiguous units 11
O
output
for pointsets 27
R2003.12
Index
148
Landmark
R2003.12
Q
qualifiers
for a units bounding picks 29
R
range
of log curve to import 11
rules
for imported grids 46
S
SEGY data
loading into Attribute Model 81-84
seismic data
converting time to depth 87
loading into Attribute Model 79-91
2V2 85-86
3DV 80-81
SEGY 81-84
sequence block grid for POSC export 132
sequence volume values 141
sequences
choosing to extract to grid 121
SGM
internal grid file
displaying 70
strat unit attributes
definition 35
filters 35
pointset fields 38
strat unit isochores
creation options 30
definition 35
filters 35
pointset fields 38
Stratigraphic Framework Model
extracting data from
to grid 118-121
stratigraphic unit
definition
in DST/RFT 35
Index
149
Landmark
surface elevation
filters 36
pointset fields 41
T
templates
loading into Attribute Model 107-111
tiploops 139
total depth
filters 36
pointset fields 42
traces
values resampled for composites in vertical
stacks 89
trimloops 135
true vertical depth sub sea, see TVDSS
true vertical depth, see TVD
TVD/TVDSS
definitions 12
U
units
bounding curve data by
when importing from OpenWorks 11
bounding picks
qualifiers for 29
depth
for exporting curves to OpenWorks 21
for exporting grids to OpenWorks 23
for importing well data 10
in building pointsets 27
filling between noncontiguous units 11
for depth interval
when importing data from OpenWorks 12
R2003.12
V
velocity model
for LGC Seismic Loading 87
volume record data
filters 36
pointset fields 43
W
well data
completions
rules for resolution method order 44
filters 36
perforations
rules for resolution method order 44
pointset fields 40-42
pressure
rules for resolution method order 44
surface elevation
rules for resolution method order 44
test
rules for resolution method order 44
total depth
rules for resolution method order 44
Well Model
loading log curve data from OpenWorks 6
well pressure data
pointset fields 41
well production data
filters 36
pointset fields 43
volume record
pointset fields 43
rules for resolution method order 44
zones
pointset fields 43
rules for resolution method order 44
well production zones
filters 36
pointset fields 43
rules for resolution method order 44
Index
150
Landmark
well sets
creating from OpenWorks curve data 14
well tests
filters 36
pointset fields 42
wells
basis for name when importing 13
data
log curves imported from OpenWorks
6-14
importing from OpenWorks
range to import 11
selecting 8
selecting depth units 10
pseudo
extracting attribute data for 115-117
with duplicates
in Point Set Builder 33
Z
z value
exaggerating
for culture data 96
using to flatten culture data 96
Z-MAP Plus Culture Loader 92-99
Associated Fault File 95
Associated Grid 95
Bias 96
Color 97
Load Parameters 98
Projection 96
Save Parameters 98
zone
in well production data 36
R2003.12
Index
151