Skip to content

Home

Jump to bottom
tommy-engels edited this page May 13, 2014 · 20 revisions

Welcome to the FLUSI/MHD wiki!

FLUSI
discreet and discrete

Install guide

The first thing to do is to install the code and its dependencies. Please follow the install guide. For M2P2 users, we have also cluster specific how-to's. https://github.com/pseudospectators/FLUSI/wiki/FLUSI-general-install-guide

Unit tests

FLUSI/MHD offer unit tests, e.g a collection of predefined parameter files with known output values. After installing and compiling the code, you can go into the test/ folder and excecute ./unittest.sh. This script calls individual unit-testing scripts, and tells you if everything seems to be okay. The output messages are dumped in *.log files. You need to be able to excecute the compiled binary file locally, which might be kind of tricky on some supercomputers (IDRIS/turing for example)

Running flusi and mhd

Now that you know you properly installed FLUSI/MHD, you can run a simulation. In general, you need the excecutable binary file and a suitable parameter file. The latter contains run-time parameters, such as the resolution, the domain size or what geometry you want to set. Note the distinction between MHD and FSI is made by choosing the appropriate executable (./mhd or ./flusi) FLUSI/MHD are MPI programs, normally run via commands like

mpirun --np 12 ./mhd params.ini mpirun --np 12 ./flusi PARAMS_insect.ini but they can also run in serial (monoprocessor).

The parameters for the run are specified in the params file, examples of which are available in the extra_files branch. Two complete parameter files, PARAMS_test_fsi.ini and PARAMS_test_mhd.ini are also in the master branch.

The code will produce three sorts of output:

  1. The messages printed on the screen about it's current state
  2. The fields data (e.g. the velocity vectors for all latice points) in *.h5 files. Please note the file naming convention is very important. These *.h5 files can be visualized with paraview (free open source software), see next section
  3. Time series of some quantities (e.g. lift/drag force, kinetic energy, time step size...) are stored in *.t files, which are ordinary ascii text files

Viewing and understanding the output

3D visualization is done by using mpi2vis, which converts the metadata associated with the HDF output into a format which can be used by Paraview. Output of the *.t files is done with either MatLab or the included Asymptote scripts, which are available in the postscripts branch.

Cluster Specific Tips & Tricks

can be found here: https://github.com/pseudospectators/FLUSI/wiki/Cluster-specific-settings-for-flusi

Compiler specific options

Options for debugging, optimization and so on for ifort and gfortran are collected here: https://github.com/pseudospectators/FLUSI/wiki/Compiler-Options

Clone this wiki locally