Subsequently is a short explanation on how to use Musubi:
then you have the repository with sub-repos aotus and treelm in the folder musubi. - Note: You need MPI in order to compile the code.
You will get .vtk files, if you have activated the output in musubi.lua. The current test case is a Gaussian Pulse with a wall in order to test the correct behavior of the bounce back boundaries.
There are several configuration options available to influence the build. You can obtain a list of those with ./waf --help.
It is possible to choose between the "PULL" (default) and "PUSH" streaming approach via the --stream=PULL or --stream=PUSH option.
Aside from the default build, there is also a debug target which creates an executable with debugging information. Other variants, for example for performance profiling can be found in the output of ./waf --help
Musubi utilizes the CoCo preprocessor to modify code at compile time. Its behavior can be modified by changing the default.coco file, and by setting the COCOFLAGS environment variable.
It is possible to restrict to build to individual targets with the --targets option. For example to only build the musubi and mus_harvesting executables, add the option --targets=musubi,mus_harvesting to the waf command.
A different geometry can be generated with the tree-based Mesh generator Seeder.
Set environment variables export CC=mpicc export FC=mpif90
You will receive a VTK file, in order to check the fluid domain. The fluid is identified by placing the seed in the correct position in seeder.f90, which will be changed later. A good start is in the first position, just make sure that it is part of the continuous fluid domain.
The parallel version has not been tackled yet but has a high priority on our task-list. The next step will be parallel functionality and inlet/outlet boundaries.
Please make sure to check out musubi and start a few runs. Please also report any bugs here in the tickets.
After updating a new version of Musubi you better do ./waf configure build. Sometimes you need to clean the coco macro files. Then you do ./waf clean build. To remove the source and the configuration files you type ./waf distclean configure build. And if you want to remove the coco executables itself you will type ./waf cleanall configure build.