anchor.diff:  compiler. The CPU version of the backend is equally valid and provides
   the same functionality. Analogously, an MPI installation is only required if the user targets
   a distributed memory system.
  +____
   
   === Running a FELTOR test or benchmark program
   
  
positive.code: You can add your Feltor Property Sheet to any new project
   by switching to the `Property Manager` again:
  click `Add Existing Property Sheet` and select `FeltorPropertySheet`.
  [TIP]
   We suggest that you generate a new project for each executable program.
  
  ===== Basic test
  In order to test the Feltor Property Sheet let us add a source file to
  
negative.code: which makes a grid with 3 polynomial coefficients, 100 cells in x, 100
  cells in y and 10 in z. If you compiled for OpenMP, you can set the
  number of threads with e.g. `export OMP_NUM_THREADS=4`.
  ____
  This is a
  benchmark program to benchmark various elemental functions the library
  is built on. Go ahead and vary the input parameters and see how your
  hardware performs. You can compile and run any other program that ends
  in `_t.cu` (test programs) or `_b.cu` (benchmark programs) in
  `feltor/inc/dg` in this way.
  ____
  
  Now, let us test the mpi setup
  ____
  You can of course skip this if you
  don't have mpi installed on your computer. If you intend to use the
  MPI backend, an implementation library of the mpi standard is required.
  Per default `mpic++` is used for compilation.
  ____
  
  [source,sh]
  ----
  