- 3 phase model works now with step sytem

- previously all objects where cached by id()
- for waLBerla simulations in each time step a new np.array view
  is created from the waLBerla field. Each of these views has a
  different id -> caching did not work for waLBerla setups
- changed hash for numpy arrays: instead of id, a tuple of
  (dataPtr, strides, shapes) is used as hash input

- scaling interface width eta instead of surface tensions tau to correct
  interface profile & surface tensions

João Victor Tozatti Risso authored 7 years ago and Martin Bauer committed 7 years ago

Concept: Generate code involving the (un)packing of fields (from)to linear
(1D) arrays, i.e. (de)serialization of the field values for buffered
communication.

A linear index is generated for the buffer, by inferring the strides and
variables of the loops over fields in the AST. In the CPU, this information is
obtained through the makeLoopOverDomain function, in
pystencils/transformations/transformations.py. On CUDA, the strides of
the fields (excluding buffers) are combined with the indexing variables to infer
the indexing of the buffer.

What is supported:
    - code generation for both CPU and GPU
    - (un)packing of fields with all the memory layouts supported by
    pystencils
    - (un)packing slices of fields (from)into the buffer
    - (un)packing subsets of cell values from the fields (from)into the buffer

Limitations:

- assumes that only one buffer and one field are being operated within
each kernel, however multiple equations involving the buffer and the
field are supported.

- (un)packing multiple cell values (from)into the buffer is supported,
however it is limited to the fields with indexDimensions=1. The same
applies to (un)packing subset of cell values of each cell.

Changes in this commit:

- add the FieldType enumeration to pystencils/field.py, to mark fields
of various types. This is replaces and is a generalization of the
isIndexedField boolean flag of the Field class. For now, the types
supported are: generic, indexed and buffer fields.

- add the fieldType property to the Field class, which indicates the
type of the field. Modifications were also performed to the member
functions of the Field class to add this property.

- add resolveBufferAccesses function, which replaces the fields marked
as buffers with the actual field access in the AST traversal.

Miscelaneous changes:

- add blockDim and gridDim variables as CUDA indexing variables.

- single function to create kernel for specified target
- data type creation from string - reuse numpy functionality
- bugfixes in dot display

- renaming because of clashes with types.py from other packages

- first vectorization tests are running
- type system: use memoized getTypeOfExpression
- casts are done using sp.Function('cast')
- C backend adapted for vectorization support
- AST nodes can required optional headers

- support for kernels that run over walberla ghost layers

- old method produced unused variables
- old method was not deterministic in the output code i.e. ordering of
  the introduced constants
- moveConstantsBeforeLoops transformation was also not deterministic

- pystencils can create now a non-compilable kernel that can be
  analyzed by kerncraft

- cache relied on uniqueness of  python id()
- id may be reused if object is freed
-> object must be held alive
-> kernel keeps all it arguments it was ever called with, alive (problematic in terms of memory consumption)

-> smaller block

- abstraction layer for selecting CUDA block and grid sizes
  - line based (was implemented before)
  - block based (new, more flexible)
-  new conditional (if/else) ast node, which is necessary for indexing schemes (guarding if)

- bugfix for CUDA kernels with variable field sizes
- extended tests for pystencils gpu kernels

- windows support
- automatic caching and creation of shared library with all generated kernels
- restrict keyword and function prefixes are preprocessor macros now -> easier to generate one code for linux, cuda, windows

problem in moveConstantBeforeLoops transformation:

--> a should end up here
{
for() {
  const int a = 5;
}
for() {
  const int a = 5
}
}

the "a" of the lower loop was not moved up, since it could not move across first loop (which is wrong)

- added sphinx files for documentation generation
- collected kernel creation functions in new "cpu" and "cudagpu" modules