Admin message

Attention: i10git will shutdown soon!

This i10git GitLab server was migrated to gitos.rrze.fau.de due to hardware issues with the current host. This affects all production repositories, including waLBerla, lbmpy, pystencils and HyTeG.

Login: Gitos supports DFN-AAI and eduGAIN. If your institution does not support either, please use our GitHub mirrors.

Onboarding: All repositories belonging to groups were migrated. To regain access, first log in to gitos.rrze.fau.de once to activate your account. Then email cs10-admin@fau.de with your old i10git and your new gitos.rrze username (the @) as shown on your respective user profiles. We will reassign your accordingly. Note: Repositories from former courses (e.g. advpt) were not migrated.

Personal repositories in individual user namespaces were not migrated. Please export these yourself before the old server is shut down.

Expected shutdown by the end of 2026. Until then, the old i10git server will still be reachable with all repositories archived (read only). However, due to the ongoing hardware issues, it may remain unreliable and will receive no further maintenance.

The parent group is archived. This project and its data are read-only.
Codegen for lattice Boltzmann methods on unstructured grids
LBM can also be used with other discretization methods (e.g. FVM, or FEM) for the streaming step. The PDFs are now associated with the nodes of a triangular or quadrilateral mesh. Since the streaming step is now irregular and involves floating point calculation, for the update rule it is common to use two separate arrays. Nevertheless, I could still use lbmpy for the collision part by setting `kernel_type='collide_only'` in the `LBMConfig`. Inspecting the prototype and code of generated kernels, e.g. ```c FUNC_PREFIX void mylbmkernel(double * RESTRICT _data_src, int64_t const _size_src_0, int64_t const _size_src_1, int64_t const _stride_src_0, int64_t const _stride_src_1, int64_t const _stride_src_2, double omega) ``` I have inferred that lbmpy assumes the PDFs are stored in a 3-dimensional (padded) array (in 2D), with either the `xyzf` or `fxyz` storage layout. In Fortran notation, assuming `fxyz` (SoA) storage this would be something like: ```fortran ! In Fortran, the order is opposite from C real(c_double), allocatable :: fcache(:,:,:,:) ! y,x,f,isrc/idst ``` For the unstructured method (FVM, FEM), however I will just use a "linear" array: ```fortran real(c_double), allocatable :: fcache( :,:,:) ! xy,f,isrc/idst ``` If I'm not mistaken, this would correspond to setting `__size_src_1 = 1, __stride_src_1 = 0` to essentially "flatten" one dimension of the array. Would it be possible for lbmpy to provide an option for applying the collision rule over a flat/one-dimensional index space? Does it make sense to do it in blocks with smaller buffers for density and velocity?
issue