OpendTect System requirements
|| Operating systems
OpendTect system requirements
[Summary] Supported platforms
OpendTect needs good hardware with up-to-date drivers - especially for 3D graphics. You can run on:
- Intel/AMD under Linux (32 or 64 bits) or MS Windows (2000, XP, Vista, 7, 8 - 32 or 64 bits)
- Mac/Intel under OS X (10.5) and up
OpendTect requires a recent well-patched OpenGL installation. OpenGL drivers should be updated at least every half year to ensure optimal performance and compliance.
Intel/AMD: Recent nVidia and AMD (ATI) graphics cards/chipsets. Well behaved are nVidia GeForce 6, 7 and 8 series and AMD (ATI) Radeon X1xx and X2xx series.
Mac:Similar to the Intel/AMD platform.
Main stream and high-end GPUs within the series are recommended, since low-level GPUs keep showing poor performances through the generations.
Shading functionaly requires special GPU features, present in the cards listed above. Nevertheless, under Linux, only nVidia provides drivers capable of using the shading feature. If you can't see any colors on graphic elements, try disabling shading (Utilities-Look and Feel).
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.
all nVidia-based cards and chipsets). Some older cards 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:
Some cards (Like some ATI cards) support shading well but things go bad for
The default is:
- Do you want shading if the card reports that it is capable of it?
- If so, do you also want it for volume rendering?
* 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
* If users get colorless inlines, time slices etc, they need to try disabling
* If users want to try improved volume rendering, they can try enabling that.
The access to these options is in the user's menu 'Utilities-Settings-Look&Feel'.
OpendTect should at least have 2 GB internal (RAM) memory available.
Depending on the size of the surveys we recommend 8-16 GB on average. In
special cases (big surveys or many data cubes) more memory may be required.
A rule of thumb is to have at least 10 times the displayed number of samples available. Thus, to be able to display 10 inlines with 2000 crosslines and 1000 samples per trace, you'll need a minimum of 200 million bytes of memory (i.e. 200 MB).
For Linux and MS Windows, a modern Intel or AMD processor is required.
Although OpendTect will run on 2 GHz processors or even less, we
recommend 3+ GHz multi-core for a good working environment. Note that OpendTect heavily uses all processors if necessary.
A modern Linux distribution is required. Minimum:
Linux distributions should be LSB compliant. You can check this using the command
lsb_release. This is particularly stringent for commercial plugins using the FlexNet system. There is documentation on installing license files for commercial plugins, and there is a page with background information.
For both SuSE and Red Hat-based distributions 32 or 64 bits releases are
available. OpendTect is known to work under Debian, Ubuntu and other distributions, as well as earlier versions of the main distributions, too. Fedora usage is not recommended - although it may work it's the only distro that regularly fails to work in combination with OpendTect. This is probably because the graphics vendors do not support it well in terms of drivers.
Mac OS X
Minimum is Mac OS X (10.5) - thus Mac/Intel. Mac/PowerPC support is not available. A 3-button mouse is highly recomended.
Windows 2000, XP, Vista, 7 and 8 are supported and both 32 and 64 bits releases are available.
If you have mega-surveys with Tera-bytes of data, and you want to do very advanced calculations, then you'll need the best you can get. What is best? The main idea is to minimize the bottlenecks.
It's clear that the number of variables is huge, and that it's simply
very difficult to predict whether a certain configuration will be good
enough for your specific needs.
Use nVidia or maybe ATI-based cards. At least these manufacturers have
good drivers for all cards. For nVidia, you may want to avoid the
'professional' series. This can be a waste of money (but may just give
you that little bit extra you want, too). In doubt, buy the top gaming
card(s) you can find.
Choose 64 bits. Many processors, high speeds. The more the better.
OpendTect will automatically use multiple threads in many situations. It
depends on the type of attribute, display, etc. but we put a lot of
effort in getting time-consuming tasks multi-threaded. We are well aware
that the number of processors will grow steadily.
Buy as much memory as you can afford (and that will fit in the
computer). The big clients for example use nothing less than 64 GB.
OpendTect doesn't have a lot of tricks to minimize memory consumption;
we figure that memory gets cheaper by the day so we greedily use memory
for our purposes (we try to not waste it, though).
- Disk storage
This is usually under-valued, but it's very often the crucial
performance component. RAID can speed up disks considerably. If you can,
work on local disks. I've seen many examples of the total performance
being miserable just because the data needed to stream through
(relatively) slow networks.