@@ -19,13 +19,10 @@ With TurTLE, the desire is to identify core functionality that should be
implemented in a library.
The core library can then be used by many problem-specific codes.
In this sense, the structuring of the code-base is non-standard.
The core functionality is implemented in C++ (classes useful for
describing working with fields or sets of particles), while a Python3
wrapper is used for generating "main" programmes to be linked against
the core library.
The core library uses a hybrid MPI/OpenMP approach for parallelization, and the Python3 wrapper
compiles this core library when being installed.
The core functionality is implemented in C++, while a Python3
wrapper is typically used for generating initial conditions and
light-weight post-processing.
The core library uses a hybrid MPI/OpenMP approach for parallelization.
Python3 "wrapper"
-----------------
...
...
@@ -36,13 +33,6 @@ launching jobs and postprocessing data.
Classes defined in the Python3 package can be used to generate executable
codes, compile/launch them, and then for accessing and postprocessing
data with a full Python3 environment.
Code generation is quite straightforward, with C++ code snippets handled
as strings in the Python3 code, such that they can be combined in
different ways.
Once a "main" file has been written, it is compiled and linked against
the core library.
Depending on machine-specific settings, the code can then be launched
directly, or job scripts appropriate for queueing systems are generated
and submitted.
...
...
@@ -50,16 +40,22 @@ and submitted.
C++ core library
----------------
TurTLE has a hierarchy of classes that provide prototypes for three basic tasks: perform a DNS, post-process existing data or test arbitrary functionality.
As a guiding principle, the distinct tasks and concepts involved in the numerical simulation in TurTLE are isolated as much as possible, which simplifies the development of extensions.
There are two types of simple objects.
Firstly, an abstract class encapsulates three elements: generic *initialization*, *do work* and *finalization* functionality.
Secondly, essential data structures (i.e. fields, sets of particles) and associated functionality (i.e. I/O) are provided by "building block"-classes.
The solver then consists of a specific arrangement of the building blocks.
The heterogeneous TurTLE development team benefits from the separation of generic functionality from building blocks:
TurTLE is naturally well-suited to the distribution of conceptually distinct work, in particular fully isolating projects such as, e.g., "implement new numerical method" from "optimize the computation of field statistics with OpenMP".
As already stated, TurTLE's main goal is to facilitate novel research
avenues.
To this end, there are two types of simple objects.
Firstly, children of an abstract class that encapsulates three elements: generic
*initialization*, *do work* and *finalization* functionality.
Secondly, essential data structures (i.e. fields, sets of particles) and
associated functionality (i.e. I/O) are provided by "building block"-classes.
Each TurTLE "solver" then consists of a specific arrangement of the building
blocks.
The heterogeneous TurTLE development team benefits from the separation of
generic functionality from building blocks:
TurTLE is naturally well-suited to the distribution of conceptually distinct
work, in particular fully isolating projects such as, e.g., "implement new
numerical method" from "optimize the computation of field statistics with
OpenMP".
---------
Equations
...
...
@@ -67,15 +63,16 @@ Equations
The code uses a fairly standard pseudo-spectral algorithm to solve fluid
equations.
The incompressible Navier Stokes equations in velocity form are as
follows:
The incompressible Navier Stokes equations in velocity form (see the
