Richard Kellnberger flavor. This is the version of FluidX3D, developed as part of my Dissertation. FluidX3D does computational fluid dynamics using Lattice Boltzmann. This version is optimized for applications in the vicinity of biofabrication.
If you found FluidX3D from social media, you are likely searching for the version by Moritz Lehmann.
This is the configure step of cmake, you only have to do this once, even when you make changes to the code.
In fluidx3d create a folder called build (technically folder name is arbitrary)
mkdir build
enter the folder
cd build
configure cmake
cmake ../
If this step gives you trouble, you are likely on windows and have configured your generator incorrectly (or rather you have not changed the default generator, which does not work correctly). If this is the case, contact me.
Make cmake build the code
cmake --build . -- -j<n>
Where <n> is to be replaced by the number of cores you want to use for the build. More is better, but be responsible!
You have to rerun whenever you change the code. Also you should rerun this after committing something to ensure the version that fluidx3d gets from git is up to date.
Due to the nontransparent dependencies and to not clutter the build directory an install step is required.
Currently this just moves the files to a dedicated install directory within fluix3d. This is subject to change.
To install run
cmake --install .
You have to do this after every build.
Now you can navigate to your install directory
cd ../install
This path is subject to change.
And run your code.
For Linux:
./FluidX3D
For Windows:
FluidX3D.exe
Your data is found in folders created here.
FluidX3D supports Linux and to some extent Windows.
Please be aware, that on windows some systems do not work fully and some are missing entirely.
You cannot use a GPU that is in use (for nvidia and amd GPUs) (this feature is currently WIP).
On Windows, when using an AMD-GPU this cannot be guaranteed.
Furthermore all AMD-GPUs are averaged on Windows.
Windows 10 supports ANSI and VT100 since v1511 (November 2015).
Because this would be too convinient Microsoft decided to not enable it.
To use it you need to set a registry key:
REG ADD HKCU\CONSOLE /f /v VirtualTerminalLevel /t REG_DWORD /d 1