User Tools

Site Tools


installing_optional

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
installing_optional [2014/11/29 16:36] – Parallel version for Windows section added johnnyonthewebinstalling_optional [2015/02/08 11:52] (current) – [Parallel version for Windows] johnnyontheweb
Line 21: Line 21:
   * Use **%%PETSC_DIR%%** and **%%PETSC_ARCH%%** to specify your PETSc installation.   * Use **%%PETSC_DIR%%** and **%%PETSC_ARCH%%** to specify your PETSc installation.
  
-=== Parallel version for Windows === +==== Parallel version for Windows ==== 
-This is intended for who uses [[http://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx|Visual Studio 2013]] and, optionally, [[https://software.intel.com/en-us/intel-visual-fortran-compiler-for-windows|Intel Fortran Compiler]] (neeeded only for [[http://www.netlib.org/scalapack/|ScaLAPACK]]).+This is intended for who uses [[http://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx|Visual Studio 2013]] and, optionally, [[https://software.intel.com/en-us/intel-visual-fortran-compiler-for-windows|Intel Fortran Compiler]] (needed only for [[http://www.netlib.org/scalapack/|ScaLAPACK]]).
  
 == Prerequisities == == Prerequisities ==
Line 30: Line 30:
  
 == Configuration of required packages == == Configuration of required packages ==
-  *First of all, one would have ParMETIS (which requires METIS) and MUMPS as direct solver (see [[http://www.mcs.anl.gov/petsc/documentation/linearsolvertable.html|here]]), which requires PETSc to be compiled with ScaLAPACK.+  *First of all, one would have ParMETIS (which requires METIS) and MUMPS as direct solver (see [[http://www.mcs.anl.gov/petsc/documentation/linearsolvertable.html|here]]), which requires PETSc compiled with ScaLAPACK.
   *METIS and ParMETIS can be installed with VS2013 and CMake using a standard procedure.   *METIS and ParMETIS can be installed with VS2013 and CMake using a standard procedure.
   *Follow the instructions for [[http://www.mcs.anl.gov/petsc/documentation/installation.html#windows|PETSc installation]] under Windows and Cygwin. You must start Cygwin within a VS command prompt to have all path to the MS compilers defined.   *Follow the instructions for [[http://www.mcs.anl.gov/petsc/documentation/installation.html#windows|PETSc installation]] under Windows and Cygwin. You must start Cygwin within a VS command prompt to have all path to the MS compilers defined.
Line 45: Line 45:
   * Run configuration with "**%%USE_PARALLEL%%**" set.   * Run configuration with "**%%USE_PARALLEL%%**" set.
   * Use **%%PETSC_DIR%%** (''arch-mswin-c-opt'') and **%%PETSC_ARCH%%** (''arch-mswin-c-opt'') to specify your PETSc installation.   * Use **%%PETSC_DIR%%** (''arch-mswin-c-opt'') and **%%PETSC_ARCH%%** (''arch-mswin-c-opt'') to specify your PETSc installation.
-  * Set **%%METIS_DIR%%** and **%%PARMETIS_DIR%%** to the appropriate paths. +  * Set **%%METIS_DIR%%** and **%%PARMETIS_DIR%%** to the appropriate paths. **%%USE_SHARED_LIB%%** must be unchecked
-  * Configure, generate and open the solution in VS2013. In the Linker Options for the ''oofem'' project, add ''C:\Program Files (x86)\Intel\ComposerXE-2011\compiler\lib\ia32'' (or the equivalent in your system) as additional directory and exclude ''LIBCMT.lib'' from linking. +  * Configure, generate and open the solution in VS2013. In the Linker Options for the ''oofem'' project, add ''C:\Program Files (x86)\Intel\ComposerXE-2011\compiler\lib\ia32'' (or the equivalent in your system) as additional directory and exclude ''LIBCMT.lib'' from linking to prevent errors ([[http://msdn.microsoft.com/en-us/library/6wtdswk0.aspx|see here]])
-  * Compile. Test your oofem.exe with <code>mpiexec -n N oofem -p -f inputdeck.in</code>+  * Compile. Test your oofem.exe with <code>mpiexec -n N oofem -p -f inputdeck.in</code> where N is the number of threads involved (you must have an input deck for each thread, named ''inputdeck.in.0'', ''inputdeck.in.1'' and so on).
 ===== OOFEG ===== ===== OOFEG =====
 OOFEG is graphical postprocessor provided with oofem. It requires X-windows libraries to be installed on the system, so it is more or less limited to unix platforms. The capabilities of OOFEG are limited in 3D visualization, therefore the recommended way for end users interested in 3D analyses is to use oofem capability to export data in VTK format and use third-party, freely available tools such as mayavi or paraview to visualize results. Another advantage is, that these tools are multiplatform and OPEN-GL based, so that they are available on both unix and windows and can fully explore the potential of your graphics hardware. OOFEG is graphical postprocessor provided with oofem. It requires X-windows libraries to be installed on the system, so it is more or less limited to unix platforms. The capabilities of OOFEG are limited in 3D visualization, therefore the recommended way for end users interested in 3D analyses is to use oofem capability to export data in VTK format and use third-party, freely available tools such as mayavi or paraview to visualize results. Another advantage is, that these tools are multiplatform and OPEN-GL based, so that they are available on both unix and windows and can fully explore the potential of your graphics hardware.
installing_optional.1417275370.txt.gz · Last modified: 2014/11/29 16:36 by johnnyontheweb