Installation/Linux/OpenFOAM-2.2.0/openSUSE

From OpenFOAMWiki

1 Introduction

This page is dedicated to explaining how to install OpenFOAM OF Version 220.png in openSUSE.

If you do not yet feel comfortable using Linux, then perhaps you better first read the page Working with the Shell and train a bit with the shell/terminal environments, so you can have a better perception of the steps shown below.


2 Copy-Paste steps

A few notes before you start copy-pasting:

  1. Lines that start with # don't have to be copy-pasted. They are just comments to let you know what's going on.
  2. One wrong character is enough for breaking this guide, so make sure you can read the characters properly or that the installed language system does not break the copied characters!


2.1 openSUSE 12.2

Here you have at least two choices:

  • You can install the RPM packages, which provide a quick and easy way for having a working installation of OpenFOAM 2.2.0. This is the quickest solution for beginners and instructions are provided here: SuSE RPM Pack Installation
  • You can install from source, by either:
    • Following the official instructions from here: Source Pack Installation
    • Or by following the detailed step-by-step instructions below...


Discussion thread where you can ask questions about these steps: none so far.

Steps:

  1. Switch to root mode (administrator), to install the necessary packages:
    sudo -s
    • If the 'sudo' command tells you're not in the sudoers list, then run:
      su -
  2. Install the necessary packages:
    zypper install -t pattern devel_C_C++
    zypper install cmake libqt4-devel qt4-x11-tools qt4-assistant-adp-devel gnuplot openmpi-devel
  3. Now exit from the root mode:
    exit
  4. Now, since we're trying to minimize the number of packages to be built, the Open-MPI package that is available with openSUSE is going to be chosen. The downside is that this requires that you logout and log back in, for the system to update the environment settings.
    Nonetheless, we can postpone logging out by running:
    source /etc/profile.d/mpi-selector.sh
    Note: But keep in mind that until you logout, use this command line on every new terminal window/tab!
  5. Download and unpack (here you can copy-paste all in single go):
    #OpenFOAM downloading and installation
    cd ~
    mkdir OpenFOAM
    cd OpenFOAM
    wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.2.0.tgz?use_mirror=mesh" -O OpenFOAM-2.2.0.tgz
    wget "http://downloads.sourceforge.net/foam/ThirdParty-2.2.0.tgz?use_mirror=mesh" -O ThirdParty-2.2.0.tgz
     
    tar -xzf OpenFOAM-2.2.0.tgz 
    tar -xzf ThirdParty-2.2.0.tgz
  6. For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of openSUSE. To check this, run:
    uname -m

    Now, accordingly:

    • For i386:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
    • For x86_64:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI
  7. Save an alias in the personal .bashrc file, simply by running the following command:
    echo "alias of220='source \$HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
    Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.2.0 shell environment. In other words, whenever you start a new terminal, you should run:
    of220
    
    For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
  8. Now let's build OpenFOAM:
    (Warning: this may take somewhere from 30 minutes to 6 hours, depending on your machine.)
    #Go into OpenFOAM's main source folder
    cd OpenFOAM-2.2.0
     
    # This next command will take a while... somewhere between 30 minutes to 3-6 hours.
    ./Allwmake > make.log 2>&1
     
    #Run it a second time for getting a summary of the installation
    ./Allwmake > make.log 2>&1
  9. To check if everything went well:
    1. Check if icoFoam is working, by running this command:
      icoFoam -help

      If it tells you how to use it, then the installation should be working as intended.

    2. If the previous command failed to work properly, then edit the file make.log and check if there are any error messages. A few examples on how you can edit this file:
      • By using kwrite:
        kwrite make.log
      • By using gedit:
        gedit make.log
      • By using nano:
        nano make.log

        You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

      Note: It's the first error message that matters.

    3. If you don't understand the output, then please compress the file make.log and attach the file make.log.tar.gz to a post in the designated thread.
      If you do not know how to create a compressed file, then try one of the following examples:
      • You can compress the file with gzip by running this command:
        gzip < make.log > make.log.gz

        Then attach the resulting package file named make.log.gz to a post in the designated thread.

      • Or you can compress one or more files into a tarball package file, by running this command:
        tar -czf make.log.tar.gz make.log

        Then attach the resulting package file named make.log.tar.gz to a post in the designated thread.

    4. Instructions on how to further diagnose the issue yourself, have a look at the section Common errors when building OpenFOAM from source code in the page FAQ/Installation and Running.
  10. Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
    cd $WM_THIRD_PARTY_DIR
    ./makeParaView
     
    cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers 
    wmSET $FOAM_SETTINGS
    ./Allwclean 
    ./Allwmake
  11. Now you can go read the User Guide: official OpenFOAM User Guide


Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.2.0 shell environment. In other words, run the following command whenever you start a new terminal:
of220
For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.


Discussion thread where you can ask questions about these steps: none so far.

2.2 openSUSE 12.3

Discussion thread where you can ask questions about these steps: none so far.

Steps:

  1. Switch to root mode (administrator), to install the necessary packages:
    sudo -s
    • If the 'sudo' command tells you're not in the sudoers list, then run:
      su -
  2. Install the necessary packages:
    zypper install -t pattern devel_C_C++
    zypper install cmake libqt4-devel qt4-x11-tools qt4-assistant-adp-devel gnuplot openmpi-devel
  3. Now exit from the root mode:
    exit
  4. Now, since we're trying to minimize the number of packages to be built, the Open-MPI package that is available with openSUSE is going to be chosen. The downside is that this requires that you logout and log back in, for the system to update the environment settings.
    Nonetheless, we can postpone logging out by running:
    source /etc/profile.d/mpi-selector.sh
    Note: But keep in mind that until you logout, use this command line on every new terminal window/tab!
  5. Download and unpack (here you can copy-paste all in single go):
    #OpenFOAM downloading and installation
    cd ~
    mkdir OpenFOAM
    cd OpenFOAM
    wget "http://downloads.sourceforge.net/foam/OpenFOAM-2.2.0.tgz?use_mirror=mesh" -O OpenFOAM-2.2.0.tgz
    wget "http://downloads.sourceforge.net/foam/ThirdParty-2.2.0.tgz?use_mirror=mesh" -O ThirdParty-2.2.0.tgz
     
    tar -xzf OpenFOAM-2.2.0.tgz 
    tar -xzf ThirdParty-2.2.0.tgz
  6. For building OpenFOAM itself, it depends on whether you have installed the i386 or x86_64 architecture of openSUSE. To check this, run:
    uname -m

    Now, accordingly:

    • For i386:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI WM_ARCH_OPTION=32
    • For x86_64:
      #here you can change 4 to the number of cores you've got
      source $HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc WM_NCOMPPROCS=4 WM_MPLIB=SYSTEMOPENMPI
  7. Save an alias in the personal .bashrc file, simply by running the following command:
    echo "alias of220='source \$HOME/OpenFOAM/OpenFOAM-2.2.0/etc/bashrc $FOAM_SETTINGS'" >> $HOME/.bashrc
    Note: This last line means that whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.2.0 shell environment. In other words, whenever you start a new terminal, you should run:
    of220
    
    For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.
  8. Now let's build OpenFOAM:
    (Warning: this may take somewhere from 30 minutes to 6 hours, depending on your machine.)
    #Go into OpenFOAM's main source folder
    cd OpenFOAM-2.2.0
     
    # This next command will take a while... somewhere between 30 minutes to 3-6 hours.
    ./Allwmake > make.log 2>&1
     
    #Run it a second time for getting a summary of the installation
    ./Allwmake > make.log 2>&1
  9. To check if everything went well:
    1. Check if icoFoam is working, by running this command:
      icoFoam -help

      If it tells you how to use it, then the installation should be working as intended.

    2. If the previous command failed to work properly, then edit the file make.log and check if there are any error messages. A few examples on how you can edit this file:
      • By using kwrite:
        kwrite make.log
      • By using gedit:
        gedit make.log
      • By using nano:
        nano make.log

        You can then exit by using the key combination Ctrl+X and following any instructions it gives you.

      Note: It's the first error message that matters.

    3. If you don't understand the output, then please compress the file make.log and attach the file make.log.tar.gz to a post in the designated thread.
      If you do not know how to create a compressed file, then try one of the following examples:
      • You can compress the file with gzip by running this command:
        gzip < make.log > make.log.gz

        Then attach the resulting package file named make.log.gz to a post in the designated thread.

      • Or you can compress one or more files into a tarball package file, by running this command:
        tar -czf make.log.tar.gz make.log

        Then attach the resulting package file named make.log.tar.gz to a post in the designated thread.

    4. Instructions on how to further diagnose the issue yourself, have a look at the section Common errors when building OpenFOAM from source code in the page FAQ/Installation and Running.
  10. Now, in order to build ParaView 3.12.0 that comes with OpenFOAM:
    cd $WM_THIRD_PARTY_DIR
    ./makeParaView
     
    cd $FOAM_UTILITIES/postProcessing/graphics/PV3Readers 
    wmSET $FOAM_SETTINGS
    ./Allwclean 
    ./Allwmake
  11. Now you can go read the User Guide: official OpenFOAM User Guide


Reminder: Whenever you start a new terminal window or tab, you should run the alias command associated to the OpenFOAM 2.2.0 shell environment. In other words, run the following command whenever you start a new terminal:
of220
For more information on this topic, read section Using aliases to help manage multiple OpenFOAM versions in the page Installation/Working with the Shell.


Discussion thread where you can ask questions about these steps: none so far.