Hampson-Russell’sH R ll’ project and database directory structures (this document is aimed to help support staff to understand the organization of Hampson Hampson-Russell Russell projects and well log databases) Using: CE8Rx releases Updated: Jan.2009 By: Tanya Colwell Table of Context 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 volumes horizons volumes, horizons, data slices and faults Other issues with HRS projects - Adding more well data to an existing project - Locating input/output seismic - Packaging and moving projects - Multi-user Multi user environment Summary by typing a table. 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. A project is created when you start a program such as AVO/ STRATA// eLOG// EMERGE// PRO4D// PROMC / ISMAP or SeisLoader. The well logs can be loaded into Geoview from ASCII. etc.Hampson-Russell Concepts: D Database b and d Project P j A database in Hampson-Russell software is a well log database created in Geoview. A project stores all the modelling and processing information (modified logs.) . horizons. LAS files. or by using our Geoframe or OpenWorks connection. models. seismic volumes. Hampson-Russell’s concepts: project j and d well ll database d b directories di i Your project directory Your well log database directory ASCII file (used Motif-based programs. like GLi3d or by old HR programs) . wdb/ It stores: Well logs & history Wavelets Culture Well viewing parameters Tip: p “wellcs. then it should be deleted and it will be rebuild the next time the well database is opened.Geoview database (also called external well log database) /simpleWellDatabase. If it is. .db” file should not be 0 in size. wdb /w*.Geoview Database: Well Logs /simpleWellDatabase.dir w*.dir store: Well header info Well logs Log history (text files) Well viewing parameters . db).wellcs. .To view the HR binary files (e.g. use the internal database editor “dbedit.exe”. It can be started from Geoview/Help menu. Geoview Database: Culture Data /simpleWellDatabase. .wdb p /overlay Tip: You may copy the /overlay directory from one db to another to prevent reloading culture. db Similarly to wellcs. this file should h ld nott b be size i 0 0. It can be removed and will be rebuild when the database is re re-opened.wdb / /wavelets. opened .Geoview Database: Wavelets /simpleWellDatabase.db.wvd l t d - Tip: wavecs. data slices. . internal well database and run-time message log) Tip: .Project directory structure: when h a project is saved d and d is not opened d These directories are called “permanent” permanent project directories These directories store data common to all HRS programs (seismic.prj/messages directory stores the run-time run time log 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 p project j is currently y opened p or that it was exited abnormally. prj/ shared dir shared. directories are not copied . then *_TMP_* remain present.dir If the program crashes. so next time the project can recover to its previous state.. ie.dir is copied p to yourProject.Project j Structure: more about temporary project directories If the project is saved saved.prj/ share TMP DIR dir share_TMP_DIR. nothing g is saved. If you exit the program without saving. then yourProject. then *_TMP_* p over. AVO and STRATA are opened using the same project.lck” files A “lock_*.lck” file exists and is locked by the operating system for each running program. . In this example.prj/“lock_*.Project Structure: yourProject. dir /f lt di /faults.prj /shared.prf prf (crossplot zones zones. Strata model info.dat (h i and d ffault lt iimportt iinformation) f ti ) .dir /share_TMP_DIR. etc.Project Structure: Horizons / Faults / Well Logs (also called “internal” internal well database) /yourProject.dir **.dir … /wellLogs.) * d t (horizon *.dir /horizons. color key key. dir /internal. th then they th are no longer l stored in the internal.dir … .Project Structure: I t Internal l Well W ll Log L Database D t b /yourProject.prj /shared.wdb IInternal t l Database D t b stores: t wells that were modified or created within the project new/modified wavelets If the wells/wavelets are exported from the project.dir /wellLogs dir /wellLogs. /share_TMP_DIR.wdb directory. Project Structure: Addi Adding more wells ll • New N wells ll will ill b be available il bl iin your project j t iimmediately. have to be implicitly p y imported p using g the “Database/Import Well changes to project” option: • if you added a dev. • All other changes. . di t l • New logs and tops that were added in Geoview will become visible in your project without any additional changes. g . • if tops/logs values were modified in Geoview. then it will be the same as the well in Geoview and no additional import is required. changes • If a well was never modified within the project. geometry curve in Geoview. if the volumes are generated by the project.sgy) is usually stored outside of the project directory.Project Structure: S i i D Seismic Data • Seismic data (*. . then the default storage directory will be default be simpleProject prj/seismic dir simpleProject.dir. • However.prj/seismic. sgy is located Common Issues with HRS projects: Locating input/output volumes .vol file to view where .Locating input/output volumes: you may open . copy the external SEG-Y volumes and their tag-alone files (. Seisworks or OpenSpirit) .prj/seismic.dir before moving the project.prj Tip: If possible. .vol.Packaging Hampson Hampson-Russell Russell projects yourGeoview.wdb yourProject.inf) into your Project. External seismic data (SEG (SEG-Y/tagY/tag alone files. Different HR programs can share the same project at the same time (for example. g Use the “Open Seismic From Project …” option.prj). .Different HR programs using the same project Two users are not allowed to modify the same project using the same program (for example.prj and user2 Avo/simpleProject.prj). user 1 Avo/simpleProject. You do not have to reload your seismic data if you are sharing the same p project j among g the different p programs. Strata and Avo both using simpleProject. 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 loss. permissions On Unix/Linux.Multiple users working on the same project If multiple users share work on the same project. loss We recommend you always export the modified wells and project j to the Geoview database. then they need to have sufficient permissions. the users need to belong to the same group and a d have a e the e same sa e “umask” u as settings. wavelets from the p . Summary This document described the following: External database/internal database directory structures P Permanent/temporary t/t project j t directories di t i Relocating/packaging projects Multiple users working on the same project and the need for sufficient permissions. particularly on Unix/Linux -The End- .