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.
Bug in Vectorization with GCC < 8.1.0 and Intel C++ Compiler
When compiled with `-Ofast -march=native` (default in lbmpy and pystencils), the following channel flow test case is subject to numerical instabilities in the PDF field. This was observed with various GCC compiler versions below GCC 8.1.0 and with the Intel C++ compiler versions 17 to 19 (20 was not tested). It could not be observed with the LLVM compiler versions 7 to 10. The bug is supposedly present in any version of lbmpy and pystencils, as it can be reproduced with lbmpy and pystencils versions 0.2.9, 0.2.13 and 0.2.14. The minimal required compile flags to get the instabilities on GCC are `-O3 -fno-signed-zeros -fno-trapping-math -fassociative-math -mavx`. The GCC commit that fixed this issue was identified to be [7c080ad](https://github.com/gcc-mirror/gcc/commit/7c080ade9d8198958a1a37854d5cc56f7b76b9f4). There, the cost estimation for vectorization changes, such that the auto-vectorization behavior differs. We tried `-fvect-cost-model=unlimited` to force vectorization irrespective of costs, but that did not make a difference. **Since we do not know which commit fixes the actual bug, it is possible that it is present in gcc 8 or even the current gcc 10** -- only the specific code sample below no longer runs into it because it does not get auto-vectorized anymore. ``` from lbmpy.session import * from lbmpy.moments import * ch = create_channel(domain_size=(300, 100), force=5e-5, initial_velocity=(0.5, 0), relaxation_rate=1.8) ch.run(6900) print(ch.velocity[0.5, :, 0]) ``` While the flow field initially seems to be stable, it becomes unstable between time steps 6800 and 6900 and ends up with NaNs.
issue