OpendTect V4.2: installation notes. First of all, you can find a sysadm manual for OpendTect on the web site (http://www.opendtect.org) and in the distribution at: data/dTectDoc/ApplMan/index.html Below you'll find the 'bare' installation instructions for Linux, MS Windows and Mac. --- All installations: As of 3.x version OpendTect will attempt to use 'shading' - this means that some calculations are done on the graphics card. Unfortunately, not all cards behave properly. Very old cards will be no problem because they report that shading is not supported. Very new cards usually support it correctly (e.g. the nVidia 6000 series). Some cards of about 1-2 years old do give problems. These report that they support shading, but they support only part or so badly that the system almost stops. There are two settings for the user to cope with this: * Do you want shading if the card reports that it is capabale of it? * If so, do you also want it for volume rendering? Some cards (Like some ATI cards) support shading well but things go bad for volume rendering. The default is: * Yes, use it if the card says it supports shading * No, do not use it for VR even if the card says it supports shading Thus: * If users get colorless inlines, time slices etc, they need to try disabling shading usage * If users want to try improved volume rendering, they can try enabling that. The access to these options is in the menu 'Utilities-Settings-Look&Feel'. Info on installing license files for commercial plugins can be found at: http://opendtect.org/lic/flexlm_installation_guide.html background at: http://opendtect.org/lic/flexlm_explained.html --- Linux Installation instructions: >> OpendTect need not be installed by 'root' (exception see note on SELinux). In fact we recommend to use an 'application manager' account. In any case, use the same user account for all application management actions. << Upgrades: If you have a previous version of OpendTect installed, there are two possibilities: 1) The version has the same release number (i.e. 4.2.x). Download the packages you need to upgrade, and use the inst_pkgs.od script (use 'chmod +x inst_pkgs.od' if necessary) to install the packages. 2) The release number is different. Use the procedure for a new installation; you will get the chance to copy settings from the old installation. License files must always be installed afterwards; copying and re-starting is too tricky to do automatically. New installations: Download the packages you need, and for commercial releases also the 'install.od' script. Put all in the same directory. Run the the package using something like 'sh pcwackage_name' (GPL) or the install.od script (commercial - use 'chmod +x install.od' or enter 'csh install.od'). When you download and save any script on Windows, but want to execute the script on a UNIX machine, make sure the file is a real UNIX text file. If necessary, run dos2unix, like: dos2unix install.od; chmod +x install.od If the text is DOS text, errors like "'': command not found" will be the result. After this, there should be an opendtect-4.2.x directory at the location you selected. That directory contains OpendTect; scripts are present in that directory to start OpendTect, batch programs, create data directories and more. If all fails, unzip and untar the packages yourself and install the software like: cd opendtect-4.2.x ./install Then: 1) If you haven't got a $DTECT_DATA directory yet, make sure of that now, use the 'mk_datadir' script to create such a directory. The resulting directory needs to have the right permissions for all users. 2) If one or more parts need FlexLM licensing, you may want to use the install.*.license scripts to import these files. If any of those is a floating license, you'll also need to bring up the license manager daemon. If you do not have your own procedures to start the daemons, you may want to use the start.*.lmgrd.cripts to do that. If you do have your own FlexLM management procedures (e.g. FlexAdmin), you have to make sure that a file 'license.*.dat' is present in the application directory containing the necessary license. 3) Now, the start_dtect script should bring up OpendTect. Note [Linux/32]: On old Linux distros, libgcc.so.6 or libgcc_s.so.1 may be a problem: either the version of the system's libs arent't OK or the ones we delivered may not be suited. In such cases, you may try to rename the shared libraries in bin/lux32/so called *-bld to the actual name, like 'mv libgcc.so.6-bld libgcc.so.6'. This fails most often, though. The advice is to install a recent, stable distro, like CentOS or OpenSuSE. Note: Red Hat 3 / 64 bits: This distro is no longer supported as from version 4.0. On ftp.opendtect.org/pub/RH3_64 there is still a version for 3.2. Note {Linux/SELinux]: Some distros have SELinux enabled by default: " [...] Linux distributions have enabled new kernel security extensions from the SELinux project at the NSA. These extensions allow finer-grained control over system security. However, SELinux also changes some default system behaviors, such as shared library loading, that can be problematic to third party programs. If you receive the error message "cannot restore segment prot after reloc: Permission denied" when launching a program, then your SELinux configuration is preventing the program from launching." If the above problem occurs, you need root permission, and issue - in the opendtect-4.2.x directory, the following command: chcon -t texrel_shlib_t `find . -name \*.so -print` (note the back-quotes there!). " Note [ArkCls workstation link]: To be able to use the data link, you should start OpendTect in a window prepared for running SeisWorks or GeoFrame. And, of course, you'll need a valid license for the arkcls part itself. If you want to connect to SeisWorks or GeoFrame from an OS different from the one you're working on, you may need to create a 'WorkstationLink' file. The system administrator's manual contains information on these issues. Development: for developing OpendTect plugins, you'll need to make sure the following tools are installed: * GNU make * GNU gcc 3.4.x or higher, including g++ * perl On Windows, you can use Visual Studio with the projects in the msvc directory. --- MS Windows Installation instructions: >> OpendTect is well prepared for separation of installation/Administrator and usage accounts. We recommend to install as Administrator and use under a non-privileged account. << If you have a previous version of OpendTect installed, un-install it. Virtually all settings will be in user areas, so no precious data should be lost in this way. Download the self-extracting executable and follow the instructions. License management issues for commercial plugins may require extra actions. If the installation fails, it might be that some Visual C++ libraries are missing. These can be downloaded from the Microsoft website. For Windows 32: http://www.microsoft.com/downloads/details.aspx?familyid=32BC1BEE-A3F9-4C13-9C99-220B62A191EE&displaylang=en For Windows 64: http://www.microsoft.com/downloads/details.aspx?familyid=90548130-4468-4BBC-9673-D6ACABD5D13B&displaylang=en Development: If you want to develop OpendTect plugins, you have to use Visual Studio. --- Mac OS/X Installation instructions: Note: It seems that StuffIt may be unable to correctly unpack the mac packages. The advice is to use Safari. On Mac OS/X, you get a tar-gzipped Application Bundle. this .tar.gz contains an OS/X bundle "opendtect.app", which contains 2 directories under the surface. A directory "opendtect-4.2.x" containing the exact same contents as on any UNIX OS and a directory "Contents" containing symbolic links at the places Mac OS/X expects them into the UNIX tree. Therefore, most of UNIX instructions are also applicable to Mac OS/X. The application bundle contains not only the basic executables but also the documentation and a demo survey. However, in order to install plugins, perform multi-machine batch processing or setup Workstation Access, you will still have to go down to the UNIX style configuration of manually editing some text files or run some scripts from a terminal window. In that case, everything should otherwise be the same as with any other UNIX OS, with that difference that the environment variable "DTECT_APPL" is basically equal to "/opendtect.app/opendtect-3.x" and that "DTECT_DATA" does not have to be set; it is normally set from the application and will then be stored in your ~/.od/settings file. Support for any OS/X version lower then 10.5 is not available. --- The Madagascar plugin will NOT install Madagascar, the GMT plugins will NOT install GMT. Madagascar and GMT must be installed separately, or you can use the Madagascar and GMT packages pre-built for OpendTect which should work out-of-the-box. --- If you have any questions, please try the following in the given order: - Take a look at the links on the download page (http://opendtect.org/index.php/download.html). - Consult the support material on http://opendtect.org or your plugin vendor. - Contact support@opendtect.org or the support of your plugin vendor. - Contact dGB by phone: +31 53 4315155 Bert Bril - dGB [$Id: INSTALL.txt,v 1.39 2009-08-10 09:18:59 cvsdgb Exp $]