The utility in all Java-based OpenWorks® Data Managers, Tools > Listen to OW Session Changes, allows you to launch different data managers across projects (ALL_DATA or Interpretation Projects that may or may not overlap) from the same OpenWorks software session for comparison and decision making. continue reading »
From the category archives:
Seismic
An interpretation project can be created using a user-defined geographical area of interest (AOI) as the means to select data from the underlying OpenWorks software project. Data falling inside the AOI are included in the interpretation project, but sometimes data falling outside the AOI are also included – so what’s going on?
Horizon data management has changed for the R5000 software from previous releases. The following post discusses the new horizon attribute header and horizon data changes. An example of an R2003 project horizon upgrade to R5000 will illustrate the process of upgrading horizons and making decisions about the creation of interpretation projects (IPs). Some best practices for QC of your upgraded horizons is included. Landmark advises a thorough QC for each project upgrade.
There are two primary tables in the database involved in cataloging and managing horizon data in OpenWorks: horizon attribute header and horizon data.
Horizon attribute header is the top-level definition of a horizon. Each row in this table represents one horizon that can be defined on any number of 3D surveys or 2D lines in an OpenWorks software project.
For each 2D line or 3D survey where a given horizon attribute header is interpreted, a row in the horizon data table is created. For a horizon created on a 3D survey, this row contains the name of the external file with the horizon data. For a horizon created on a 2D line, this row contains the horizon data defined for that line. There is no external file for 2D horizon data in R5000 software version. continue reading »
