Migrating Existing Projects
For 5000.0.0, the GeoProbe® software data directory structure has dramatically changed to allow for a more thoughtful handling of multi-survey objects. Older vintage projects must be migrated to follow this directory structure. Beneath the top-level OpenWorks® or GeoProbe software project, GeoProbe objects are now separated based upon whether they exist on a project or survey level. By making this change, the same horizon or fault can now extend from one survey area, or 2D line, to another. In addition, state files now encompass all objects within a project and are no longer restricted to only saving objects or a survey-by-survey basis.
As more GeoProbe objects are converted to honor world coordinates in future releases, they will eventually move out of the individual survey directories into the project directory. Currently, objects that can span multiple surveys include horizons, swFaults, 2D data, TSurf and AGF files.
continue reading »
Tagged as:
GeoProbe,
Horizons,
OpenWorks,
Project Directories
Use this procedure to upgrade your GeoProbe® only flat-file data structures that are not connected to OpenWorks® software. The user will be able to access any object stored in OpenWorks directly from OpenWorks after the OpenWorks project has been migrated to R5000.
continue reading »
Tagged as:
GeoProbe,
OpenWorks,
Upgrade
R5000 data migration starts with a general analysis of the R2003 projects and seismic data. The PreR5000 utility provided free by Landmark is used to analyze OpenWorks and SeisWorks R2003 projects and seismic data. The PreR5000 utility is not an R5000 application and is designed to validate the data in OpenWorks and SeisWorks R2003 projects before the R5000 upgrade.
continue reading »
OpenWorks Changes to Enforce Interpretation ID Permissions on Well Header
OpenWorks R5000.0.0.2 starts the well security model with enforcement of well interpretation ID permission, much like it does for well picks and other interpreted data. A user can modify or delete a well only if that user has access to the data source or interpretation ID assigned to the well. This feature was added to R5000 in response to common requests from clients. Its addition is critical to R5000 well management because wells are shared between interpretation projects, and users with appropriate permissions can delete a well while connected to any interpretation project. By design, this action removes the well from the project database as well as all associated interpretation projects. This new well security model allows clients to enforce a policy that restricts the update or deletion of wells to privileged users.
continue reading »
Tagged as:
Database,
OpenWorks,
Security
