| OpendTect Application Management Documentation version 4.2 |
|---|
| Prev |
|
Next
|
OpendTect was not designed for extensive data management; Although it may be used for this purpose, we realize that in many cases OpendTect maintains project-storage for data further maintained in company data stores like OpenWorks or GeoFrame.
Users can choose to put projects on any storage area they like. In addition, large data objects like seismic cubes can be relocated to other directories using for example the 'Manage-Seismics' dialog. This relocation is possible because selection of cubes is not done on basis of file name. Rather, the user specifies a name for each cube, and the system translates this automatically into a default filename. Later, location and file name may be changed, whilst retaining the same object ID and name.
Seismic cubes can have a class, like Imported, Steering, and Attribute cubes. This difference is maintained in the Object Manager, but is not apparent on the Operating System level. In the 'Object Management File' (Seismics/.omf) the type can be seen as in:
#Type : Steering
All Seismic cubes are stored in the 'CBVS' file format, which is an efficient platform-specific binary format. Although the storage is platform-dependent, all CBVS files can be read by OpendTect, fully transparently across platform boundaries. CBVS cubes can be stored in multiple files, where the first file usually contains most of the header info. Subsequent files belonging to the same cube can be recognised by the ^01 , ^02 etc. in the filename. For 2D seismics, this system is also used, now for the different lines in a line set.
OpendTect projects can be copied on the Operating System level, at the $DTECT_DATA level. Therefore, a command like:
cp -a $DTECT_DATA/Name1 $DTECT_DATA/Name2
will result in a fully functional new project in directory Name2 immediately. Note that the user recognizes a survey by the directory name.