H R llHampson-Russells project and database directory

structures(this document is aimed to help support staff to understand the

organization of Hampson Russell projects and well log databases)organization of Hampson-Russell projects and well log databases)

Using: CE8Rx releasesUsing: CE8Rx releasesUpdated: Jan.2009By: Tanya Colwell

Table of ContextTable of Context Hampson-Russells concepts of well database and projects

General well log database directory structure:well logs, culture, wavelets, display settings

Project structure:internal well database, program-specific data, seismic volumes horizons data slices and faultsvolumes, horizons, data slices and faults

Other issues with HRS projectsAdding more well data to an existing project- Adding more well data to an existing project

- Locating input/output seismic- Packaging and moving projects

Multi user environment- Multi-user environment

Summary

Hampson-Russell Concepts: D b d P j Database and Project A database in Hampson-Russell software is a well log

database created in Geoview. This database is usually referred to as an external database. Loading of the well logs into the Geoview database is always done as the first step.

The well logs can be loaded into Geoview from ASCII, LAS files, by typing a table, or by using our Geoframe or OpenWorks connection.

A project is created when you start a program such as AVO/ STRATA/ eLOG/ EMERGE/ PRO4D/ PROMC / ISMAP or / / / / /SeisLoader.

A project stores all the modelling and processing information A project stores all the modelling and processing information (modified logs, seismic volumes, horizons, models, etc.)

Hampson-Russells concepts: j d ll d b di iproject and well database directories

Your project directory

Your well log database directory

ASCII file (used Motif-based programs, like GLi3d or by oldHR programs)

Geoview database Geoview database (also called external well log database)/simpleWellDatabase.wdb/

It stores: Well logs & history Wavelets Culture Well viewing parameters

Tip: pwellcs.db file should not be 0 in size. If it is, then it should be deleted and it will be rebuild the next time the well database is opened.

Geoview Database: Well LogsGeoview Database: Well Logs

/simpleWellDatabase.wdb

/w*.dir

w*.dir store: Well header info Well logsWell logs Log history (text files) Well viewing

parametersparameters

To view the HR binary files (e.g.wellcs.db), use the internal database editor dbedit.exe. It can be started from Geoview/Help menu.

Geoview Database: Culture DataGeoview Database: Culture Data

/simpleWellDatabase.wdb

/overlay

p

Tip: You may copy the /overlay directory from one db to anotherdirectory from one db to another to prevent reloading culture.

Geoview Database: WaveletsGeoview Database: Wavelets

/simpleWellDatabase.wdb

/ l t d/wavelets.wvd

Tip: wavecs.db- Similarly to wellcs.db, this file

h ld t b i 0should not be size 0.- It can be removed and

will be rebuild when the database is re openeddatabase is re-opened.

Project directory structure:h d d dwhen a project is saved and is not opened

TheseThese directories are called permanentpermanent project directories

These directories store data common to all HRS

Tip:.prj/messages directory stores the run time logto all HRS

programs (seismic, data slices, internal well database and

the run-time log files that may be useful for support purposes.

run-time message log)

Project Structure: when a project is opened or exited abnormally

The existence of the temporary *TMP* directories indicates that the project is currently opened or p j y pthat it was exited abnormally.

Project Structure:jmore about temporary project directories

If the project is saved thenIf the project is saved, then

yourProject.prj/share TMP DIR dir is copied to

yourProject.prj/shared dirshare_TMP_DIR.dir p shared.dir

If the program crashes, then *_TMP_* remain present,so next time the project can recover to its previous state.

If you exit the program without saving, then *_TMP_* directories are not copied over, ie. nothing is saved.p , g

Project Structure:yourProject.prj/lock_*.lck files

A lock_*.lck file exists and is locked by the operating system for each running program. In this example, AVO and STRATA are opened using the same project.

Project Structure:Horizons / Faults / Well Logs (also called internal well database)Horizons / Faults / Well Logs (also called internal well database)

/yourProject.prj

/f lt di

/shared.dir/share_TMP_DIR.dir

/faults.dir

/horizons.dir

/wellLogs.dir

* prf (crossplot zones color key*.prf (crossplot zones, color key, Strata model info, etc.)

* d t (h i d f lt i t i f ti )*.dat (horizon and fault import information)

Project Structure:I t l W ll L D t bInternal Well Log Database

/yourProject.prj

/wellLogs dir

/shared.dir /share_TMP_DIR.dir

I t l D t b t

/wellLogs.dir

/internal.wdb

Internal Database stores: wells that were modified or

created within the project new/modified wavelets new/modified wavelets

If the wells/wavelets are exported from the project, th th l then they are no longer stored in the internal.wdb directory.

Project Structure:Addi ll Adding more wells

N ll ill b il bl i j t i di t l New wells will be available in your project immediately.

New logs and tops that were added in Geoview will become visible in your project without any additional changesvisible in your project without any additional changes.

If a well was never modified within the project, then it will be the same as the well in Geoview and no additional import isthe same as the well in Geoview and no additional import is required.

All other changes, have to be implicitly imported using the g , p y p gDatabase/Import Well changes to project option:

if you added a dev. geometry curve in Geoview. if tops/logs values were modified in Geoview.

Project Structure:S i i DSeismic Data

Seismic data (*.sgy) is usually stored outside of the project directory.

However, if the volumes are generated by the project, then the default storage directory will be default be simpleProject prj/seismic dirsimpleProject.prj/seismic.dir.

Locating input/output volumes:you may open .vol file to view where .sgy is locatedyou may open .vol file to view where .sgy is located

Common Issues with HRS projects:Common Issues with HRS projects:Locating input/output volumesLocating input/output volumesLocating input/output volumesLocating input/output volumes

Packaging Hampson-Russell projectsPackaging Hampson Russell projects

yourProject.prjyourGeoview.wdb

External seismic data (SEG-Y/tag-

Tip: If possible, copy the external SEG-Y volumes and

data (SEG Y/tagalone files, Seisworks or OpenSpirit)external SEG-Y volumes and

their tag-alone files (.vol, .inf) into your Project.prj/seismic.dirbefore moving the project

OpenSpirit)

before moving the project.

Different HR programs using the same project

Two users are not allowed to modify the same project using

Different HR programs using the same project

the same program (for example, user 1 Avo/simpleProject.prj and user2 Avo/simpleProject.prj).

Different HR programs can share the same project at the same time (for example, Strata and Avo both using simpleProject.prj).

You do not have to reload your seismic data if you are sharing the same project among the different programs. Use the p j g p gOpen Seismic From Project option.

Multiple users working on the same project

If multiple users share work on the same project, then they need to have sufficient permissions

Multiple users working on the same project

need to have sufficient permissions.

On Unix/Linux, the users need to belong to the same group and have the same umask settings.a d a e e sa e u as se gs

The lack of permissions is usually reported under View Help/Run-time messages and should not be ignored as it may lead to data losslead to data loss.

We recommend you always export the modified wells and wavelets from the project to the Geoview database.p j

SummarySummaryThis document described the following:

External database/internal database directory structures

P t/t j t di t i Permanent/temporary project directories

Relocating/packaging projects

Multiple users working on the same project and the need for sufficient permissions, particularly on Unix/Linux

-The End-