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.
Improved modelling of Boundary Conditions
The development and implementation of new boundary conditions is often times complicated in lbmpy. This issue should document problems that people face with implementing boundary conditions and should therefore function as a blueprint to improve this situation. As a first part, information that is often needed (but hard to extract in lbmpy) should be listed. 1. **Equilibrium:** For many boundary conditions (UBB, Pressure, InterpolationBB) the equilibrium near to the wall needs to be computed. This is not trivial, because usually the equilibrium is given direction-wise in lbmpy thus a simple, and ugly solution is to use a large if cascade over with the direction index. 2. **Shear stress, drag etc:** Wall models often need to take the shear drag. This goes into the same direction as the first point. Basically, it is important to be able to easily obtain the PDF values next to the wall to implement equations calculating this information. 3. **Wall distance:** For wall models and interpolation boundary conditions, the distance to the wall needs to be known 4. **Normal direction:** It should be easy, to obtain the normal direction to the wall (see: FreeSlip BC etc) 5. **Second neighbour:** For more complex BC, more fluid cells needs to be taken into account (see: NoSlipLinearBouzidi). This might lead to complications for refinement algorithms etc. 6. **Information from previous timesteps:** Some interpolation BC, need PDFs from precious timesteps (see: ExtrapolationOutflow) 7. **Optimisation methods:** Especially wall models, often rely on Newton steps to fit a certain velocity profile. Without `While` loops these can only be implemented by unrolling a fixed number of iterations Furthermore, as stated in the book by Tim Krüger: "Despite the large number of methods available, all LB boundary conditions for straight boundaries belong to one of two groups: link-wise and wet-node". At the moment, all boundaries are formulated link-wise. While wet-node BC might not be superior they still make some problems easier to formulate and providing a good interface to support both would be easier for users who are more familiar with one or the other.
issue