ampson- usse s project and database directory structures (this document is aimed to help support staff to understand the -
Updated: Jan.2009 By: Tanya Colwell
Hampson-Russell’s 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 , , Other issues with HRS projects - Locating input/output seismic - Packaging and moving projects -
Summary
Hampson-Russell Concepts: ata ase an ro ect
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.
(modified logs, seismic volumes, horizons, models, etc.)
Hampson-Russell’s concepts: pro ect an we ata ase rector es
Your project directory Your well log database directory ASCII file (used Motif-based programs, like GLi3d or by old HR programs)
(also called external well log database)
/simpleWellDatabase.wdb/
It stores: Well logs & history Wavelets Culture Well viewing parameters
Tip: “wellcs.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.
/simpleWellDatabase.wdb /w*.dir
w*.dir store: Well header info
Log history (text files) Well viewing
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 Data /simpleWellDatabase.wdb /overlay
Tip: You may copy the /overlay to prevent reloading culture.
/simpleWellDatabase.wdb wave e s.wv
-
Tip: wavecs.db Similarly to wellcs.db, this file s ou no e s ze . It can be removed and will be rebuild when the .
Project directory structure: w en a project is save an
is not opene
directories are called “ ” project directories These directories store data common programs (seismic, data slices, internal well database and run-time message log)
Tip: .prj/messages directory stores files that may be useful for support purposes.
Project Structure: when a project is opened or exited abnormally
The existence of the “temporary” *TMP* directories indicates that the ro ect is currentl o ened or that it was exited abnormally.
Pro ect Structure: more about temporary project directories
,
yourProject.prj/ _ _ .
is co ied to
yourProject.prj/ .
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 co ied over ie. nothin is saved.
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: “
”
/yourProject.prj /shared.dir
/share_TMP_DIR.dir au s. r …
/horizons.dir /wellLogs.dir
. , Strata model info, etc.) . a
or zon an
au
,
mpor n orma on
Project Structure: n erna
e
og
a a ase
/yourProject.prj /shared.dir
/share_TMP_DIR.dir . …
/internal.wdb
n erna a a ase s ores: wells that were modified or created within the project
If the wells/wavelets are exported from the project, en ey are no onger stored in the internal.wdb directory.
Project Structure: ng more we s •
ew we s w
e ava a e n your pro ec mme a e y.
• New logs and tops that were added in Geoview will become . • If a well was never modified within the project, then it will be required. • All other chan es, have to be im licitl im orted usin the “Database/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: e sm c ata • 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 s mp e ro ec .pr se sm c. r.
Locating input/output volumes: .
.
Common Issues with HRS projects:
-
yourGeoview.wdb yourProject.prj
Tip:
If possible, copy the
their tag-alone files (.vol, .inf) into your Project.prj/seismic.dir
.
External seismic data SEG-Y/ta alone files, Seisworks or
Two users are not allowed to modify the same project using 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 ro ect amon the different ro rams. Use the “Open Seismic From Project …” option.
If multiple users share work on the same project, then they . On Unix/Linux, the users need to belong to the same group and have the same “umask” settin s. The lack of permissions is usually reported under View Help/Run-time messages and should not be ignored as it may . We recommend you always export the modified wells and wavelets from the ro ect to the Geoview database.
This document described the following:
External database/internal database directory structures ermanen
emporary pro ec
rec or es
Relocating/packaging projects Multiple users working on the same project and the need for sufficient permissions, particularly on Unix/Linux
-The End-
