Philosophy of examples and how to run them
The idea of our examples is to present the functionality of the library in an accessible and incremental manner.
The examples present different solutions to problems ranging in difficulty from the simple Poisson's equation to more specific examples, such as Fluid mechanics.
Each examples consists of a name, e.g. poisson_implicit_dirichlet_2D
and its corresponding
- source code, e.g.
poisson_implicit_dirichlet_2D.cpp
- plot script, e.g.
poisson_implicit_dirichlet_2D.m
Additional appropriately named input files might be present for more complicated examples and similarly named output files might be produced. The examples and their plot scripts are intended to work out of the box, so the reader can simply run the examples on their machine. The procedure for running examples is simple and the same for all examples. The accompanying plot scripts can be run with Matlab or octave and they produce the figures the reader sees in the Examples category of this wiki.
Let us now illustrate the process of running an example named example
.
First the example needs to be built (compiled). The building is done in the build/
directory. When you are in the folder where your example (and a CMakeLists.txt
file where it is registered) is located, run
mkdir -p build # creates the directory build, if it does not exist
cd build # goes to that directory
cmake .. # creates Makefiles
make example # builds your example (substitute "example" with an actual example name)
to compile your example. Note that you only have to run cmake
once, after that
only make is sufficient. Compiled binary used to run the example is placed into bin/
folder and libraries are placed into lib/
folder.
To build all examples, you can just run (after running cmake at least once)
make all
To run the built example, go back to the initial folder where the source code for your example was, and run
./bin/example
The output will be saved WHERE??
After, just run the corresponding plot script and you should see a figure, usually showing the solution.
Some more feature specific examples are found in the technical documentation TODO LINK and in the library tests.